A minor CPU adjustment caused a crash during Windows startup.
A minor CPU adjustment caused a crash during Windows startup.
Ok here's the deal! In the past I had my CPU OCed to 4.6ghz sturdy. Stressed it with Realbench everything was good. For some reason, I don't remember why, I reset my bios back to default and left it as is because I wasn't gaming alot, or rendering videos so I didn't worry about it much.
Anyway a few days ago I decided to OC my CPU again, starting out small of course, only at 4.2 with 1.20 voltage. Everything seemed fine while doing a benchmark to start on realbench. Temps only maxed out high 40s to low 50s. Anyway I rebooted my system and Windows would not boot up at all. It would boot into the start of splash screen and freeze half way through it, then go back to option to start normally or run start up repair. So of course I run startup repair with no resolve. I ran different sfc/boot scans on cmd/exe still with no resolve. Could not boot into safe more even.
End result is I had to reformat my system which resolved the situation.
What I am asking is, is what can cause this kind of problems with Windows from just a small OC??????
Here's the the method I used to OC
AI overclock tuner= auto
Core Ratio= 42
Restart the CMOS? That means you either removed the switch or the jumper on the motherboard, or you entered "Reset to Factory Defaults" into the BIOS.
I assumed you meant to adjust the BIOS settings. Did you perhaps overlook other parameters such as memory timings, voltages, base clock, or PCI-E clock while working at 4.6 GHz? Or could it be something else entirely, like a failing hard drive?
Restart the CMOS? That means you either removed the switch or the jumper on the motherboard, or you entered "Reset to Factory Defaults" into the BIOS.
I just installed Crystaldiscinfo
http://crystalmark.info/software/Crystal...dex-e.html
and it reports the HDD is healthy.
I've already reviewed that information and updated my bios without success. After adjusting the bios and setting them to default, I tried another small OC at 4.2ghz with 1.25v this time. The computer restarts itself but then hangs without any monitor signal. It requires a hard reboot just for my PC to display beep codes—specifically one long followed by three short—without any further indication. The issue seems related to memory failure or graphics, though I have no concrete evidence to support that. Maybe my MOBO or PSU is the cause, but I'm not sure.