Overclock.net banner

Corrupted OS from OCing

309 Views 8 Replies 7 Participants Last post by  aod2002
Well I tried to bump up my OC today and failed miserably... BSOD upon boot so I upped the vCore to 1.4v from 3.875v and tried again. It booted but once I got into the OS my theme had been changed to the classic high visibility and Aero wasn't even available on the list of possibe options. Also all my services like audio and wireless card were disabled... So I tried booting with stock settings and I immediately get a BSOD...

Tell me something isn't broken... Im running MemTest now and then reformatting...



+REP to helpful answers.

±B±
See less See more
1 - 9 of 9 Posts
Have you tried running a restore point or recovery console?
Before reformatting, try using the Chkdsk command via your Windows CD. Then you might want to try the repair function - this will revert you to your original install but keep all your files intact.

Next time, remember to only use stable settings on your main drive. Set up a 10GB or similar drive with a bare OS, Prime95, CPU-Z and HWmonitor. Do all overclock testing on this separate hard drive to avoid OS corruption.
4
Quote:

Originally Posted by killa_concept View Post
Before reformatting, try using the Chkdsk command via your Windows CD. Then you might want to try the repair function - this will revert you to your original install but keep all your files intact.

Next time, remember to only use stable settings on your main drive. Set up a 10GB or similar drive with a bare OS, Prime95, CPU-Z and HWmonitor. Do all overclock testing on this separate hard drive to avoid OS corruption.
Great idea!


I just reformatted ad it seams all hardware is good to go... Funnily enough I didn't have any crazy volts going through anything... Little bit scared to OC now

Now to redownload and install everything


±B±
See less See more
Something that I do is run memtest for a while before I boot into windows. This usually gives a show of atleast a little bit of stability and ensures your ram is stable which is the quickest OS killer.
you could get a mini xp live cd or something, this way you know its not corruptable and try running orthos or prime on it? If it passes for like 8 hours or somthing, and you install windows again and it borks again, you can be pretty sure at that point its your HDD.
Quote:


Originally Posted by MADMAX22
View Post

Something that I do is run memtest for a while before I boot into windows. This usually gives a show of atleast a little bit of stability and ensures your ram is stable which is the quickest OS killer.

I ran MemTest and there were no errors. That's what the first thing that came to my mind... Funny enough all that I adjusted when I went into the OS was the me timings from 5 5 5 15 to 5 5 5 12 and upped the DRAM Voltage from 1.8v to 2.0 and raised the GTL to .67

Weird...

~B~
See less See more
3
Quote:


Originally Posted by BlankThis
View Post

Well I tried to bump up my OC today and failed miserably... BSOD upon boot so I upped the vCore to 1.4v from 3.875v and tried again.

Um, is that a typo? I think any vcore that high would bake your computer.


And it does sound like your OS is cooked. Try doing a repair install of Windows, without formatting. Repairing windows does wonders
See less See more
Also look into something like Acronis True Image so you can do a fresh install with all your favorite programs already installed
.
See less See more
1 - 9 of 9 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top