Knowledge (XXG)

Fatal system error

Source 📝

139: 40: 231:
The user will only see the blue screen if the system is not configured to automatically restart (which became the default setting in Windows XP SP2). Otherwise, it appears as though the system simply rebooted (though a blue screen may be visible briefly). In Windows, bug checks are only supported by
219:
If the user has enabled it, the system will also write an entry to the system event log. The log entry contains information about the bug check (including the bug check code and its parameters) as well as a link that will report the bug and provide the user with prescriptive suggestions if the cause
223:
Next, if a kernel debugger is connected and active when the bug check occurs, the system will break into the debugger where the cause of the crash can be investigated. If no debugger is attached, then a blue text screen is displayed that contains information about why the error occurred, which is
215:
When a bug check is issued, a crash dump file will be created if the system is configured to create them. This file contains a "snapshot" of useful low-level information about the system that can be used to debug the root cause of the problem and possibly other things in the background.
255:
documentation both have reference information about most bug checks. The WinDbg package is available as a free download and can be installed by most users. The Windows DDK is larger and more complicated to install.
196:
function. However, this should only be done as a last option when a critical driver is corrupted and is impossible to recover. This design parallels that in
381: 554: 57: 123: 590: 104: 353: 585: 549: 76: 347: 317: 61: 83: 289: 374: 28: 429: 90: 50: 616: 580: 233: 637: 544: 72: 367: 138: 472: 449: 539: 444: 241: 225: 185: 611: 477: 248: 20: 97: 606: 434: 424: 181: 564: 518: 170: 439: 414: 322: 294: 265: 523: 631: 559: 390: 467: 419: 270: 204: 143: 24: 240:, does not halt the system like bug checks do. Instead, it displays the infamous " 513: 404: 173:
halts because it has reached a condition where it can no longer operate safely (
39: 508: 503: 498: 493: 177:
where critical data could be lost or the system damaged in other ways).
197: 252: 188:
can be deliberately caused from a kernel-mode driver with either the
137: 359: 201: 363: 33: 236:. The corresponding system routine in Windows 9x, named 244:" (BSoD) and allows the user to attempt to continue. 599: 573: 532: 486: 460: 397: 237: 193: 189: 64:. Unsourced material may be challenged and removed. 375: 8: 220:of the check is definitive and well-known. 382: 368: 360: 124:Learn how and when to remove this message 281: 16:Error that stops the operating system 7: 62:adding citations to reliable sources 14: 591:List of SMTP server return codes 38: 586:List of FTP server return codes 290:"KeBugCheckEx function (wdm.h)" 49:needs additional citations for 1: 348:Debugging Tools for Windows 654: 23:. For the short film, see 18: 617:2024 CrowdStrike incident 581:List of HTTP status codes 207:concept is very similar. 545:Bad command or file name 354:Bug Check Code Reference 318:"Kernel-Mode Dump Files" 487:Device and data errors 238:SHELL_SYSMODAL_Message 146: 27:. For other uses, see 473:Fatal exception error 228:or bug check screen. 141: 242:blue screen of death 224:commonly known as a 73:"Fatal system error" 58:improve this article 612:Windows wait cursor 550:Halt and Catch Fire 540:Abort, Retry, Fail? 461:Application failure 478:Segmentation fault 410:Fatal system error 356:at Microsoft Learn 350:at Microsoft Learn 326:. 28 December 2023 298:. 25 February 2022 186:fatal system error 151:fatal system error 147: 21:Fatal System Error 19:For the book, see 625: 624: 607:Spinning pinwheel 430:Red Ring of Death 425:Linux kernel oops 182:Microsoft Windows 169:) occurs when an 153:(also known as a 134: 133: 126: 108: 645: 565:Does not compute 519:Not a typewriter 384: 377: 370: 361: 336: 335: 333: 331: 314: 308: 307: 305: 303: 286: 239: 195: 191: 171:operating system 129: 122: 118: 115: 109: 107: 66: 42: 34: 653: 652: 648: 647: 646: 644: 643: 642: 638:Computer errors 628: 627: 626: 621: 595: 569: 528: 482: 456: 440:Screen of death 415:Guru Meditation 393: 388: 344: 339: 329: 327: 323:Microsoft Learn 316: 315: 311: 301: 299: 295:Microsoft Learn 288: 287: 283: 279: 266:Screen of death 262: 232:the Windows NT 213: 130: 119: 113: 110: 67: 65: 55: 43: 32: 17: 12: 11: 5: 651: 649: 641: 640: 630: 629: 623: 622: 620: 619: 614: 609: 603: 601: 597: 596: 594: 593: 588: 583: 577: 575: 571: 570: 568: 567: 562: 557: 552: 547: 542: 536: 534: 530: 529: 527: 526: 524:PC LOAD LETTER 521: 516: 511: 506: 501: 496: 490: 488: 484: 483: 481: 480: 475: 470: 464: 462: 458: 457: 455: 454: 453: 452: 447: 437: 432: 427: 422: 417: 412: 407: 401: 399: 398:System failure 395: 394: 391:Error messages 389: 387: 386: 379: 372: 364: 358: 357: 351: 343: 342:External links 340: 338: 337: 309: 280: 278: 275: 274: 273: 268: 261: 258: 212: 209: 132: 131: 46: 44: 37: 15: 13: 10: 9: 6: 4: 3: 2: 650: 639: 636: 635: 633: 618: 615: 613: 610: 608: 605: 604: 602: 598: 592: 589: 587: 584: 582: 579: 578: 576: 572: 566: 563: 561: 560:Out of memory 558: 556: 553: 551: 548: 546: 543: 541: 538: 537: 535: 531: 525: 522: 520: 517: 515: 512: 510: 507: 505: 502: 500: 497: 495: 492: 491: 489: 485: 479: 476: 474: 471: 469: 466: 465: 463: 459: 451: 448: 446: 443: 442: 441: 438: 436: 433: 431: 428: 426: 423: 421: 418: 416: 413: 411: 408: 406: 403: 402: 400: 396: 392: 385: 380: 378: 373: 371: 366: 365: 362: 355: 352: 349: 346: 345: 341: 325: 324: 319: 313: 310: 297: 296: 291: 285: 282: 276: 272: 269: 267: 264: 263: 259: 257: 254: 250: 245: 243: 235: 229: 227: 221: 217: 210: 208: 206: 203: 199: 187: 183: 178: 176: 172: 168: 164: 160: 156: 152: 145: 140: 136: 128: 125: 117: 106: 103: 99: 96: 92: 89: 85: 82: 78: 75: –  74: 70: 69:Find sources: 63: 59: 53: 52: 47:This article 45: 41: 36: 35: 30: 26: 22: 420:Kernel panic 409: 328:. Retrieved 321: 312: 300:. Retrieved 293: 284: 271:System crash 246: 230: 222: 218: 214: 205:kernel panic 194:KeBugCheckEx 179: 174: 166: 163:kernel error 162: 158: 155:system crash 154: 150: 148: 144:kernel panic 135: 120: 114:January 2011 111: 101: 94: 87: 80: 68: 56:Please help 51:verification 48: 25:System Error 514:lp0 on fire 249:Windows DDK 226:blue screen 29:Fatal error 277:References 211:In Windows 190:KeBugCheck 159:stop error 142:Linux 3.8 84:newspapers 405:Bomb icon 167:bug check 632:Category 555:HTTP 418 509:HTTP 500 504:HTTP 404 499:HTTP 403 494:HTTP 402 260:See also 251:and the 600:Related 435:Sad Mac 198:OpenVMS 98:scholar 253:WinDbg 234:kernel 200:. The 100:  93:  86:  79:  71:  574:Lists 533:Other 468:ABEND 450:Black 330:1 May 302:1 May 165:, or 105:JSTOR 91:books 445:Blue 332:2024 304:2024 247:The 202:Unix 184:, a 175:i.e. 77:news 192:or 180:In 60:by 634:: 320:. 292:. 161:, 157:, 149:A 383:e 376:t 369:v 334:. 306:. 127:) 121:( 116:) 112:( 102:· 95:· 88:· 81:· 54:. 31:.

Index

Fatal System Error
System Error
Fatal error

verification
improve this article
adding citations to reliable sources
"Fatal system error"
news
newspapers
books
scholar
JSTOR
Learn how and when to remove this message

kernel panic
operating system
Microsoft Windows
fatal system error
OpenVMS
Unix
kernel panic
blue screen
kernel
blue screen of death
Windows DDK
WinDbg
Screen of death
System crash
"KeBugCheckEx function (wdm.h)"

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.