Jump to content

BSOD WHEA_UNCORRECTABLE_ERROR fix needed

Colt_0pz
By Colt_0pz
in Troubleshooting
 Share
Posted

So this is starting to annoy the fuck outta me. Frequently my pc blue screens and i have to restart the pc or press the reset switch on my mobo. i need a solution. Here's a link to the results of using system bsod collection application with dump file from C:windows\minidump: https://drive.google.com/file/d/0B-rZBINV_Ix_RGZCcUtleGVMUTA/view?usp=sharing. 

 

System info: OS: windows 8.1 pro 64 bit

New parts

never reinstalled OS

CPU: 4690K @4.4Ghz @1.3 volts

GPU: GTX 970 with windforce cooling (NOT THE G1 GAMING)

MOBO: ASRock Z97 Extreme6 with dual swappable bios updated to 2.3.

PSU: Seasonic SSR-650M

Desktop (obviously)

Link to comment
https://linustechtips.com/topic/403887-bsod-whea_uncorrectable_error-fix-needed/
Share on other sites
Link to post
Share on other sites
Posted

yup, bunch of files that don't really help at all...

An actuall picture of the of the BSOD would be more helpful

 

WHEA_UNCORRECTABLE_ERROR - is this the error code you're getting? Looks like the error is uncorrectable! Badum-ptss....

 

Try this one though:

https://msdn.microsoft.com/en-us/library/windows/hardware/ff557321(v=vs.85).aspx

 

Try to remember when the BSOD's started, try to link it to some event, like driver update for your GPU, I've heard nVidia release some quite buggy drivers recently (:

As microsoft suggets, run Windows Update and also check for any updated drivers for GPU, MoBo.

If the BSOD's started after updating GPU driver and you are already on the latest release, try rolling back to older version.

 

Try running disk error check

Run Memtest for couple of hours

CPU: Intel i7 5820K @ 4.20 GHz | Motherboard: MSI X99S SLI PLUS | RAM: Corsair LPX 16GB DDR4 @ 2666MHz | GPU: Sapphire R9 Fury (x2 CrossFire)
Storage: Samsung 950Pro 512GB // OCZ Vector150 240GB // Seagate 1TB | PSU: Seasonic 1050 Snow Silent | Case: NZXT H440 | Cooling: Nepton 240M
FireStrike // Extreme // Ultra // 8K // 16K

 

Link to post
Share on other sites
Posted

That error only happens to me if my CPU overclock is unstable. Does it pass an 8-hour stress test on Intel Extreme Testing Utility with that overclock?

Why is the God of Hyperdeath SO...DARN...CUTE!?

 

Also, if anyone has their mind corrupted by an anthropomorphic black latex bat, please let me know. I would like to join you.

Link to post
Share on other sites
Posted

Haven't even run the program :P

Have you done anything to determine if that speed is stable? If not, then that's the problem.

Why is the God of Hyperdeath SO...DARN...CUTE!?

 

Also, if anyone has their mind corrupted by an anthropomorphic black latex bat, please let me know. I would like to join you.

Link to post
Share on other sites
Posted

i will see if it's stable then i will get back to you

Okay. I hope you get things sorted out. :)

Why is the God of Hyperdeath SO...DARN...CUTE!?

 

Also, if anyone has their mind corrupted by an anthropomorphic black latex bat, please let me know. I would like to join you.

Link to post
Share on other sites
Posted

 

Some aspect of your overclock is unstable. The BSOD was triggered by an cache failure in the CPU.

 

Are you running your Memory on an XMP profile?

