• Stop message 0x0000001E Descriptive text: KMODE_EXCEPTION_NOT_HANDLED
  
• Stop message 0x000000D1 Descriptive text: DRIVER_IRQL_NOT_LESS_OR_EQUAL
  
• Stop message 0x000000EA Descriptive text: THREAD_STUCK_IN_DEVICE_DRIVER
  
• Stop message 0x00000050 Descriptive text: PAGE_FAULT_IN_NONPAGED_AREA
  
• Stop message 0x000000BE Descriptive text: ATTEMPTED_WRITE_TO_READONLY_MEMORY
  
• Stop message 0x0000000A on an existing installation Descriptive text: IRQL_NOT_LESS_OR_EQUAL
  
• Stop message 0x0000000A on a new installation Descriptive text: IRQL_NOT_LESS_OR_EQUAL
  
• Stop messages 0x00000023 and 0x00000024 Descriptive text: FAT_FILE_SYSTEM or NTFS_FILE_SYSTEM
  
• Stop message 0x0000007B Descriptive text: INACCESSIBLE_BOOT_DEVICE
  
• Stop message 0x0000007F Descriptive text: UNEXPECTED_KERNEL_MODE_TRAP
  
• Stop message 0x0000009F Descriptive text: DRIVER_POWER_STATE_FAILURE
  
• Stop message 0xC000021A Descriptive text: FATAL_SYSTEM_ERROR
  
• Stop message 0xC0000221 Descriptive text: BAD_IMAGE_CHECKSUM
  
• Stop message 0xC0000218 Descriptive text: UNKNOWN_HARD_ERROR

