Go Back   Tech Support Forum > Microsoft Support > BSOD, App Crashes And Hangs

User Tag List

windows vista bsod STOP error (error posted)...any thoughts?

This is a discussion on windows vista bsod STOP error (error posted)...any thoughts? within the BSOD, App Crashes And Hangs forums, part of the Tech Support Forum category. Hi guys, I was using my computer today and for the first time ever (had computer for 10 months) I


Closed Thread
 
Thread Tools Search this Thread
Old 08-06-2008, 12:38 PM   #1
Guest
 
Join Date: Aug 2008
Posts: 1
OS:



Hi guys,

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

DEBUG_FLR_IMAGE_TIMESTAMP: 0

WHEA_ERROR_RECORD: !errrec ffffffff849784e0

BUGCHECK_STR: 0x124_GenuineIntel

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

STACK_TEXT:
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


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
ajcool123 is offline  
Sponsored Links
Advertisement
 
Old 08-06-2008, 02:35 PM   #2
Administrator
Manager, Microsoft Support
Acting Manager, Security
BSOD Kernel Dump Expert
Microsoft Windows Insider MVP
 
jcgriff2's Avatar

Microsoft Most Valuable Professional
 
Join Date: Sep 2007
Location: New Jersey Shore
Posts: 34,336
OS: Windows 10, 8.1 + Windbg :)



Quote:
Originally Posted by ajcool123 View Post
Hi guys,

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

DEBUG_FLR_IMAGE_TIMESTAMP: 0

WHEA_ERROR_RECORD: !errrec ffffffff849784e0

BUGCHECK_STR: 0x124_GenuineIntel

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

STACK_TEXT:
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


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
Hi. . .

A bugcheck of 0x00000124 = 0x124 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 = 0x81c00000, 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 -
Code:
SRV*c:\symbols*https://msdl.microsoft.com/download/symbols
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. . .

jcgriff2

.
jcgriff2 is offline  
Old 08-08-2008, 10:52 PM   #3
Guest
 
Join Date: May 2008
Posts: 123
OS:



Dump the error record like the debugger spew says.

FYI a simple ".symfix" will patch up the symbol situation for the session. You need to issue a ".reload" regardless of how you set the symbol path in order to run those commands.
bdesmondMVP is offline  
Closed Thread

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is on
Smilies are on
[IMG] code is on
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off


Post a Question


» Site Navigation
 > FAQ
  > 10.0.0.2
Powered by vBadvanced CMPS v3.2.3


All times are GMT -7. The time now is 01:52 PM.


Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2020, vBulletin Solutions, Inc.
vBulletin Security provided by vBSecurity v2.2.2 (Pro) - vBulletin Mods & Addons Copyright © 2020 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.1.0 (Pro) - vBulletin Mods & Addons Copyright © 2020 DragonByte Technologies Ltd.
Copyright 2001 - 2018, Tech Support Forum

Windows 10 - Windows 7 - Windows XP - Windows Vista - Trojan Removal - Spyware Removal - Virus Removal - Networking - Security - Top Web Hosts