Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD occurences


  • Please log in to reply
6 replies to this topic

#1 ase1972

ase1972

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:12:27 AM

Posted 03 May 2009 - 03:08 PM

This was the info I got from running Windows Debugging tool. Any help dechipering this would be helpful


Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18226.amd64fre.vistasp1_gdr.090302-1506
Machine Name:
Kernel base = 0xfffff800`01c5b000 PsLoadedModuleList = 0xfffff800`01e20db0
Debug session time: Sun May 3 09:11:37.511 2009 (GMT-5)
System Uptime: 0 days 10:12:05.121
Loading Kernel Symbols
...............................................................
....................................................Page ae696 not present in the dump file. Type ".hh dbgerr004" for details
....Page a986b not present in the dump file. Type ".hh dbgerr004" for details
........
..............
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffd6018). Type ".hh dbgerr001" for details
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80067a6030, b6092000, 80000135}

Page ae696 not present in the dump file. Type ".hh dbgerr004" for 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 ***
*** ***
*************************************************************************
Page ae696 not present in the dump file. Type ".hh dbgerr004" for details
Page a986b not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 000007ff`fffd6018). Type ".hh dbgerr001" for details
Page ae696 not present in the dump file. Type ".hh dbgerr004" for details
Page a986b not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 000007ff`fffd6018). Type ".hh dbgerr001" for details
Probably caused by : hardware

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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: fffffa80067a6030, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b6092000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000080000135, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------

Page ae696 not present in the dump file. Type ".hh dbgerr004" for 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 ***
*** ***
*************************************************************************
Page ae696 not present in the dump file. Type ".hh dbgerr004" for details
Page a986b not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 000007ff`fffd6018). Type ".hh dbgerr001" for details
Page ae696 not present in the dump file. Type ".hh dbgerr004" for details
Page a986b not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 000007ff`fffd6018). Type ".hh dbgerr001" for details

BUGCHECK_STR: 0x124_AuthenticAMD

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: iexplore.exe

CURRENT_IRQL: f

STACK_TEXT:
fffffa60`005f3958 fffff800`01c1c72a : 00000000`00000124 00000000`00000000 fffffa80`067a6030 00000000`b6092000 : nt!KeBugCheckEx
fffffa60`005f3960 fffff800`01d7e3b3 : 00000000`00000001 00000000`00000001 00000000`00000000 00000000`00000001 : hal!HalBugCheckSystem+0x12e
fffffa60`005f39d0 fffff800`01c1c097 : fffffa60`00000c3e fffffa60`005f3bb0 fffffa60`005f3c30 00000000`00000000 : nt!WheaReportHwError+0x243
fffffa60`005f3a30 fffff800`01cae8b1 : 00000000`00000000 fffffa60`005f3c30 00000000`0310eb50 00000000`00000000 : hal!HalpMcaExceptionHandler+0xf3
fffffa60`005f3a70 fffff800`01cae6f5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x71
fffffa60`005f3bb0 00000000`7172959c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0xf5
00000000`0310e770 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7172959c


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD__UNKNOWN

BUCKET_ID: X64_0x124_AuthenticAMD__UNKNOWN

Followup: MachineOwner
---------



BC AdBot (Login to Remove)

 


#2 ase1972

ase1972
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:12:27 AM

Posted 05 May 2009 - 11:33 AM

Bump...I was wondering did I post the right info or is this wrong topic??

#3 woodyblade

woodyblade

  • Members
  • 670 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Local time:06:27 AM

Posted 05 May 2009 - 03:32 PM

You haven't set the symbols correctly to debug the Minidump, they need to be set so you can debug the Minidump properly, try following the instructions here - http://www.microsoft.com/whdc/devtools/deb...bugstart.mspx#a
You can either download the symbols pack which is over 750MB for a 32bit system or over 640MB for a 64bit system or just set the Online File path which I find is best and is what I have linked you to above, although downloading the symbols pack obviously has it's advantages of being used when you can't access the Internet, it's up to you what option you choose.

Run the debugger again and post this back in your next reply, it seems to point to "hardware" as the possible cause in reference to the "Module Name" and "Image Name", but since it wasn't debugged right this might be wrong so we'll see.

#4 ase1972

ase1972
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:12:27 AM

Posted 05 May 2009 - 03:39 PM

I will do it again tonight thanks for the info....I figured I had done something wrong since it looked like more non-sense then anything else.

I had set the file path before running it but I think the file path I had was for 32bit windows, not the 64bit.

Edited by ase1972, 05 May 2009 - 03:43 PM.


#5 ase1972

ase1972
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:12:27 AM

Posted 05 May 2009 - 11:39 PM

Ok...I DL Current Release version 6.11.1.404 - March 27, 2009 Install 64-bit Native x64 version 6.11.1.404 [15.2 MB]


Then I DL Windows Vista RTM x64 retail symbols, all languages (File size: 196 MB) & Windows Vista SP1 RTM and Windows Server 2008 RTM x64 retail symbols, all languages
Loading Dump File [C:\Windows\MEMORY.DMP]

These are the results I'm still getting.....

Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: C:\Windows\Symbols
Executable search path is:
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18226.amd64fre.vistasp1_gdr.090302-1506
Machine Name:
Kernel base = 0xfffff800`01c18000 PsLoadedModuleList = 0xfffff800`01ddddb0
Debug session time: Tue May 5 18:57:47.896 2009 (GMT-5)
System Uptime: 0 days 2:11:52.037
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
Loading unloaded module list
......
*** ERROR: Symbol file could not be found. Defaulted to export symbols for hal.dll -
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800680b030, b6062000, 135}

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

Page 122e1f not present in the dump file. Type ".hh dbgerr004" for 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: nt!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************


Edited by ase1972, 05 May 2009 - 11:58 PM.


#6 ase1972

ase1972
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:12:27 AM

Posted 06 May 2009 - 03:24 PM

Still not sure what I'm doing wrong with the debugger...I tried using the online version per the instructions and it was not working. So then I DL the files and put them in a symbols fold on my c drive and it still would not work. I guess I will have to do more research on this and figure it out.

#7 woodyblade

woodyblade

  • Members
  • 670 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Local time:06:27 AM

Posted 07 May 2009 - 06:03 PM

Hi,

Sorry I can't help much on this, all I can do is provide you with some links to try and help get the Debugger working right, here are a few from the Microsoft Website that may be useful

This whole section may be useful, Debuggers - http://msdn.microsoft.com/en-us/library/cc267861.aspx

You could try the CDB or NTSD debuggers listed here if you can't get WinDbg working - http://msdn.microsoft.com/en-us/library/cc266318.aspx

Overall it should provide all your answers and ways to start it working, While I reply back I'll tell you the 0x124 error which is in these Minidumps is mostly caused by Faulty Hardware hence the WHEA it mentions (Windows Hardware Error Architecture), but can also be caused by Device Drivers which cause the hardware to throw up a fault.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users