blue screen

[Fred]

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?

[RobD]

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" > wrote in message
...
> 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?

[Johnny Moses]

I ran the debugging program as you suggested but kept gettin the following
errors and wondered what I was doing wrong. Thanks for any help.

Use !analyze -v to get detailed debugging information.
BugCheck B8, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for asusehcd.sys
*** ERROR: Module load completed but symbols could not be loaded for
asusehcd.sys
Probably caused by : asusehcd.sys ( asusehcd+75c0 )
Followup: MachineOwner
---------
kd> .reload
Loading Kernel Symbols
.................................................. ...........................
.................................................. ............
Loading unloaded module list
................
Loading User Symbols
kd> analyze -v
*** WARNING: Unable to verify timestamp for mdmxsdk.sys
*** ERROR: Module load completed but symbols could not be loaded for
mdmxsdk.sys
*** WARNING: Unable to verify timestamp for atintuxx.sys
*** ERROR: Module load completed but symbols could not be loaded for
atintuxx.sys
*** WARNING: Unable to verify timestamp for atinrvxx.sys
*** ERROR: Module load completed but symbols could not be loaded for
atinrvxx.sys
*** WARNING: Unable to verify timestamp for atinxsxx.sys
*** ERROR: Module load completed but symbols could not be loaded for
atinxsxx.sys
*** WARNING: Unable to verify timestamp for winacusb.sys
*** ERROR: Module load completed but symbols could not be loaded for
winacusb.sys
*** WARNING: Unable to verify timestamp for ctac32k.sys
*** ERROR: Module load completed but symbols could not be loaded for
ctac32k.sys
*** WARNING: Unable to verify timestamp for ctsfm2k.sys
*** ERROR: Module load completed but symbols could not be loaded for
ctsfm2k.sys
*** WARNING: Unable to verify timestamp for emupia2k.sys
*** ERROR: Module load completed but symbols could not be loaded for
emupia2k.sys
*** WARNING: Unable to verify timestamp for ha10kx2k.sys
*** ERROR: Module load completed but symbols could not be loaded for
ha10kx2k.sys
*** WARNING: Unable to verify timestamp for hap16v2k.sys



"RobD" > wrote in message
...
> 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" > wrote in message
> ...
> > 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?
>
>