1. Example Entry:
2. STOP 0x00000001: APC_INDEX_MISMATCH
3. STOP 0x00000002: DEVICE_QUEUE_NOT_BUSY
4. STOP 0x00000003: INVALID_AFFINITY_SET
5. STOP 0x00000004: INVALID_DATA_ACCESS_TRAP
6. STOP 0x00000005: INVALID_PROCESS_ATTACH_ATTEMPT
7. STOP 0x00000006: INVALID_PROCESS_DETACH_ATTEMPT
8. STOP 0x00000007: INVALID_SOFTWARE_INTERRUPT
9. STOP 0x00000008: IRQL_NOT_DISPATCH_LEVEL
10. STOP 0x00000009: IRQL_NOT_GREATER_OR_EQUAL
11. STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
12. STOP 0x0000000B: NO_EXCEPTION_HANDLING_SUPPORT
13. STOP 0x0000000C: MAXIMUM_WAIT_OBJECTS_EXCEEDED
14. STOP 0x0000000D: MUTEX_LEVEL_NUMBER_VIOLATION
15. STOP 0x0000000E: NO_USER_MODE_CONTEXT
16. STOP 0x0000000F: SPIN_LOCK_ALREADY_OWNED
17. STOP 0x00000010: SPIN_LOCK_NOT_OWNED
18. STOP 0x00000011: THREAD_NOT_MUTEX_OWNER
19. STOP 0x00000012: TRAP_CAUSE_UNKNOWN
20. STOP 0x00000013: EMPTY_THREAD_REAPER_LIST
21. STOP 0x00000014: CREATE_DELETE_LOCK_NOT_LOCKED
22. STOP 0x00000015: LAST_CHANCE_CALLED_FROM_KMODE
23. STOP 0x00000016: CID_HANDLE_CREATION
24. STOP 0x00000017: CID_HANDLE_DELETION
25. STOP 0x00000018: REFERENCE_BY_POINTER
26. STOP 0x00000019: BAD_POOL_HEADER
27. STOP 0x0000001A: MEMORY_MANAGEMENT
28. STOP 0x0000001B: PFN_SHARE_COUNT
29. STOP 0x0000001C: PFN_REFERENCE_COUNT
30. STOP 0x0000001D: NO_SPIN_LOCK_AVAILABLE
31. STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
32. STOP 0x0000001F: SHARED_RESOURCE_CONV_ERROR
33. STOP 0x00000020: KERNEL_APC_PENDING_DURING_EXIT
34. STOP 0x00000021: QUOTA_UNDERFLOW
35. STOP 0x00000022: FILE_SYSTEM
36. STOP 0x00000023: FAT_FILE_SYSTEM
37. STOP 0x00000024: NTFS_FILE_SYSTEM
38. STOP 0x00000025: NPFS_FILE_SYSTEM
39. STOP 0x00000026: CDFS_FILE_SYSTEM
40. STOP 0x00000027: RDR_FILE_SYSTEM
41. STOP 0x00000028: CORRUPT_ACCESS_TOKEN
42. STOP 0x00000029: SECURITY_SYSTEM
43. STOP 0x0000002A: INCONSISTENT_IRP
44. STOP 0x0000002B: PANIC_STACK_SWITCH
45. STOP 0x0000002C: PORT_DRIVER_INTERNAL
46. STOP 0x0000002D: SCSI_DISK_DRIVER_INTERNAL
47. STOP 0x0000002E: DATA_BUS_ERROR
48. STOP 0x0000002F: INSTRUCTION_BUS_ERROR
49. STOP 0x00000030: SET_OF_INVALID_CONTEXT
50. STOP 0x00000031: PHASE0_INITIALIZATION_FAILED
51. STOP 0x00000032: PHASE1_INITIALIZATION_FAILED
52. STOP 0x00000033: UNEXPECTED_INITIALIZATION_CALL
53. STOP 0x00000034: CACHE_MANAGER
54. STOP 0x00000035: NO_MORE_IRP_STACK_LOCATIONS
55. STOP 0x00000036: DEVICE_REFERENCE_COUNT_NOT_ZERO
56. STOP 0x00000037: FLOPPY_INTERNAL_ERROR
57. STOP 0x00000038: SERIAL_DRIVER_INTERNAL
58. STOP 0x00000039: SYSTEM_EXIT_OWNED_MUTEX
59. STOP 0x0000003A: SYSTEM_UNWIND_PREVIOUS_USER
60. STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
61. STOP 0x0000003C: INTERRUPT_UNWIND_ATTEMPTED
62. STOP 0x0000003D: INTERRUPT_EXCEPTION_NOT_HANDLED
63. STOP 0x0000003E: MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED
64. STOP 0x0000003F: NO_MORE_SYSTEM_PTES
65. STOP 0x00000040: TARGET_MDL_TOO_SMALL
66. STOP 0x00000041: MUST_SUCCEED_POOL_EMPTY
67. STOP 0x00000042: ATDISK_DRIVER_INTERNAL
68. STOP 0x00000043: NO_SUCH_PARTITION
69. STOP 0x00000044: MULTIPLE_IRP_COMPLETE_REQUESTS
70. STOP 0x00000045: INSUFFICIENT_SYSTEM_MAP_REGS
71. STOP 0x00000046: DEREF_UNKNOWN_LOGON_SESSION
72. STOP 0x00000047: REF_UNKNOWN_LOGON_SESSION
73. STOP 0x00000048: CANCEL_STATE_IN_COMPLETED_IRP
74. STOP 0x00000049: PAGE_FAULT_WITH_INTERRUPTS_OFF
75. STOP 0x0000004A: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
76. STOP 0x0000004B: STREAMS_INTERNAL_ERROR
77. STOP 0x0000004C: FATAL_UNHANDLED_HARD_ERROR
78. STOP 0x0000004D: NO_PAGES_AVAILABLE
79. STOP 0x0000004E: PFN_LIST_CORRUPT
80. STOP 0x0000004F: NDIS_INTERNAL_ERROR
81. STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
82. STOP 0x00000051: REGISTRY_ERROR
83. STOP 0x00000052: MAILSLOT_FILE_SYSTEM
84. STOP 0x00000053: NO_BOOT_DEVICE
85. STOP 0x00000054: LM_SERVER_INTERNAL_ERROR
86. STOP 0x00000055: DATA_COHERENCY_EXCEPTION
87. STOP 0x00000056: INSTRUCTION_COHERENCY_EXCEPTION
88. STOP 0x00000057: XNS_INTERNAL_ERROR
89. STOP 0x00000058: FTDISK_INTERNAL_ERROR
90. STOP 0x00000059: PINBALL_FILE_SYSTEM
91. STOP 0x0000005A: CRITICAL_SERVICE_FAILED
92. STOP 0x0000005B: SET_ENV_VAR_FAILED
93. STOP 0x0000005C: HAL_INITIALIZATION_FAILED
94. STOP 0x0000005D: UNSUPPORTED_PROCESSOR
95. STOP 0x0000005E: OBJECT_INITIALIZATION_FAILED
96. STOP 0x0000005F: SECURITY_INITIALIZATION_FAILED
97. STOP 0x00000060: PROCESS_INITIALIZATION_FAILED
98. STOP 0x00000061: HAL1_INITIALIZATION_FAILED
99. STOP 0x00000062: OBJECT1_INITIALIZATION_FAILED
100. STOP 0x00000063: SECURITY1_INITIALIZATION_FAILED
101. STOP 0x00000064: SYMBOLIC_INITIALIZATION_FAILED
102. STOP 0x00000065: MEMORY1_INITIALIZATION_FAILED
103. STOP 0x00000066: CACHE_INITIALIZATION_FAILED
104. STOP 0x00000067: CONFIG_INITIALIZATION_FAILED
105. STOP 0x00000068: FILE_INITIALIZATION_FAILED
106. STOP 0x00000069: IO1_INITIALIZATION_FAILED
107. STOP 0x0000006A: LPC_INITIALIZATION_FAILED
108. STOP 0x0000006B: PROCESS1_INITIALIZATION_FAILED
109. STOP 0x0000006C: REFMON_INITIALIZATION_FAILED
110. STOP 0x0000006D: SESSION1_INITIALIZATION_FAILED
111. STOP 0x0000006E: SESSION2_INITIALIZATION_FAILED
112. STOP 0x0000006F: SESSION3_INITIALIZATION_FAILED
113. STOP 0x00000070: SESSION4_INITIALIZATION_FAILED
114. STOP 0x00000071: SESSION5_INITIALIZATION_FAILED
115. STOP 0x00000072: ASSIGN_DRIVE_LETTERS_FAILED
116. STOP 0x00000073: CONFIG_LIST_FAILED
117. STOP 0x00000074: BAD_SYSTEM_CONFIG_INFO
118. STOP 0x00000075: CANNOT_WRITE_CONFIGURATION
119. STOP 0x00000076: PROCESS_HAS_LOCKED_PAGES
120. STOP 0x00000077: KERNEL_STACK_INPAGE_ERROR
121. STOP 0x00000078: PHASE0_EXCEPTION
122. STOP 0x00000079: MISMATCHED_HAL
123. STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR
124. STOP 0x0000007B: INACCESSIBLE_BOOT_DEVICE
125. STOP 0x0000007C: BUGCODE_NDIS_DRIVER
126. STOP 0x0000007D: INSTALL_MORE_MEMORY
127. STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
128. STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP
129. STOP 0x00000080: NMI_HARDWARE_FAILURE
130. STOP 0x00000081: SPIN_LOCK_INIT_FAILURE
131. STOP 0x00000082: DFS_FILE_SYSTEM
132. STOP 0x00000083: OFS_FILE_SYSTEM
133. STOP 0x00000084: RECOM_DRIVER
134. STOP 0x00000085: SETUP_FAILURE
135. STOP 0x00000086: AUDIT_FAILURE
136. STOP 0x00000087:
137. STOP 0x00000088:
138. STOP 0x00000089:
139. STOP 0x0000008A:
140. STOP 0x0000008B: MBR_CHECKSUM_MISMATCH
141. STOP 0x0000008C:
142. STOP 0x0000008D:
143. STOP 0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
144. STOP 0x0000008F: PP0_INITIALIZATION_FAILED
145. STOP 0x00000090: PP1_INITIALIZATION_FAILED
146. STOP 0x00000091: WIN32K_INIT_OR_RIT_FAILURE
147. STOP 0x00000092: UP_DRIVER_ON_MP_SYSTEM
148. STOP 0x00000093: INVALID_KERNEL_HANDLE
149. STOP 0x00000094: KERNEL_STACK_LOCKED_AT_EXIT
150. STOP 0x00000095: PNP_INTERNAL_ERROR
151. STOP 0x00000096: INVALID_WORK_QUEUE_ITEM
152. STOP 0x00000097: BOUND_IMAGE_UNSUPPORTED
153. STOP 0x00000098: END_OF_NT_EVALUATION_PERIOD
154. STOP 0x00000099: INVALID_REGION_OR_SEGMENT
155. STOP 0x0000009A: SYSTEM_LICENSE_VIOLATION
156. STOP 0x0000009B: UDFS_FILE_SYSTEM
157. STOP 0x0000009C: MACHINE_CHECK_EXCEPTION
158. STOP 0x0000009D:
159. STOP 0x0000009E: USER_MODE_HEALTH_MONITOR
160. STOP 0x0000009F: DRIVER_POWER_STATE_FAILURE
161. STOP 0x000000A0: INTERNAL_POWER_ERROR
162. STOP 0x000000A1: PCI_BUS_DRIVER_INTERNAL
163. STOP 0x000000A2: MEMORY_IMAGE_CORRUPT
164. STOP 0x000000A3: ACPI_DRIVER_INTERNAL
165. STOP 0x000000A4: CNSS_FILE_SYSTEM_FILTER
166. STOP 0x000000A5: ACPI_BIOS_ERROR
167. STOP 0x000000A6: FP_EMULATION_ERROR
168. STOP 0x000000A7: BAD_EXHANDLE
169. STOP 0x000000A8: BOOTING_IN_SAFEMODE_MINIMAL
170. STOP 0x000000A9: BOOTING_IN_SAFEMODE_NETWORK
171. STOP 0x000000AA: BOOTING_IN_SAFEMODE_DSREPAIR
172. STOP 0x000000AB: SESSION_HAS_VALID_POOL_ON_EXIT
173. STOP 0x000000AC: HAL_MEMORY_ALLOCATION
174. STOP 0x000000AD: VIDEO_DRIVER_DEBUG_REPORT_REQUEST
175. STOP 0x000000AE:
176. STOP 0x000000AF:
177. STOP 0x000000B0:
178. STOP 0x000000B1:
179. STOP 0x000000B2:
180. STOP 0x000000B3:
181. STOP 0x000000B4: VIDEO_DRIVER_INIT_FAILURE
182. STOP 0x000000B5: BOOTLOG_LOADED
183. STOP 0x000000B6: BOOTLOG_NOT_LOADED
184. STOP 0x000000B7: BOOTLOG_ENABLED
185. STOP 0x000000B8: ATTEMPTED_SWITCH_FROM_DPC
186. STOP 0x000000B9: CHIPSET_DETECTED_ERROR
187. STOP 0x000000BA: SESSION_HAS_VALID_VIEWS_ON_EXIT
188. STOP 0x000000BB: NETWORK_BOOT_INITIALIZATION_FAILED
189. STOP 0x000000BC: NETWORK_BOOT_DUPLICATE_ADDRESS
190. STOP 0x000000BD: INVALID_HIBERNATED STATE
191. STOP 0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY
192. STOP 0x000000BF: MUTEX_ALREADY_OWNED
193. STOP 0x000000C0: PCI_CONFIT_SPACE_ACCESS_FAILURE
194. STOP 0x000000C1: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
195. STOP 0x000000C2: BAD_POOL_CALLER
196. STOP 0x000000C3: BUGCODE_PSS_MESSAGE_SIGNATURE
197. STOP 0x000000C4: DRIVER_VERIFIER_DETECTED_VIOLATION
198. STOP 0x000000C5: DRIVER_CORRUPTED_EXPOOL
199. STOP 0x000000C6: DRIVER_CAUGHT_MODIFYING_FREED_POOL
200. STOP 0x000000C7: TIMER_OR_DPC_INVALID
201. STOP 0x000000C8: IRQL_UNEXPECTED_VALUE
202. STOP 0x000000C9: DRIVER_VERIFIER_IOMANAGER_VIOLATION
203. STOP 0x000000CA: PNP_DETECTED_FATAL_ERROR
204. STOP 0x000000CB: DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS
205. STOP 0x000000CC: PAGE_FAULT_IN_FREED_SPECIAL_POOL
206. STOP 0x000000CD: PAGE_FAULT_BEYOND_END_OF_ALLOCATION
207. STOP 0x000000CE: DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
208. STOP 0x000000CF: TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE
209. STOP 0x000000D0: DRIVER_CORRUPTED_MMPOOL
210. STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
211. STOP 0x000000D2: BUGCODE_ID_DRIVER
212. STOP 0x000000D3: DRIVER_PORTION_MUST_BE_NONPAGED
213. STOP 0x000000D4: SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD
214. STOP 0x000000D5: DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL
215. STOP 0x000000D6: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION
216. STOP 0x000000D7: DRIVER_UNMAPPING_INVALID_VIEW
217. STOP 0x000000D8: DRIVER_USED_EXCESSIVE_PTES
218. STOP 0x000000D9: LOCKED_PAGES_TRACKER_CORRUPTION
219. STOP 0x000000DA: SYSTEM_PTE_MISUSE
220. STOP 0x000000DB: DRIVER_CORRUPTED_SYSPTES
221. STOP 0x000000DC: DRIVER_INVALID_STACK_ACCESS
222. STOP 0x000000DD:  ???BIOS IS NOT ACPI COMPLIANT???
223. STOP 0x000000DE: POOL_CORRUPTION_IN_FILE_AREA
224. STOP 0x000000DF: IMPERSONATING_WORKER_THREAD
225. STOP 0x000000E0: ACPI_BIOS_FATAL_ERROR
226. STOP 0x000000E1: WORKER_THREAD_RETURNED_AT_BAD_IRQL
227. STOP 0x000000E2: MANUALLY_INITIATED_CRASH
228. STOP 0x000000E3: RESOURCE_NOT_OWNED
229. STOP 0x000000E4: WORKER_INVALID
230. STOP 0x000000E5: POWER_FAILURE_SIMULATE
231. STOP 0x000000E6: DRIVER_VERIFIER_DMA_VIOLATION
232. STOP 0x000000E7: INVALID_FLOATING_POINT_STATE
233. STOP 0x000000E8: INVALID_CANCEL_OF_FILE_OPEN
234. STOP 0x000000E9: ACTIVE_EX_WORKER_THREAD_TERMINATION
235. STOP 0x000000EA: THREAD_STUCK_IN_DEVICE_DRIVER
236. STOP 0x000000EB: DIRTY_MAPPED_PAGES_CONGESTION
237. STOP 0x000000EC: SESSION_HAS_VALID_SPECIAL_POOL_ON_EXIT
238. STOP 0x000000ED: UNMOUNTABLE_BOOT_VOLUME
239. STOP 0x000000EE:
240. STOP 0x000000EF: CRITICAL_PROCESS_DIED
241. STOP 0x000000F0:
242. STOP 0x000000F1: SCSI_VERIFIER_DETECTED_VIOLATION
243. STOP 0x000000F2: HARDWARE_INTERRUPT_STORM
244. STOP 0x000000F3: DISORDERLY_SHUTDOWN
245. STOP 0x000000F4: CRITICAL_OBJECT_TERMINATION
246. STOP 0x000000F5: FLTMGR_FILE_SYSTEM
247. STOP 0x000000F6: PCI_VERIFIER_DETECTED_VIOLATION
248. STOP 0x000000F7: DRIVER_OVERRAN_STACK_BUFFER
249. STOP 0x000000F8: RAMDISK_BOOT_INITIALIZATION_FAILED
250. STOP 0x000000F9: DRIVER_RETURNED_STATUS_REPARSE_FOR_VOLUME_OPEN
251. STOP 0x000000FA: HTTP_DRIVER_CORRUPTED
252. STOP 0x000000FB: RECURSIVE_MACHINE_CHECK
253. STOP 0x000000FC: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
254. STOP 0x000000FD: DIRTY_NOWRITE_PAGES_CONGESTION
255. STOP 0x000000FE: BUGCODE_USB_DRIVER
256. STOP 0x000000FF: RESERVE_QUEUE_OVERFLOW
257. STOP 0x000000MN:
258. STOP 0x00000100: LOADER_BLOCK_MISMATCH
259. STOP 0x00000101: CLOCK_WATCHDOG_TIMEOUT
260. STOP 0x00000102: DPC_WATCHDOG_TIMEOUT
261. STOP 0x00000103: MUP_FILE_SYSTEM
262. STOP 0x00000104: AGP_INVALID_ACCESS
263. STOP 0x00000105: AGP_GART_CORRUPTION
264. STOP 0x00000106: AGP_ILLEGALLY_REPROGRAMMED
265. STOP 0x00000107: KERNEL_EXPAND_STACK_ACTIVE
266. STOP 0x00000108: THIRD_PARTY_FILE_SYSTEM_FAILURE
267. STOP 0x00000109: CRITICAL_STRUCTURE_CORRUPTION
268. STOP 0x0000010A: APP_TAGGING_INITIALIZATION_FAILED
269. STOP 0x0000010B: DFSC_FILE_SYSTEM
270. STOP 0x0000010C: FSRTL_EXTRA_CREATE_PARAMETER_VIOLATION
271. STOP 0x0000010D: WDF_VIOLATION
272. STOP 0x0000010E: VIDEO_MEMORY_MANAGEMENT_INTERNAL
273. STOP 0x0000010F: RESOURCE_MANAGER_EXCEPTION_NOT_HANDLED
274. STOP 0x00000110: DRIVER_INVALID_CRUNTIME_PARAMETER
275. STOP 0x00000111: RECURSIVE_NMI
276. STOP 0x00000112: MSRPC_STATE_VIOLATION
277. STOP 0x00000113: VIDEO_DXGKRNL_FATAL_ERROR
278. STOP 0x00000114: VIDEO_SHADOW_DRIVER_FATAL_ERROR
279. STOP 0x00000115: AGP_INTERNAL
280. STOP 0x00000116: VIDEO_TDR_ERROR
281. STOP 0x00000117: VIDEO_TDR_TIMEOUT_DETECTED
282. STOP 0x00000118: NTHV_GUEST_ERROR
283. STOP 0x00000119: VIDEO_SCHEDULER_INTERNAL_ERROR
284. STOP 0x0000011A: EM_INITIALIZATION_FAILURE
285. STOP 0x0000011B: DRIVER_RETURNED_HOLDING_CANCEL_LOCK
286. STOP 0x0000011C: ATTEMPTED_WRITE_TO_CM_PROTECTED_STORAGE
287. STOP 0x0000011D: EVENT_TRACING_FATAL_ERROR
288. STOP 0x0000011E: TOO_MANY_RECURSIVE_FAULTS
289. STOP 0x0000011F: INVALID_DRIVER_HANDLE
290. STOP 0x00000120: BITLOCKER_FATAL_ERROR
291. STOP 0x00000121: DRIVER_VIOLATION
292. STOP 0x00000122: WHEA_INTERNAL_ERROR
293. STOP 0x00000123: CRYPTO_SELF_TEST_FAILURE
294. STOP 0x00000124: WHEA_UNCORRECTABLE_ERROR
295. STOP 0x00000125: NMR_INVALID_STATE
296. STOP 0x00000126: NETIO_INVALID_POOL_CALLER
297. STOP 0x00000127: PAGE_NOT_ZERO
298. STOP 0x00000128: WORKER_THREAD_RETURNED_WITH_BAD_IO_PRIORITY
299. STOP 0x00000129: WORKER_THREAD_RETURNED_WITH_BAD_PAGING_IO_PRIORITY
300. STOP 0x0000012A: MUI_NO_VALID_SYSTEM_LANGUAGE
301. STOP 0x0000012B: FAULTY_HARDWARE_CORRUPTED_PAGE
302. STOP 0x0000012C: EXFAT_FILE_SYSTEM
303. STOP 0x0000012D: VOLSNAP_OVERLAPPED_TABLE_ACCESS
304. STOP 0x0000012E: INVALID_MDL_RANGE
305. STOP 0x0000012F: VHD_BOOT_INITIALIZATION_FAILED
306. STOP 0x00000130: DYNAMIC_ADD_PROCESSOR_MISMATCH
307. STOP 0x00000131: INVALID_EXTENDED_PROCESSOR_STATE
308. STOP 0x00000132: RESOURCE_OWNER_POINTER_INVALID
309. STOP 0x00000133: DPC_WATCHDOG_VIOLATION
310. STOP 0x00000134: DRIVE_EXTENDER
311. STOP 0x00000135: REGISTRY_FILTER_DRIVER_EXCEPTION
312. STOP 0x00000136: VHD_BOOT_HOST_VOLUME_NOT_ENOUGH_SPACE
313. STOP 0x00000333:
314. STOP 0x00000BFE: BC_BLUETOOTH_VERIFIER_FAULT
315. STOP 0x0000C1F5:
316. STOP 0x00020001: HYPERVISOR_ERROR
317. STOP 0x1000000A: IRQL_NOT_LESS_OR_EQUAL
318. STOP 0x10000050: PAGE_FAULT_IN_NONPAGED_AREA_M
319. STOP 0x1000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
320. STOP 0x1000007F: UNEXPECTED_KERNEL_MODE_TRAP_M
321. STOP 0x1000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
322. STOP 0x100000B8: ATTEMPTED_SWITCH_FROM_DPC
323. STOP 0x100000CF: TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE
324. STOP 0x100000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
325. STOP 0x100000D6: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION_M
326. STOP 0x100000EA: THREAD_STUCK_IN_DEVICE_DRIVER_M
327. STOP 0x40000082: BUGCODE_PSS_MESSAGE
328. STOP 0x40000083: BUGCHECK_TECH_INFO
329. STOP 0x40000087: WINDOWS_NT_CSD_STRING
330. STOP 0x40000088: WINDOWS_NT_INFO_STRING
331. STOP 0x40000089: WINDOWS_NT_MP_STRING
332. STOP 0x4000008A: THREAD_TERMINATE_HELD_MUTEX
333. STOP 0x4000008B: BUGCODE_PSS_CRASH_INIT
334. STOP 0x4000008C: BUGCODE_PSS_CRASH_PROGRESS
335. STOP 0x4000008D: BUGCODE_PSS_CRASH_DONE
336. STOP 0x4000009D: WINDOWS_NT_INFO_STRING_PLURAL
337. STOP 0x4000009E: WINDOWS_NT_RC_STRING
338. STOP 0x400000AD: VIDEO_DRIVER_DEBUG_REPORT_REQUEST
339. STOP 0x8086:
340. STOP 0x9087:
341. STOP 0x9088:
342. STOP 0xC000009A: STATUS_INSUFFICIENT_RESOURCES
343. STOP 0xC0000135: UNABLE_TO_LOCATE_DLL
344. STOP 0xC0000142: DLL Initialization Failure
345. STOP 0xC0000218: STATUS_CANNOT_LOAD_REGISTRY_FILE
346. STOP 0xC000021A: STATUS_SYSTEM_PROCESS_TERMINATED
347. STOP 0xC0000221: STATUS_IMAGE_CHECKSUM_MISMATCH
348. STOP 0xC0000244:  AUDIT_FAILED
349. STOP 0xC000026C: ???FATAL SYSTEM ERROR???
350. STOP 0xDEADDEAD: MANUALLY_INITIATED_CRASH1

