What you need to do it get a dump of the exception.
To setup the system to create a dump in these condition: (you may need to
start in safe mode to set this up):
- start System applet in control panel.
- go to the Advanced tab.
- Click Startup and Recovery.
- Select Small memory dump (64KB).
- Click OK and restart the computer.
Now when an unhandled exception (aka stop screen, aka blue screen, aka BSOD)
occurs you will get a dump. You can see what caused the dump using the
debugging tools for Windows. You can download the debugging tools at
http://www.microsoft.com/whdc/ddk/debugging/installx86.mspx (select the
Install 32 bit version link).
To look at the dump:
- Start Windbg (under the Debugging Tools for Windows),
- click File,
- Open Dump,
- navigate to your mini dump file and click Open. The dump will open.
- the command prompt will come up at the bottom. I'd recommend you set the
symbol path, force a symbol reload and then do analyze (using the following
command):
..sympath srv*
http://msdl.microsoft.com/download/symbols
..reload
!analyze -v
Note that the .reload command may take a little while to complete. You know
it's down when the 0:kd prompt is back.
The output of the analyze command should give you a driver name. If you
unsure how to read the output post it here (look under Edit for save command
output) and someone will help you.
Good luck.
