Blue screens everywhere suddenly

D

-Doug-

n00b
Joined
Nov 20, 2011
Messages
55
Specs:

i7 3930k @ 4.8Ghz
16GB Corsair DDR3 1866mhz 1.5V
ASUS P9X79 Deluxe
BFG 1200W-EX PSU
EVGA GTX480 Superclocked
Crucial M4 SSD
Custom Water Loop

Alright so my computer has been rock solid since I finished overclocking it a few months ago. No BSODs, ever. Prime95 for 12+ hours, etc... Suddenly, within the past week or so, I'm getting blue screens whenever I'm doing something resource intensive (gaming, video encoding, etc). The blue screen messages vary, and include:

-The clock interrupt error message
-IRQL_NOT_LESS_THAN_OR_EQUAL
-PAGE_FAULT_IN_NONPAGED_AREA

Like I said, this computer has been stable for months without a single crash, but now it's happening all the time. Temps are good. I even tried increasing the vCore to no avail. What on Earth could be causing this all of a sudden? I've been running at fairly safe voltages, below 1.5V, usually about 1.45-1.48V for my vCore. 1.5V on my RAM (as specified), and 1.1 VCCSA.

Edit: whew, just hit post before another bluescreen hit. (I was encoding). Also, I've reset my clocks and voltages to stock. I'm back to encoding, so we'll see if she crashes. I don't see why the overclock would turn unstable all of a sudden though.

Thanks.
 
Last edited:
It is still not well understood what overclocking can cause to components but for sure it greatly shortens the life span and makes them unstable over a time. And owning an extreme edition CPU wont protect you against this either(especially it varies from piece to piece and OC results are not covered in warranty so hope you didn't harm your CPU). This issue is definitely caused by RAM or CPU. Try to remove some RAM sticks or try each one separately, if the issue occurs, try different CPU.

Ofc tell us if it crashes on stock.
 
Yeah, I'm gonna test it on stock for a while, see what happens. If it's stable, then I suppose I'll just have to go with a milder overclock, or none at all. It perplexes me how an overclock can be stable for 2 months and then just decide to die. Not like I was using extreme voltages or crappy cooling.
 
Shit happens even to the most well prepared and well thought out PCs.

Run Memtest the next time the system BSODs.
 
It should be very easy to understand how a once stable OC has suddenly gone unstable - you're running the parts above spec! OC'ing requires more power, more power requires more heat, more heat shortens the lifespan of components. I'd try a lower RAM speed while going for a higher CPU speed. I haven't bothered with RAM OC'ing in a while since the real world performance gains aren't very noticeable, IMO.
 
enginurd said:
It should be very easy to understand how a once stable OC has suddenly gone unstable - you're running the parts above spec! OC'ing requires more power, more power requires more heat, more heat shortens the lifespan of components. I'd try a lower RAM speed while going for a higher CPU speed. I haven't bothered with RAM OC'ing in a while since the real world performance gains aren't very noticeable, IMO.
Click to expand...
Sometimes I believe the overclocking is become less effective how time goes by. Litography of CPUs decreased by 6 times in last 10 years. And the conductive ways within die structures are already too thin to carry extensive current. So I'm not wondering why his i7 gave up after 2 months being overclocked.
 
I really don't see the point in OC'n bleeding edge hardware like that then expecting it to be reliable....
 
: whew, just hit post before another bluescreen hit. (I was encoding). Also, I've reset my clocks and voltages to stock. I'm back to encoding, so we'll see if she crashes. I don't see why the overclock would turn unstable all of a sudden though.
Click to expand...

Reseat the memory. Also, there's crash dump analyzers for a reason. It should help narrow down whats causing the issue for you.
 
stiltner said:
Reseat the memory. Also, there's crash dump analyzers for a reason. It should help narrow down whats causing the issue for you.
Click to expand...

Whocrashed is a good, easy to use one that doesn't require symbols installation.

Most of my "clock interrupt" type blue screens are from bad vcore values. Could be other things though.
 
You must log in or register to reply here.
Back
Top