[SOLVED] Windows BSOD after overclocking

Ultradreamz

Honorable
Nov 29, 2014
22
0
10,510
Not sure if this would go in hardware or software, since it deals with overclocking.

So I just recently built a fresh PC, got a 2700x with a 2060 and tried overclocking it. I got it to about 4.2ghz and I thought it was stable as it didnt crash while gaming for about 2 days then it started crashing randomly. Thinking it was the overclock, I just went back to stock speeds, but the random BSOD's didn't stop. I've since then reset my bios to defaults and did a CMOS reset but still can't stay in windows for more than 2 minutes before it BSOD's. None of this happened till after I tried overclocking.

Some of the stop codes include:
SYSTEM THREAD EXCEPTION NOT HANDLED
IRQL NOT LESS OR EQUAL
PAGE FAULT IN NONPAGED AREA
KERNAL SECURITY CHECK FAILURE

It seems to be random. Sometimes happening on startup, sometimes 2 minutes after I log into windows. I tried doing a sfc scan and DISN scan and both didn't do anything to stop the problem.
 
Solution
Doesn't sound like it has something wrong with the software though. It'd give the same BSOD if so. Though you should create a Windows 10 USB and create dumps for as much different fails as you can, so we might see some correlation, follow https://forums.tomshardware.com/thr...nclude-in-blue-screen-of-death-posts.3468965/ but no need to send the dumps yet, keep them at hand though. Do you have another PC nearby? Can you troubleshoot by replacing parts one by one? For example, try running with one RAM or different processor if you can.
Doesn't sound like it has something wrong with the software though. It'd give the same BSOD if so. Though you should create a Windows 10 USB and create dumps for as much different fails as you can, so we might see some correlation, follow https://forums.tomshardware.com/thr...nclude-in-blue-screen-of-death-posts.3468965/ but no need to send the dumps yet, keep them at hand though. Do you have another PC nearby? Can you troubleshoot by replacing parts one by one? For example, try running with one RAM or different processor if you can.
 
Solution