ErrorVault.comSearch for your error:
Example: "0x00000013"| Error name | Error number | Error description |
|---|---|---|
| 101. INTERNAL_POWER_ERROR | Error 0xA0 | The INTERNAL_POWER_ERROR bug check has a value of 0x000000A0. This bug check indicates that the power policy manager experienced a fatal error. |
| 102. INTERRUPT_EXCEPTION_NOT_HANDLED | Error 0x3D | The INTERRUPT_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000003D. |
| 103. INTERRUPT_UNWIND_ATTEMPTED | Error 0x3C | The INTERRUPT_UNWIND_ATTEMPTED bug check has a value of 0x0000003C. |
| 104. INVALID_AFFINITY_SET | Error 0x3 | The INVALID_AFFINITY_SET bug check has a value of 0x00000003. |
| 105. INVALID_CANCEL_OF_FILE_OPEN | Error 0xE8 | The INVALID_CANCEL_OF_FILE_OPEN bug check has a value of 0x000000E8. This indicates that an invalid file object was passed to IoCancelFileOpen. |
| 106. INVALID_DATA_ACCESS_TRAP | Error 0x4 | The INVALID_DATA_ACCESS_TRAP bug check has a value of 0x00000004. |
| 107. INVALID_FLOATING_POINT_STATE | Error 0xE7 | The INVALID_FLOATING_POINT_STATE bug check has a value of 0x000000E7. This indicates that a thread's saved floating-point state is invalid. |
| 108. INVALID_KERNEL_HANDLE | Error 0x93 | The INVALID_KERNEL_HANDLE bug check has a value of 0x00000093. This bug check indicates that an invalid or protected handle was passed to NtClose. |
| 109. INVALID_PROCESS_ATTACH_ATTEMPT | Error 0x5 | The INVALID_PROCESS_ATTACH_ATTEMPT bug check has a value of 0x00000005. This generally indicates that the thread was attached to a process in a situation where that is not allowed. For example, this bug check could occur if KeAttachProcess was called when |
| 110. INVALID_PROCESS_DETACH_ATTEMPT | Error 0x6 | The INVALID_PROCESS_DETACH_ATTEMPT bug check has a value of 0x00000006. |
| 111. INVALID_REGION_OR_SEGMENT | Error 0x99 | The INVALID_REGION_OR_SEGMENT bug check has a value of 0x00000099. This bug check indicates that ExInitializeRegion or ExInterlockedExtendRegion was called with an invalid set of parameters. |
| 112. INVALID_SOFTWARE_INTERRUPT | Error 0x7 | The INVALID_SOFTWARE_INTERRUPT bug check has a value of 0x00000007. |
| 113. INVALID_WORK_QUEUE_ITEM | Error 0x96 | The INVALID_WORK_QUEUE_ITEM bug check has a value of 0x00000096. This bug check indicates that a queue entry was removed that contained a NULL pointer. |
| 114. IO1_INITIALIZATION_FAILED | Error 0x69 | The IO1_INITIALIZATION_FAILED bug check has a value of 0x00000069. This bug check indicates that the initialization of the I/O system failed for some reason. |
| 115. IRQL_GT_ZERO_AT_SYSTEM_SERVICE | Error 0x4A | The IRQL_GT_ZERO_AT_SYSTEM_SERVICE bug check has a value of 0x0000004A. This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL. |
| 116. IRQL_NOT_DISPATCH_LEVEL | Error 0x8 | The IRQL_NOT_DISPATCH_LEVEL bug check has a value of 0x00000008. |
| 117. IRQL_NOT_GREATER_OR_EQUAL | Error 0x9 | The IRQL_NOT_GREATER_OR_EQUAL bug check has a value of 0x00000009. |
| 118. IRQL_NOT_LESS_OR_EQUAL | Error 0xA | The IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x0000000A. This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. |
| 119. IRQL_UNEXPECTED_VALUE | Error 0xC8 | The IRQL_UNEXPECTED_VALUE bug check has a value of 0x000000C8. This indicates that the processor's IRQL is not what it should be at this time. |
| 120. KERNEL_APC_PENDING_DURING_EXIT | Error 0x20 | The KERNEL_APC_PENDING_DURING_EXIT bug check has a value of 0x00000020. This indicates that an asynchronous procedure call (APC) was still pending when a thread exited. |
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