I own a ASUS Z87 Pro and an Intel 4670K that I’ve overclocked to a respectable 4.4 GHz which had started exhibiting problems. I noticed a few weeks ago that the bus speed was fluctuating between 95-99 MHz by looking at it with CPU-Z. I orginally believed that this was happening due to an imminant motherboard death. In attempts to debug the problem I had: Increased input voltage to 1.9v Decreased/increase uncore multiplier Changed CPU multipliers Increased/decreased voltage Force BCLK to 100 Mhz Disabled/enabled spread spectrum RMA’d my motherboard to ASUS Oddly, the problem only exhibited itself when I was overclocked because the behavior disappeared when I reset to BIOS factory default settings. In truth, the issue was because I had Hyper-V installed on my Windows 8 machine! I discovered this after I disabled Virtualization support in the BIOS and noticed that the fluctuations stopped. After that, I uninstalled Hyper-V, re-enabled Virtualization...
Keep reading

Copy and paste the following into your blog description: <script src="https://cdn.rawgit.com/google/code-prettify/master/loader/run_prettify.js"></script> Use the following <pre/> tags in any of your Tumblr posts: <pre class="prettyprint"> Many lines of code </pre>
Keep reading

I’ve recently started using a new Tumblr theme called Optica. It’s awesome, it’s minimalistic, it looks exactly like what I want it to look; but it doesn’t allow me to display Tweets. Bummer! But wait, there must be a way we can hack it in, right? We can always hack the theme’s HTML directly but then we will lose any sort of improvements that happen naturally when the author updates it. So let’s hack it in by (ab)using your blog’s description! Create a embedded-timeline widget using your Twitter account. Edit your Tumblr blog’s theme. Append a custom <div/> element to your blog’s description. For example:
Keep reading

Bugs and exploits are a natural part of this world. The Synolocker ransomware was recently running rampant and hacking into Synology devices running DSM 4.3 and below. It did this by identifying your device if ports 5000 or 5001 were exposed and then exploiting a bug to implant itself. The only fool-proof solution to preventing being exploited permanently is to be paranoid. Shut down all unnecessary Synology services and never expose any ports to the web. This is far from a convenient solution though. For example, I still want to share access to my Synology device because it hosts a few websites for my family. This required me to find a good balance between security and availability. I decided that the best way to do this was to install the Synology VPN service and use a L2TP/IPSec VPN. I would only expose ports 80, 443 for web serving and ports 1701, 500, and 4500 for VPN. The...
Keep reading

I have a photo library that is well over 20GBs in size and only seems to have picked up in pace as cameras got more beefy and packed on the pixels. I am traveling to Scandinavia today, and I really wanted one place that I could store everything and beautifully display it at the same time.
Keep reading