[SOLVED] OC CPU blue screen

[Norryv]

Hi guys,

I have had i5 2500k OC on 4.2 for about a week now and everything was fine until now. First I put it on 4.4 but I got blue screen while stress testing it. Today I got the blue screen mid-game, but I have been playing games and doing everything normally since I OCed it a week ago.

Should I be concerned about that or should I just keep doing everything like I used to?

 

[Dragos Manea]

I dont understand you get the BSOD while still OC or stock?

 

[Norryv]

I dont understand you get the BSOD while still OC or stock?

While still OC at 4.2, but there were no problems before at 4.2

 

[Dragos Manea]

You may need to increase voltage, there is a chance that it was never completly stable and it was a matter of time before this would happen.

 

[Norryv]

You may need to increase voltage, there is a chance that it was never completly stable and it was a matter of time before this would happen.

Thank you for your advice, I will try that.

 

[compprob237]

What specific blue screen did you get? Bluescreenview can tell you what the last BSOD was.

Cross reference the BSOD code/name with this list:

Spoiler: BSOD codes/names and their possible cause

0x101 = CLOCK_WATCHDOG_TIMEOUT = increase VCore
0x124 = WHEA_UNCORRECTABLE_ERROR = increase/decrease VCore (Usually increase) or QPI/VTT (Depends, usually increase)... You have to test to see which one it is.
0x0A = IRQL_LESS_OR_NOT_EQUAL = unstable RAM/IMC, increase QPI first, if that doesn't work increase VCore
0x1A = MEMORY_MANAGEMENT = It usually means a bad stick of Ram. Test with Memtest or whatever you prefer. Also, try raising your RAM voltage.
0x1E = KMODE_EXCEPTION_NOT_HANDLED = increase VCore
0x3B = SYSTEM_SERVICE_EXCEPTION = increase VCore
0x3D = INTERRUPT_EXCEPTION_NOT_HANDLED = increase VCore
0xD1 = DRIVER_IRQL_NOT_LESS_OR_EQUAL = QPI/VTT, increase/decrease as necessary
0x9C = MACHINE_CHECK_EXCEPTION = QPI/VTT most likely, but increasing VCore has helped in some instances
0x50 = PAGE_FAULT_IN_NONPAGED_AREA = RAM timings/Frequency or Uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
0x109 = CRITICAL_STRUCTURE_CORRUPTION = Not enough or too Much memory voltage
0x116 = VIDEO_TDR_ERROR = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)
0x7E = SYSTEM_THREAD_EXCEPTION_NOT_HANDLED = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r
0x139 = KERNEL_SECURITY_CHECK_FAILURE = Corrupt/out of date driver, possible corrupt OS file (I've had a bad drive), possibly bad/badly seated RAM, maybe increase VCore
0xF7 = DRIVER_OVERRAN_STACK_BUFFER = Bad system file read/corrupt. Issue with the OS or the storage. -> "HDD bad", or increase VCore
0x7F = UNEXPECTED_KERNEL_MODE_TRAP = QPI/VTT, Vcore, or RAM voltage. Have to test which.
0xC0000255 = Strange boot up = Corrupt BIOS config/behavior probably by RAM overclock. -> load defaults or reset CMOS to fix.

 

[Norryv]

What specific blue screen did you get? Bluescreenview can tell you what the last BSOD was.

Cross reference the BSOD code/name with this list:

Spoiler: BSOD codes/names and their possible cause

0x101 = CLOCK_WATCHDOG_TIMEOUT = increase VCore
0x124 = WHEA_UNCORRECTABLE_ERROR = increase/decrease VCore (Usually increase) or QPI/VTT (Depends, usually increase)... You have to test to see which one it is.
0x0A = IRQL_LESS_OR_NOT_EQUAL = unstable RAM/IMC, increase QPI first, if that doesn't work increase VCore
0x1A = MEMORY_MANAGEMENT = It usually means a bad stick of Ram. Test with Memtest or whatever you prefer. Also, try raising your RAM voltage.
0x1E = KMODE_EXCEPTION_NOT_HANDLED = increase VCore
0x3B = SYSTEM_SERVICE_EXCEPTION = increase VCore
0x3D = INTERRUPT_EXCEPTION_NOT_HANDLED = increase VCore
0xD1 = DRIVER_IRQL_NOT_LESS_OR_EQUAL = QPI/VTT, increase/decrease as necessary
0x9C = MACHINE_CHECK_EXCEPTION = QPI/VTT most likely, but increasing VCore has helped in some instances
0x50 = PAGE_FAULT_IN_NONPAGED_AREA = RAM timings/Frequency or Uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
0x109 = CRITICAL_STRUCTURE_CORRUPTION = Not enough or too Much memory voltage
0x116 = VIDEO_TDR_ERROR = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)
0x7E = SYSTEM_THREAD_EXCEPTION_NOT_HANDLED = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r
0x139 = KERNEL_SECURITY_CHECK_FAILURE = Corrupt/out of date driver, possible corrupt OS file (I've had a bad drive), possibly bad/badly seated RAM, maybe increase VCore
0xF7 = DRIVER_OVERRAN_STACK_BUFFER = Bad system file read/corrupt. Issue with the OS or the storage. -> "HDD bad", or increase VCore
0x7F = UNEXPECTED_KERNEL_MODE_TRAP = QPI/VTT, Vcore, or RAM voltage. Have to test which.
0xC0000255 = Strange boot up = Corrupt BIOS config/behavior probably by RAM overclock. -> load defaults or reset CMOS to fix.

Thank you friend, this is very good to know.
It seems that I need to change Vcore