to further identify what driver is causing the issue you
can try adding the following registry key:
PROCESS_HAS_LOCKED_PAGES (76)
Caused by a driver not cleaning up completely after an
I/O. Set
HKLM\SYSTEM\CurrentControlSet\Control\Session
Manager\Memory Management\TrackLockedPages
to a DWORD 1 value and reboot. Then the system will save
stack traces
so the guilty driver can be identified. There is no other
way to find out
which driver is neglecting to clean up the I/Os. When you
enable this flag,
if the driver commits the error again you will see a
different
bugcheck - DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS (0xCB) -
which can identify the
offending driver(s).
This addition has proven to be very useful for trouble
shooting ambigious BSODs like you mention.
>-----Original Message-----
>I got a new 256meg USB stick, which works fine on most
>PCs. When I plug it into any of the 3 work Dell
>Workstations (running XP Pro) and try to "Safely remove"
>or just pull it out, I get a Blue Screen with
>Bad_Pool_Caller. There's no drivers for it because XP
>(pro & home) happily recognises it and works fine with
it -
> until I try to remove it. Dell don't know, the USB
stick
>manufacturer don't know either!
>.
>
|