The easiest way to keep your disks defragmented

When was the last time you defragmented your hard drive?  Is your computer a little slower to load lately?

JkDefrag is a fantastic alternative to the Disk Defragmenter tool that comes with Windows (2000/2003/XP/Vista/2008).  It does it better than Windows.  (For a full explanation, read on the website)

But how often should it be done? What if you forget to keep doing it? An easy “set and forget” solution is to install this as a screensaver.  Download JkDefrag from the website, and extract the archive.  Copy the two files:

  • JkDefragScreenSaver.exe
  • JkDefragScreenSaver.scr

to the c:\Windows\ directory.

Then on your desktop, right click and go to Properties.  Under the Screen Saver tab, select JkDefrag as your screen saver.  Select it to not start unless it hasn’t been done for 24 hours, and select your preferred screen saver to come on after the defrag is complete.  It will now defrag every disk drive connected to your system on a regular basis, and it doubles up as a pretty good screen saver in itself!

Overclocking: Lapping the Q6600(B3) & Scythe Ninja

Warning: if you’re not a computer g33k don’t bother reading this post, you just won’t understand!

In December, I started playing a little more of the game Colin McRae Rally: Dirt. However, I decided that my beast of a machine (refer here, here, & here) wasn’t performing quite fast enough for maximum off-road rally driving pleasure. Thus, my recent overclocking obsession came to be!