Example Entry:

STOP 0x00000001: APC_INDEX_MISMATCH    (go to top of page)

The APC_INDEX_MISMATCH bug check has a value of 0x00000001. This indicates that there has been a mismatch in the APC state index.

The following parameters are displayed on the blue screen.

The most common cause of this bug check is when a file system has a mismatched sequence of KeEnterCriticalRegion calls and KeLeaveCriticalRegion calls.

This is a kernel internal error which can occur only on a checked build. This error occurs on exit from a system call.

STOP 0x00000002: DEVICE_QUEUE_NOT_BUSY    (go to top of page)

The DEVICE_QUEUE_NOT_BUSY bug check has a value of 0x00000002.

This bug check appears very infrequently.

STOP 0x00000003: INVALID_AFFINITY_SET    (go to top of page)

The INVALID_AFFINITY_SET bug check has a value of 0x00000003.

This bug check appears very infrequently.

STOP 0x00000004: INVALID_DATA_ACCESS_TRAP    (go to top of page)

The INVALID_DATA_ACCESS_TRAP bug check has a value of 0x00000004.

This bug check appears very infrequently.

STOP 0x00000005: INVALID_PROCESS_ATTACH_ATTEMPT    (go to top of page)

The INVALID_PROCESS_ATTACH_ATTEMPT bug check has a value of 0x00000005.

This bug check appears very infrequently.

STOP 0x00000006: INVALID_PROCESS_DETACH_ATTEMPT    (go to top of page)

The INVALID_PROCESS_DETACH_ATTEMPT bug check has a value of 0x00000006.

This bug check appears very infrequently.

STOP 0x00000007: INVALID_SOFTWARE_INTERRUPT    (go to top of page)

The INVALID_SOFTWARE_INTERRUPT bug check has a value of 0x00000007.

This bug check appears very infrequently.

STOP 0x00000008: IRQL_NOT_DISPATCH_LEVEL    (go to top of page)

The IRQL_NOT_DISPATCH_LEVEL bug check has a value of 0x00000008.

This bug check appears very infrequently.

STOP 0x00000009: IRQL_NOT_GREATER_OR_EQUAL    (go to top of page)

The IRQL_NOT_GREATER_OR_EQUAL bug check has a value of 0x00000009.

This bug check appears very infrequently.

STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL    (go to top of page)

The following parameters are displayed on the blue screen.

This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.

The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.

If you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.

If a kernel debugger is available, obtain a stack trace.

1. Restart your computer.
2. Press F8 at the character-based menu that displays the operating system choices.
3. Select the Last Known Good Configuration option from the Windows Advanced Options menu. This option is most effective when only one driver or service is added at a time.

1. Check the System Log in Event Viewer for error messages that might identify the device or driver that caused the error.
2. Try disabling memory caching of the BIOS.
3. Run the hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owner's manual for your computer.
4. Make sure the latest Service Pack is installed.
5. If your system has small computer system interface (SCSI) adapters, contact the adapter manufacturer to obtain updated Windows drivers. Try disabling sync negotiation in the SCSI BIOS, checking the cabling and the SCSI IDs of each device, and confirming proper termination.
6. For integrated device electronics (IDE) devices, define the onboard IDE port as Primary only. Also, check each IDE device for the proper master/subordinate/stand-alone setting. Try removing all IDE devices except for hard disks.

If the message appears during an installation of Windows, make sure that the computer and all installed peripherals are listed in the Microsoft Windows Marketplace Tested Products List.

Here is a debugging example:

kd> .bugcheck       [Lists bug check data.]
Bugcheck code 0000000a
Arguments 00000000 0000001c 00000000 00000000

kd> kb       [Lists the stack trace.]
ChildEBP RetAddr  Args to Child
8013ed5c 801263ba 00000000 00000000 e12ab000 NT!_DbgBreakPoint
8013eecc 801389ee 0000000a 00000000 0000001c NT!_KeBugCheckEx+0x194
8013eecc 00000000 0000000a 00000000 0000001c NT!_KiTrap0E+0x256
8013ed5c 801263ba 00000000 00000000 e12ab000
8013ef64 00000246 fe551aa1 ff690268 00000002 NT!_KeBugCheckEx+0x194

kd> kv       [Lists the trap frames.]
ChildEBP RetAddr  Args to Child
8013ed5c 801263ba 00000000 00000000 e12ab000 NT!_DbgBreakPoint (FPO: [0,0,0])
8013eecc 801389ee 0000000a 00000000 0000001c NT!_KeBugCheckEx+0x194
8013eecc 00000000 0000000a 00000000 0000001c NT!_KiTrap0E+0x256 (FPO: [0,0] TrapFrame @ 8013eee8)
8013ed5c 801263ba 00000000 00000000 e12ab000
8013ef64 00000246 fe551aa1 ff690268 00000002 NT!_KeBugCheckEx+0x194

kd> .trap 8013eee8       [Gets the registers for the trap frame at the time of the fault.]
eax=dec80201 ebx=ffdff420 ecx=8013c71c edx=000003f8 esi=00000000 edi=87038e10
eip=00000000 esp=8013ef5c ebp=8013ef64 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
ErrCode = 00000000
00000000 ???????????????       [The current instruction pointer is NULL.]

kd> kb       [Gives the stack trace before the fault.]
ChildEBP RetAddr  Args to Child
8013ef68 fe551aa1 ff690268 00000002 fe5620d2 NT!_DbgBreakPoint
8013ef74 fe5620d2 fe5620da ff690268 80404690
NDIS!_EthFilterIndicateReceiveComplete+0x31
8013ef64 00000246 fe551aa1 ff690268 00000002 elnkii!_ElnkiiRcvInterruptDpc+0x1d0

