m0rph’s

Today I installed the Scythe Ninja Plus Rev B heatsink, and here’s how it performed. At 3.0ghz the e8400 gave an idle temperature reading of 35C- So no bad, even though I think I might have applied a little too much thermal paste. Nevertheless, the max load temperature was 42C, which I am happy with.

I overclocked the e8400 to 3.6ghz with ease- I am amazed at how fast I was able to fix the bios settings on the Gigabyte ex38-dq6 motherboard. Much to my satisfaction, the overclock temperatures were 36C-37C idle, and 46C while running Prime95. I didn’t run Prime95 for very long, so I’d say the absolute max could be around 50C. Finally, I have to say that I am content with the Ninja’s performance with the 120mm fan on it. Now I’ve got a total of 3 120mm fans in the Antec Sonata III case- One at the front sucking in, second on the Ninja and the third at the back blowing out. All of the fans blow in the same direction to maximize air flow.

I previously told you that I was going to build a new pc for myself, and I gave a list about the parts. Now I’ve had the rig up and running for about an week, and I’m mostly happy. The e8400 processor is very nice, and in combination with the gigabyte ex38-dq6 motherboard, there shouldn’t be any problems overclocking it. However, the stock heatsink doesn’t do it’s job efficiently enough for my standards (min: 35C, max: 46C, avg: 38C with factory clock), so I’ve ordered a Scythe Ninja Plus. I hope I can fit it in the case

The Zotac Geforce 8800 GT AMP! card is working like a charm. I ran 3DMark and scored just below 13000 with stock settings, and when I’ve got the new heatsink and some overclock, I’ll run it again and post the results.

It seems I was a little too hasty in giving Firefox 3 Beta 5 as much credit as I did earlier. Ffb5 does work extremely well, untill it doesn’t. As far as I am able to tell, the browser becomes extremely slow at random times often after keeping the browser open for some time, this is a result of a boost in memory usage and cpu load for no apparent reason. Surprisingly this problem does not occur to everyone, I only found a few reports. Nevertheless, this is a very big issue, that didn’t occur in ffb4. Obviously the browser is in beta stage, so whining is out of question. However, I could have recommended ffb4 to those willing to experience the speed improvement with only a few downsides, but I can’t say the same for ffb5. As the release of Firefox 3 draws nearer, I hope this problem gets fixed as soon as possible. I will still keep using ffb5 Post comments if you are having a similar problem and also if you know what’s causing it.