Finding cause of BAD_POOL_CALLER

NTFSD
1

Does anyone have a technique for resolving an intermittent BAD_POOL_CALLER
blue screen? I’ve run my driver with the driver verifier and gflags.exe, but
neither have revealed a problem. I’ve run pooltag to watch for memory leaks.
I’ve run the driver on both the Win2k checked and free builds.

Any ideas here?

Brad Sahr

You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com

2

I just thought that I’d mention that I found the cause of the
BAD_POOL_CALLER blue screen that I was having. The technique that I used was
to enable driver verifier for srv.sys and ntfs.sys. This allowed driver
verifier to catch the fact that my filter was mis-handling a buffer that
srv.sys passed to my filter. So enabling driver verifier for -other-
drivers, in particular drivers that may end up passing you requests, is one
technique for finding the cause of BAD_POOL_CALLER.

One side effect of enabling driver verifier for srv.sys was that the
intermittent blue screen turned into a bugcheck that occurred at the same
place every time. Ah, reproducibility!

Brad

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Brad Sahr
Sent: Friday, February 16, 2001 4:04 PM
To: File Systems Developers
Subject: [ntfsd] Finding cause of BAD_POOL_CALLER

Does anyone have a technique for resolving an intermittent BAD_POOL_CALLER
blue screen? I’ve run my driver with the driver verifier and
gflags.exe, but
neither have revealed a problem. I’ve run pooltag to watch for
memory leaks.
I’ve run the driver on both the Win2k checked and free builds.

Any ideas here?

Brad Sahr

You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com