Before upgrading to a new version of Windows, remove all third-party device drivers and system services, and disable any virus scanners. Contact the software manufacturers to obtain updates of these third-party tools.

STOP 0x0000000B: NO_EXCEPTION_HANDLING_SUPPORT    (go to top of page)

The NO_EXCEPTION_HANDLING_SUPPORT bug check has a value of 0x0000000B.

This bug check appears very infrequently.

STOP 0x0000000C: MAXIMUM_WAIT_OBJECTS_EXCEEDED    (go to top of page)

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.

None

This bug check results from the improper use of KeWaitForMultipleObjects or FsRtlCancellableWaitForMultipleObjects.

The caller may pass a pointer to a buffer in this routine's WaitBlockArray parameter. The system will use this buffer to keep track of wait objects.

If a buffer is supplied, the Count parameter may not exceed MAXIMUM_WAIT_OBJECTS. If no buffer is supplied, the Count parameter may not exceed THREAD_WAIT_OBJECTS.

If the value of Count exceeds the allowable value, this bug check is issued.

STOP 0x0000000D: MUTEX_LEVEL_NUMBER_VIOLATION    (go to top of page)

The MUTEX_LEVEL_NUMBER_VIOLATION bug check has a value of 0x0000000D.

This bug check appears very infrequently.

STOP 0x0000000E: NO_USER_MODE_CONTEXT    (go to top of page)

The NO_USER_MODE_CONTEXT bug check has a value of 0x0000000E.

This bug check appears very infrequently.

STOP 0x0000000F: SPIN_LOCK_ALREADY_OWNED    (go to top of page)

The SPIN_LOCK_ALREADY_OWNED bug check has a value of 0x0000000F. This indicates that a request for a spin lock has been initiated when the spin lock was already owned.

None

Typically, this error is caused by a recursive request for a spin lock. It can also occur if something similar to a recursive request for a spin lock has been initiated—for example, when a spin lock has been acquired by a thread, and then that same thread calls a function, which also tries to acquire a spin lock. The second attempt to acquire a spin lock is not blocked in this case because doing so would result in an unrecoverable deadlock. If the calls are made on more than one processor, then one processor will be blocked until the other processor releases the lock.

This error can also occur, without explicit recursion, when all threads and all spin locks are assigned an IRQL. Spin lock IRQLs are always greater than or equal to DPC level, but this is not true for threads. However, a thread that is holding a spin lock must maintain an IRQL greater than or equal to that of the spin lock. Decreasing the thread IRQL below the IRQL level of the spin lock that it is holding allows another thread to be scheduled on the processor. This new thread could then attempt to acquire the same spin lock.

Ensure that you are not recursively acquiring the lock. And, for threads that hold a spin lock, ensure that you are not decreasing the thread IRQL to a level below the IRQL of the spin lock that it is holding.

STOP 0x00000010: SPIN_LOCK_NOT_OWNED    (go to top of page)

The SPIN_LOCK_NOT_OWNED bug check has a value of 0x00000010.

This bug check appears very infrequently.

STOP 0x00000011: THREAD_NOT_MUTEX_OWNER    (go to top of page)

The THREAD_NOT_MUTEX_OWNER bug check has a value of 0x00000011.

This bug check appears very infrequently.

STOP 0x00000012: TRAP_CAUSE_UNKNOWN    (go to top of page)

The TRAP_CAUSE_UNKNOWN bug check has a value of 0x00000012. This indicates that an unknown exception has occurred.

The following parameters are displayed on the blue screen.

STOP 0x00000013: EMPTY_THREAD_REAPER_LIST    (go to top of page)

The EMPTY_THREAD_REAPER_LIST bug check has a value of 0x00000013.

This bug check appears very infrequently.

STOP 0x00000014: CREATE_DELETE_LOCK_NOT_LOCKED    (go to top of page)

The CREATE_DELETE_LOCK_NOT_LOCKED bug check has a value of 0x00000014.

This bug check appears very infrequently.

STOP 0x00000015: LAST_CHANCE_CALLED_FROM_KMODE    (go to top of page)

The LAST_CHANCE_CALLED_FROM_KMODE bug check has a value of 0x00000015.

This bug check appears very infrequently.

STOP 0x00000016: CID_HANDLE_CREATION    (go to top of page)

The CID_HANDLE_CREATION bug check has a value of 0x00000016.

This bug check appears very infrequently.

STOP 0x00000017: CID_HANDLE_DELETION    (go to top of page)

The CID_HANDLE_DELETION bug check has a value of 0x00000017.

This bug check appears very infrequently.

STOP 0x00000018: REFERENCE_BY_POINTER    (go to top of page)

The REFERENCE_BY_POINTER bug check has a value of 0x00000018. This indicates that the reference count of an object is illegal for the current state of the object.

The following parameters are displayed on the blue screen.

The reference count of an object is illegal for the current state of the object. Each time a driver uses a pointer to an object, the driver calls a kernel routine to increase the reference count of the object by one. When the driver is done with the pointer, the driver calls another kernel routine to decrease the reference count by one.

Drivers must match calls to the routines that increase (reference) and decrease (dereference) the reference count. This bug check is caused by an inconsistency in the object’s reference count. Typically, the inconsistency is caused by a driver that decreases the reference count of an object too many times, making extra calls that dereference the object. This bug check can occur because an object's reference count goes to zero while there are still open handles to the object. It might also occur when the object’s reference count drops below zero, whether or not there are open handles to the object.

Make sure that the driver matches calls to the routines that increase and decrease the reference count of the object. Make sure that your driver does not make extra calls to routines that dereference the object (see Parameter 2).

You can use a debugger to help analyze this problem. To find the handle and pointer count on the object, use the !object debugger command.

kd> !object address

Where address is the address of the object given in Parameter 2.

STOP 0x00000019: BAD_POOL_HEADER    (go to top of page)

The BAD_POOL_HEADER bug check has a value of 0x00000019. This indicates that a pool header is corrupt.

The following parameters are displayed on the blue screen. Parameter 1 indicates the type of violation. The meaning of the other parameters depends on the value of Parameter 1.

The pool is already corrupted at the time of the current request.

This may or may not be due to the caller.

The internal pool links must be walked to figure out a possible cause of the problem.

Then you can use special pool for the suspect pool tags, or use Driver Verifier on the suspect driver. The !analyze extension may be of help in pinpointing the suspect driver, but this is frequently not the case with pool corrupters.

STOP 0x0000001A: MEMORY_MANAGEMENT    (go to top of page)

The MEMORY_MANAGEMENT bug check has a value of 0x0000001A. This indicates that a severe memory management error occurred.

The following parameters are displayed on the blue screen. Parameter 1 is the only parameter of interest; this identifies the exact violation.

STOP 0x0000001B: PFN_SHARE_COUNT    (go to top of page)

The PFN_SHARE_COUNT bug check has a value of 0x0000001B.

This bug check appears very infrequently.

STOP 0x0000001C: PFN_REFERENCE_COUNT    (go to top of page)

The PFN_REFERENCE_COUNT bug check has a value of 0x0000001C.

This bug check appears very infrequently.

STOP 0x0000001D: NO_SPIN_LOCK_AVAILABLE    (go to top of page)

The NO_SPIN_LOCK_AVAILABLE bug check has a value of 0x0000001D.

This bug check appears very infrequently.

STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED    (go to top of page)

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.

The following parameters are displayed on the blue screen.

This is a very common bug check. To interpret it, you must identify which exception was generated.

Common exception codes include:

• 0x80000002: STATUS_DATATYPE_MISALIGNMENT

  An unaligned data reference was encountered.

• 0x80000003: STATUS_BREAKPOINT

  A breakpoint or ASSERT was encountered when no kernel debugger was attached to the system.

• 0xC0000005: STATUS_ACCESS_VIOLATION

  A memory access violation occurred. (Parameter 4 of the bug check is the address that the driver attempted to access.)

For a complete list of exception codes, see the ntstatus.h file located in the inc directory of the Windows Driver Kit.

If you are not equipped to debug this problem, you should use some basic troubleshooting techniques. If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates. Try changing video adapters. Check with your hardware vendor for any BIOS updates. Disable BIOS memory options such as caching or shadowing.

If you plan to debug this problem, you may find it difficult to obtain a stack trace. Parameter 2 (the exception address) should pinpoint the driver or function that caused this problem.

If exception code 0x80000003 occurs, this indicates that a hard-coded breakpoint or assertion was hit, but the system was started with the /NODEBUG switch. This problem should rarely occur. If it occurs repeatedly, make sure a kernel debugger is connected and the system is started with the /DEBUG switch.

If exception code 0x80000002 occurs, the trap frame will supply additional information.

If the specific cause of the exception is unknown, the following should be considered:

Hardware incompatibility. First, make sure that any new hardware installed is listed in the Microsoft Windows Marketplace Tested Products List.

Faulty device driver or system service. In addition, a faulty device driver or system service might be responsible for this error. Hardware issues, such as BIOS incompatibilities, memory conflicts, and IRQ conflicts can also generate this error.

If a driver is listed by name within the bug check message, disable or remove that driver. Disable or remove any drivers or services that were recently added. If the error occurs during the startup sequence and the system partition is formatted with NTFS file system, you might be able to use Safe Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process in Safe Mode, you need to start the computer by using the Recovery Console to access the file.

If the problem is associated with Win32k.sys, the source of the error might be a third-party remote control program. If such software is installed, the service can be removed by starting the system using the Recovery Console and deleting the offending system service file.

Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing bug check 0x1E. Disabling memory caching of the BIOS might also resolve the error. You should also run hardware diagnostics, especially the memory scanner, supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer.

The error that generates this message can occur after the first restart during Windows Setup, or after Setup is finished. A possible cause of the error is a system BIOS incompatibility. BIOS problems can be resolved by upgrading the system BIOS version.

1. Use the kb (Display Stack Backtrace) command to display parameters in the stack trace. Look for the call to NT!PspUnhandledExceptionInSystemThread. (If this function is not listed, see the note below.)
2. The first parameter to NT!PspUnhandledExceptionInSystemThread is a pointer to a structure, which contains pointers to an except statement:typedef struct _EXCEPTION_POINTERS {
       PEXCEPTION_RECORD ExceptionRecord;
       PCONTEXT ContextRecord;
       } EXCEPTION_POINTERS, *PEXCEPTION_POINTERS;
   

   
   ULONG PspUnhandledExceptionInSystemThread(
       IN PEXCEPTION_POINTERS ExceptionPointers
       )
   
   

   Use the dd (Display Memory) command on that address to display the necessary data.

3. The first retrieved value is an exception record and the second is a context record. Use the .exr (Display Exception Record) command and the .cxr (Display Context Record) command with these two values as their arguments, respectively.
4. After the .cxr command executes, use the kb command to display a stack trace that is based on the context record information. This stack trace indicates the calling stack where the unhandled exception occurred.

