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

Analyze and Help with Blue screen.


  • Please log in to reply
1 reply to this topic

#1 Haas360

Haas360

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:04:08 AM

Posted 26 January 2012 - 03:48 AM

Alright so i am new to this place but not to computers. I want to learn how to analyze blue screens with windows debug. here is a post of what blue screens i have been getting. Whats wrong? and how did you get that outa this!?

Simple
Thanks!
Braiden



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 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0385e000 PsLoadedModuleList = 0xfffff800`03aa3670
Debug session time: Wed Jan 25 10:40:10.087 2012 (GMT-7)
System Uptime: 0 days 10:08:36.899
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols

Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa801042b028, be200000, 5110a}

*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : hardware

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

3: 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: fffffa801042b028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000005110a, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR: 0x124_GenuineIntel

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

STACK_TEXT:
fffff880`033dfb58 fffff800`03827a3b : 00000000`00000124 00000000`00000000 fffffa80`1042b028 00000000`be200000 : nt!KeBugCheckEx
fffff880`033dfb60 fffff800`039eb513 : 00000000`00000001 fffffa80`102bac60 00000000`00000000 fffffa80`102bacb0 : hal!HalBugCheckSystem+0x1e3
fffff880`033dfba0 fffff800`03827700 : 00000000`00000728 fffffa80`102bac60 fffff880`033dff30 fffff880`033dff00 : nt!WheaReportHwError+0x263
fffff880`033dfc00 fffff800`03827052 : fffffa80`102bac60 fffff880`033dff30 fffffa80`102bac60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`033dfd50 fffff800`03826f0d : 00000000`00000008 00000000`00000001 fffff880`033dffb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`033dfd90 fffff800`0381ae88 : 00000000`00000001 fffff880`033d7180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`033dfdc0 fffff800`038d952c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`033dfdf0 fffff800`038d9393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`033dff30 fffff880`030a6c61 : fffff800`038e44a9 00000000`00328cdd fffffa80`0d5192d0 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`033ffb58 fffff800`038e44a9 : 00000000`00328cdd fffffa80`0d5192d0 00000000`00000000 00000000`00000000 : intelppm+0x2c61
fffff880`033ffb60 fffff800`038d293c : fffff880`033d7180 fffff880`00000001 00000000`00000001 fffff800`00000000 : nt!PoIdle+0x52a
fffff880`033ffc40 00000000`00000000 : fffff880`03400000 fffff880`033fa000 fffff880`033ffc00 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE

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

3: 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: fffffa801042b028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000005110a, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR: 0x124_GenuineIntel

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

STACK_TEXT:
fffff880`033dfb58 fffff800`03827a3b : 00000000`00000124 00000000`00000000 fffffa80`1042b028 00000000`be200000 : nt!KeBugCheckEx
fffff880`033dfb60 fffff800`039eb513 : 00000000`00000001 fffffa80`102bac60 00000000`00000000 fffffa80`102bacb0 : hal!HalBugCheckSystem+0x1e3
fffff880`033dfba0 fffff800`03827700 : 00000000`00000728 fffffa80`102bac60 fffff880`033dff30 fffff880`033dff00 : nt!WheaReportHwError+0x263
fffff880`033dfc00 fffff800`03827052 : fffffa80`102bac60 fffff880`033dff30 fffffa80`102bac60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`033dfd50 fffff800`03826f0d : 00000000`00000008 00000000`00000001 fffff880`033dffb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`033dfd90 fffff800`0381ae88 : 00000000`00000001 fffff880`033d7180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`033dfdc0 fffff800`038d952c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`033dfdf0 fffff800`038d9393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`033dff30 fffff880`030a6c61 : fffff800`038e44a9 00000000`00328cdd fffffa80`0d5192d0 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`033ffb58 fffff800`038e44a9 : 00000000`00328cdd fffffa80`0d5192d0 00000000`00000000 00000000`00000000 : intelppm+0x2c61
fffff880`033ffb60 fffff800`038d293c : fffff880`033d7180 fffff880`00000001 00000000`00000001 fffff800`00000000 : nt!PoIdle+0x52a
fffff880`033ffc40 00000000`00000000 : fffff880`03400000 fffff880`033fa000 fffff880`033ffc00 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE

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

BC AdBot (Login to Remove)

 


#2 Allan

Allan

  • BC Advisor
  • 8,575 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:07:08 AM

Posted 26 January 2012 - 08:14 AM

Just for the clarity and length of this thread, please delete the bugcheck "log" in your above post and do the following instead in your NEXT post (below this one):

Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users