Microsoft KB Archive/229903

From BetaArchive Wiki
Knowledge Base

Partial List of Possible Error Codes with Driver Verifier

Article ID: 229903

Article Last Modified on 9/12/2007


  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Professional Edition
  • Microsoft Windows 2000 Datacenter Server

This article was previously published under Q229903


Driver Verifier is designed to test kernel-mode drivers. The tool may issue the following bug checks if it identifies a problem with the selected driver during testing. Driver Verifier performs extensive tests and checks the target drivers. If the driver uses memory at an improper IRQL, if the driver improperly calls or releases spin locks and memory allocations, or if the driver frees memory pool without first removing any timers, Driver Verifier issues the appropriate bug checks from the list below.


  • Bug Check 0x0A IRQL_NOT_LESS_OR_EQUAL, defined as 0x0A, signals that the driver accessed paged memory at DISPATCH_LEVEL or above.
  • Bug Check 0xBE ATTEMPTED_WRITE_TO_READONLY_MEMORY, defined as 0xBE, is issued if a driver attempts to write to a read-only memory segment.
  • Bug Check 0xC1 SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION, defined as 0xC1, signals that the driver wrote to an invalid section of the special memory pool. Typically, the current thread's backtrace will reveal the source of the error.
  • Bug Check 0xC4 DRIVER_VERIFIER_DETECTED_VIOLATION, defined as 0xC4, is the general bug check code for fatal errors found by Driver Verifier. The following parameters are those passed to KeBugCheckEx and displayed on the blue screen.
  • Bug Check 0xC5 DRIVER_CORRUPTED_POOL, defined as 0xC5, indicates that the system attempted to access invalid memory at a process IRQL that was too high.
  • Bug Check 0xC6 DRIVER_CAUGHT_MODIFYING_FREED_POOL, defined as 0xC6, indicates that the driver attempted to write to a freed memory pool.
  • Bug Check 0xC7 TIMER_OR_DPC_INVALID, defined as 0xC7, is issued if a kernel timer or DPC is found somewhere in memory where it is not permitted. This condition is usually caused by a driver not canceling the timer or DPC before freeing the memory in which they reside.
  • Bug Check 0xC9 DRIVER_VERIFIER_IOMANAGER_VIOLATION, defined as 0xC9, is the bug check code for all I/O Driver Verifier violations.
  • Bug Check 0x50 PAGE_FAULT_IN_NONPAGED_AREA, defined as 0x50, is issued if invalid system memory is referenced.

For more information please see the Windows Device Driver Kit (DDK).

Additional query words: blue screen bluescreen

Keywords: kbinfo KB229903