Microsoft KB Archive/298690

From BetaArchive Wiki
Knowledge Base


Error Message When You Use the Driver Verifier Utility to Monitor a Driver

Article ID: 298690

Article Last Modified on 9/12/2007



APPLIES TO

  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Service Pack 1
  • Microsoft Windows 2000 Service Pack 2
  • Microsoft Windows 2000 Service Pack 1
  • Microsoft Windows 2000 Service Pack 2
  • the operating system: Microsoft Windows 2000



This article was previously published under Q298690


SYMPTOMS

When you use the Driver Verifier utility (Verifer.exe) to monitor a driver or drivers with the Special Pool option enabled, your computer may stop responding (hang), and you may receive the following error message:

STOP 0x000000C4 (0x00000038 0x00000000 0x00000000 0xbe68dfc8)

DRIVER_VERIFIER_DETECTED_VIOLATION


Parameter 1 = 0x00000038 - a resource is being released but APCs are not disabled.
Parameter 2 = current IRQL
Parameter 3 = thread APC disable count

Parameter 4 = resource

CAUSE

This issue is caused by the driver that is being monitored.

RESOLUTION

To resolve this issue, contact the manufacturer of the third-party driver to inquire about the availability of an updated driver that resolves this issue. Note the value of Parameter 2 in the error text. If Parameter 2 is 0x00000000 (Passive IRQL), there is a problem with the driver that made the call. Contact the manufacturer of the driver to resolve the problem. If Parameter 2 is 0x00000002 (DPC IRQL), the driver's process thread was running in the context of a User mode thread. DPC level is not permitted in the context of a User mode thread. Contact the manufacturer of the driver to resolve the problem.

MORE INFORMATION

For additional information about the Driver Verifier utility, click the following article numbers to view the articles in the Microsoft Knowledge Base:

244617 How to Use Driver Verifier to Troubleshoot Device Drivers in Windows 2000


229903 Partial List of Possible Error Codes with Driver Verifier


251233 Things to Consider Before You Enable Driver Verifier Manager on Production Servers


Keywords: kberrmsg kbbug kbprb KB298690