OCing messing up registry?

[sackynut]

Hi all! Well I have a bit of a question and possibly a problem.
Lets see:

Well my PSU was failing on me, so I went out and bought a brand new one. a 650watt. I usually know what I am doing, and once I hooked up the PSU i decided "hey! why dont I flip the 'stupid' switch on and overclock like a madman now that I have a new better PSU".

so I started OCing. it didnt really pass boot that much , but once (with my HT at 1200mhz) I passed boot. I logged in and i got a error message that said something like "one or more of the files contaning the registry is deleted or corrupted" and within about 2 seconds my computer rebooted itself and I decided to go back down to stock settings. My computer SEEMS to bee fine since, and I havent received that error since either.

But im wondering, why/how does OCing mess up the registry?



and

since I have not gotten that message anymore does it mean my registry is back to normal?
I really do not want to reformat again...
I am posting this in the software section too.

 

[Dr_House]

The errors are caused usually by Page File errors or corrupt data due to excessive speed (overclocking) and not being able to maintain the file integrity. Your registry was never really corrupt, but rather only the Memory was corrupting Windows Files since it was at too high of speed, once you lower the speed back down, the corruption goes away.

Don't worry, your system is fine.

 

[sackynut]

thank you!

 

[julius]

theres usually no bad consequences doing this, ive had it happen to me plenty of times, even as bad as not getting to windows loading screen with too high of an oc, but dont get carried away doing that. theres going to be a time when it will really butcher your windows installation, just like sometimes you reboot after it freezes and theres no problem, and other times you reboot, and windows is corrupt, and it wont be too pleasant. ive learned to boot to memtest86 or prime on a disk and testing if its stable before letting it boot to windows.

 

[Dr_House]

1 thing people should know is that no matter how much you overclock, an overclock should never permanently hurt a Windows Installation. Anything can be fixed by:

1) Underclock the CPU or RAM if you get BSoD's

2) Run CHKDSK if errors continue after underclocking

3) Underclock CPU or RAM if you get Registry Errors

4) Flash BIOS to newest and put on newest Chipset Drivers

 

[julius]

again, yes you can screw windows up with an overclock. ive done so... ive also done it with shutting down the system while the hard drive was paging. ive screwed up not just the registry, but the allocation tables on the hard drive itself, where i had problems with reinstalling windows until i did a full format. so yes, windows can be corrupted, dont make assumptions without experience.

 

[Dr_House]

again, yes you can screw windows up with an overclock. ive done so... ive also done it with shutting down the system while the hard drive was paging. ive screwed up not just the registry, but the allocation tables on the hard drive itself, where i had problems with reinstalling windows until i did a full format. so yes, windows can be corrupted, dont make assumptions without experience.

You must not have read my message, the Internet can be a crowded place, so let me reiterate:

Due to OVERCLOCKING, Windows can never become PERMANENTLY corrupted.

Don't make assumptions w/o experience

No disrespect, but I guarantee I've had more experience in IT than you.

 

[7H4_D00D3]

been there......

Now I won't OC til I have a second HDD (yeah right, as soon as I have new fans the OC will resume!!!)

Try to OC first with very relaxed latencies, that way it'll be hard to corrup stuff or mess stuff up or stuff the stuff up

 

[julius]

what the hell does permanently corrupted mean in your dictionary... windows can get corrupted to point of a need to reformat, thats pretty permanent...

 

[Dr_House]

what the hell does permanently corrupted mean in your dictionary... windows can get corrupted to point of a need to reformat, thats pretty permanent...

Are we on the same planet?

I'm talking about OVERCLOCKING, not turning off your computer while it's swapping.

 

[julius]

yes, im talking about the exact same thing. its happened to me during oc'ing as well as swapping. check disk never found anything wrong, windows gives eror messages at end of install, reformat and errors gone. when the memory writes enough bull, its enough to corrupt the filesystem...

 

[Dr_House]

yes, im talking about the exact same thing. its happened to me during oc'ing as well as swapping. check disk never found anything wrong, windows gives eror messages at end of install, reformat and errors gone. when the memory writes enough bull, its enough to corrupt the filesystem...

I'm going to try and dissect this:

If you're overclocking, and it's causing errors you will most likely get a BSoD or error at boot or when you attempt to run an application. If you're able to run several applications and it runs fine for awhile, and crashes after awhile, it's most likely a stable system, which means the overclock DID cause the crash, but that it isn't severe.

Now, if you have a File System Corruption, a combo of Chipset Driver re-installation and CHKDSK will fix most of the errors and everything will be nice.

Now, for the .01% of us who get the unlucky day where a BSoD does more than show fireworks, it actually starts a fire, that is very rare, as I have done some insane overclocks and had system crashes from 1st boot to after 72hrs of constant on, and no corruption. Now, my original statement of "An overclock should never cause a permanent corruption" is still valid, since Should is not Won't, and it refers to common cases. If I said NEVER Causes, than I'd be wrong, but I kept it broad for the most of people.

The poster's question was answered in post #2 by me, so this thread can now R.I.P.

 

[J-Micro]

Well, I would say that since you received this error when overclocking, there is a potential problem with you motherboard not locking the PCI bus.
The PCI bus runs at....33 MHZ, but once you past the 37 MHZ mark (overclocking your FSB (HTT)- you can cause your Hard drives (and other peripherals that use that bus to exchange information) to either corrupt data, or improperly operate as such high a frequency....causing error messages such as that one.

If your PCI bus is locked, it could be something else. What motherboard do you have? Are you running a RAID configuration? (many motherboards
do not have full PCI bus locking capabilities when SATA is used.

 

[julius]

the mobo i have now is not the one that the erors occured, now i have a dfi cfx3200. before i had an nforce 2 board, which does have a pci lock. i never ran raid.