Note  This procedure assumes that you can locate NT!PspUnhandledExceptionInSystemThread. However, in some cases (such as an access violation crash) you will not be able to do this. In that case, look for ntoskrnl!KiDispatchException. The third parameter passed to this function is a trap frame address. Use the .trap (Display Trap Frame) command with this address to set the Register Context to the proper value. You can then perform stack traces and issue other commands.

Here is an example of bug check 0x1E on an x86 processor:

kd> .bugcheck                 get the bug check data
Bugcheck code 0000001e
Arguments c0000005 8013cd0a 00000000 0362cffff

kd> kb                        start with a stack trace 
FramePtr  RetAddr   Param1   Param2   Param3   Function Name 
8013ed5c  801263ba  00000000 00000000 fe40cb00 NT!_DbgBreakPoint 
8013eecc  8013313c  0000001e c0000005 8013cd0a NT!_KeBugCheckEx+0x194
fe40cad0  8013318e  fe40caf8 801359ff fe40cb00 NT!PspUnhandledExceptionInSystemThread+0x18
fe40cad8  801359ff  fe40cb00 00000000 fe40cb00 NT!PspSystemThreadStartup+0x4a
fe40cf7c  8013cb8e  fe43a44c ff6ce388 00000000 NT!_except_handler3+0x47
00000000  00000000  00000000 00000000 00000000 NT!KiThreadStartup+0xe

kd> dd fe40caf8 L2            dump EXCEPTION_POINTERS structure
0xFE40CAF8  fe40cd88 fe40cbc4                   ..@...@.

kd> .exr fe40cd88             first DWORD is the exception record
Exception Record @ FE40CD88:
   ExceptionCode: c0000005
  ExceptionFlags: 00000000
  Chained Record: 00000000
ExceptionAddress: 8013cd0a
NumberParameters: 00000002
   Parameter[0]: 00000000
   Parameter[1]: 0362cfff

kd> .cxr fe40cbc4             second DWORD is the context record
CtxFlags: 00010017
eax=00087000 ebx=00000000 ecx=03ff0000 edx=ff63d000 esi=0362cfff edi=036b3fff
eip=8013cd0a esp=fe40ce50 ebp=fe40cef8 iopl=0         nv dn ei pl nz ac po cy
vip=0    vif=0
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010617
0x8013cd0a  f3a4             rep movsb

kd> kb                        kb gives stack for context record
ChildEBP RetAddr  Args to Child
fe40ce54 80402e09 ff6c4000 ff63d000 03ff0000 NT!_RtlMoveMemory@12+0x3e
fe40ce68 80403c18 ffbc0c28 ff6ce008 ff6c4000 HAL!_HalpCopyBufferMap@20+0x49
fe40ce9c fe43b1e4 ff6cef90 ffbc0c28 ff6ce009 HAL!_IoFlushAdapterBuffers@24+0x148
fe40ceb8 fe4385b4 ff6ce388 6cd00800 ffbc0c28 QIC117!_kdi_FlushDMABuffers@20+0x28
fe40cef8 fe439894 ff6cd008 ffb6c820 fe40cf4c QIC117!_cqd_CmdReadWrite@8+0x26e
fe40cf18 fe437d92 ff6cd008 ffb6c820 ff6e4e50 QIC117!_cqd_DispatchFRB@8+0x210
fe40cf30 fe43a4f5 ff6cd008 ffb6c820 00000000 QIC117!_cqd_ProcessFRB@8+0x134
fe40cf4c 80133184 ff6ce388 00000000 00000000 QIC117!_kdi_ThreadRun@4+0xa9
fe40cf7c 8013cb8e fe43a44c ff6ce388 00000000 NT!_PspSystemThreadStartup@8+0x40

STOP 0x0000001F: SHARED_RESOURCE_CONV_ERROR    (go to top of page)

The SHARED_RESOURCE_CONV_ERROR bug check has a value of 0x0000001F.

This bug check appears very infrequently.

STOP 0x00000020: KERNEL_APC_PENDING_DURING_EXIT    (go to top of page)

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.

The following parameters are displayed on the blue screen.

The key data item is the thread's APC disable count (Parameter 2). If this is non-zero, it will indicate the source of the problem.

The APC disable count is decremented each time a driver calls KeEnterCriticalRegion, KeWaitForSingleObject, KeWaitForMultipleObjects, KeWaitForMutexObject, or FsRtlEnterFileSystem. The APC disable count is incremented each time a driver calls KeLeaveCriticalRegion, KeReleaseMutex, or FsRtlExitFileSystem.

Since these calls should always be in pairs, this value should be zero when a thread exits. A negative value indicates that a driver has disabled APC calls without re-enabling them. A positive value indicates that the reverse is true.

If you ever see this error, be very suspicious of all drivers installed on the machine — especially unusual or non-standard drivers.

This current IRQL (Parameter 3) should be zero. If it is not, that a driver's cancellation routine may have caused this bug check by returning at an elevated IRQL. In this case, carefully note what was running (and what was closing) at the time of the crash, and note all of the installed drivers at the time of the crash. The cause in this case is usually a severe bug in a driver.

STOP 0x00000021: QUOTA_UNDERFLOW    (go to top of page)

The QUOTA_UNDERFLOW bug check has a value of 0x00000021. This indicates that quota charges have been mishandled by returning more quota to a particular block than was previously charged.

The following parameters are displayed on the blue screen.

STOP 0x00000022: FILE_SYSTEM    (go to top of page)

The FILE_SYSTEM bug check has a value of 0x00000022.

This bug check appears very infrequently.

STOP 0x00000023: FAT_FILE_SYSTEM    (go to top of page)

The FAT_FILE_SYSTEM bug check has a value of 0x00000023. This indicates that a problem occurred in the FAT file system.

The following parameters are displayed on the blue screen.

One possible cause of this bug check is disk corruption. Corruption in the file system or bad blocks (sectors) on the disk can induce this error. Corrupted SCSI and IDE drivers can also adversely affect the system's ability to read and write to the disk, thus causing the error.

Another possible cause is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.

To debug this problem: Use the .cxr (Display Context Record) command with Parameter 3, and then use kb (Display Stack Backtrace).

To resolve a disk corruption problem: Check Event Viewer for error messages from SCSI and FASTFAT (System Log) or Autochk (Application Log) that might help pinpoint the device or driver that is causing the error. Try disabling any virus scanners, backup programs, or disk defragmenter tools that continually monitor the system. You should also run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer. Run Chkdsk /f /r to detect and resolve any file system structural corruption. You must restart the system before the disk scan begins on a system partition.

To resolve a nonpaged pool memory depletion problem: Add new physical memory to the computer. This will increase the quantity of nonpaged pool memory available to the kernel.

STOP 0x00000024: NTFS_FILE_SYSTEM    (go to top of page)

The NTFS_FILE_SYSTEM bug check has a value of 0x00000024. This indicates a problem occurred in ntfs.sys, the driver file that allows the system to read and write to NTFS drives.

The following parameters are displayed on the blue screen.

One possible cause of this bug check is disk corruption. Corruption in the NTFS file system or bad blocks (sectors) on the hard disk can induce this error. Corrupted SCSI and IDE drivers can also adversely affect the system's ability to read and write to disk, thus causing the error.

Another possible cause is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.

To debug this problem: Use the .cxr (Display Context Record) command with Parameter 3, and then use kb (Display Stack Backtrace).

To resolve a disk corruption problem: Check Event Viewer for error messages from SCSI and FASTFAT (System Log) or Autochk (Application Log) that might help pinpoint the device or driver that is causing the error. Try disabling any virus scanners, backup programs, or disk defragmenter tools that continually monitor the system. You should also run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer. Run Chkdsk /f /r to detect and resolve any file system structural corruption. You must restart the system before the disk scan begins on a system partition.

To resolve a nonpaged pool memory depletion problem: Either add new physical memory to the computer (thus increasing the quantity of nonpaged pool memory available to the kernel), or reduce the number of files on the Services for Macintosh (SFM) volume.

STOP 0x00000025: NPFS_FILE_SYSTEM    (go to top of page)

The NPFS_FILE_SYSTEM bug check has a value of 0x00000025. This indicates that a problem occurred in the NPFS file system.

The following parameters are displayed on the blue screen.

One possible cause of this bug check is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.

To resolve a nonpaged pool memory depletion problem: Add new physical memory to the computer. This will increase the quantity of nonpaged pool memory available to the kernel.

STOP 0x00000026: CDFS_FILE_SYSTEM    (go to top of page)

The CDFS_FILE_SYSTEM bug check has a value of 0x00000026. This indicates that a problem occurred in the CD file system.

The following parameters are displayed on the blue screen.

One possible cause of this bug check is disk corruption. Corruption in the file system or bad blocks (sectors) on the disk can induce this error. Corrupted SCSI and IDE drivers can also adversely affect the system's ability to read and write to the disk, thus causing the error.

Another possible cause is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.

To debug this problem: Use the .cxr (Display Context Record) command with Parameter 3, and then use kb (Display Stack Backtrace).

To resolve a disk corruption problem: Check Event Viewer for error messages from SCSI and FASTFAT (System Log) or Autochk (Application Log) that might help pinpoint the device or driver that is causing the error. Try disabling any virus scanners, backup programs, or disk defragmenter tools that continually monitor the system. You should also run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer. Run Chkdsk /f /r to detect and resolve any file system structural corruption. You must restart the system before the disk scan begins on a system partition.

To resolve a nonpaged pool memory depletion problem: Add new physical memory to the computer. This will increase the quantity of nonpaged pool memory available to the kernel.

STOP 0x00000027: RDR_FILE_SYSTEM    (go to top of page)

The RDR_FILE_SYSTEM bug check has a value of 0x00000027. This indicates that a problem occurred in the SMB redirector file system.

The following parameters are displayed on the blue screen.

One possible cause of this bug check is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.

To debug this problem: Use the .cxr (Display Context Record) command with Parameter 3, and then use kb (Display Stack Backtrace).

To resolve a nonpaged pool memory depletion problem: Add new physical memory to the computer. This will increase the quantity of nonpaged pool memory available to the kernel.

STOP 0x00000028: CORRUPT_ACCESS_TOKEN    (go to top of page)

The CORRUPT_ACCESS_TOKEN bug check has a value of 0x00000028.

This bug check appears very infrequently.

STOP 0x00000029: SECURITY_SYSTEM    (go to top of page)

The SECURITY_SYSTEM bug check has a value of 0x00000029.

This bug check appears very infrequently.

STOP 0x0000002A: INCONSISTENT_IRP    (go to top of page)

The INCONSISTENT_IRP bug check has a value of 0x0000002A. This indicates that an IRP was found to contain inconsistent information.

The following parameters are displayed on the blue screen.

An IRP was discovered to be in an inconsistent state. Usually this means some field of the IRP was inconsistent with the remaining state of the IRP. An example would be an IRP that was being completed, but was still marked as being queued to a driver's device queue.

This bug check code is not currently being used in the system, but exists for debugging purposes.

STOP 0x0000002B: PANIC_STACK_SWITCH    (go to top of page)

The PANIC_STACK_SWITCH bug check has a value of 0x0000002B. This indicates that the kernel mode stack was overrun.

