ErrorVault.com

Blue Screen Errors


Error Troubleshooting > Blue Screen Errors


1. DATA_BUS_ERROR Error 0x2E The DATA_BUS_ERROR bug check has a value of 0x0000002E. This typically indicates that a parity error in system memory has been detected.
2. DATA_COHERENCY_EXCEPTION Error 0x55 The DATA_COHERENCY_EXCEPTION bug check has a value of 0x00000055.
3. DEREF_UNKNOWN_LOGON_SESSION Error 0x46 The DEREF_UNKNOWN_LOGON_SESSION bug check has a value of 0x00000046.
4. DEVICE_QUEUE_NOT_BUSY Error 0x2 The DEVICE_QUEUE_NOT_BUSY bug check has a value of 0x00000002.
5. DEVICE_REFERENCE_COUNT_NOT_ZERO Error 0x36 The DEVICE_REFERENCE_COUNT_NOT_ZERO bug check has a value of 0x00000036. This indicates that a driver attempted to delete a device object that still had a positive reference count.
6. DFS_FILE_SYSTEM Error 0x82 The DFS_FILE_SYSTEM bug check has a value of 0x00000082.
7. DIRTY_MAPPED_PAGES_CONGESTION Error 0xEB The DIRTY_MAPPED_PAGES_CONGESTION bug check has a value of 0x000000EB. This indicates that no free pages are available to continue operations.
8. DIRTY_NOWRITE_PAGES_CONGESTION Error 0xFD The DIRTY_NOWRITE_PAGES_CONGESTION bug check has a value of 0x000000FD. This indicates that there are no free pages available to continue basic system operations.
9. DISORDERLY_SHUTDOWN Error 0xF3 The DISORDERLY_SHUTDOWN bug check has a value of 0x000000F3. This indicates that Windows was unable to shut down due to lack of memory.
10. DPC_WATCHDOG_VIOLATION Error 0x133 The DPC_WATCHDOG_VIOLATION bug check has a value of 0x00000133. This bug check indicates that the DPC watchdog executed, either because it detected a single long-running deferred procedure call (DPC), or because the system spent a prolonged time at an int
11. DRIVER_CAUGHT_MODIFYING_FREED_POOL Error 0xC6 The DRIVER_CAUGHT_MODIFYING_FREED_POOL bug check has a value of 0x000000C6. This indicates that the driver attempted to access a freed memory pool.
12. DRIVER_CORRUPTED_EXPOOL Error 0xC5 The DRIVER_CORRUPTED_EXPOOL bug check has a value of 0x000000C5. This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
13. DRIVER_CORRUPTED_MMPOOL Error 0xD0 The DRIVER_CORRUPTED_MMPOOL bug check has a value of 0x000000D0. This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
14. DRIVER_CORRUPTED_SYSPTES Error 0xDB The DRIVER_CORRUPTED_SYSPTES bug check has a value of 0x000000DB. This indicates that an attempt was made to touch memory at an invalid IRQL, probably due to corruption of system PTEs.
15. DRIVER_INVALID_STACK_ACCESS Error 0xDC The DRIVER_INVALID_STACK_ACCESS bug check has a value of 0x000000DC. This indicates that a driver accessed a stack address that lies below the stack pointer of the stack's thread.
16. DRIVER_IRQL_NOT_LESS_OR_EQUAL Error 0xD1 The DRIVER_IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x000000D1. This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
17. DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS Error 0xCB The DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS bug check has a value of 0x000000CB. This indicates that a driver or the I/O manager failed to release locked pages after an I/O operation.
18. DRIVER_OVERRAN_STACK_BUFFER Error 0xF7 The DRIVER_OVERRAN_STACK_BUFFER bug check has a value of 0x000000F7. This indicates that a driver has overrun a stack-based buffer.
19. DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION Error 0xD6 The DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION bug check has a value of 0x000000D6. This indicates the driver accessed memory beyond the end of its pool allocation.
20. DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL Error 0xD5 The DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL bug check has a value of 0x000000D5. This indicates that a driver has referenced memory which was earlier freed.
21. DRIVER_PORTION_MUST_BE_NONPAGED Error 0xD3 The DRIVER_PORTION_MUST_BE_NONPAGED bug check has a value of 0x000000D3. This indicates that the system attempted to access pageable memory at a process IRQL that was too high.
22. DRIVER_POWER_STATE_FAILURE Error 0x9F The DRIVER_POWER_STATE_FAILURE bug check has a value of 0x0000009F. This bug check indicates that the driver is in an inconsistent or invalid power state.
23. DRIVER_RETURNED_HOLDING_CANCEL_LOCK Error 0x11B The DRIVER_RETURNED_HOLDING_CANCEL_LOCK bug check has a value of 0x0000011B. This bug check indicates that a driver has returned from a cancel routine that holds the global cancel lock. This causes all later cancellation calls to fail, and results in eith
24. DRIVER_RETURNED_STATUS_REPARSE_FOR_VOLUME_OPEN Error 0xF9 The DRIVER_RETURNED_STATUS_REPARSE_FOR_VOLUME_OPEN bug check has a value of 0x000000F9. This indicates that a driver returned STATUS_REPARSE to an IRP_MJ_CREATE request with no trailing names.
25. DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS Error 0xCE The DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS bug check has a value of 0x000000CE. This indicates that a driver failed to cancel pending operations before unloading.
26. DRIVER_UNMAPPING_INVALID_VIEW Error 0xD7 The DRIVER_UNMAPPING_INVALID_VIEW bug check has a value of 0x000000D7. This indicates a driver is trying to unmap an address that was not mapped.
27. DRIVER_USED_EXCESSIVE_PTES Error 0xD8 The DRIVER_USED_EXCESSIVE_PTES bug check has a value of 0x000000D8. This indicates that there are no more system page table entries (PTE) remaining.
28. DRIVER_VERIFIER_DETECTED_VIOLATION Error 0xC4 The DRIVER_VERIFIER_DETECTED_VIOLATION bug check has a value of 0x000000C4. This is the general bug check code for fatal errors found by Driver Verifier. For more information, see Handling a Bug Check When Driver Verifier is Enabled.
29. DRIVER_VERIFIER_DMA_VIOLATION Error 0xE6 The DRIVER_VERIFIER_DMA_VIOLATION bug check has a value of 0x000000E6. This is the bug check code for all Driver Verifier DMA Verification violations.
30. DRIVER_VERIFIER_IOMANAGER_VIOLATION Error 0xC9 The DRIVER_VERIFIER_IOMANAGER_VIOLATION bug check has a value of 0x000000C9. This is the bug check code for all Driver Verifier I/O Verification violations.
31. DRIVER_VIOLATION Error 0x121 The DRIVER_VIOLATION bug check has a value of 0x00000121. This bug check indicates that a driver has caused a violation.
Home     Blog     About     Privacy Policy     Contact Us


Microsoft & Windows® logos are registered trademarks of Microsoft. Disclaimer: ErrorVault.com is not affiliated with Microsoft, nor does it claim such affiliation.
The information on this page is provided for informational purposes only. © Copyright 2018