ErrorVault.comSearch for your error:
Example: "0x00000013"| Error name | Error number | Error description |
|---|---|---|
| 121. KERNEL_DATA_INPAGE_ERROR | Error 0x7A | The KERNEL_DATA_INPAGE_ERROR bug check has a value of 0x0000007A. This bug check indicates that the requested page of kernel data from the paging file could not be read into memory. |
| 122. KERNEL_MODE_EXCEPTION_NOT_HANDLED | Error 0x8E | The KERNEL_MODE_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000008E. This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch. |
| 123. KERNEL_MODE_EXCEPTION_NOT_HANDLED_M | Error 0x1000008E | The KERNEL_MODE_EXCEPTION_NOT_HANDLED_M bug check has a value of 0x1000008E. This indicates that a kernel-mode program generated an exception which the error handler did not catch. |
| 124. KERNEL_SECURITY_CHECK_FAILURE | Error 0x139 | The KERNEL_SECURITY_CHECK_FAILURE bug check has a value of 0x00000139. This bug check indicates that the kernel has detected the corruption of a critical data structure. |
| 125. KERNEL_STACK_INPAGE_ERROR | Error 0x77 | The KERNEL_STACK_INPAGE_ERROR bug check has a value of 0x00000077. This bug check indicates that the requested page of kernel data from the paging file could not be read into memory. |
| 126. KERNEL_STACK_LOCKED_AT_EXIT | Error 0x94 | The KERNEL_STACK_LOCKED_AT_EXIT bug check has a value of 0x00000094. This bug check indicates that a thread exited while its kernel stack was marked as not swappable |
| 127. KMODE_EXCEPTION_NOT_HANDLED | Error 0x1E | The KMODE_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000001E. This indicates that a kernel-mode program generated an exception which the error handler did not catch. |
| 128. LAST_CHANCE_CALLED_FROM_KMODE | Error 0x15 | The LAST_CHANCE_CALLED_FROM_KMODE bug check has a value of 0x00000015. |
| 129. LM_SERVER_INTERNAL_ERROR | Error 0x54 | The LM_SERVER_INTERNAL_ERROR bug check has a value of 0x00000054. |
| 130. LOADER_BLOCK_MISMATCH | Error 0x100 | The LOADER_BLOCK_MISMATCH bug check has a value of 0x00000100. This indicates that either the loader block is invalid, or it does not match the system that is being loaded. |
| 131. LOCKED_PAGES_TRACKER_CORRUPTION | Error 0xD9 | The LOCKED_PAGES_TRACKER_CORRUPTION bug check has a value of 0x000000D9. This indicates that the internal locked-page tracking structures have been corrupted. |
| 132. LPC_INITIALIZATION_FAILED | Error 0x6A | The LPC_INITIALIZATION_FAILED bug check has a value of 0x0000006A. |
| 133. 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. |
| 134. MAILSLOT_FILE_SYSTEM | Error 0x52 | The MAILSLOT_FILE_SYSTEM bug check has a value of 0x00000052. |
| 135. 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. |
| 136. 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. |
| 137. 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. |
| 138. 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. |
| 139. MEMORY1_INITIALIZATION_FAILED | Error 0x65 | The MEMORY1_INITIALIZATION_FAILED bug check has a value of 0x00000065. |
| 140. 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. |
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