if i may you may want to look at your system settings, sorry i can't name the exact dialog right now but the windows startup and error recovery stuff has options on what kind of crash dump it creates. some systems this may be set to none.
turn it on and there are tools that can read the dump file and tell a msft tech all kinds of details about what had loaded and what was crashing.
you can get the tools and learn how to read the crash dump log or you can start a support case with msft and have them read the log and tell you what seems to be the root cause.
also sometimes the bsod screen names the most probable files .... not all the time but often you will see something like
fault at 0x004774657848 in nV[something].sys
you may also have a code like x014 or 0x1E
the short code is "what kind of error" like hardware interupt, invalid memory address etc....
the fault at is a memory address and the in [name] is the driver or system component
some times the os object may take the hit and the driver is 2-3 steps back in the stack trace of the crash.
like say if it was xp you might see:
USER
GDI
NV_____.sys
maning that NV puked on GDI it then passed the error to USER and user said "I give up"
hope that helps..
ASP.NET: Presenting in Europe Next Week
WindowsClient: You know your post rate has gone down...
Silverlight: Geek Profiles – Scott Guthrie
