Hi folks,
More info on a bugcheck that had me confused…
After some further investigation, which incidentally occurred because I was
setting up the dev environment for another guy, and he didn’t initially have
verifier enabled,
I can confirm that this problem only occurs with driver verifier running.
Additionally, we now have a machine where if you load 10 or so drivers using
this library, with the verifier running, it’ll bugcheck just about every time.
If I get the chance, I’ll try and find out which verifier settings cause the
problem.
On reflection, the only time I’ve seen this bugcheck is when the verifier is
running.
MH.
-----Original Message-----
From: “Chuck Batson” smtp:xxxxx
Sent: 13 December 2004 14:49
To: “Windows System Software Devs Interest List” smtp:xxxxx
Subject: Re:(ntdev) RE:(ntdev) (ntdev) Utterly mystified by this bugc
>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
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@snellwilcox.com To
unsubscribe send a blank email to xxxxx@lists.osr.com
This email and any attachments is confidential, may be legally privileged and is intended for the use of the addressee only. If you are not the intended recipient, please note that any use, disclosure, printing or copying of this email is strictly prohibited and may be unlawful. If received in error, please delete this email and any attachments and confirm this to the sender.</smtp:xxxxx></smtp:xxxxx>