RE: FOR FAQ: Windows XP BSOD

NTDEV
1

This should be in the FAQ too! :slight_smile:
Mat

-----Original Message-----
From: Michal Vodicka [mailto:xxxxx@veridicom.cz.nospam]
Sent: Thursday, July 24, 2003 7:49 PM
To: Windows System Software Developers Interest List
Subject: [ntdev] RE: Windows XP BSOD

Both windbg and DS allow it. Download latest windbg, install it, configure
symbol server, load crash dump and invoke “!analyze -v” command. After about
15 minutes of work you can see the instruction which caused BSOD. Next
analyze can take hours or days depending on problem.

Best regards,

Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]

From: xxxxx@yahoo.com[SMTP:xxxxx@yahoo.com]
Reply To: xxxxx@lists.osr.com
Sent: Friday, July 25, 2003 1:37 AM
To: xxxxx@lists.osr.com
Subject: [ntdev] RE: Windows XP BSOD

I don’t want to do line by line debugging. I just want
to analyze the crash dump and locate the instruction
that is causing BSOD.

You are currently subscribed to ntdev as: xxxxx@guillemot.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

2

“windbg -z DumpFileName”

----- Original Message -----
From: “Tom Pr”
To: “Windows System Software Developers Interest List”
Sent: Friday, July 25, 2003 1:39 AM
Subject: [ntdev] Windows XP BSOD

> All,
>
> What are the tools availabe to analyze a crash dump
> for Windows XP WDM drivers?
>
> Tom
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software
> http://sitebuilder.yahoo.com
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com