Windows 10: WHEA_UNCORRECTABLE_ERROR

C:\Windows\Minidump folder dpmwindowsMemtest86+



Microsoft R Windows Debugger Version 6.12.0002.633 AMD64

Copyright c Microsoft Corporation. All rights reserved.





Loading Dump File [C:\Windows\minidump\020320-9828-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available



Symbol search path is: *** Invalid ***

****************************************************************************

* Symbol loading may be unreliable without a symbol search path. *

* Use .symfix to have the debugger choose a symbol path. *

* After setting your symbol path, use .reload to refresh symbol locations. *

****************************************************************************

Executable search path is:

*********************************************************************

* Symbols can not be loaded because symbol path is not initialized. *

* *

* The Symbol Path can be set by: *

* using the _NT_SYMBOL_PATH environment variable. *

* using the -y <symbol_path> argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

Unable to load image ntoskrnl.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Windows 7 Kernel Version 18362 MP 8 procs Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Machine Name:

Kernel base = 0xfffff804`17c00000 PsLoadedModuleList = 0xfffff804`18048210

Debug session time: Mon Feb 3 16:00:24.374 2020 UTC + 8:00

System Uptime: 0 days 0:06:39.206

*********************************************************************

* Symbols can not be loaded because symbol path is not initialized. *

* *

* The Symbol Path can be set by: *

* using the _NT_SYMBOL_PATH environment variable. *

* using the -y <symbol_path> argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

Unable to load image ntoskrnl.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Loading Kernel Symbols

...............................................................

................................................................

................................................................

...........................

Loading User Symbols

Loading unloaded module list

...................

Cannot read PEB32 from WOW64 TEB32 000117e9 - Win32 error 0n30

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************



Use !analyze -v to get detailed debugging information.



BugCheck 124, {0, ffffe6821d10a028, ba000000, 11000402}



*** WARNING: Unable to verify timestamp for mssmbios.sys

*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys

***** Kernel symbols are WRONG. Please fix symbols to do analysis.



*************************************************************************

*** ***

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files such as the public OS symbols do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***

*** ***

*************************************************************************

*************************************************************************

*** ***

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files such as the public OS symbols do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***

*** ***

*************************************************************************

Unable to load image PSHED.dll, Win32 error 0n2

*** WARNING: Unable to verify timestamp for PSHED.dll

*** ERROR: Module load completed but symbols could not be loaded for PSHED.dll

*************************************************************************

*** ***

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files such as the public OS symbols do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***

*** ***

*************************************************************************

*************************************************************************

*** ***

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files such as the public OS symbols do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***

*** ***

*************************************************************************

*************************************************************************

*** ***

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files such as the public OS symbols do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***

*** ***

*************************************************************************

*************************************************************************

*** ***

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files such as the public OS symbols do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***

*** ***

*************************************************************************

*************************************************************************

*** ***

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files such as the public OS symbols do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***

*** ***

*************************************************************************

*************************************************************************

*** ***

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files such as the public OS symbols do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: nt!_KPRCB ***

*** ***

*************************************************************************

*************************************************************************

*** ***

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files such as the public OS symbols do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: nt!_KPRCB ***

*** ***

*************************************************************************

*************************************************************************

*** ***

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files such as the public OS symbols do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: nt!_KPRCB ***

*** ***

*************************************************************************

Probably caused by : hardware



Followup: MachineOwner

---------



*** Memory manager detected 71657 instances of page corruption, target is likely to have memory corruption.





:)

 

How to fix Whea_Uncorrectable_Error

Hi Alexander,

Thank you for posting in Microsoft Community, we appreciate your interest in Windows 10.

Do let us know the following to assist you better with this issue:

• What is the complete error message along with the error code of this issue?
• Have you made any changes to the operating system prior to this issue?
• From when are you facing this issue?
• What is the make and model of your device?
• Are you able to boot the device to desktop?

I would like to inform that the WHEA_UNCORRECTABLE_ERROR bug check has a value of 0x00000124. 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).

I suggest you to refer to the below article, try the troubleshooting steps mentioned and check if it helps.

Refer: Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR

Hope it helps. If the issue still persist reply to the post with the required information and updated status of this issue for further assistance.

 

Stop Code: WHEA_UNCORRECTABLE_ERROR

Hi,

This might be caused by faulty driver, hardware issues or antivirus software problems. We suggest checking this
article that has steps on how to resolve stop code WHEA_UNCORRECTABLE_ERROR.

Keep us in the loop with the result.

 

how to fix WHEA_UNCORRECTABLE_ERROR (124) ???

Hi,

Thank you for writing to Microsoft Community Forums.

I appreciate your effort on this. However, In order to help you with the appropriate troubleshooting steps, we will need the following details:

• When do you the error message?
  
• Which build version and edition of Windows are you using? To check type:
  winver in the search bar on the Taskbar and hit
  Enter.
  
• What is the make and model of the computer?
  

As per the dump file shared by you, the error seems to be with the Cache of the Intel processor. I suggest you to refer the troubleshooting steps mentioned in the article

How to fix WHEA_UNCORRECTABLE_ERROR and see if that helps.

You may also refer the troubleshooting steps in the article
Troubleshoot blue screen errors and see if that helps.

Please reply with the status of the issue, we will be glad to help you further.

Regards,

Nikhar Khare

Microsoft Community - Moderator