Hi All,
I am getting a customer dump with a:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2)
MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18267.amd64fre.vistasp2_gdr.100608-0458
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: 0000000000000000, Machine Check Exception
Arg2: fffffa800bd90030, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b6000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000200001, Low order 32-bits of the MCi_STATUS value.
II found a thread that seems to indicate it is possible to further
identify the error from the BugCheck code if someone happens to know
this one. Probably someone from Microsoft.
It is also interesting that it seems in 2005, the pdb files knew about
a _WHEA_ERROR_RECORD, but now have forgotten about it.
Although I’m not a developer, I do read a lot of memory dump analysis’. I do user level post-mortem debugging on online forums - to help the users who have BSOD issues.
As such, I see a lot of STOP 0x124 errors - which replaced the STOP 0x9C errors around the time that Vista came out.
STOP 0x124 errors are hardware errors - but they come in a couple of different types:
hardware failure
hardware connection issues
compatibility issues
I also suspect, but cannot find documentation to support this, that corrupted drivers can cause this error also.
Analysis of the STOP 0x124 error is way, way beyond my skill level. I’ve read the Intel documentation about this error anyways, and it seems to me that an analysis wouldn’t point to a specific cause in most cases.
Finally, not long ago forced a huge video card into a Dell desktop (it barely fit). Naturally, as soon as I booted it up I got a STOP 0x124 error. Reseating the card a bit more carefully “fixed” the error.