my overclocked 3.82 i7-930 finally started blue screening :(

[finbarqs]

Does this mean my CPU is bad? or my memory? I can put it back to factory clocks, and it'll boot into windows.

Darn.. lasted about a year

 

[tweakboy]

Hmmmm, Are you positive its the CPU dying ? If your settings in BIOS are the same I dont know why this would happen.

I say the culprit is your RAM . RAM is 80 percent of all blue screens its cuz of RAM.

Take out your ram and test it one by one. Stock settings btw on CPU and GPU ...dont OC for now. let us know

 

[Suspicious-Teach8788]

with BSODs always provide BSOD codes

check this link:
http://www.overclock.net/12165349-post1111.html

BSOD codes for overclocking
0x101 = increase vcore
0x124 = increase/decrease vcore or QPI/VTT...have to test to see which one it is
0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
0x1E = increase vcore
0x3B = increase vcore
0x3D = increase vcore
0xD1 = QPI/VTT, increase/decrease as necessary
0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances
0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
0x109 = Not enough or too Much memory voltage
0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)

 

[cubeless]

or is the hsf full of dust?

 

[finbarqs]

it's a coolit ECO system

 

[BTRY B 529th FA BN]

with BSODs always provide BSOD codes

check this link:
http://www.overclock.net/12165349-post1111.html

WOW!!! :thumbsup:

 

[blackened23]

with BSODs always provide BSOD codes

check this link:
http://www.overclock.net/12165349-post1111.html

That certainly isn't what the microsoft bsod code's mean, this is all speculative and done by an enthusiast. The OS has no way of knowing if your CPU needs more voltage or increased PLL voltage, are you kidding me? You could interchange any of those and it will still be a fantasy. Do you really think microsoft would return error codes that tell you "oh hey you need to increase voltage...no wait...PLL....nowait BCLK..." gimme a break. Thats a good fantasy though, I got a good laugh out of it. Also from the OP , I understand that he ran his system for a year with no changes. Why would he suddenly overnight need to increase voltage?

To the OP, i've had longtime overclocked CPU's fail before, and was verified to be the CPU by replacing them - they usually occured after a year of continuous 24/7 use. You will slowly get errors/BSOD's and they will increase in frequency, you can try fiddling with things but you may have to get a new system...or revert to factory clock if it works. I had a CPU that started BSOD'ing overclocked after a year of use, then I had to revert to stock...then stock started BSOD'ing a few days later.

 

[LOL_Wut_Axel]

Does this mean my CPU is bad? or my memory? I can put it back to factory clocks, and it'll boot into windows.

Darn.. lasted about a year

CPU degradation, probably. What voltage are you running through it?

 

[BTRY B 529th FA BN]

That certainly isn't what the microsoft bsod code's mean, this is all speculative and done by an enthusiast. The OS has no way of knowing if your CPU needs more voltage or increase PLL voltage, are you kidding me? You could interchange any of those and it will still be a fantasy. Do you really think microsoft would return error codes that tell you "oh hey you need to increase voltage...no wait...PLL....nowait BCLK..." gimme a break. Thats a good fantasy though, I got a good laugh out of it.

To the OP, i've had longtime overclocked CPU's fail before, and was verified to be the CPU by replacing them - they usually occured after a year of continuous 24/7 use. You will slowly get errors/BSOD's and they will increase in frequency, you can try fiddling with things but you may have to get a new system.

Both the link and what you say have about the same amount of validity. We all get hunches about where a problem may reside. I'm not knocking you I'm just saying.