Re: x64 2K3 R2 BSODs when FC Tape Library is Rebooted
  Home FAQ Contact Sign in
microsoft.public.storage only
 
Advanced search
POPULAR GROUPS

more...

microsoft.public.storage Profile…
 Up
Re: x64 2K3 R2 BSODs when FC Tape Library is Rebooted         


Author: Eric
Date: Jun 13, 2007 08:37

I uninstalled SANSurfer, turned on driver verifier for the drivers you
listed, and rebooted. Then I rebooted the tape library which in turn BSODs
my hosts as expected. However, I got a 0xC5 BSOD on one host and a 0xD1 BSOD
on the other. Below is the bugcheck analysis on the kernel dump of the host
that got the 0xC5 after driver verifier was turned on. I'm thoroughly lost
at this point. Any suggestions now?

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is
caused by drivers that have corrupted the system pool. Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: 00000000000b5430, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff800011abd85, address which referenced memory

Debugging Details:
------------------
Show full article (19.58Kb)
no comments

RELATED THREADS
SubjectArticles qty Group
Unattended (Winnt.sif) being ignored on 2k3 x64 CD install but works on 2k3 x86 CDmicrosoft.public.windows.server.general ·