We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

BSOD: WHEA_UNCORRECTABLE_ERROR (124) minidump attached

Medium Priority
3,156 Views
Last Modified: 2013-12-12
Can someone please look at the code below and see why this is happening.

Thanks a million
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 00000000, Machine Check Exception
Arg2: 862c7d18, Address of the WHEA_ERROR_RECORD structure.
Arg3: f2000040, High order 32-bits of the MCi_STATUS value.
Arg4: 00000800, Low order 32-bits of the MCi_STATUS value.
 
Debugging Details:
------------------
 
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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                ***
***                                                                   ***
*************************************************************************
 
BUGCHECK_STR:  0x124_GenuineIntel
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
 
PROCESS_NAME:  System
 
CURRENT_IRQL:  a
 
STACK_TEXT:  
820eef84 823a6f1f 00000124 00000000 849ae1b8 nt!KeBugCheckEx+0x1e
820eefa0 820cee6a 849ae1b8 849af890 00000001 hal!HalBugCheckSystem+0x37
820eefc0 823a6ede 849af890 849af9a8 820eeff4 nt!WheaReportHwError+0x10c
820eefd0 823a6fff 00000003 849af890 00000000 hal!HalpReportMachineCheck+0x28
820eeff4 823a389f 8014e000 00000000 00000000 hal!HalpMcaExceptionHandler+0xc3
820eeff4 00000000 8014e000 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x77
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: hardware
 
IMAGE_NAME:  hardware
 
DEBUG_FLR_IMAGE_TIMESTAMP:  0
 
FAILURE_BUCKET_ID:  0x124_GenuineIntel__UNKNOWN
 
BUCKET_ID:  0x124_GenuineIntel__UNKNOWN
 
Followup: MachineOwner
---------

Open in new window

Comment
Watch Question

Commented:
vhange the extension to .txt from .dmp and post the dmp file. all drivers up to date?

Author

Commented:
No problem,

Please note that all generic TS steps have been taken.
I am looking for a debugging solution from someone who understands the code in a similar fashion to the following;
https://www.experts-exchange.com/Software/Development/Management_Debug/Debugging/Q_24490615.html 

thanks in advance

Commented:
all drivers up to date? Can you test your harddisc ram and cpu for errors with: http://www.ultimatebootcd.com/ ?

Memory Tests with: Memtest86
CPU Tests with: CPU Burn-in, Mersenne Prime Test & StressCPU
Hard Disk Diagnostic with: your Hard Disk Manufacturers tool. (Drive Fitness Test (IBM/Hitachi) works with most)
If evrything passes, I would try removing all of your component down to just the cpu and ram and see if that helps.

Author

Commented:
Hi,

thanks for your help. I appreciate it but all of the above guidelines have been followed and more.
However, I am looking for assistance in explaining the debug information above rather TS steps in the same fashion as the link I provided above.

thanks
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
what OS ?  vista 64 ?

here it was nvidia :  http://social.technet.microsoft.com/Forums/en-US/w7itprohardware/thread/c7ca0505-2ae1-40da-94b8-3324f1a3c785

This error relates to the hardware, but does not say what hardware...  The sites below can help :
Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR

BSOD:0x124 issue under Vista SP1

BSOD:0x124 - NVIDIA Forums

Author

Commented:
thanks I saw that website

I have done the TS and researched the error using Google already.
Really looking more for a breakdown of the debug code
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
fine with me.

Author

Commented:
thanks for your help though
Consultant
CERTIFIED EXPERT
Commented:
Unlock this solution with a free trial preview.
(No credit card required)
Get Preview
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a free trial preview!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.