Basically, I overclocked my Q6600 B3 revision Intel Quad Core CPU from the stock 2.4GHz speed to 2.6GHz. However, after countless hours upon hours of running CPU stress testing (specifically, Prime95 v25.6 build #2), and comparing to temperatures measured by other people with almost exactly the same hardware configurations, I came to the conclusion that I am unlucky to be one that has received a CPU chip that just runs at a hotter temperature than the average manufactured chip. Upon exhaustive research through overclocking forums on the net, I discovered that lapping (making something flat via sanding) the Q6600 Core 2 Quad CPU is generally a very beneficial thing to do for increasing the thermal transfer of the CPU cover to the heatsink. I suspect the manufacturing process that Intel use to fix the CPU cover to the cores causes the cover to bend slightly. Consequently, the outside edges of the CPU cover (and a section in the middle) are slightly raised from the rest of the cover, leading to big air gaps that require filling with thermal paste in order to transfer heat half reasonably. Since it is the outside edge that is most raised, I can see why my CPU heatsink created a big air-gap when it was installed. This definitely contributes to a hotter CPU, which means less overclocking is possible before you risk overheating it.

Lapping CPU _01_.JPG
Lapping CPU _02_.JPG
Lapping CPU _03_.JPG
Lapping CPU _07_.JPG

I used the razor blade with torch behind it technique to determine how flat both surfaces really were, but I found that the razor blade wasn’t rigid enough to provide consistency for a good idea of how much curvature existed. The heatsink seemed relatively flat already, but the CPU definitely had big gaps of light coming through. Regardless, I decided to lap the heatsink so I could practise my lapping technique before doing the CPU.
I conducted the lapping process using a large piece of tempered

Lapping CPU _19_.JPG

glass (compliments of Scoobth) which I used to tape the wet-and-dry sandpaper on for a flat surface. I used a spray bottle of water to keep the sandpaper moist at all times. The sandpaper grit sizes I used were 200, 400, 600, 800, 1000, and 1200.

The most time consuming stage was using the very coarse 200 grit size, just to get the surfaces flat before I could progressively smooth them down. I only had 1 piece of each grit size for the CPU, and 1 piece of each grit size for the heatsink, and all of the sandpaper became too worn for them to be worthwhile using anymore. If I were to do it again I would have a lot more sandpaper handy because once it wears down, the efficiency of the sanding action decreases dramatically and you really just waste time.

Lapping CPU _09_.JPG

I couldn’t work out how to remove the thermal plate surface from the heat-pipes of the Scythe Ninja heatsink, which made for a very high centre of gravity as the complete unit slid over the sandpaper. Consequently I found it difficult to stop the heatsink from shuddering.


The CPU was much easier to sand because as a flat plate it has a very low centre of gravity. I held it with the black piece of protective plastic that it came with, so that way I didn’t touch any of the sensitive side of the unit. You can see after starting to sand, the edges of the unit were scratching away (nice shiny silver instead of a matte finish). It took a large amount of sanding to actually notice this. After a while, you could notice a circle in the middle also start to sand away

Lapping CPU _12_.JPG

I kept using the 200 grit sized sandpaper up until about this stage where I switched to the 400 grit sized because the 200 grit had completely worn out! Probably a good idea anyway, because there wasn’t much sanding now at this stage to get it completely flat.

Lapping CPU _20_.JPG

By the time I got to about here, the 400 grit paper was also fairly worn out, but I kept going until all the plate was uniformly shiny and all of the matte surface had gone. I read on a few forums that the silver surface is a nickel plating. The only reason I can think of why nickel plating would be used on a CPU cover would be for corrosion resistance, because I would imagine corrosion of (what appears to be) copper underneath the nickel plating would have a very low thermal conductivity.

Lapping CPU _25_.JPG

Somewhere at about this stage, I noticed a red liquid appearing on the sandpaper. It was blood from my finger, which I didn’t feel was being sanded to the flesh as my hand was numb from holding the CPU! Lesson to be learned: keep lots of fresh sandpaper handy so you don’t have to waste time sanding with worn out sandpaper!

Eventually, after going through all the grades of sandpaper, the end result!

Lapping CPU _28_.JPG
Lapping CPU _30_.JPG

I then cleaned the surfaces using a few drops of the Arctic Silver ArctiClean product (compliments of Scoobth) and applied a line of Arctic Silver ArcticSilver5.
I applied the line of AS5 as the instructions suggested, although I think the instructions would be written with the non-flat surface of the Core 2 Quad Q6600 in mind, and I should probably have used a much thinner line.

Lapping CPU _31_.JPG

Next time I ever do it I would definitely still use it in a line for the purpose of ensuring all cores have good contact in the immediate vicinity, but just used a lot less. It would perhaps have been easier to apply if I heated the AS5 liquid up somehow. Not in the microwave as it contains metal particles, but perhaps out in the hot Australian sun or in the oven on a maximum of 30 degrees celcius. The AS5 compound probably doesn’t reduce in viscosity when it heats up, but it would be worth a try.

The core temperatures of the CPU instantly ran about 10 degrees celcius lower, and after a few thermal cycles and a few days about 12 degrees celcius lower. I tested this temperature drop using ambient temperature that was plus or minus 2 degrees celcius, and taking measurements using SpeedFan & CoreTemp after about 1 hour of Prime95 v25.6 build #2 using the small FFT torture test.

I was then able to overclock my CPU to 2.7GHz, but the cores were starting to run in the red zone (above the maximum rated temperature of 71 degrees Celcius) so I also used another overclocking hardware modification called the pencil Vdroop mod. This mod involves using a graphite pencil to shade over a (I think the component was a) resistor to effectively lower the resistance by adding another resistor (the conductive graphite) in parallel. Now although I’m a qualified Mechatronic engineer, I have absolutely no idea what any of the circuitry on the mainboard does, so I was taking a giant leap of faith from fellow overclockers on the internet! The idea is you keep lowering the resistance until the voltage across the CPU core(s) is exactly the same voltage regardless of whether or not the CPU is experiencing a full load or not. That is, there is not voltage drop (aka droop) when the CPU is under computational load. The bad side of this is temperatures immediately sky-rocket when you start to next apply computational load because the voltage doesn’t decrease at the same time. So, the idea is to lower the overall voltage to compensate. The end effect is increased voltage stability of the CPU due to it not fluctuating, which means the CPU is less likely to produce errors, and there is less heat generated at idle capacity. It definitely helped to decrease the temperature of my cores under load, which is particularly important for this computer as it’s used to do 24/7/ number crunching for Team_Bammann.

So I now have a 2.4GHz Core 2 Quad running at 2.7GHz, at a lower temperature than it was before! I’ve also upgraded all of the case fans to medium speed Scythe S-Flex fans, and the fan for the CPU heatsink to the high speed Scythe S-Flex fan. So there is also more airflow but with less noise, and this also further cools the CPU cores by another couple degrees.

This definitely helped the performance of the Colin McRae: Dirt game, but what REALLY helped the performance of the game was adding an extra 2Gb of RAM to a total of 4Gb. Unfortunately I can only use 3.0Gb due to the Vista 32bit limitation with my mainboard and graphics card, so an effective total of 3Gb. This SERIOUSLY increased the gaming performance, completely eliminating the stuttering that was occuring at times when lots of cars were on the track. What I realise now is that Windows Vista Ultimate uses so much RAM that 2Gb is just not enough for computer games. I expect that if you want to get serious about a beast of a gaming machine with a Vista installation, you need to go for 64bit and get a minimum of 4Gb.

I then also added (as I mentioned in a previous post) the Logitech Momo steering wheel so that I can really enjoy the new gaming beast I have. :-)

