• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Has OCing corrupted your OS?

bigdogchris

bigdogchris

Fully [H]
Joined
Feb 19, 2008
Messages
19,090
I was on my Vista x64 install for 2 months just fine and dandy. I decided to OC my e3110 (e8400) to 3.6ghz just by setting the FSB to 400mhz, no votage tweaks were needed. Memory is pc800 so that was fine at 800. It was prime stable for 20 hours or so one day another another 15 a few days later. Temps were low 50's under load. About 2 weeks after this my OS just started to boot really slowly, taking 3-4 times longer. I did a system restore and it was fine for another day, then went back to taking 3-4 times longer. I set my cpu back to stock and just delt with the long boot time since then. I haven't had any other issues. Hell, I can't even prove that that OCing is what caused it to start taking much longer. The performance logs show boot degradation (or at least did) but it was all just system files listed, no extra software even starts up. Using system restore to temporarily fix it though to me kinda proves the system files were messed up.

I'm not looking for assistance to the problem since I'm leaving it the way it is since it's fine, just taking longer to boot than normal, but has OCing ever done anything like this to you guys before?
 
I've seen an overclock make a machine unbootable, so yes, to answer the original question, I have had an overclock corrupt an OS. It is the main reason I keep a backup.
 
Absolutely. Even with a small overclock I totally fubar'd my Vista64. I had to do a clean install. It's making me gunshy to try again..
 
This happens to me about every 3 months and I have to re-do the OS. Keeps my Windows snappy ;)
 
yeah vista 64 is really picky with overclocks and since vista lacks the ability to do a non destructive restore its a pain in the ass.. ive lost count how many times ive fubar'd vista 64 on different systems doing overclocking.. gave up and went back to xp 32bit since i do not like xp 64bit..
 
I have not blown a OS out since the Dos/Win 3.1/OS/2 Warp or early NT/Nix days related to OC'ing. And even those failures I think can be traced back to failing controllers or drives that reared there ugly heads down the road be it IDE or SCSI. i have not had a SCSI setup in a long time now. But I do keep a 4 gig 7200 rpm SCSI drive and controller card in my drawer for benching and trouble shooting. :)
 
artless1 said:
I re-format At Least every 3 mos. just to keep my Speed on :cool: <slipstream>
Click to expand...

I haven't redone my XP Pro install in over a year. I use to do OS reinstalls. But in the end. You end up with a reinstall running like you had on your past install, because thats how you use your puter.

Do your house keeping and manage your OS and software. You end up with the real deal. :cool:
 
Been running a couple systems overclocked for a year on the same Vista install. Never had a problem as long as I locked the PCI at 33 and the PCIe at 100. I think (and I'm not expert) that the HD corruption comes from overclocking your PCI/PCIe busses, since your hard drive cannot be overclocked. As long as your motherboard supports the PCI lock, you should be fie.

I don't like to re-install my OS because it seriously takes me months of using the computer to get everything back to just the way I liked it, installing all the programs I use, getting shortcuts setup, etc. Plus I tend to upgrade oftem, so I'm more likely to do a new build than re-install the OS on an old system. ;)
 
I've been overclocking since PIII days and haven't had to reinstall an OS yest due to the overclock corruption (haven't tried Vista 64 yet). IMHO if you test and find the max OC and back off a wee bit then make sure the OC is stable with some of the stress programs you can go a long ways towards preventing OS corruption.
 
Overclocking CPU, or MEM, FSB / etc. from windows CAN corrupt your disk drive OS.
Use Prime95 or Memtest85/86 to test sys. from DOS at bootup, both these programs are free on net ie. http://www. majorgeeks.com or find a copy of "Ultimate Boot Cd" or "Hiren's Boot Disk" all free.

See also thread on ultimate bood cd.

Some ver. of CPUid or CBid also allow clocking from win. depending on MB. "easy and quick way to crash sys. "you too can boot into bluescreen with strange code and nothin else". "I see a reformat in your future!".

Test cpu till stable, then mem. till stable, then test together for final stablity only then boot into winXX.

If you corrupt sys (disk) your looking at reformat unless you keep backups - I have 3 - 250gb. sata at raid 0, - 3 partitions (main drives @ 3x7200rpm = 21,600rpm +/- ) and/ 2 - 320gb. ide drives - 3 parts.ea.(secondaries for backups and storage @ 5200rpms).

I use "XXClone" to do full bootable backups to at least 2 partitions. XXClone also duplicates disk ID, and MBR info to new copy see "cooltools tab". Its THE BEST program I've used for backups.

After that just select boot partition from BIOs - easy-easy-easy!
 
You must log in or register to reply here.
Back
Top