Stop 0x000000C4 analysis   

Not sure if this isthe right group, but...

Hi, I've been getting, seemingly random, DRIVER_CORRUPTED_EXPOOL Blue 
Screens on a number of machines with Windows 2000 SP4. Following this clue, 
I've enabled checking for pool overruns, and now get a Stop 0x000000C4  blue 
screen on boot.

The full details are:

"Stop 0x000000C4 (0x00000060,0x00000000,0x0000300,0x00000001)
A device driver attempting to corrupt the system has been caught. The faulty 
driver currently on the kernel stack must be replaced with a working version."

Picking that info apart:
Para 1 (0x00000060) - The driver is unloading without first freeing its pool 
allocations.
Para 2 (0x00000000) - paged pool bytes
Para 3 (0x00003000) - nonpaged pool bytes
Para 4 (0x00000001) - Total allocations not freed

No memory dump occurs, regardless of settings.

Boot logging shows the last driver loaded was audio related, disabling all 
audo devices doesn't help.

Where the blue screen states "The faulty driver currently on the kernel 
stack must be replaced with a working version", how can I find which driver 
is the cause?

date: Thu, 2 Oct 2008 17:14:01 -0700   author:   PBHR