Server Downtime / Disc Brake Finger Tip Slicing & Dicing

You may or may not have noticed that this blog has been dead for a couple weeks. This is firstly because due to a recent price drop in Intel Quad Core CPU’s (specifically, the Q6600) I decided it was a good time to upgrade (even though I just got my first Core 2 Duo CPU this year). I also upgraded the graphics card to a Gainward 8800GTS Golden Sample.

An hour after getting the beast home, and pushing electrons through the thing, it started to die a horrible death of blue screens and random reboots. A logical conclusion (I thought at the time) was that the new CPU that got put in, was a dud. It turns out that the new brand of RAM I had been using (GeIL DDRII 667MHz Dual Channel 2×1GB CAS 3-4-4-8 passively cooled RAM) was not a very good product, and there has been a relatively high percentage of this RAM not working in particular configurations of machines! The store swapped me over to Corsair CAS 4 RAM, and now all is sweet again. It’s possibly slightly slower, but at least it works!

I also just happened by chance to discover a major security loophole with my webserver that delayed me putting it back online. I haven’t got around to fixing it for a couple weeks until now, and it only took about 10 minutes to fix, I just didn’t get around to it.

Recently a friend Nick asked me to join him as a duo in the foxy1000 mountain bike race at Fox Creek, which is a total of a 100km race, 25km per lap, and each lap involves 1000m of vertical ascending. The idea is we would do 50km each, i.e. 2000m ascending each in total. Since I’ve done stuff all riding this year, I went out to Fox Creek on Sunday to get in some training with Nick. As I was putting my bike back together (I have a small boot to fit it in) I put the front wheel on the wrong way around. I then squeezed the front brake and realised instantly the error of my way. With hydraulic disc brakes, if you squeeze the lever with no disc in, the pads get stuck closed together. I tried prying the two pads apart, to no avail. I then tried calling half a dozen bike stores for help, but being a Sunday, none seemed to be open. I also tried phoning a friend to see if they could quickly look up on the internet what to do. Getting really frustrated, and flat phone battery, I gave a screwdriver one last good hard push through the brake pads and voila!! Fixed like new. I think the problem was I wasn’t prying them open from both sides, which would have wedged the two pistons back on an angle and created too much friction due to the angle of force.

