Robert Pendell wrote:
> Using windbg to identify the culprit helps.
Yes, anything else is pointless speculation; these kinds of crashes are way
too esoteric to waste time guessing at. Enable full crash dumps in the system
preferences, install windbg, trigger the crash, then (after rebooting) open
memory.dmp in windbg; the output of "analyze -v" should tell you at once which
driver was on top of the stack and so should be suspected. If you're lucky,
you'll see the driver name on the BSoD and won't have to go to such lengths,
but if it's a level or two up the stack when the crash happens, you'll need a
debugger to show you the relevant module name.
cheers,
DaveK
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