Windows 8 Kernel Version 9600 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 9600.17736.amd64fre.winblue_r9.150322-1500Machine Name:Kernel base = 0xfffff800`01e06000 PsLoadedModuleList = 0xfffff800`020df850Debug session time: Thu Jul  9 16:35:27.672 2015 (UTC - 4:00)System Uptime: 0 days 1:08:07.297********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffffe001c0e96028, Address of the WHEA_ERROR_RECORD structure.Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x124_GenuineIntelCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  googleearth.exCURRENT_IRQL:  fSTACK_TEXT:  ffffd000`975e8cf8 fffff800`025d1213 : 00000000`00000124 00000000`00000000 ffffe001`c0e96028 00000000`bf800000 : nt!KeBugCheckExffffd000`975e8d00 fffff800`01fcbf2d : 00000000`00000001 ffffe001`bfc86180 ffffe001`bfc86180 ffffe001`c0e96028 : hal!HalBugCheckSystem+0xcfffffd000`975e8d40 fffff800`025d16a0 : 00000000`00000728 00000000`00000003 ffffd000`975e9130 00000000`00000000 : nt!WheaReportHwError+0x22dffffd000`975e8da0 fffff800`025d1a0d : ffffe001`00000010 ffffe001`bfc86180 ffffd000`975e8f48 ffffe001`bfc86180 : hal!HalpMcaReportError+0x50ffffd000`975e8ef0 fffff800`025d18f8 : ffffe001`bfc858c0 00000000`00000001 00000000`00000003 00000000`00000000 : hal!HalpMceHandlerCore+0xe1ffffd000`975e8f40 fffff800`025d1b42 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4ffffd000`975e8f80 fffff800`025d1ccf : ffffe001`bfc858c0 ffffd000`975e91b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xceffffd000`975e8fb0 fffff800`01f617bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40ffffd000`975e8fe0 fffff800`01f61571 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7bffffd000`975e9120 fffff800`01e40a4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171ffffd000`339c0410 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CcMapAndCopyInToCache+0x29aSTACK_COMMAND:  kbFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: GenuineIntelIMAGE_NAME:  GenuineIntelDEBUG_FLR_IMAGE_TIMESTAMP:  0FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEBUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEFollowup: MachineOwner 

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to post
Share on other sites
Posted (edited)
  • Author

 

Some aspect of your overclock is unstable. The BSOD was triggered by an cache failure in the CPU.

 

Are you running your Memory on an XMP profile?

My memory is on XMP, but @ it's default speed @1600 mhz 

EDIT: how did you get that reference?

Windows 8 Kernel Version 9600 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 9600.17736.amd64fre.winblue_r9.150322-1500Machine Name:Kernel base = 0xfffff800`01e06000 PsLoadedModuleList = 0xfffff800`020df850Debug session time: Thu Jul  9 16:35:27.672 2015 (UTC - 4:00)System Uptime: 0 days 1:08:07.297********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffffe001c0e96028, Address of the WHEA_ERROR_RECORD structure.Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x124_GenuineIntelCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  googleearth.exCURRENT_IRQL:  fSTACK_TEXT:  ffffd000`975e8cf8 fffff800`025d1213 : 00000000`00000124 00000000`00000000 ffffe001`c0e96028 00000000`bf800000 : nt!KeBugCheckExffffd000`975e8d00 fffff800`01fcbf2d : 00000000`00000001 ffffe001`bfc86180 ffffe001`bfc86180 ffffe001`c0e96028 : hal!HalBugCheckSystem+0xcfffffd000`975e8d40 fffff800`025d16a0 : 00000000`00000728 00000000`00000003 ffffd000`975e9130 00000000`00000000 : nt!WheaReportHwError+0x22dffffd000`975e8da0 fffff800`025d1a0d : ffffe001`00000010 ffffe001`bfc86180 ffffd000`975e8f48 ffffe001`bfc86180 : hal!HalpMcaReportError+0x50ffffd000`975e8ef0 fffff800`025d18f8 : ffffe001`bfc858c0 00000000`00000001 00000000`00000003 00000000`00000000 : hal!HalpMceHandlerCore+0xe1ffffd000`975e8f40 fffff800`025d1b42 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4ffffd000`975e8f80 fffff800`025d1ccf : ffffe001`bfc858c0 ffffd000`975e91b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xceffffd000`975e8fb0 fffff800`01f617bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40ffffd000`975e8fe0 fffff800`01f61571 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7bffffd000`975e9120 fffff800`01e40a4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171ffffd000`339c0410 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CcMapAndCopyInToCache+0x29aSTACK_COMMAND:  kbFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: GenuineIntelIMAGE_NAME:  GenuineIntelDEBUG_FLR_IMAGE_TIMESTAMP:  0FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEBUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEFollowup: MachineOwner 
Edited by Colt_0pz
Link to post
Share on other sites
Posted

My memory is on XMP, but @ it's default speed @1600 mhz 

EDIT: how did you get that reference?

Can you try disabling XMP? Enabling XMP actually increases the CPU FSB, which can lead to errors such as what you are experiencing. 

 

As for how I got the dump output, look up WinDbg, its from the Windows Debugger which is a part of the Windows SDK.

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to post
Share on other sites
Posted
  • Author

Can you try disabling XMP? Enabling XMP actually increases the CPU FSB, which can lead to errors such as what you are experiencing. 

 

As for how I got the dump output, look up WinDbg, its from the Windows Debugger which is a part of the Windows SDK.

i haven't crashed since i increased my cpu voltage from 1.249 (which was the actual voltage) to 1.303. if it still crashes, i will take your advice

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing Troubleshooting

×