How To Repair Meltdown Stop Bsod

How to Fix a Windows Blue Screen of Death (BSOD)

(Paradigm credit: Shutterstock)

Few things are more frustrating. Y'all're in the middle of working on a project, reaching a major milestone in a game or maybe just booting upward your Windows 10 computer and, just like that, the unabridged OS crashes and presents yous with a Blue Screen of Expiry, normally for no immediately apparent reason.

In Windows-speak, the term "Blue Screen of Death" is commonly abbreviated equally BSOD. It describes an error of some kind that hits the operating organization hard enough that it's forced to quit. Microsoft itself labels such errors with "stopcodes." Thus these errors may also be generically named "end errors." Here's an example that shows what a BSOD sometimes looks like:

Understanding the BSOD Screen

The screen starts with an old-fashioned unhappy confront emoticon " :( " (a colon, followed by an open parenthesis). Next, you see a cursory explanation that "Your PC ran into a trouble and needs to restart." Windows writes 1 or more log files when a end error occurs, and so y'all see language about "collecting some error info" and a counter that keeps rails while it's writing that data (shows every bit "25% consummate) above.

Microsoft provides a scannable QR code in modernistic BSODs (lower left) that you can scan with a smartphone and look up that way. The bulletin as well provides a lookup URL for stopcodes, where y'all tin can enter a numeric stopcode (and where you'll see most common stopcodes, including the 1 shown above). The most common stop codes include:

CRITICAL_PROCESS_DIED
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
IRQL_NOT_LESS_OR_EQUAL
VIDEO_TDR_TIMEOUT_DETECTED
PAGE_FAULT_IN_NONPAGED_AREA
SYSTEM_SERVICE_EXCEPTION
DPC_WATCHDOG_VIOLATION

You can also download the Microsoft Error Lookup Tool (current version: Err_6.4.5.exe) to wait up numeric error codes at a command prompt or in PowerShell, if you prefer.

In Windows 10, BSODs Aren't E'er Blue

Before Windows 8 came along in October 2022, BSODs always appeared on nighttime blue screens. These were chock-full of text and instructions (see below). With Windows 8, Microsoft switched to a kinder, gentler format shown in the preceding screencap. They likewise whittled down the information that appears on screen. In fact, the background color in Windows x is sometimes green, which is why you may encounter some of them chosen GSODs ("Green Screens of Decease"). Hither's an case of an one-time-fashioned, pre-Windows-eight BSOD to put this information into historical context:

Making Sense of BSOD Data

Though nobody wants to encounter a BSOD on a Windows PC, they exercise occur from time to time. In the vast majority of cases, the PC will restart itself automatically after an error log, called a crash dump or a dump file (extension .dmp) is created. By default, Windows 10 stores dump files in one of 2 locations.

You can manage crash dumps through Advanced System Settings in Windows x (blazon "Advanced Arrangement Settings" into the search box, and then click "Settings" in the Startup and Recovery pane). You can also choose to toggle "Automated restart" to off here, if you would prefer that any futurity BSODs stay on the screen until y'all go a adventure to see them and write downward (or take motion picture of) any relevant information.

If y'all select "Small memory dump" as the selection for saving crash dumps, such files prove up every bit Minidump.dmp files. For all other selections, the crash dump is named Retention.dmp. Crash dumps go written to the %SystemRoot% folder, which usually expands to C:\Windows. By blueprint, small retentivity dump files are limited to 256KB in size. Other retention dumps will vary in size up to the size of memory on the PC where the dump is collected. Thus, on a PC with 16 GB of RAM, a Complete memory dump file will always be xvi GB in size (and other dump files, except for the small-scale memory dumps, can be as big every bit 16 GB, simply will oftentimes be smaller).

