Yup, the obvious settings are all there.
-----Original Message-----
From: Phung, Tri T [mailto:xxxxx@unisys.com]
Sent: Wednesday, September 03, 2003 6:54 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Sometimes I just can’t get crash dump files to
gener ate…
Did you verify that the “Write Debugging Information” option in the
“Startup
and Recovery” popup is set to “Kernel Memory Dump” or “Complete Memory
Dump”? The “Startup and Recovery” popup can be brought up by clicking
the
“Startup and Recovery” button in the “Advanced” tap of the System
Properties
screen.
Tri
-----Original Message-----
From: Nate Bushman [mailto:xxxxx@powerquest.com]
Sent: Tuesday, September 02, 2003 6:29 PM
To: Kernel Debugging Interest List
Subject: [windbg] Sometimes I just can’t get crash dump files to
generate…
Every once in a while I run across a customer who experiences a blue
screen but just can’t seem to generate a crash dump file. I have them
make sure that their page file is on their boot volume, and that their
page file size is greater than the amount of installed RAM, but still no
crash dump file is generated during the BSOD.
What am I missing here? What are some of the other requirements for
successful dump file generation?
I just heard a (likely distorted) third-hand rumor, supposedly sourced
at Microsoft, that crash dump files will never be generated for certain
bug check codes. Can this be true? If so, why, and for which codes?
Nate
You are currently subscribed to windbg as: xxxxx@unisys.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
You are currently subscribed to windbg as: xxxxx@powerquest.com
To unsubscribe send a blank email to xxxxx@lists.osr.com