Very excitedly, I span the wheel. For some reason, I stuck my finger dangerously close to the rotor. I didn’t realise at the time just quite how sharp all the machined holes are in these disc rotors. My finger nail brushed up against the rotor, and the rotor cut into the middle of my finger nail, grabbing the tip of my finger and wedging it into the brake pad. This cut a third of the way across my finger nail, all the way through. At the time I just grabbed my finger and compressed it to numb the pain, and it didn’t seem to hurt that much. After walking around in circles a little bit trying to distract myself from the pain, I opened up my hand to find it covered in tomato sauce. For some reason I absolutely panicked, possibly because I haven’t actually seen any blood for a few years. Worried what was going to happen to my finger, I drove straight home, and then to a GP clinic where I waited almost 2 hours to get a tetanus shot. By the time I got home, I had wasted 6 hours of my Sunday – most unhappy!!

Vista Woes on FlammobammoMk3

I haven’t updated my blog (as promised) about the new computer I’m using these days. I’ve finally got 2 x 120mm Scythe S-Flex Fluid Dynamic Bearing fans, and a Scythe Ninja CPU heat-sink in the system. It is kind of disturbing that just those parts cost $160, and they don’t do anything except make the computer more silent than it already was. I kind of justified it though by the fact that it would also cool the computer better (in particular the CPU) which is a high priority considering I’m running the Core 2 Duo CPU at 100% on each core with Prime95, and that system stability is almost just as important to me these days as cardiac stability of my body (so true, so true…).

Anyway, here are a few pics of my system (aka FlammobammoMk3) in action! :-)

FlammobammoMk3FlammobammoMk3FlammobammoMk3FlammobammoMk3

I’ve learned the majority of the ins and outs of Windows Vista now, and discovered that all the software problems I was experiencing have been due to DEP (Data Execution Prevention) which Vista by default enables this for Vista programs and services, although I had also enabled it for all other programs. Sure enough, turning it back to the default DEP setting did wonders. I’m slightly disappointed with Vista as a whole as it appears that Microsoft have realised all the weaknesses of Windows XP (compared to Linux distributions, and Mac OS X Leopard) and fixed or implemented features to produce Vista, but I would have thought that for such a long time between OS releases, and given the budget that Microsoft have, it could be much better.

One major annoyance I have is not been able to run custom services without using 3rd party software such as FireDaemon Trinity (which by the way, is absolutely awesome software for anyone wanting to run Vista as some form of server, and I highly recommend it).

Another example is for an OS that is meant to be so security focussed, I’m amazed at how unintuitive the interface for assigning permissions to specific users is. I’m also disappointed that (apart from Windows Server 2003) there is no version of Windows Vista that will allow total denial of access to a particular folder, whilst allowing access to an adjacent folder (i.e. in the same parent folder). All it does is deny access to open the folder – that is, you can actually see the folder you’re being denied access to. I can understand the algorithm of permission assignment requires significantly more processing if it is to filter out displaying of unauthorised access, but considering the resource hog that Vista already is I wouldn’t have thought a little bit more resource hogging would be a problem. The ability to do this is called ABE (Access Based Enumeration), and Microsoft have implemented this in Windows Server 2003.

Another annoyance is that when I resized my system partition, Windows Complete PC Backup no longer works, because it doesn’t recognise the fact that the partitions have changed. As far as I can tell, the only way to fix error 80780010 is to reinstall the system on exactly the same hard drive. This is completely stupid, as if I have to restore my entire computer due to a hard drive failure, of course I’m going to replace it with a new bigger, faster drive. Therefore, my verdict of Windows Complete PC Backup is: “INTO THE BIN!!!!”

Windows Complete PC Backup is Crap

I’ve now considered going back to using SyncBack which I was previously using before Vista, but now that hard drives are so cheap and my system is running so beautifully, and I know how long it takes to get everything back up and running again, I’m fully endorsing drive imaging as the optimum backup solution. I’ve tried using Paragon Drive Backup, but I’m not 100% satisfied with it due to its lack of ability to do incremental backups of the entire drive, and the fact that you can’t specify what priority of system resources it should use (such as hard drive and CPU throttling so you can use the system productively in the background). I’m going to try using Acronis instead, and will report back with my experience.