F5F Stay Refreshed Power Users Overclocking Need assistance! I experience a BSOD when trying to boot Windows after failing the 6700K OC process.

Need assistance! I experience a BSOD when trying to boot Windows after failing the 6700K OC process.

Need assistance! I experience a BSOD when trying to boot Windows after failing the 6700K OC process.

N
Nikos3434
Member
133
09-05-2016, 01:22 PM
#1
My setup includes an i7 6700K processor, Vengeance Corsair 3000Mhz DDR4 RAM with two 8GB modules, two GTX 970 SLI graphics cards, and an Asus z170 gaming motherboard.
I plan to recount the events in order, hoping someone will understand what transpired, since I’m still unclear at the moment.
I increased my 6700K overclock to 47x with an adaptive voltage of 1,215V plus 0.165V, which equals 1.38V. After running a stress test using RealBench, I observed that the voltage would occasionally spike up to 1,404V instead of staying at 1.38V. When this happened repeatedly, I stopped the test because the voltage rise was unsettling.
After pressing stop test, I encountered a blue screen that forced my PC to restart. Now, every time I restart, I see the same blue screen, immediately after the Windows logo appears with the loading icon below.
I accessed the BIOS and reset all overclocking parameters, but the computer still wouldn’t boot. I’m currently performing a fresh installation using an old Win10 USB drive, though I lost all my files—repair attempts were unsuccessful.
The ability to complete a fresh install on this machine suggests it wasn’t a hardware failure. It might be related to RealBench or its compatibility with SLI.
What exactly could have gone wrong? I’m looking for answers for future reference. Thank you.
N
Nikos3434
09-05-2016, 01:22 PM #1

My setup includes an i7 6700K processor, Vengeance Corsair 3000Mhz DDR4 RAM with two 8GB modules, two GTX 970 SLI graphics cards, and an Asus z170 gaming motherboard.
I plan to recount the events in order, hoping someone will understand what transpired, since I’m still unclear at the moment.
I increased my 6700K overclock to 47x with an adaptive voltage of 1,215V plus 0.165V, which equals 1.38V. After running a stress test using RealBench, I observed that the voltage would occasionally spike up to 1,404V instead of staying at 1.38V. When this happened repeatedly, I stopped the test because the voltage rise was unsettling.
After pressing stop test, I encountered a blue screen that forced my PC to restart. Now, every time I restart, I see the same blue screen, immediately after the Windows logo appears with the loading icon below.
I accessed the BIOS and reset all overclocking parameters, but the computer still wouldn’t boot. I’m currently performing a fresh installation using an old Win10 USB drive, though I lost all my files—repair attempts were unsuccessful.
The ability to complete a fresh install on this machine suggests it wasn’t a hardware failure. It might be related to RealBench or its compatibility with SLI.
What exactly could have gone wrong? I’m looking for answers for future reference. Thank you.

M
Mommola
Member
62
09-07-2016, 05:43 AM
#2
I've been experiencing some unusual issues too. At 4.7ghz with 1.32v on my 4690k, I would encounter BSODs. Then I'd enter an endless repair cycle in Windows 10, which took a long time to resolve, and now my computer feels slightly unstable. I've never seen Windows behave so oddly after overclocking. I'm curious if these problems are connected. If this happens again, try using the Windows Repair (F8) key or reinstalling from the disk. Either way, use CMD and run a chkdsk scan.
M
Mommola
09-07-2016, 05:43 AM #2

I've been experiencing some unusual issues too. At 4.7ghz with 1.32v on my 4690k, I would encounter BSODs. Then I'd enter an endless repair cycle in Windows 10, which took a long time to resolve, and now my computer feels slightly unstable. I've never seen Windows behave so oddly after overclocking. I'm curious if these problems are connected. If this happens again, try using the Windows Repair (F8) key or reinstalling from the disk. Either way, use CMD and run a chkdsk scan.

P
PXgame_br
Junior Member
49
09-07-2016, 08:58 PM
#3
What stresstesting tool were you examining? It seems to involve methods aimed at exceeding the voltage limit. The Extreme Tweaking utility performed without issues, while the other tool consistently exceeded the 1,379V setpoint.
P
PXgame_br
09-07-2016, 08:58 PM #3

What stresstesting tool were you examining? It seems to involve methods aimed at exceeding the voltage limit. The Extreme Tweaking utility performed without issues, while the other tool consistently exceeded the 1,379V setpoint.