Blue screens please help

[ashepherd316]

ever since i overclocked my i5 2500k cpu yesterday to 5ghz with vcore at 1.45 on my asrock p67 pro3 mobo i have been getting these blue screens very strange as the cpu temps are all good please can anyone help thanks.On Tue 12/07/2011 19:35:31 GMT your computer crashedcrash dump file: C:\Windows\Minidump\071211-19281-01.dmpThis was probably caused by the following module: Unknown (0xFFFFF80003096D29) Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFF80003096D29, 0xFFFFF880009A9898, 0xFFFFF880009A90F0)Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_MBug check description: This indicates that a system thread generated an exception which the error handler did not catch.This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown . Google query: Unknown SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_MOn Tue 12/07/2011 19:35:31 GMT your computer crashedcrash dump file: C:\Windows\memory.dmpThis was probably caused by the following module: Unknown (0xFFFFF800030CED00) Bugcheck code: 0x7E (0xFFFFFFFFC000001D, 0xFFFFF80003096D29, 0xFFFFF880009A9898, 0xFFFFF880009A90F0)Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLEDBug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown . Google query: Unknown SYSTEM_THREAD_EXCEPTION_NOT_HANDLEDOn Tue 12/07/2011 19:08:37 GMT your computer crashedcrash dump file: C:\Windows\Minidump\071211-22308-01.dmpThis was probably caused by the following module: Unknown (0xFFFFF800030D1D00) Bugcheck code: 0x124 (0x0, 0xFFFFFA8008D81028, 0xBE200000, 0x5110A)Error: WHEA_UNCORRECTABLE_ERRORBug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown . Google query: Unknown WHEA_UNCORRECTABLE_ERROROn Tue 12/07/2011 18:49:25 GMT your computer crashedcrash dump file: C:\Windows\Minidump\071211-31465-01.dmpThis was probably caused by the following module: hal.dll (hal+0x12A3B) Bugcheck code: 0x124 (0x0, 0xFFFFFA8008DE5028, 0xBE200000, 0x5110A)Error: WHEA_UNCORRECTABLE_ERRORfile path: C:\Windows\system32\hal.dllproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: Hardware Abstraction Layer DLLBug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. On Tue 12/07/2011 17:51:08 GMT your computer crashedcrash dump file: C:\Windows\Minidump\071211-21871-01.dmpThis was probably caused by the following module: Unknown (0xFFFFF800030DFD00) Bugcheck code: 0x124 (0x0, 0xFFFFFA8008E24028, 0xBE200000, 0x5110A)Error: WHEA_UNCORRECTABLE_ERRORBug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown . Google query: Unknown WHEA_UNCORRECTABLE_ERROROn Mon 11/07/2011 18:51:26 GMT your computer crashedcrash dump file: C:\Windows\Minidump\071111-20982-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00) Bugcheck code: 0x3B (0xC000001D, 0xFFFFF800030DDE63, 0xFFFFF8800969FFD0, 0x0)Error: SYSTEM_SERVICE_EXCEPTIONfile path: C:\Windows\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemBug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Mon 11/07/2011 18:47:05 GMT your computer crashedcrash dump file: C:\Windows\Minidump\071111-20186-01.dmpThis was probably caused by the following module: Unknown (0xFFFFF800030D6D00) Bugcheck code: 0x124 (0x0, 0xFFFFFA8008E85028, 0xBE200000, 0x5110A)Error: WHEA_UNCORRECTABLE_ERRORBug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown . Google query: Unknown WHEA_UNCORRECTABLE_ERROR

[clum]

All the ones citing "0x124" are due to insufficient vcore. You're already very high at 1.45 so I'd suggest that you probably don't have a safe 5GHz chip, unless you don't care about it having a decent life cycle. In which case, pump some more voltage into it.

[cmeeks]

I was getting BSODs while doing nothing but internet browsing... or even nothing at all! I eventually fed it a little more vcore and I've been running solid ever since. Currently running 4.8GHz at 1.40v. What are you typically doing when these BSODs occur? Some chips, while they will boot into Windows perfectly fine and act seemingly fine, just aren't happy at 5.0GHz. I can boot into Windows at 4.8GHz with 1.36v, or 5.0GHz with 1.40v, but what voltage is fine for bootup, or even a few hours of prime95, doesn't necessarily cover the gamut of day to day operations.

[Guest Kosta]

According to some, 1.5 is safe for 24/7. Up to 1.6 for benchmarking but not 24/7...I say up to 1.53 if you can afford a new chip in case it burns...Otherwise back down to 4.8 and stay below 5ghz.Also this isn't a guarantee it will hold. OCing is a risk - always.

[ashepherd316]

put it on 1.47 so hopefully that will be enough if it does burn ill get an i7 2600k

[ashepherd316]

works but core temps were getting upto 98c so i put it down to 4.8ghz and 1.43 vcore

[ryanbatc]

works but core temps were getting upto 98c so i put it down to 4.8ghz and 1.43 vcore

STOP NOW DANGER lol!When OCing you don't want to go above 80C (let me rephrase that - I wouldn't want my temps above 80 as a very maximum, under P95 or OCCT full load)

[ashepherd316]

yeh i know ive chnged the cpu to 4.8ghz and vcore to 1.38 all seems to be running fine now

[ashepherd316]

i thought sod it went and bought an i7 2600k so hopefully that will do better than my 2500k its only at 4ghz now and max temps are 72c hopefully i can do better with the 2600k.