(several WinDbg analyses of crash dumps appended below)
Increasingly (now every few days) I'm getting "stop error" blue screen crashes when I do one of the following:
- removing a USB drive (thumb or larger) either by telling the system to safely unmount it or by just pulling it out
- putting the system to sleep (suspend) or waking it up from suspension (shut down / startup don't seem to crash)
It doesn't usually blue screen until I do one of the above (in which case it blue screens about 1/3 of the time), but it CAN blue screen at other times. The first debugger crash info attached below was from a crash a few minutes ago that happened when I just went to the Start menu and selected "My Computer". Bang! BSOD.
-- Another hint: the little green arrow system tray icon that I use to tell it to safely unmount a USB device started disappearing occasionally at the same time this problem started. I would want to safely unmount a thumb drive, look for the icon in the tray, and it wouldn't be there. No way to tell it to safely unmount. At other times, it might be there, but wouldn't show all devices. Very often when it is there and I tell it to unmount a device, I get an immediate BSOD, but (naturally) it doesn't always happen. If the device list it shows is incomplete, for example only showing one of the two USB drives that are plugged in, then telling it to unmount something does seem to reliably cause a blue screen crash. It seems to blue screen less often if I just pluck the thumb drives off without unmounting them properly (something I never did before the problems started), though that also sometimes causes a blue screen a couple of seconds after I pluck out a drive.
It doesn't matter what app I'm running. It has even happened when it was just sitting there (not being suspended or revived, no drives being removed, me not asking it to poll for system information, me not even touching the keyboard) but that is rare.
-- It is almost always associated with an obvious need to start up, shut down, unmount, or look for hardware.
-- If it's a case I can fix by somehow replacing a driver, that would be great, but I have no idea which one to replace. I can't think of anything I might have installed just prior to this problem beginning.
-- I have attached windbg analyses of a few recent crash dumps (there were more crashes in between these; these are just a sampling).
-- Most of the analyses seem to claim:
Could not read faulting driver name
Probably caused by : ntkrnlpa.exe ( nt!ExAllocatePoolWithTag+7af )
-- But #2 below is an exception. It claims:
Unable to load image drvmcdb.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for drvmcdb.sys
*** ERROR: Module load completed but symbols could not be loaded for drvmcdb.sys
Probably caused by : drvmcdb.sys ( drvmcdb+6378 )
Any ideas would be appreciated.
EDIT: Removed debug reports (unwieldy, incomplete) because BlueScreenView is better tool most used in this forum ~ Hamluis.
Edited by hamluis, 04 March 2011 - 07:11 AM.