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/ repairs on cmd/exe still with no resolve. Could not boot into safe mode 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
Max CPU cache= Auto
Min CPU cache= Auto
Full Manual Mode= Disabled
Core Voltage= Adaptive
Additional turbo mode CPU core=1.200
Additional turbo mode cache= Auto
Eventual CPU Volts= 1.90
DRAM volts= Auto
Switch to full manual mode and attempt the following settings:
Core Ratio= 4.2
Max CPU cache= Auto
Min CPU cache= Auto
Core Voltage/Vcore = 1.3
All else = Auto
It should boot without stress-testing, as it may overheat at 1.3v.
Gradually reduce the Vcore by about 0.005V, testing for 10 minutes.
If successful, lower further until failure occurs, then reset to the stable setting.
For a 4.6GHz target, ensure adequate cooling and repeat the process.
Note: This will require higher voltages and increase temperatures.
Do you recall the Windows issue shown? It didn’t display a clear error message. The screen lit up with a blue alert and then restarted automatically, allowing the system to launch normally or start the recovery process.
Do you have the most recent BIOS and mobo drivers from the manufacturers website?
Thanks for joining. I’m aware I’m behind on the BIOS, but how could that lead to a corrupt file during my Windows boot after a minor OC? I’d like to understand this better, but it’s also a valuable learning moment.
I’ve downloaded the latest BIOS, but haven’t uploaded from flash yet. While checking versions in BIOS, I noticed my RAM (Corsair Vengeance 16GB, 2x8GB DDR3, 1866 MHz) was being read at 1333 MHz. Still, that shouldn’t cause this kind of problem?
Now I'm encountering another problem! It's really frustrating, like trying to push a snowball down a hill.
Anyway, I'm having trouble updating my UEFI BIOS from 2012 to 2801. I downloaded the BIOS from the ASUS website and copied it into a formatted 8 gigabit flash drive. After rebooting the PC into BIOS/advanced mode and using Asus EZ flash, I selected the drive with the BIOS and got this response (the selected files aren't the proper BIOS).
What's going on here?
I finally updated Bios and tried a minor OC again (chose 1.25v instead of 1.3v). It didn’t boot into Windows and just stopped, losing signal to my monitor. I had to force restart by holding the power button. After rebooting, I saw no beep codes—just a long three followed by a short—which suggests memory or GPU issues, though I’m not sure what’s causing it.
Bigj73nsb:
I finally updated the BIOS and tried a minor overclock again (chose 1.25v instead of 1.3v). It didn’t boot into Windows; it just stopped and lost signal to my monitor. I had to force restart by holding the power button. After rebooting, I saw no beep codes—just a long three short—which suggests memory or GPU issues, though I’m not sure.
Reset CMOS, then get Windows working without any overclocking, and gradually increase it from there.