ErrorVault.comSearch for your error:
Example: "0x00000013"| Error name | Error number | Error description |
|---|---|---|
| 1. MACHINE_CHECK_EXCEPTION | Error 0x9C | The MACHINE_CHECK_EXCEPTION bug check has a value of 0x0000009C. This bug check indicates that a fatal machine check exception has occurred. |
| 2. MAILSLOT_FILE_SYSTEM | Error 0x52 | The MAILSLOT_FILE_SYSTEM bug check has a value of 0x00000052. |
| 3. MANUALLY_INITIATED_CRASH | Error 0xE2 | The MANUALLY_INITIATED_CRASH bug check has a value of 0x000000E2. This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard. |
| 4. MANUALLY_INITIATED_CRASH1 | Error 0xDEADDEAD | The MANUALLY_INITIATED_CRASH1 bug check has a value of 0xDEADDEAD. This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard. |
| 5. MAXIMUM_WAIT_OBJECTS_EXCEEDED | Error 0xC | The MAXIMUM_WAIT_OBJECTS_EXCEEDED bug check has a value of 0x0000000C. This indicates that the current thread exceeded the permitted number of wait objects. |
| 6. MBR_CHECKSUM_MISMATCH | Error 0x8B | The MBR_CHECKSUM_MISMATCH bug check has a value of 0x0000008B. This bug check indicates that a mismatch has occurred in the MBR checksum. |
| 7. MEMORY1_INITIALIZATION_FAILED | Error 0x65 | The MEMORY1_INITIALIZATION_FAILED bug check has a value of 0x00000065. |
| 8. MEMORY_IMAGE_CORRUPT | Error 0xA2 | The MEMORY_IMAGE_CORRUPT bug check has a value of 0x000000A2. This bug check indicates that corruption has been detected in the image of an executable file in memory. |
| 9. MEMORY_MANAGEMENT | Error 0x1A | The MEMORY_MANAGEMENT bug check has a value of 0x0000001A. This indicates that a severe memory management error occurred. |
| 10. MISMATCHED_HAL | Error 0x79 | The MISMATCHED_HAL bug check has a value of 0x00000079. This bug check indicates that the Hardware Abstraction Layer (HAL) revision level or configuration does not match that of the kernel or the computer. |
| 11. MSRPC_STATE_VIOLATION | Error 0x112 | The MSRPC_STATE_VIOLATION bug check has a value of 0x00000112. This indicates that the Msrpc.sys driver has initiated a bug check. |
| 12. MULTIPLE_IRP_COMPLETE_REQUESTS | Error 0x44 | The MULTIPLE_IRP_COMPLETE_REQUESTS bug check has a value of 0x00000044. This indicates that a driver has tried to request an IRP be completed that is already complete. |
| 13. MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED | Error 0x3E | The MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED bug check has a value of 0x0000003E. This indicates that the system has multiple processors, but they are asymmetric in relation to one another. |
| 14. MUP_FILE_SYSTEM | Error 0x103 | The MUP_FILE_SYSTEM bug check has a value of 0x00000103. This bug check indicates that the multiple UNC provider (MUP) has encountered invalid or unexpected data. As a result, the MUP cannot channel a remote file system request to a network redirector, th |
| 15. MUST_SUCCEED_POOL_EMPTY | Error 0x41 | The MUST_SUCCEED_POOL_EMPTY bug check has a value of 0x00000041. This indicates that a kernel-mode thread has requested too much must-succeed pool. |
| 16. MUTEX_ALREADY_OWNED | Error 0xBF | The MUTEX_ALREADY_OWNED bug check has a value of 0x000000BF. This indicates that a thread attempted to acquire ownership of a mutex it already owned. |
| 17. MUTEX_LEVEL_NUMBER_VIOLATION | Error 0xD | The MUTEX_LEVEL_NUMBER_VIOLATION bug check has a value of 0x0000000D. |
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