Originally Posted by ajcool123
I was using my computer today and for the first time ever (had computer for 10 months) I had a BSOD. Here is what I found. Anyone have any thoughts?
FAULTING_MODULE: 81c00000 nt
WHEA_ERROR_RECORD: !errrec ffffffff849784e0
WARNING: Stack unwind information not available. Following frames may be wrong.
81ceef84 81fa6f1f 00000124 00000000 849b3578 nt+0xd8681
81ceefa0 81cced6a 849b3578 84ac2de8 00000001 hal+0x5f1f
81ceefc0 81fa6ede 84ac2de8 84ac2f00 81ceeff4 nt+0xced6a
81ceefd0 81fa6fff 00000003 84ac2de8 00000000 hal+0x5ede
81ceeff4 81fa389f 8014a000 00000000 00000000 hal+0x5fff
00000000 00000000 00000000 00000000 00000000 hal+0x289f
Hi. . .
A bugcheck of 0x00000124
indicates that a fatal hardware error has occurred. The reference to WHEA is Windows Hardware Error Architecture. There is an event log for WHEA, under Applications and Services\Microsoft\Windows\Kernel-WHEA. It usually contains entries stating that WHEA was successfully initialized, that x# error sources are active and the record format of WHEA. I have never seen any other entries in it besides ones like these.
In the STACK_TEXT above, 81c00000 nt
, the starting memory address for nt
which is the Microsoft Kernel and system module ntkrnlmp.exe
. It is listed as the probable cause because of its expansive memory address range and whatever happened occurred within that memory range. hal
= Hardware Abstraction Layer.
I suggest that you look in the Event Viewer, the Device Manager, WERCON (Windows Problem Reports and Solutions) and also PERFMON (Reliability and Performance Monitor - look at both).
As for the graphical interface dbugger - Windbg - use the symbol path -
Then at kd>
enter !analyze -v;r;kv;lmtn
This should resolve the symbol errors and provide you with additional information. Please post the full STOP error code (bugcheck) and the four parameters found in the brackets.
Regards. . .