Q6600, bios & overclock???

[da2ca]

I have just fitted a Q6600 I had it running 1.35v @3600MHz the only thing was on boot i got an error and had to press F1 to continue(Asus Commando). I googled the problem and i needed a new bios update. I updated to the latest bios but since then i have to up the v a notch on the CPU and windows is not even seeing the O/C? In bios and CPU-Z it shows 3600MHz but in windows (so on the sidebar gadgets) it show stock 2.4????

Has anyone come across this before?

 

[Rastalovich]

If the cpu is actually performing @ 3.6g, which u could test with something like SuperPI, cpu-z says 3.6, maybe CoreTemp says 3.6, it could be that the gadget program is just displaying the ID of the processor.

If u ask windows about the processor, in WindowsWelcome thingy for Vista or just right-click(MyComputer)->properties in XP (or control panel->System), it`ll show how the cpu is running as far as windows is concerned.

Often it`ll say [cpu-ID] Intel Q6600 2.4ghz [speed] @ 3.6ghz or similar. Ur gadget prog may just be displaying the first bit.

 

[da2ca]

If the cpu is actually performing @ 3.6g, which u could test with something like SuperPI, cpu-z says 3.6, maybe CoreTemp says 3.6, it could be that the gadget program is just displaying the ID of the processor.

If u ask windows about the processor, in WindowsWelcome thingy for Vista or just right-click(MyComputer)->properties in XP (or control panel->System), it`ll show how the cpu is running as far as windows is concerned.

Often it`ll say [cpu-ID] Intel Q6600 2.4ghz [speed] @ 3.6ghz or similar. Ur gadget prog may just be displaying the first bit.

Core temp + CPU-Z + bios say 3600MHz

Windows says 2.4GHz the gadgets i presume get there reading from windows.

 

[Rastalovich]

I`m pretty much thinking the same.

I`d still run some bench tests just to be sure.

I`m also assuming u have the likes of eist, c1e and whatever other cpu throttling stuff ur mobo may have, disabled.

 

[Mr. Smith]

I`m also assuming u have the likes of eist, c1e and whatever other cpu throttling stuff ur mobo may have, disabled.

I think that is the issue right there. Easily overlooked...