Win XP seems to be "preventing" O/Cing??

[Caveman]

Tried running up the FSB on my MoBo the other night... Temps are fine (never above 41 C), and the moBo is highly O/C able. But... Anything past 142 MHz and Win XP pops an error at boot saying that my hardware is running beyond capability and that Win XP will not boot because of this...

Hmmm.

I'm guessing that Win XP has a way to check the MoBo FSB at boot and prevent XP from loading??? Perhaps the value that the OS sees at install is stored in the registry and is checked at each bootup? Perhaps at each boot, there is a tolerance allowed to go past the "previos" setting and if that is not exceeding, one could surmise that an O/C could be "crept up on"??? Perhaps I just need to reinstall XP with a high FSB setting???


Any ideas here? Any registry fixes or anthing?

 

[CTho9305]

did you post this question 3 different places? I replied to one of the others . Mods dont like it if you post in multiple places, so post somewhere, then if you get no replies try another place later

 

[RudeBoie]

Temps aren't simply the only reason why an oc won't work. Sometimes the CPU can't handle it. I don't think XP has any negative stops against oc'ing. Chances are, if you got in, you'd immediately crash or wouldn't be able to pass all the standard stability tests.

If you can, increase the voltage.

 

[Vic]

What exactly does the error message say?
Most likely you are OC'ing one of your PCI devices too far.

 

[Zugzwang152]

Xp doesnt stop oc'ing, so the problem is from elsewhere. my cpu is slightly oc'd and xp reads it at 1.12Ghz just fine..

 

[Xtasy]

Xp dropped my fsb by 5 mhz. I could run 190x5 P3 at 950 on win 9x, but in win xp, totally unstable.

 

[Yoshi]

This is nothing new, Windows 2000 has similar overclocking limitations due to it's intolerance of errors. A lot of people who switched from 9x to 2000 found that they could not overclock as much as before.