Re: blue screen
From: RobD (robden12_at_adelphia.NOSPAM.net)
Date: 02/11/04
- Next message: Frank: "Re: USB 2.0 External Hard Drive Problem"
- Previous message: Frank: "Re: monitor installing"
- In reply to: Fred: "blue screen"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 10 Feb 2004 21:29:53 -0800
If you want to stare at the BSOD longer, you can disable auto restart (My
Computer->Properties->Advanced->Startup and Recovery.Settings). The first
few lines will tell you most of what you need to know. The best way to see
what is wrong is to run windbg on the dump file. A post-mortem debug is
involved and requires some knowledge of Windows (WDM, kernel, etc.) and
possibly the driver in question. But, here's a simple check anyone can do
to get an idea what has happened.
1. download/install windbg from Microsoft Debugging Tools
(http://www.microsoft.com/whdc/ddk/debugging/default.mspx)
2. create a directory for downloaded symbols (ex.: c:\websymbols)
3. double-click the mini-dump file located in c:\Windows\Minidump
(pick the current timestamp)
4. close assembly window. Also check "Windows->auto arrange" and "arrange
all windows."
5. under "File->Symbol File Path..." enter the symbol server path:
srv*c:\websymbols*http://msdl.microsoft.com/download/symbols
(substitute the symbols directory you created between the asterisks).
6. from command window (single-line entry near bottom), enter "!reload" to
reload symbols.
7. enter "!analyze -v" to run windbg analysis.
This will display a quick analysis of which driver crashed and the most
probable cause. If the symbols loaded correctly, you should see a
reasonable backtrace and register contents at the time of the crash. A lot
more info can be obtained from a dump file but it's too involved to describe
here. However, from the simple windbg analysis command, you will know more
about the problem than you would with the BSOD. For more info read the
online help manual in windbg.
- Robert -
"Fred" <anonymous@discussions.microsoft.com> wrote in message
news:e2ee01c3f005$0d924ba0$a501280a@phx.gbl...
> I'm getting a lot of blue screen errors at statup lately.
> The response to the error report says it's a devise
> driver. I have no idea which device driver it could be
> since I have not installed any new devices at all. So it
> must be software (or an original device which has gone
> bad (or its driver)). Software I do have a lot, no way to
> know which is causing this.
>
> Can the blue screen be made to last longer so that it can
> be read?
>
> How can I go about figuring what is causing the problem?
- Next message: Frank: "Re: USB 2.0 External Hard Drive Problem"
- Previous message: Frank: "Re: monitor installing"
- In reply to: Fred: "blue screen"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
