>Not as far as I can tell. This particular error occured whilst loading
the
drivers during a warm boot, running the free version of the kernel,
with driver
verifier enabled. I was testing something else entirely, and I just
happened to
boot with the /debug switch and the debugger connected, but I hadn’t
actually
done anything with the debugger or set any breakpoints since power on
in the
morning.
Just out of curiosity, have you had this bugcheck occur while NOT using
driver verifier?
Another “long shot” I’ve been tempted to consider is whether switching
IRQ level
might unmask some sort of pending error or interrupt.
The only other thing I can think of is to check the actual section
attribute bits in the driver image to make sure the section with your
function is actually marked as non-pageable. The map file tells us your
function is in a section named “.text” but it doesn’t tell us whether
the section is marked pageable or not. Is there something like DUMPBIN
for drivers that can tell you this easily?
Chuck