The following parameters are displayed on the blue screen.

This error normally appears when a kernel-mode driver uses too much stack space. It can also appear when serious data corruption occurs in the kernel.

STOP 0x0000002C: PORT_DRIVER_INTERNAL    (go to top of page)

The PORT_DRIVER_INTERNAL bug check has a value of 0x0000002C.

This bug check appears very infrequently.

STOP 0x0000002D: SCSI_DISK_DRIVER_INTERNAL    (go to top of page)

The SCSI_DISK_DRIVER_INTERNAL bug check has a value of 0x0000002D.

This bug check appears very infrequently.

STOP 0x0000002E: DATA_BUS_ERROR    (go to top of page)

The DATA_BUS_ERROR bug check has a value of 0x0000002E. This typically indicates that a parity error in system memory has been detected.

The following parameters are displayed on the blue screen.

This error is almost always caused by a hardware problem — a configuration issue, defective hardware, or incompatible hardware.

The most common hardware problems that can cause this error are defective RAM, Level 2 (L2) RAM cache errors, or video RAM errors. Hard disk corruption can also cause this error.

This bug check can also be caused when a device driver attempts to access an address in the 0x8xxxxxxx range that does not exist (in other words, that does not have a physical address mapping).

Resolving a hardware problem: If hardware has recently been added to the system, remove it to see if the error recurs.

If existing hardware has failed, remove or replace the faulty component. You should run hardware diagnostics supplied by the system manufacturer to determine which hardware component has failed. For details on these procedures, see the owner's manual for your computer. Check that all adapter cards in the computer are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure that adapter card contacts are clean.

If the problem occurs on a newly installed system, check the availability of updates for the BIOS, the SCSI controller or network cards. Updates of this kind are typically available on the Web site or the bulletin board system (BBS) of the hardware manufacturer.

If the error occurs after installing a new or updated device driver, the driver should be removed or replaced. If, under this circumstance, the error occurs during startup and the system partition is formatted with NTFS, you might be able to use Safe Mode to rename or delete the faulty driver.

If the driver is used as part of the system startup process in Safe Mode, you need to start the computer using the Recovery Console in order to access the file.

For additional error messages that might help pinpoint the device or driver that is causing the error, check the System Log in Event Viewer. Disabling memory caching or shadowing in the BIOS might also resolve this error. In addition, check the system for viruses, using any up-to-date commercial virus scanning software that examines the Master Boot Record of the hard disk. All Windows file systems can be infected by viruses.

Resolving a hard disk corruption problem: Run Chkdsk /f /r on the system partition. You must restart the system before the disk scan begins. If you cannot start the system due to the error, use the Recovery Console and run Chkdsk /r.

Warning  If your system partition is formatted with the file allocation table (FAT) file system, the long filenames used by Windows can be damaged if Scandisk or another Microsoft MS-DOS-based hard disk tool is used to verify the integrity of your hard disk from MS-DOS. Always use the version of Chkdsk that matches your Windows version.

STOP 0x0000002F: INSTRUCTION_BUS_ERROR    (go to top of page)

The INSTRUCTION_BUS_ERROR bug check has a value of 0x0000002F.

This bug check appears very infrequently.

STOP 0x00000030: SET_OF_INVALID_CONTEXT    (go to top of page)

The SET_OF_INVALID_CONTEXT bug check has a value of 0x00000030. This indicates that the stack pointer in a trap frame had an invalid value.

The following parameters are displayed on the blue screen.

This bug check occurs when some routine attempts to set the stack pointer in the trap frame to a lower value than the current stack pointer value.

If this error were not caught, it would cause the kernel to run with a stack pointer pointing to stack which is no longer valid.

STOP 0x00000031: PHASE0_INITIALIZATION_FAILED    (go to top of page)

The PHASE0_INITIALIZATION_FAILED bug check has a value of 0x00000031. This indicates that system initialization failed.

None

System initialization failed at a very early stage.

A debugger is required to analyze this.

STOP 0x00000032: PHASE1_INITIALIZATION_FAILED    (go to top of page)

The PHASE1_INITIALIZATION_FAILED bug check has a value of 0x00000032. This indicates that system initialization failed.

The following parameters are displayed on the blue screen.

STOP 0x00000033: UNEXPECTED_INITIALIZATION_CALL    (go to top of page)

The UNEXPECTED_INITIALIZATION_CALL bug check has a value of 0x00000033.

This bug check appears very infrequently.

STOP 0x00000034: CACHE_MANAGER    (go to top of page)

The CACHE_MANAGER bug check has a value of 0x00000034. This indicates that a problem occurred in the file system's cache manager.

The following parameters are displayed on the blue screen.

One possible cause of this bug check is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.

To resolve a nonpaged pool memory depletion problem: Add new physical memory to the computer. This will increase the quantity of nonpaged pool memory available to the kernel.

STOP 0x00000035: NO_MORE_IRP_STACK_LOCATIONS    (go to top of page)

The NO_MORE_IRP_STACK_LOCATIONS bug check has a value of 0x00000035. This bug check occurs when the IoCallDriver packet has no more stack locations remaining.

The following parameters are displayed on the blue screen.

A higher-level driver has attempted to call a lower-level driver through the IoCallDriver interface, but there are no more stack locations in the packet. This will prevent the lower-level driver from accessing its parameters.

This is a disastrous situation, since the higher level driver is proceeding as if it has filled in the parameters for the lower level driver (as required). But since there is no stack location for the latter driver, the former has actually written off the end of the packet. This means that some other memory has been corrupted as well.

STOP 0x00000036: DEVICE_REFERENCE_COUNT_NOT_ZERO    (go to top of page)

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.

The following parameters are displayed on the blue screen.

A device driver has attempted to delete one of its device objects from the system, but the reference count for that object was non-zero.

This means there are still outstanding references to the device. (The reference count indicates the number of reasons why this device object cannot be deleted.)

This is a bug in the calling device driver.

STOP 0x00000037: FLOPPY_INTERNAL_ERROR    (go to top of page)

The FLOPPY_INTERNAL_ERROR bug check has a value of 0x00000037.

This bug check appears very infrequently.

STOP 0x00000038: SERIAL_DRIVER_INTERNAL    (go to top of page)

The SERIAL_DRIVER_INTERNAL bug check has a value of 0x00000038.

This bug check appears very infrequently.

STOP 0x00000039: SYSTEM_EXIT_OWNED_MUTEX    (go to top of page)

The SYSTEM_EXIT_OWNED_MUTEX bug check has a value of 0x00000039. This indicates that the worker routine returned without releasing the mutex object that it owned.

The following parameters are displayed on the blue screen.

The worker routine returned while it still owned a mutex object. The current worker thread will proceed to run other unrelated work items, and the mutex will never be released.

A debugger is required to analyze this problem. To find the driver that caused the error, use the ln (List Nearest Symbols) debugger command:

kd> ln address

Where address is the worker routine given in Parameter 1.

STOP 0x0000003A: SYSTEM_UNWIND_PREVIOUS_USER    (go to top of page)

The SYSTEM_UNWIND_PREVIOUS_USER bug check has a value of 0x0000003A.

This bug check appears very infrequently.

STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION    (go to top of page)

The SYSTEM_SERVICE_EXCEPTION bug check has a value of 0x0000003B. This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

The following parameters are displayed on the blue screen.

This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

STOP 0x0000003C: INTERRUPT_UNWIND_ATTEMPTED    (go to top of page)

The INTERRUPT_UNWIND_ATTEMPTED bug check has a value of 0x0000003C.

This bug check appears very infrequently.

STOP 0x0000003D: INTERRUPT_EXCEPTION_NOT_HANDLED    (go to top of page)

The INTERRUPT_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000003D.

This bug check appears very infrequently.

STOP 0x0000003E: MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED    (go to top of page)

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.

None

In order to be symmetric, all processors must be of the same type and level. This system contains processors of different types (for example, a Pentium processor and an 80486 processor).

STOP 0x0000003F: NO_MORE_SYSTEM_PTES    (go to top of page)

The NO_MORE_SYSTEM_PTES bug check has a value of 0x0000003F. This is the result of a system which has performed too many I/O actions. This has resulted in fragmented system page table entries (PTE).

The following parameters are displayed on the blue screen.

In almost all cases, the system is not actually out of PTEs. Rather, a driver has requested a large block of memory, but there is no contiguous block of sufficient size to satisfy this request.

Often video drivers will allocate large amounts of kernel memory that must succeed. Some backup programs do the same.

A possible work-around: Modify the registry to increase the total number of system PTEs. If this does not help, remove any recently-installed software, especially backup utilities or disk-intensive applications.

Debugging the problem: The following method can be used to debug bug check 0x3F.

First, get a stack trace, and use the !sysptes 3 extension command.

Then set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\TrackPtes equal to DWORD 1, and reboot. This will cause the system to save stack traces.

This allows you to display more detailed information about the PTE owners. For example:

0: kd> !sysptes 4

0x2c47 System PTEs allocated to mapping locked pages

VA       MDL     PageCount  Caller/CallersCaller
f0e5db48 eb6ceef0        1 ntkrpamp!MmMapLockedPages+0x15/ntkrpamp!IopfCallDriver+0x35
f0c3fe48 eb634bf0        1 netbt!NbtTdiAssociateConnection+0x1f/netbt!DelayedNbtProcessConnect+0x17c
f0db38e8 eb65b880        1 mrxsmb!SmbMmAllocateSessionEntry+0x89/mrxsmb!SmbCepInitializeExchange+0xda
f8312568 eb6df880        1 rdbss!RxCreateFromNetRoot+0x3d7/rdbss!RxCreateFromNetRoot+0x93
f8363908 eb685880        1 mrxsmb!SmbMmAllocateSessionEntry+0x89/mrxsmb!SmbCepInitializeExchange+0xda
f0c54248 eb640880        1 rdbss!RxCreateFromNetRoot+0x3d7/rdbss!RxCreateFromNetRoot+0x93
f0ddf448 eb5f3160        1 mrxsmb!MrxSmbUnalignedDirEntryCopyTail+0x387/mrxsmb!MRxSmbCoreInformation+0x36
f150bc08 eb6367b0        1 mrxsmb!MrxSmbUnalignedDirEntryCopyTail+0x387/mrxsmb!MRxSmbCoreInformation+0x36
f1392308 eb6fba70        1 netbt!NbtTdiOpenAddress+0x1fb/netbt!DelayedNbtProcessConnect+0x17c
eb1bee64 edac5000      200 VIDEOPRT!pVideoPortGetDeviceBase+0x118/VIDEOPRT!VideoPortMapMemory+0x45
f139b5a8 edd4b000       12 rdbss!FsRtlCopyWrite2+0x34/rdbss!RxDriverEntry+0x149
eb41f400 ede92000       20 VIDEOPRT!pVideoPortGetDeviceBase+0x139/VIDEOPRT!VideoPortGetDeviceBase+0x1b
eb41f198 edf2a000       20 NDIS!NdisReadNetworkAddress+0x3a/NDIS!NdisFreeSharedMemory+0x58
eb41f1e4 eb110000       10 VIDEOPRT!pVideoPortGetDeviceBase+0x139/VIDEOPRT!VideoPortGetDeviceBase+0x1b
......

