Cool' n' Quiet Problem on MSI K8N Neo2

Aries64

Golden Member
Jul 30, 2004
1,030
0
0
I have the MSI K8N Neo2 and a FX-53 (939) and I cannot successfully get into Windows (2000 Pro) with Cool' n' Quiet enabled in the BIOS (found under the "Cell Menu") option of the BIOS. I've tried setting the Power Saving to "User Defined", "Min Power Saving" and "Maximum Power Saving in the BIOS, as well as through the operating system under "Power Management". Windows looks like its loading fine, but then right before I get the sign-in screen I get the "Blue Screen of Death" and a reboot.

With Cool' n' Quiet disabled in the BIOS the system runs fine. I would like to use the C n' Q feature so while for the past month my inability to use it has only been an annoyance it is starting to piss me off now. Anybody else have this problem? If so, have you been able to resolve it. I'm running the newest mobo BIOS (v1.2) but have not updated to the most current N' Force driver set (Version 5.10).

Thanks in advance for everyone's help.
 

jwarren

Junior Member
Sep 24, 2004
1
0
0
Aries, I've been having probs with CnQ also, although a little different. I wasn't able to successfully reboot Winxp with CnQ enabled. I found that bumping up my Vcore from 1.50 to 1.55 volts resolved that (although now I need a better HSF than stock).

 

Aries64

Golden Member
Jul 30, 2004
1,030
0
0
I found that bumping up my Vcore from 1.50 to 1.55 volts resolved that (although now I need a better HSF than stock).

jwarren,

Sorry for taking so long to reply to your post. After reading your post I tried increasing the vcore to 1.55 but that didn't help at all ORIGINALLY. This was including fiddling with the Power Management options in the BIOS and the Windows Control Panel. I had done this with the original BIOS that shipped on my board as well as with BIOS v.1.20.

Even when BIOS v1.30 was released I couldn't get Cool N' Quiet to work initially. However, I finally got C N' Q to work by:

(1) Updating to BIOS v.130
(2) Increasing the vcore to 1.55
(3) Increasing the FSB to 205. This bumped by CPU speed to 2460 Mhz. (FSB 205 x 12 Multiplier = 2460). Don't know for sure, but I wouldn't see why this should have ANY EFFECT AT ALL on C N' Q)!

Cool N' Quiet finally worked, reducing processor speed to 1230 (exactly half of the OC) unless playing 3D games. Cool! Then, while I should have left "well enough alone" a new Cool N' Quiet driver was released (v1.70).

Interestingly, I updated to v1.70, and then I was able to take the vcore back down to the default of 1.50v, as well as run the FSB at (the default of) 200 Mhz. I've found that with my fastest timings of 2-2-2-5 1T my FSB is not stable above 205.

I may try bumping the memory to the programmed SPD settings (speed of 217 Mhz with 2-3-3-7 timings) to see if I can get any speed increases that are noticible. I understand that lower memory latency is less important on AMD processors' than on Intel processors (Intel using a separate memory controller and the quad-pumped 800 Mhz FSB ala 875P and later chipsets) so maybe a few more megahertz is more useful thatn faster timings?

This seems to be especially pronounced on the AMD processors with integrated memory controllers such as the Athlon 64 and the FX-53s'. I'm still learning. This system is my first AMD platform after having built and used only Intel systems.

BTW, I recently upgraded to the Thermaltake Venus 7 (A1772) for S939. It is a direct replacement for the stock HSF that came with my (Retail) FX-53. It uses the exact same mounting system as the stock HSF that came in the box, and is one of the "Qualified" HSFs' recommended by AMD on their web site.

And, being a direct replacement recommended by AMD, it also has the three-wire connector incorporating the fan speed controller tied to the mobo BIOS for CPU cooling. You probably know this, but Thermaltake supplies many of the stock HSFs that come with the Retail AMD CPUs.

I'm sure there are more efficient HSFs out there for the S939 but this one is an easy replacement for someone whos is not going to OC their system too much if at all. Thanks for your input on the vcore.