Examining a crash dump file tin be helpful when troubleshooting related causes. For more details, run into our story on how to use a minidump file to fix your Windows BSOD. That said, many users but search on the stopcode and/or the numeric error code when seeking remediation communication. (Note that Microsoft calls that numeric code a "bug check lawmaking" or "issues check string."

What To Exercise When Troubleshooting a BSOD

The firsthand trend post-obit a BSOD is to become right into fix-information technology style, start looking things up, and attempting repairs. Not so fast! Microsoft explains the entire troubleshooting process in its "Troubleshoot blue screen errors" tutorial. While you tin – and probably should – read the Microsoft advice in its entirety, here'south a summary of key recommendations:

Close downwardly the Windows PC that experienced the BSOD
Disconnect all USB-attached devices except for mouse and keyboard (or wireless dongles).
Reboot your system into safe style from the Windows Recovery Environment (WinRE)
If y'all recently installed new software, uninstall that software.
If you lot recently installed a new device driver (or your BSOD info points to a driver or device), uninstall or roll back that driver (if yous don't really need the device you can disable it temporarily instead)
Restart the PC, and see if the BSOD recurs. If not, you lot've probably isolated the cause and tin starting time researching some kind of fix.

If the BSOD recurs despite the items taken out of the film by removing, disabling or uninstalling them, whatever's nonetheless left in the film remains problematic. At this point y'all want to reboot into safe mode once over again, and open an administrative command prompt or PowerShell session. From the command line, enter these commands, one at a time:

DISM /Online /Cleanup-prototype /Restorehealth
SFC /scannow

The beginning of these two commands finds and replaces any damaged operating organization components in the side-past-side filestore (aka WinSxS). The second of these commands runs the System File Checker (SFC) and will repair whatsoever damaged files information technology finds.

Annotation that if SFC finds and fixes anything, you should run the command until it comes back with a make clean bill of wellness (in some cases, I've had to run it two or three times before information technology came back make clean). Note further that running either or both of these commands can take some time to complete, especially if i or both detect items in need of fixing. Here'due south what you lot want to see afterwards your final SFC run:

There'due south a consummate BSOD handling infrastructure available from Microsoft, built effectually a tool called the Windows Debugger (aka WinDBG). Yous can download it as function of Microsoft'southward free Windows Developer Kit if you actually desire to dig into the gory details. In that location are a lot of details to learn about, and minutiae to address, if you want to put this tool to work on crash dumps. For non-IT professionals or non-developers, I recommend Nir Sofer's excellent BlueScreenView utility instead. It's set to automatically load the symbol tables it needs to resolve error codes, and information technology knows where to detect crash dumps in need of analysis. It also presents crash dump information in a highly-readable grade.

Equally an illustration, I forced one of my test laptops (a Lenovo ThinkPad X390 Yoga) to bluish screen at an authoritative command line. There, I entered the string taskkill /im svchost.exe /f. Warning: typing this string into an administrative command prompt or PowerShell session volition crash the PC immediately. That's because it kills a key program named svchost.exe (Service Host) that supports DLLs in the Windows runtime environment. Because most (if non all) Windows programs use one or more than DLLs this basically makes Windows inoperable. Thus, information technology causes an firsthand BSOD with the CRITICAL_PROCESS_DIED stopcode (shown in the pb-in graphic for this very story).

When I fired up BlueScreenView on that PC, it found the Memory.dmp file that this BSOD created during its post-crash cleanup phase. Here'due south what the application looks like:

The top pane of the window shows all the crash dumps it finds on the target PC. Because there's only 1 in this instance, I shrunk it downwards to show as many details from the bottom pane as possible. Even and then, the data in the top pane is important, with information in certain columns of special interest. Column 1 shows the proper noun of the dump file. Column 3 shows the stopcode, which it labels "Bug Cheque Cord." Cavalcade 3 shows the associated hexadecimal error lawmaking, 0x000000ef, which it labels "Problems Check Lawmaking."

For most genuine BSODs (remember, I forced this one to happen) the stopcode and the mistake lawmaking will oftentimes assistance affected users zero in on causes and potential cures for their woes. In my feel, at least 90% of BSODs become fixable simply based on this information. That's considering it will often be solved by disconnecting, disabling, or uninstalling related devices, drivers, applications, or updates – just as Microsoft recommends, and I summarized in the previous department.

What About that Other Problematic 10% of BSODs?

Some BSODs won't be acquiescent to quick and easy fixes. When they come up, as they sometimes will, information technology's time to ask for aid in getting things figured out. I can recommend 2 terrific sources of troubleshooting help available online, each with its own dedicated user forum specifically focused on solving BSOD issues. Likewise, each one stipulates sure requirements on users seeking BSOD help.

Source number i comes from TenForums.com (primal disclosures: I am a VIP member of this community; I contribute input and suggestions to its members daily). The TenForums venue is in its BSOD Crashes and Debugging forum. Posting instructions are explicitly provided, along with a collection of BSOD tutorials, including those on WinDBG Basics,and how to Install and Configure WinDBG for BSOD Analysis, Run BSOD Error Troubleshooter in Windows 10, and Enable or Disable BSOD Automatic Restart in Windows 10.

Source number 2 comes from British PC security and troubleshooting site BleepingComputer.com. They operate a user forum named Windows Crashes and Blue Screen of Death (BSOD) Help and Support. There, you'll detect pinned threads for the following topics (all of which are worth reading through):

Sysnative Blue Screen of Death (BSOD) Academy: A series of detailed questions readers should answer to enquire the experts at Sysnative for aid with BSOD bug.
BSOD Posting instructions: what information users should get together (based on downloading and running a Sysnative app) to obtain necessary dump files and content.
BSODs just no Dump Files: instructions on how to configure a Windows PC to produce dump files whenever a BSOD occurs. Essential to know considering diagnosis without dumps is nigh impossible.

Thus, y'all'll have to read up a bit, download some tools, run some scripts and/or collect some logs that you'll submit to make a semi-formal request for BSOD assistance. This will take one or more hours and force y'all to do some homework earlier such help becomes available. Information technology may also involve numerous back-and-along communications, where you're asked to run additional diagnostic tools and collect additional logs and data to shed more light on your situation. Trust me: these guys know what they're doing. I've seen only a handful of issues where users did everything asked of them where the BSOD experts couldn't assistance them get things fixed.

Ultimately, where there's enough volition to get a Windows BSOD stock-still, there's a way to make that happen. Keep at information technology, and you'll learn this for yourself.