From a similar question I asked last October, answered by Molly Brown:
This verifier code is new to Server 2003 SP1. It indicates that your
driver has pool still allocated when your driver unloads.
Parameter 1 is the verifier code (0x62)
Parameter 2 is the pointer to the driver name string
Parameter 3 is an internal verifier structure
Parameter 4 is the total number of non-freed paged and non-paged pool
allocations for your driver
Also, to get more useful information, try:
!verifier 0x3
HTH,
Ken
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ivan Bublikov
Sent: Monday, November 14, 2005 7:54 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Can’t find doc for subclass 62 of
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this
driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA
will
be among the most commonly seen crashes.
Parameter 1 = 0x1000 … 0x1020 - deadlock verifier error codes.
Typically the code is 0x1001 (deadlock detected) and you can
issue a ‘!deadlock’ KD command to get more information.
Arguments:
Arg1: 0000000000000062, subclass of driver violation.
Arg2: fffffadffabce980
Arg3: fffffadffabce8e0
Arg4: 0000000000000001
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@comcast.net
To unsubscribe send a blank email to xxxxx@lists.osr.com