Windbg hangs while debugging XPe BSOD

  • Thread starter Thread starter Mark K Vallevand
  • Start date Start date
M

Mark K Vallevand

I've been dragged back into the XPe world to help with a problem we are
seeing on our embedded system.
We have been pretty stable for 2 1/2 years. But, recently we've seen BSOD
on many systems. We have a headless, EWF-enabled Compact Flash system. We
enable debugging and set windbg on the serial port. We can catch the rare,
elusive BSOD in windbg. We can do some basic debugging, but commands like
'!memusage' or (horrors) '.dump /f' will hang windbg. We haven't caught the
problem since I've come back, so I haven't done any 'live' debugging. All I
have is '!analyze -v' from the previous catches.

So, anyone know why windbg might be hanging?

Has anyone been successful getting kernel crash dumps by disabling EWF and
enabling a swapfile? (We're willing to burnup Compact Flash to resolve this
problem.)

Are the components that can be added to the image to help?

--
Regards.
Mark K Vallevand (e-mail address removed)

Beer is living proof that God loves us and wants us to be happy.
- Benjamin Franklin


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you received
this in error, please contact the sender and delete the e-mail and its
attachments from all computers.
 
We can disable EWF and enable a swap file and enable dumps. But no dump
occurs when we force a BSOD.

It looks like there is a "Disk Dump Drivers" component that is missing from
our image.

Anyone know if just adding the diskdump.sys to an existing image will be OK.
It doesn't look like any registry settings or other stuff is in the
component. Just the one file. May be worth a shot.

--
Regards.
Mark K Vallevand (e-mail address removed)

Beer is living proof that God loves us and wants us to be happy.
- Benjamin Franklin


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you received
this in error, please contact the sender and delete the e-mail and its
attachments from all computers.
 
Back
Top