Lets Build – Problems Encountered On Build

In the last post, I added in the graphics card and 2 hard drives from my old build. Windows 7 had been installed, as has Office 2010, Macromedia Fireworks, FileZilla, Realplayer, Notepad++ and also some diagnostic things like CPUID’s HWMonitor.

Major Problems Encountered

So far I had encountered a few major problems:

  • Whenever the computer booted, it would report “CPU FAN ERROR” – press F1 to continue. I first changed the option in the BIOS to tell it to carry on in the event of an error. I email scan and told them I had tried the CPU fan in all the headers, and it was still the same. After a few days, they replied asking me if I had put it in the CPU_FAN header, which it was already in. After a few attempts at contacting them again, they replied saying they thought it was the motherboard, and did I want them to send me another. Replacing the board would have meant starting right from the start again – rethermaling the CPU, fitting the cooler back on top of it, the RAM, updating the BIOS, probably re-installing Windows and all of the drivers.. at least I could have followed this blog if I got stuck. In the end I consulted with a friend who advised me to have a look at the BIOS settings again regarding the fan. I went in and changed the CPU LOW FAN SPEED from 600RPM to 200RPM. I believe this value means the value at which an error will be thrown if the CPU fan goes too slow, rather than setting the lowest fan speed – as you may imagine. The CPU fan seems to spin around 590 – 700RPM. With the new low value set – the error was gone, as the fan was spinning quicker than it’s warning value. (My fan spins slower than most CPU fans as it is a 120mm fan rather than an 82 or 90mm). The fan is quiet, the CPU is still cool, so it is good enough for me – and I am not going to try a new board.
  • All the issues with updaing the SSD firmware, see this blog post if you want to know how to hopefully avoid these issues, and my recommendations.
  • Blue screen on boot – when changing that SATA leads around, the BIOS decided that it would rather try and boot off the old Samsung drive with it’s old Windows 7 on it. The Asus EFI BIOS (simple version) only showed a little picture of my Samsung drive – so I had to go to the advanced options – boot and give them proper boot priorities as you would in a normal BIOS. Not really a problem – but worth watching out for.
  • Trying to update my Samsung drives with an OCZ firmware and breaking the Windows installation. I’d recommend completely disconnecting all non essential hard drives when playing around with updating firmware and Linux commands.