If the system runs out of PTEs again after the TrackPtes registry value has been set, bug check 0xD8 (DRIVER_USED_EXCESSIVE_PTES) will be issued instead of 0x3F. The name of the driver causing this error will be displayed as well.

STOP 0x00000040: TARGET_MDL_TOO_SMALL    (go to top of page)

The TARGET_MDL_TOO_SMALL bug check has a value of 0x00000040. This indicates that a driver has improperly used IoBuildPartialMdl.

None

This is a driver bug. A driver has called the IoBuildPartialMdl function and passed it an MDL to map part of a source MDL, but the target MDL is not large enough to map the entire range of addresses requested.

The source and target MDLs, as well as the address range length to be mapped, are the first, second, and fourth arguments to the IoBuildPartialMdl function. Therefore, doing a stack trace on this particular function might help during the debugging process. Ensure that your code is correctly calculating the necessary size for the target MDL for the address range length that you are passing to this function.

STOP 0x00000041: MUST_SUCCEED_POOL_EMPTY    (go to top of page)

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.

The following parameters are displayed on the blue screen.

In Microsoft Windows 2000, only a small amount of must-succeed pool is permitted. In Windows XP and later, no driver is permitted to request must-succeed pool.

If a must-succeed request cannot be filled, this bug check is issued.

Replace or rewrite the driver which is making the request. A driver should not request must-succeed pool. Instead, it should ask for normal pool and gracefully handle the scenario where the pool is temporarily empty.

The kb (Display Stack Backtrace) command will show the driver that caused the error.

Additionally, it is possible that a second component has depleted the must-succeed pool. To determine if this is the case, first use the kb command. Then use !vm 1 to display total pool usage, !poolused 2 to display per-tag nonpaged pool usage, and !poolused 4 to display per-tag paged pool usage. The component associated with the tag using the most pool is probably the source of the problem.

STOP 0x00000042: ATDISK_DRIVER_INTERNAL    (go to top of page)

The ATDISK_DRIVER_INTERNAL bug check has a value of 0x00000042.

This bug check appears very infrequently.

STOP 0x00000043: NO_SUCH_PARTITION    (go to top of page)

The NO_SUCH_PARTITION bug check has a value of 0x00000043.

This bug check appears very infrequently.

STOP 0x00000044: MULTIPLE_IRP_COMPLETE_REQUESTS    (go to top of page)

The MULTIPLE_IRP_COMPLETE_REQUESTS bug check has a value of 0x00000044. This indicates that a driver has tried to requested an IRP be completed that is already complete.

The following parameters are displayed on the blue screen.

A driver has called IoCompleteRequest to ask that an IRP be completed, but the packet has already been completed.

This is a tough bug to find because the simplest case — a driver that attempted to complete its own packet twice — is usually not the source of the problem. More likely, two separate drivers each believe that they own the packet, and each has attempted to complete it. The first request succeeds, and the second fails, resulting in this bug check.

Tracking down which drivers in the system caused the error is difficult, because the trail of the first driver has been covered by the second. However, the driver stack for the current request can be found by examining the device object fields in each of the stack locations.

STOP 0x00000045: INSUFFICIENT_SYSTEM_MAP_REGS    (go to top of page)

The INSUFFICIENT_SYSTEM_MAP_REGS bug check has a value of 0x00000045.

This bug check appears very infrequently.

STOP 0x00000046: DEREF_UNKNOWN_LOGON_SESSION    (go to top of page)

The DEREF_UNKNOWN_LOGON_SESSION bug check has a value of 0x00000046.

This bug check appears very infrequently.

STOP 0x00000047: REF_UNKNOWN_LOGON_SESSION    (go to top of page)

The REF_UNKNOWN_LOGON_SESSION bug check has a value of 0x00000047.

This bug check appears very infrequently.

STOP 0x00000048: CANCEL_STATE_IN_COMPLETED_IRP    (go to top of page)

The CANCEL_STATE_IN_COMPLETED_IRP bug check has a value of 0x00000048. This indicates that an I/O request packet (IRP) was completed, and then was subsequently canceled.

The following parameters are displayed on the blue screen.

An IRP that had a Cancel routine set was completed normally, without cancellation. But after it was complete, a driver called the IRP's Cancel routine.

This could be caused by a driver that completed the IRP and then attempted to cancel it.

It could also be caused by two drivers each trying to access the same IRP in an improper way.

The cancel routine parameter can be used to determine which driver or stack caused the bug check.

STOP 0x00000049: PAGE_FAULT_WITH_INTERRUPTS_OFF    (go to top of page)

The PAGE_FAULT_WITH_INTERRUPTS_OFF bug check has a value of 0x00000049.

This bug check appears very infrequently.

STOP 0x0000004A: IRQL_GT_ZERO_AT_SYSTEM_SERVICE    (go to top of page)

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.

The following parameters are displayed on the blue screen.

STOP 0x0000004B: STREAMS_INTERNAL_ERROR    (go to top of page)

The STREAMS_INTERNAL_ERROR bug check has a value of 0x0000004B.

This bug check appears very infrequently.

STOP 0x0000004C: FATAL_UNHANDLED_HARD_ERROR    (go to top of page)

The FATAL_UNHANDLED_HARD_ERROR bug check has a value of 0x0000004C.

This bug check appears very infrequently.

STOP 0x0000004D: NO_PAGES_AVAILABLE    (go to top of page)

The NO_PAGES_AVAILABLE bug check has a value of 0x0000004D. This indicates that no free pages are available to continue operations.

The following parameters are displayed on the blue screen.

To see general memory statistics, use the !vm 3 extension.

This bug check can occur for any of the following reasons:

• A driver has blocked, deadlocking the modified or mapped page writers. Examples of this include mutex deadlocks or accesses to paged out memory in file system drivers or filter drivers. This indicates a driver bug.

  If Parameter 1 or Parameter 2 is large, then this is a possibility. Use !vm 3.

• A storage driver is not processing requests. Examples of this are stranded queues and non-responding drives. This indicates a driver bug.

  If Parameter 1 or Parameter 2 is large, then this is a possibility. Use !vm 8, followed by !process 0 7.

• A high-priority realtime thread has starved the balance set manager from trimming pages from the working set, or starved the modified page writer from writing them out. This indicates a bug in the component that created this thread.

  This situation is difficult to analyze. Try using !ready. Try also !process 0 7 to list all threads and see if any have accumulated excessive kernel time as well as what their current priorities are. Such processes may have blocked out the memory management threads from making pages available.

• Windows XP and Windows 2000: Not enough pool is available for the storage stack to write out modified pages. This indicates a driver bug.

  If Parameter 3 is small, then this is a possibility. Use !vm and !poolused 2.

• Windows 2000: All the processes have been trimmed to their minimums and all modified pages written, but still no memory is available. The freed memory must be stuck in transition pages with non-zero reference counts — thus they cannot be put on the freelist.

  A driver is neglecting to unlock the pages preventing the reference counts from going to zero which would free the pages. This may be due to transfers that never finish, causing the driver routines to run endlessly, or to other driver bugs.

  If Parameter 4 is large, then this is a possibility. But it is very hard to find the driver. Try the !process 0 1 extension and look for any drivers that have a lot of locked pages.

If the problem cannot be found, then try booting with a kernel debugger attached from the beginning, and monitor the situation.

STOP 0x0000004E: PFN_LIST_CORRUPT    (go to top of page)

The PFN_LIST_CORRUPT bug check has a value of 0x0000004E. This indicates that the page frame number (PFN) list is corrupted.

The following parameters are displayed on the blue screen. Parameter 1 indicates the type of violation. The meaning of the other parameters depends on the value of Parameter 1.

This error is typically caused by a driver passing a bad memory descriptor list. For example, the driver might have called MmUnlockPages twice with the same list.

If a kernel debugger is available, examine the stack trace.

STOP 0x0000004F: NDIS_INTERNAL_ERROR    (go to top of page)

The NDIS_INTERNAL_ERROR bug check has a value of 0x0000004F.

This bug check appears very infrequently.

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA    (go to top of page)

The PAGE_FAULT_IN_NONPAGED_AREA bug check has a value of 0x00000050. This indicates that invalid system memory has been referenced.

The following parameters are displayed on the blue screen.

If the driver responsible for the error can be identified, its name is printed on the blue screen and stored in memory at the location (PUNICODE_STRING) KiBugCheckDriver.

Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

Another common cause is the installation of a faulty system service.

Antivirus software can also trigger this error, as can a corrupted NTFS volume.

Resolving a faulty hardware problem: If hardware has been added to the system recently, remove it to see if the error recurs. If existing hardware has failed, remove or replace the faulty component. You should run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer.

Resolving a faulty system service problem: Disable the service and confirm that this resolves the error. If so, contact the manufacturer of the system service about a possible update. If the error occurs during system startup, restart your computer, and press F8 at the character-mode menu that displays the operating system choices. At the resulting Windows Advanced Options menu, choose the Last Known Good Configuration option. This option is most effective when only one driver or service is added at a time.

Resolving an antivirus software problem: Disable the program and confirm that this resolves the error. If it does, contact the manufacturer of the program about a possible update.

Resolving a corrupted NTFS volume problem: Run Chkdsk /f /r to detect and repair disk errors. You must restart the system before the disk scan begins on a system partition. If the hard disk is SCSI, check for problems between the SCSI controller and the disk.

Finally, check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. Disabling memory caching of the BIOS might also resolve it.

Typically, this address is in freed memory or is simply invalid.

This cannot be protected by a try - except handler — it can only be protected by a probe.

STOP 0x00000051: REGISTRY_ERROR    (go to top of page)

The REGISTRY_ERROR bug check has a value of 0x00000051. This indicates that a severe registry error has occurred.

The following parameters are displayed on the blue screen.

Something has gone wrong with the registry. If a kernel debugger is available, get a stack trace.

This error may indicate that the registry encountered an I/O error while trying to read one of its files. This can be caused by hardware problems or file system corruption.

It may also occur due to a failure in a refresh operation, which is used only in by the security system, and then only when resource limits are encountered.

STOP 0x00000052: MAILSLOT_FILE_SYSTEM    (go to top of page)

The MAILSLOT_FILE_SYSTEM bug check has a value of 0x00000052.

This bug check appears very infrequently.

STOP 0x00000053: NO_BOOT_DEVICE    (go to top of page)

The NO_BOOT_DEVICE bug check has a value of 0x00000053.

This bug check appears very infrequently.

STOP 0x00000054: LM_SERVER_INTERNAL_ERROR    (go to top of page)

The LM_SERVER_INTERNAL_ERROR bug check has a value of 0x00000054.

This bug check appears very infrequently.

STOP 0x00000055: DATA_COHERENCY_EXCEPTION    (go to top of page)

The DATA_COHERENCY_EXCEPTION bug check has a value of 0x00000055.

This bug check appears very infrequently.

