Download windows 10 blue screen troubleshooter

WhatsApp Messenger. Talking Tom Cat. Clash of Clans. Subway Surfers. TubeMate 3. Google Play. The Best Black Friday deals. Bill Gates' favorite books of Hawkeye review.

Xbox Game Pass Ultimate review. Windows Windows. Most Popular. New Releases. Desktop Enhancements. Networking Software. Trending from CNET. Free Registry Fix Free to try. Scan your Registry for possible problems and fix them. Advanced SystemCare Free Free. Unlock full PC potential with accelerating, optimizing, cleaning, and shielding diagnostics and one-click-fix maintenance.

Free Window Registry Repair Free. Scan, repair, and optimize your Windows registry. Wise Registry Cleaner Free. Finding the root cause of the crash may not be easy. Hardware problems are especially difficult to diagnose because they may cause erratic and unpredictable behavior that can manifest itself in various symptoms.

When a Stop error occurs, you should first isolate the problematic components, and then try to cause them to trigger the Stop error again. If you can replicate the problem, you can usually determine the cause. The next section discusses how to use this tool. Advanced troubleshooting of crash dumps can be very challenging if you are not experienced with programming and internal Windows mechanisms.

We have attempted to provide a brief insight here into some of the techniques used, including some examples. However, to really be effective at troubleshooting a crash dump, you should spend time becoming familiar with advanced debugging techniques. Also see the advanced references listed below. Verify that the computer is set up to generate a complete memory dump file when a crash occurs.

See the steps here for more information. Locate the memory. On the other computer, download the Windows 10 SDK. Start the install and choose Debugging Tools for Windows.

This installs the WinDbg tool. This is the recommended method. If the computer is not connected to the Internet, you must specify a local symbol path. Click on Open Crash Dump , and then open the memory. See the example below. There should be a link that says! Click that link. This will enter the command! There will be rows of numbers with each row followed by a colon and some text.

See Using the! There are many possible causes of a bugcheck and each case is unique. The problem here is with mpssvc which is a component of the Windows Firewall. The problem was repaired by disabling the firewall temporarily and then resetting firewall policies. Additional examples are provided in the Debugging examples section at the bottom of this article. We estimate that about 75 percent of all Stop errors are caused by faulty drivers.

The Driver Verifier tool provides several methods to help you troubleshoot. These include running drivers in an isolated memory pool without sharing memory with other components , generating extreme memory pressure, and validating parameters. If the tool encounters errors in the execution of driver code, it proactively creates an exception to let that part of the code be examined further. Driver Verifier consumes lots of CPU and can slow down the computer significantly. You may also experience additional crashes.

Verifier disables faulty drivers after a Stop error occurs, and continues to do this until you can successfully restart the system and access the desktop. You can also expect to see several dump files created. This can degrade performance and make the system unusable. This also limits the effectiveness of the tool. If you continue to experience non-analyzable crashes, try enabling verification on all third-party and unsigned drivers.

Additionally, if the computer cannot boot into the desktop because of Driver Verifier, you can disable the tool by starting in Safe mode. This is because the tool cannot run in Safe mode. For more information, see Driver Verifier. This section doesn't contain a list of all error codes, but since many error codes have the same potential resolutions, your best bet is to follow the steps below to troubleshoot your error. The resolution method is to disable the network device in device manager and try the upgrade again.

Disconnecting the device and retrying the upgrade is a possible solution. Bug Check Code Reference. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info.

Contents Exit focus mode. Is this page helpful? Please rate your experience Yes No. Any additional feedback? Note If you're not a support agent or IT professional, you'll find more helpful information about Stop error "blue screen" messages in Troubleshoot blue screen errors. Note The root cause of Stop errors is never a user-mode process. Note If there are no updates available from a specific manufacturer, it is recommended that you disable the related service.

Note Advanced troubleshooting of crash dumps can be very challenging if you are not experienced with programming and internal Windows mechanisms. Submit and view feedback for This product This page. View all page feedback. In this article. Apply the latest updates for the driver by applying the latest cumulative updates for the system through the Microsoft Update Catalog website.

Update an outdated NIC driver. Contact the hardware vendor to update the NIC driver for a resolution. If a driver is identified in the Stop error message, contact the manufacturer for an update.

If no updates are available, disable the driver, and monitor the system for stability. You must restart the system before the disk scan begins on a system partition.