Windows Xp/Vista no longer showing overclock

[soccerballtux]

All I did was move the sata drive from Port 1 to Port 6 on my IP35-E.

Now, even though it's detecting the overclock and showing the CPU as 3.4Ghz in the BIOS, somehow when I get to Windows it's not showing it. WTF!!

This OC is 8 hours Orthos Small stable.

 

[Rhonda the Sly]

If it's detecting your processor as 6x 340 = 2040 then EIST/C1E is on and the sticky is officially a damned curse.

 

[myocardia]

Originally posted by: soccerballtux
All I did was move the sata drive from Port 1 to Port 6 on my IP35-E.

Now, even though it's detecting the overclock and showing the CPU as 3.4Ghz in the BIOS, somehow when I get to Windows it's not showing it. WTF!!

So move your HD back to Port 1, and see what happens.

 

[tvdang7]

Did you fix this? im having the same damn problem!!!

 

[nerp]

Clear CMOS and re-input OC settings. The IP35-E loves CMOS resets and it seems to resolve lots of weird issues.

I was having issues with my system after I upgraded the CPU from an E2180 to E8400. Resetting the CMOS worked wonders.

 

[tvdang7]

i have a ds3l however. ive cleared the cmos and redone it already. the wierd thing is that it accepts the ram timings but not anything else. This overclock used to work perfectly for me on xp. im a new vista user.

 

[soccerballtux]

 

[VirtualLarry]

So its not just gigabyte boards with this issue

 

[brencat]

Originally posted by: tvdang7
Did you fix this? im having the same damn problem!!!

Save your OC as a profile using the 'Save CMOS to Bios' feature in the main bios menu. The DS3L has a habit of 'forgetting' OCs from time to time unless you save the OC profile.

Also, did you remove the power cord from the wall recently or turn standby power off on the surge protector recently? My IP35-E will do the same thing if power goes out in a storm and is restored in < 2 hrs.