Random freezing after OC
Random freezing after OC
CPU : Intel Core i5-6600K
COOLER : SilentiumPC Fera 3 HE1224
MOBO : GIGABYTE Z170-Gaming K3
RAM : Kingston 8 GB DDR4 2133 MHz CL14 HyperX Fury Black Series
GPU : 1060gtx 6gb
PSU : Corsair Vengeance Series 550M
I have the same problem but using an i5-3570K ASUS MMO P8Z77-V and Cooler Artic Freezer 13. Even at 3.6 GHz (stock is 3.4) at 1.25V, I experience freezes after one hour of testing with Prime95 blend test. If you discover a solution, please let me know!
BlackWings :
Details :
CPU : Intel Core i5-6600K
COOLER : SilentiumPC Fera 3 HE1224
MOBO : GIGABYTE Z170-Gaming K3
RAM : Kingston 8 GB DDR4 2133 MHz CL14 HyperX Fury Black Series
GPU : 1060gtx 6gb
PSU : Corsair Vengeance Series 550M
Hi. I attempted to overclock my CPU but the system would freeze after a few hours of operation. I am currently running at 4.4ghz @ 1.330V, which should provide sufficient voltage. Even in CPUID HWMonitor, the core voltage maxes out at 1.300V. Temperatures remained below 70°C during the Prime95 test. All systems appear normal, so I’m unsure of the issue’s origin. I also experimented with 4.0ghz, 4.2ghz and various voltages/auto settings, but the PC still freezes. I have to keep pressing the power button and restarting the system. No BSOD appears. Could this be related to the BIOS?
🙁
Thank you for your help.
Your motherboard’s VRMs seem fine; it might struggle with an i7 at 4.6GHz+, but it shouldn’t affect an i5. I believe the VRM issue can be ruled out.
I’m not familiar with the Corsair Vengeance Series power supply model (e.g., RM750x, AX1200i).
I have the same problem but with an i5-3570K ASUS mobo P8Z77-V and a Cooler Artic Freezer 13. Even at 3.6 GHz (stock is 3.4) at 1.25V, I experience freezes after about an hour of testing with prime95 blend test. If you have any solutions, please let me know!
For both of you, when accessing Event Viewer, do you notice any driver errors or Kernel-Power errors? These might appear in the error category, and sometimes they are also classified as critical.
for the both of you, when you open Event Viewer, do you notice any driver or Kernel-Power errors? These might appear in specific error categories, sometimes even critical ones. Yes! I detected Kernel-Power errors. The number matches the freezes that occurred. IMAGE
But my PSU seems fine. It's this one
LINK
. What should I do? How can I fix it?
BlackWings :
weberdarren97 :
Checking Event Viewer for both of you, do you see any driver or Kernel-Power errors? These might appear in the error category, and sometimes they're also marked as critical.
Yes! I did find Kernel-Power errors. The number matches the frequency of freezes I experienced.
IMAGE
My PSU seems fine. It's this one:
LINK
What should I do? How can I resolve this?
I've dealt with similar issues before. It's really frustrating, but I'm trying to walk you through the steps in the advanced menus. Just stay calm and stick to what I suggest.
First, let's try 1.35V. It's possible you lost the silicon and ended up with a chip that struggles with overclocking. After all, Intel never guaranteed successful overclocking. The K in the name just means you're free to experiment without voiding warranty.
I didn't mention this before, here it is as an update: Your power supply looks solid. I wasn't aware Corsair had a Vengeance lineup. It's not listed in the Tier List, but Johnny Guru rated it 9.2, so it's not a bad choice. Good voltage regulation, minimal ripple, voltage stays stable under load, and it can deliver slightly more power than advertised. I'm very unlikely the PSU is the issue.
WeberDarren97 shared his experience in the Event Viewer, noting driver and Kernel-Power errors. He found Kernel-Power errors matching the number of freezes he experienced. He mentioned his PSU seems fine but pointed to a specific model with a link for more details. He suggested trying a 1.35V setting first, as it might be due to a chip issue rather than the power supply itself. He also highlighted that the PSU is uncommon and recommended checking availability in Slovakia. Regarding updates, he didn’t specify but implied testing could help.
BlackWings :
weberdarren97 :
BlackWings :
weberdarren97 :
For both of you, when you open Event Viewer, do you see any driver or Kernel-Power errors? These might appear in the error category, and sometimes they also show up in the critical category.
Yes! I detected Kernel-Power errors. The number matches how many freezes occurred.
IMAGE
My PSU seems fine. It's this one
LINK
. What actions should I take? How can I resolve this?
I've faced similar issues before. It's really frustrating, I know. I'll attempt to walk you through the steps in the advanced menus. Please stay calm and avoid making changes outside of what I suggest.
First, let's try setting it to 1.35V. It's possible you lost the chip and ended up with one that isn't ideal for overclocking. After all, Intel didn't guarantee successful overclocking. The 'K' in the name just means you're allowed to experiment without voiding warranty.
I overlooked mentioning this earlier; here it is as an update: Your power supply appears fine. Corsair's Vengeance lineup isn't listed in the Tier List, but Johnny Guru rated it 9.2, so it's not a bad choice. It offers good voltage regulation, minimal ripple, stable voltage under load, and can deliver slightly more power than advertised. I doubt your PSU is the cause.
This particular PSU is relatively unknown. Only one store in Slovakia carries it, and I had to wait two weeks for it.
It's challenging to test it because it freezes quickly. Should I run a test like Prime95 for a few hours, or should I just let it run normally and see how long?
Is there any chance updating the BIOS could fix this?
If the BIOS is corrupted, the issue would have appeared as soon as you powered on the computer. Since the problem only started after you began overclocking, the BIOS isn't the root cause.
Given your high-quality components, the most likely reason is that your system doesn't tolerate those settings well.
Always stress-test the system during overclock attempts. Don't just use it at normal speed—push it to its limits. For example, run Prime95 until it crashes or stays stable for 24 hours.
You might want to enter BIOS and apply optimized defaults, then restart with your OC settings.
When doing this, keep a record of every BIOS setting you adjust while overclocking. Note the previous values and any changes you made. Having a notebook and pen ready will help you track what you're doing during testing.
The unusual thing is that when I first tried to overclock (adding a 0.005v offset voltage from 34 to 36), I received an error message indicating the S.M.A.R.T status was bad. Backup and replace were necessary. After scanning my disk, it turned out some sectors on my HDD were damaged and needed replacement. This might explain why I could always run one-hour tests under full load without exceeding 80°C, meaning my OC was actually stable. The only mystery left is why the first attempt could have caused an S.M.A.R.T error—was it coincidence?