Blue Screen Of Death Windows 10 How To Fix

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

(Image credit: Shutterstock)

Few things are more frustrating. You're in the centre of working on a project, reaching a major milestone in a game or mayhap just booting upwardly your Windows x computer and, just like that, the entire Bone crashes and presents you with a Blueish Screen of Death, commonly for no immediately credible reason.

In Windows-speak, the term "Blue Screen of Expiry" is usually abbreviated equally BSOD. Information technology describes an mistake of some kind that hits the operating system difficult plenty that information technology's forced to quit. Microsoft itself labels such errors with "stopcodes." Thus these errors may besides be generically named "finish errors." Hither'south an instance that shows what a BSOD sometimes looks like:

Understanding the BSOD Screen

The screen starts with an erstwhile-fashioned unhappy face emoticon " :( " (a colon, followed by an open parenthesis). Next, y'all come across a brief caption that "Your PC ran into a problem and needs to restart." Windows writes one or more log files when a end fault occurs, then you meet language about "collecting some error info" and a counter that keeps track while it's writing that information (shows as "25% complete) above.

Microsoft provides a scannable QR code in mod BSODs (lower left) that you can browse with a smartphone and wait up that fashion. The bulletin also provides a lookup URL for stopcodes, where yous can enter a numeric stopcode (and where you lot'll see most mutual stopcodes, including the one shown higher up). 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 Fault Lookup Tool (current version: Err_6.iv.5.exe) to look up numeric error codes at a command prompt or in PowerShell, if y'all prefer.

In Windows 10, BSODs Aren't Ever Bluish

Before Windows 8 came along in October 2012, BSODs e'er appeared on nighttime bluish screens. These were clogged of text and instructions (see below). With Windows eight, Microsoft switched to a kinder, gentler format shown in the preceding screencap. They also whittled down the data that appears on screen. In fact, the background color in Windows 10 is sometimes green, which is why you lot may see some of them called GSODs ("Green Screens of Death"). Here's an example of an former-fashioned, pre-Windows-eight BSOD to put this information into historical context:

Making Sense of BSOD Information

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

Y'all can manage crash dumps through Advanced System Settings in Windows 10 (type "Advanced System Settings" into the search box, and so click "Settings" in the Startup and Recovery pane). Yous can too choose to toggle "Automatic restart" to off here, if y'all would prefer that any future BSODs stay on the screen until y'all get a chance to see them and write down (or accept pic of) any relevant data.

If you select "Minor retention dump" as the choice for saving crash dumps, such files testify up equally Minidump.dmp files. For all other selections, the crash dump is named Memory.dmp. Crash dumps become written to the %SystemRoot% binder, which normally expands to C:\Windows. Past design, small-scale memory dump files are limited to 256KB in size. Other retentiveness dumps will vary in size upward to the size of memory on the PC where the dump is collected. Thus, on a PC with 16 GB of RAM, a Consummate memory dump file volition always exist 16 GB in size (and other dump files, except for the minor retentivity dumps, can be as large as 16 GB, but will often be smaller).

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

What To Practice When Troubleshooting a BSOD

The immediate tendency following a BSOD is to get correct into gear up-information technology fashion, get-go looking things upward, and attempting repairs. Non so fast! Microsoft explains the unabridged troubleshooting procedure in its "Troubleshoot bluish screen errors (opens in new tab)" tutorial. While you tin can – and probably should – read the Microsoft advice in its entirety, here'south a summary of key recommendations:

Close down 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 way from the Windows Recovery Environment (WinRE)
If y'all recently installed new software, uninstall that software.
If y'all recently installed a new device commuter (or your BSOD info points to a driver or device), uninstall or coil back that driver (if y'all don't really demand the device you can disable it temporarily instead)
Restart the PC, and come across if the BSOD recurs. If not, you've probably isolated the cause and can start researching some kind of fix.

If the BSOD recurs despite the items taken out of the picture show by removing, disabling or uninstalling them, whatever'southward still left in the motion-picture show remains problematic. At this bespeak you desire to reboot into safe mode one time again, and open up an administrative control prompt or PowerShell session. From the control line, enter these commands, 1 at a time:

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

The first of these two commands finds and replaces any damaged operating organisation components in the side-past-side filestore (aka WinSxS). The 2nd of these commands runs the System File Checker (SFC) and will repair any damaged files it finds.

Notation that if SFC finds and fixes anything, you should run the control until it comes back with a clean bill of health (in some cases, I've had to run it two or three times earlier it came back make clean). Annotation farther that running either or both of these commands can take some time to complete, particularly if one or both discover items in need of fixing. Here's what you desire to see afterward your terminal SFC run:

There's a complete BSOD handling infrastructure bachelor from Microsoft, congenital around a tool called the Windows Debugger (aka WinDBG). Y'all tin can download it every bit office of Microsoft's free Windows Developer Kit (opens in new tab) if you really want to dig into the gory details. In that location are a lot of details to learn most, and minutiae to address, if you desire to put this tool to work on crash dumps. For non-IT professionals or non-developers, I recommend Nir Sofer'due south fantabulous BlueScreenView utility instead. It's ready up 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 data in a highly-readable form.

As an illustration, I forced one of my exam laptops (a Lenovo ThinkPad X390 Yoga) to blueish screen at an administrative command line. There, I entered the cord taskkill /im svchost.exe /f. Alarm: typing this string into an administrative command prompt or PowerShell session volition crash the PC immediately. That'southward because it kills a primal programme named svchost.exe (Service Host) that supports DLLs in the Windows runtime environment. Because most (if not all) Windows programs utilize one or more than DLLs this basically makes Windows inoperable. Thus, information technology causes an immediate BSOD with the CRITICAL_PROCESS_DIED stopcode (shown in the pb-in graphic for this very story).

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

The superlative pane of the window shows all the crash dumps it finds on the target PC. Because in that location'southward simply one in this case, I shrunk information technology downwards to show as many details from the bottom pane as possible. Even and so, the information in the top pane is important, with information in certain columns of special interest. Cavalcade 1 shows the name of the dump file. Cavalcade 3 shows the stopcode, which it labels "Bug Check String." Column three shows the associated hexadecimal mistake code, 0x000000ef, which information technology labels "Bug Check Lawmaking."

For most genuine BSODs (call back, I forced this one to happen) the stopcode and the error code will ofttimes help affected users cipher in on causes and potential cures for their woes. In my feel, at to the lowest degree ninety% of BSODs go fixable simply based on this information. That's because it will often be solved by disconnecting, disabling, or uninstalling related devices, drivers, applications, or updates – merely as Microsoft recommends, and I summarized in the previous section.

What About that Other Problematic 10% of BSODs?

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

Source number ane comes from TenForums.com (key 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 Mistake Troubleshooter in Windows 10, and Enable or Disable BSOD Automatic Restart in Windows x.

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

Sysnative Blue Screen of Expiry (BSOD) Academy: A serial of detailed questions readers should answer to ask the experts at Sysnative for help with BSOD issues.
BSOD Posting instructions: what data users should gather (based on downloading and running a Sysnative app) to obtain necessary dump files and content.
BSODs merely 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 nearly impossible.

Thus, y'all'll accept 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 help. This volition take ane or more hours and strength you to exercise some homework before such assistance becomes available. It 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 than light on your state of affairs. Trust me: these guys know what they're doing. I've seen merely a handful of issues where users did everything asked of them where the BSOD experts couldn't aid them get things fixed.

Ultimately, where there'south plenty will to get a Windows BSOD stock-still, there's a fashion to make that happen. Go along at information technology, and you'll larn this for yourself.

Ed Tittel is a long-time IT writer, researcher and consultant, and occasional contributor to Tom's Hardware. A Windows Insider MVP since 2018, he likes to cover OS-related driver, troubleshooting, and security topics.

Source: https://www.tomshardware.com/how-to/fix-windows-bsod

Posted by: landermomp1940.blogspot.com