STOP 0x00000056: INSTRUCTION_COHERENCY_EXCEPTION    (go to top of page)

The INSTRUCTION_COHERENCY_EXCEPTION bug check has a value of 0x00000056.

This bug check appears very infrequently.

STOP 0x00000057: XNS_INTERNAL_ERROR    (go to top of page)

The XNS_INTERNAL_ERROR bug check has a value of 0x00000057.

This bug check appears very infrequently.

STOP 0x00000058: FTDISK_INTERNAL_ERROR    (go to top of page)

The FTDISK_INTERNAL_ERROR bug check has a value of 0x00000058. This is issued if the system is booted from the wrong copy of a mirrored partition.

None

The hives are indicating that the mirror is valid, but it is not. The hives should actually be pointing to the shadow partition.

This is almost always caused by the primary partition being revived.

Reboot the system from the shadow partition.

STOP 0x00000059: PINBALL_FILE_SYSTEM    (go to top of page)

The PINBALL_FILE_SYSTEM bug check has a value of 0x00000059. This indicates that a problem occurred in the Pinball file system.

The following parameters are displayed on the blue screen.

One possible cause of this bug check is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.

To resolve a nonpaged pool memory depletion problem: Add new physical memory to the computer. This will increase the quantity of nonpaged pool memory available to the kernel.

STOP 0x0000005A: CRITICAL_SERVICE_FAILED    (go to top of page)

The CRITICAL_SERVICE_FAILED bug check has a value of 0x0000005A.

This bug check appears very infrequently.

STOP 0x0000005B: SET_ENV_VAR_FAILED    (go to top of page)

The SET_ENV_VAR_FAILED bug check has a value of 0x0000005B.

This bug check appears very infrequently.

STOP 0x0000005C: HAL_INITIALIZATION_FAILED    (go to top of page)

The HAL_INITIALIZATION_FAILED bug check has a value of 0x0000005C.

This indicates that the HAL initialization failed.

STOP 0x0000005D: UNSUPPORTED_PROCESSOR    (go to top of page)

The UNSUPPORTED_PROCESSOR bug check has a value of 0x0000005D. This indicates that the computer is attempting to run Windows on an unsupported processor.

None

Windows requires a higher-grade processor than the one you are using.

STOP 0x0000005E: OBJECT_INITIALIZATION_FAILED    (go to top of page)

The OBJECT_INITIALIZATION_FAILED bug check has a value of 0x0000005E.

This bug check appears very infrequently.

STOP 0x0000005F: SECURITY_INITIALIZATION_FAILED    (go to top of page)

The SECURITY_INITIALIZATION_FAILED bug check has a value of 0x0000005F.

This bug check appears very infrequently.

STOP 0x00000060: PROCESS_INITIALIZATION_FAILED    (go to top of page)

The PROCESS_INITIALIZATION_FAILED bug check has a value of 0x00000060.

This bug check appears very infrequently.

STOP 0x00000061: HAL1_INITIALIZATION_FAILED    (go to top of page)

The HAL1_INITIALIZATION_FAILED bug check has a value of 0x00000061.

This bug check appears very infrequently.

STOP 0x00000062: OBJECT1_INITIALIZATION_FAILED    (go to top of page)

The OBJECT1_INITIALIZATION_FAILED bug check has a value of 0x00000062.

This bug check appears very infrequently.

STOP 0x00000063: SECURITY1_INITIALIZATION_FAILED    (go to top of page)

The SECURITY1_INITIALIZATION_FAILED bug check has a value of 0x00000063.

This bug check appears very infrequently.

STOP 0x00000064: SYMBOLIC_INITIALIZATION_FAILED    (go to top of page)

The SYMBOLIC_INITIALIZATION_FAILED bug check has a value of 0x00000064.

This bug check appears very infrequently.

STOP 0x00000065: MEMORY1_INITIALIZATION_FAILED    (go to top of page)

The MEMORY1_INITIALIZATION_FAILED bug check has a value of 0x00000065.

This bug check appears very infrequently.

STOP 0x00000066: CACHE_INITIALIZATION_FAILED    (go to top of page)

The CACHE_INITIALIZATION_FAILED bug check has a value of 0x00000066.

This bug check appears very infrequently.

STOP 0x00000067: CONFIG_INITIALIZATION_FAILED    (go to top of page)

The CONFIG_INITIALIZATION_FAILED bug check has a value of 0x00000067. This bug check indicates that the registry configuration failed.

The following parameters appear on the blue screen.

The registry could not allocate the pool that it needed to contain the registry files. This situation should never occur, because the register allocates this pool early enough in system initialization so that plenty of paged pool should be available.

STOP 0x00000068: FILE_INITIALIZATION_FAILED    (go to top of page)

The FILE_INITIALIZATION_FAILED bug check has a value of 0x00000068.

This bug check appears very infrequently.

STOP 0x00000069: IO1_INITIALIZATION_FAILED    (go to top of page)

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.

None

There is very little information available to analyze this error.

Most likely, the setup routine has improperly installed the system, or a user has reconfigured the system.

STOP 0x0000006A: LPC_INITIALIZATION_FAILED    (go to top of page)

The LPC_INITIALIZATION_FAILED bug check has a value of 0x0000006A.

This bug check appears very infrequently.

STOP 0x0000006B: PROCESS1_INITIALIZATION_FAILED    (go to top of page)

The PROCESS1_INITIALIZATION_FAILED bug check has a value of 0x0000006B. This bug check indicates that the initialization of the Microsoft Windows operating system failed.

The following parameters appear on the blue screen.

Any part of the disk subsystem can cause the PROCESS1_INITIALIZATION_FAILED bug check, including bad disks, bad or incorrect cables, mixing different ATA-type devices on the same chain, or drives that are not available becuase of hardware regeneration.

This bug check can also be caused by a missing file from the boot partition or by a driver file that a user accidentally disabled in the Drivers tab.

STOP 0x0000006C: REFMON_INITIALIZATION_FAILED    (go to top of page)

The REFMON_INITIALIZATION_FAILED bug check has a value of 0x0000006C.

This bug check appears very infrequently.

STOP 0x0000006D: SESSION1_INITIALIZATION_FAILED    (go to top of page)

The SESSION1_INITIALIZATION_FAILED bug check has a value of 0x0000006D. This bug check indicates that the initialization of the Microsoft Windows operating system failed.

The following parameters appear on the blue screen.

STOP 0x0000006E: SESSION2_INITIALIZATION_FAILED    (go to top of page)

The SESSION2_INITIALIZATION_FAILED bug check has a value of 0x0000006E. This bug check indicates that the initialization of the Microsoft Windows operating system failed.

The following parameters appear on the blue screen.

STOP 0x0000006F: SESSION3_INITIALIZATION_FAILED    (go to top of page)

The SESSION3_INITIALIZATION_FAILED bug check has a value of 0x0000006F. This bug check indicates that the initialization of the Microsoft Windows operating system initialization.

The following parameters appear on the blue screen.

STOP 0x00000070: SESSION4_INITIALIZATION_FAILED    (go to top of page)

The SESSION4_INITIALIZATION_FAILED bug check has a value of 0x00000070. This bug check indicates that the initialization of the Microsoft Windows operating system failed.

The following parameters appear on the blue screen.

STOP 0x00000071: SESSION5_INITIALIZATION_FAILED    (go to top of page)

The SESSION5_INITIALIZATION_FAILED bug check has a value of 0x00000071. This bug check indicates that the initialization of the Microsoft Windows operating system failed.

The following parameters appear on the blue screen.

STOP 0x00000072: ASSIGN_DRIVE_LETTERS_FAILED    (go to top of page)

The ASSIGN_DRIVE_LETTERS_FAILED bug check has a value of 0x00000072.

This bug check appears very infrequently.

STOP 0x00000073: CONFIG_LIST_FAILED    (go to top of page)

The CONFIG_LIST_FAILED bug check has a value of 0x00000073. This bug check indicates that one of the top-level registry keys, also known as core system hives, cannot be linked in the registry tree.

The following parameters appear on the blue screen.

The registry hive that cannot be linked might be SAM, SECURITY, SOFTWARE, or DEFAULT. The hive is valid, because it was loaded successfully.

Examine Parameter 2 to see why the hive could not be linked in the registry tree. One common cause of this error is that the Windows operating system is out of disk space on the system drive. (In this situation, this parameter is 0xC000017D, STATUS_NO_LOG_SPACE.) Another common problem is that an attempt to allocate pool has failed. (In this situation, Parameter 2 is 0xC000009A, STATUS_INSUFFICIENT_RESOURCES.) You must investigate other status codes.

STOP 0x00000074: BAD_SYSTEM_CONFIG_INFO    (go to top of page)

The BAD_SYSTEM_CONFIG_INFO bug check has a value of 0x00000074. This bug check indicates that there is an error in the registry.

The following parameters appear on the blue screen.

The BAD_SYSTEM_CONFIG_INFO bug check occurs if the SYSTEM hive is corrupt. However, this corruption is unlikely, because the boot loader, known as NT Loader (NTLDR) in versions of Windows prior to Vista, checks a hive for corruption when it loads the hive.

This bug check can also occur if some critical registry keys and values are missing. These keys and values might be missing if a user manually edited the registry.

Try restarting the computer by selecting "last known good configuration" in the boot options.

If the restart does not fix the problem, the registry damage is too extensive. You must reinstall the OS or use the Emergency Repair Disk (ERD) that you previously created by using the Windows Backup tool.

STOP 0x00000075: CANNOT_WRITE_CONFIGURATION    (go to top of page)

The CANNOT_WRITE_CONFIGURATION bug check has a value of 0x00000075. This bug check indicates that the SYSTEM registry hive file cannot be converted to a mapped file.

The following parameters appear on the blue screen.

The CANNOT_WRITE_CONFIGURATION bug check typically occurs if the system is out of pool and the Windows operating system cannot reopen the hive.

This bug check should almost never occur, because the conversion of the hive file occurs early enough during system initialization so that enough pool should be available.

STOP 0x00000076: PROCESS_HAS_LOCKED_PAGES    (go to top of page)

The PROCESS_HAS_LOCKED_PAGES bug check has a value of 0x00000076. This bug check indicates that a driver failed to release locked pages after an I/O operation.

The following parameters appear on the blue screen.

A driver failed to release pages that it locked.

First, use the !search extension on the current process pointer throughout all of physical memory. This extension might find at least one memory descriptor list (MDL) that points to the current process. Next, use !search on each MDL that you find to obtain the I/O request packet (IRP) that points to the current process. From this IRP, you can identify which driver is leaking the pages.

Otherwise, you can detect which driver caused the error by editing the registry:

1. In the \\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management registry key, create or edit the TrackLockedPages value, and then set it equal to DWORD 1.
2. Restart the computer.

The system then saves stack traces, so you can easily identify the driver that caused the problem. If the driver causes the same error again, bug check 0xCB (DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS) is issued, and the name of the driver that causes this error is displayed.

STOP 0x00000077: KERNEL_STACK_INPAGE_ERROR    (go to top of page)