Error Stop 0x000000C5 (0x6e496D4D 0x0000000002 0x000000001 0x805529EC) DRIVER_CORRUPTED_EXPOOL secondary slave drive
Posted on 2005-03-15
Error Stop 0x000000C5 (0x6e496D4D 0x0000000002 0x000000001 0x805529EC) DRIVER_CORRUPTED_EXPOOL
A customer brought in a hard drive that, no matter what system I put it on, slave, master, USB attached, whatever,
it brings down the system with the above hard stop. The customer wants me to get the data off the drive.
The error stop message goes on to say that one can try to stop caching or shadowing memory options. I haven't
seen any such options in bios setup for the systems I've tried attaching this drive to.
I’m trying to understand the mechanism by which a secondary hard drive could cause such a stop at system startup,
and if there’s any way on any system to get around it at least long enough to get the data off it,
even using something like GetDataBack over a network link.
Searches indicate that the problem is supposedly caused by a bad driver. But I would think that a bad driver would
only apply to the drivers defined on the system being booted up. In this case the drive is not being booted. It’s a slave drive.