Windows does not want to overclock?! (Protection error message when using higher FSB) [asus a7v] [protection error]

Q: I was crazy about overclocking today on my T-bird 900 on an , everything was going well with 1911 x 100 multiplier, so I decided to try using 8.0 x 133, my system good start, but when windows loaded it gave me some protection u0026quot; u0026quot, error and told me that I need to get my computer to restart.

Anyone know what the hell is going on?


Re:You also might have to pump up your I/O voltage, besides the vcore, a little if you have "generic" memory or even PC100 (feel your memory chips and if they get hot don't keep that voltage setting). Also PC100 memory just might not cut it at 133.

Does anyone in here know if Sisoft's Mainboard info (specifically memory modules) reads the module information correctly? Cuz I bought PC133 generic but Sisoft Sandra reads it as PC100-333-622 and I can't take my Athlon over 138.


Re:increase the voltage until you can access windows. then stress-test the cpu. if successful, try pushing it further.

Re:<< /me thinks ASUS boards dont like u fiddling with the multiplier >>

you thinks wrong:)


Re:have you tried bumping up the voltage a notch or two?

Re:funny that im running with an ASUS a7v133 and get some message when i change the CPU multiplier too. allthough mine was upping the multiplier, see the thread i created above this on it, as i hadnt seen this. /me thinks ASUS boards dont like u fiddling with the multiplier

Re:its the a7v133… bump for more help

Re::D i've done that with my k7v (slotA mobo, 100fsb) and the PCI goes up to 44. my sound card makes static and my HD gets a few corrupt files each boot. but basically, either your CPU or one of your devices can't handle how far out of spec it's running

Re:Is it the A7V, or A7V133? If it's the A7V, using the 133FSB, your peripherals are running way out of spec. The onboard HDD controllers included, which is most likely what's causing the problem. Many people have gotten corrupted files from overclocking the FSB too much, because the harddrives and hdd controller can't handle much more than 33mhz

Related posts

Leave a comment

0 Comments.

Leave a Reply


click to changeSecurity Code

[ Ctrl + Enter ]