Elliott Back's Blog - Latest Comments in How To Analyze Windows XP BSOD Minidump Files

Re: How To Analyze Windows XP BSOD Minidump Files

Mitch — Fri, 23 Jan 2009 19:23:23 -0000

This is what it says in my analysis:

READ_ADDRESS: e1e5c000

CURRENT_IRQL: 2

FAULTING_IP:
+fffffffff1f3ed50
f1f3ed50 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from f1f402a8 to f1f3ed50

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
f7c37d64 f1f402a8 804e48b0 ff676980 ffffffff 0xf1f3ed50
f7c37d7c 804e23b5 85187860 00000000 853c6b30 0xf1f402a8
f7c37dac 80575723 85187860 00000000 00000000 nt!ExpWorkerThread+0xef
f7c37ddc 804ec6d9 804e22f1 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: 0xD1_ANALYSIS_INCONCLUSIVE

BUCKET_ID: 0xD1_ANALYSIS_INCONCLUSIVE

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

Re: How To Analyze Windows XP BSOD Minidump Files

Mitch — Fri, 23 Jan 2009 19:18:43 -0000

My computer has the blue screen of death constantly and only since i found this website did i find any help. But i follow all your directions andwhere the juicy information is kept it just says ANALYSIS_INCONCLUSIVE.
I really need some help ith my computer cause whenever i install something it crashes and i have 67 minidump files - 67 times my computer has crashed without me knowing why... please help

Re: How To Analyze Windows XP BSOD Minidump Files

Brian — Mon, 19 Jan 2009 10:25:01 -0000

you rock man, this is the coolest trick in the book. I love reading these logs and seeing how jacked up MS really is :)

Re: How To Analyze Windows XP BSOD Minidump Files

John — Wed, 10 Dec 2008 01:03:48 -0000

Good Information, exactly what I was looking for!

Re: How To Analyze Windows XP BSOD Minidump Files

jim — Fri, 28 Nov 2008 21:24:13 -0000

Mark,
I couldn't agree more, better than the latin on MS page!

Re: How To Analyze Windows XP BSOD Minidump Files

Mark — Sun, 05 Oct 2008 03:55:54 -0000

Useful and straightforward info, unlike the twaddle from the Microsoft "Support" site. Thanks!

Re: How To Analyze Windows XP BSOD Minidump Files

Elliott Back — Sun, 03 Aug 2008 17:51:24 -0000

Oops, let me fix that...

Re: How To Analyze Windows XP BSOD Minidump Files

Christian — Sun, 03 Aug 2008 17:19:58 -0000

You link for WinDbg is linking to Windows Installer 1.1 and not the debugging tool.

The correct link for debugging tool is:
http://msdl.microsoft.com/download/symbols/debu...

Re: How To Analyze Windows XP BSOD Minidump Files

Oigen — Thu, 17 Jul 2008 12:50:05 -0000

Apparently my bsod woes may be caused by ntoskrnl.exe
Would replacing it be of any use?

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {177, 1c, 0, 804de637}

Probably caused by : ntoskrnl.exe ( nt!KiTrap0C+107 )

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!KiTrap0C+107

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 45e54690

FAILURE_BUCKET_ID: 0xA_nt!KiTrap0C+107

BUCKET_ID: 0xA_nt!KiTrap0C+107