Photograph the blue screen, especially the file after "What failed". If Windows crashes at startup, use Safe Mode (recovery menu > Troubleshoot > Advanced options > Startup Settings > Restart > 4). If Windows cannot start, see the startup guide.
Work through these checks
0 of 7 complete01Note the driver file on the blue screen
Microsoft explains that when the driver is identified, its name is shown on the blue screen.
- Look for "What failed: name.sys" and search the file name to find its device or program.
- Examples: Netwtw*.sys or rtwlan*.sys (Wi-Fi), rt640x64.sys or e1d*.sys (Ethernet), ndis.sys or tcpip.sys (Windows network components, usually triggered by a network driver or VPN).
You know which driver or device is involved.
If it does not helpIf no file is shown, continue with step 2.
02Check Event Viewer
Microsoft recommends the System log for messages that identify the device or driver.
- Open Event Viewer (Win + R, eventvwr.msc) > Windows Logs > System.
- Look at errors and warnings just before the BugCheck event (ID 1001), especially from network adapters or drivers.
You find the device or driver that logged problems before the crash.
If it does not helpContinue with step 3 for that driver.
03Update, roll back or remove the driver
Microsoft's advice for a named driver is to disable it or get an update from the maker.
- If the crashes began after a driver update, open Device Manager > device Properties > Driver > Roll Back Driver.
- Otherwise install the latest driver from the device or PC maker (for Wi-Fi and Ethernet, the laptop maker or Intel, Realtek, Killer).
- If the device is not needed, disable it in Device Manager to confirm it is the cause.
Avoid driver updater programs.
The crashes stop.
If it does not helpIf the named file is a Windows network file such as ndis.sys or tcpip.sys, update the network adapter driver and check step 4.
04Remove VPN and security software that adds drivers
VPN clients, firewalls and antivirus programs install network and filter drivers that commonly trigger this stop code.
- Uninstall recently installed or updated VPN, firewall, antivirus or network monitoring software in Settings > Apps > Installed apps.
- Restart and use the PC normally.
Keep Microsoft Defender on while another antivirus is removed.
The crashes stop without the program.
If it does not helpInstall the newest version later and check whether the crash returns.
05Check new hardware compatibility
Microsoft recommends confirming that newly installed hardware is compatible with your Windows version.
- If you added a device recently (Wi-Fi card, USB adapter, capture card), disconnect it and test.
- Check the maker's website for drivers for your exact Windows version.
You know whether the new device causes the crash.
If it does not helpReplace devices that have no driver for your Windows version.
06Test the memory
Faulty RAM can corrupt the data a driver works with, which looks like a driver bug.
- Turn off XMP or EXPO in the BIOS for testing.
- Run Windows Memory Diagnostic (Win + R, mdsched.exe) > Restart now and check for problems.
The memory test passes.
If it does not helpIf it fails, follow the memory test errors guide on this site.
07Find the driver with Driver Verifier
Microsoft recommends Driver Verifier, verifying as few drivers as possible, to catch the faulty driver.
- Create a restore point (search "Create a restore point").
- Open Command Prompt (Admin), type verifier, choose Create standard settings > Select driver names from a list, and tick only non-Microsoft drivers.
- Restart and use the PC until it crashes; the blue screen names the driver. Then run verifier /reset and restart.
Driver Verifier deliberately crashes the PC when it finds a problem. Turn it off when you are done.
A specific driver is named for you to update or remove.
If it does not helpIf Windows does not start with Driver Verifier on, start in Safe Mode and run verifier /reset.
Possible causes
- A faulty or outdated driver, often network, Wi-Fi, USB or audio
- VPN, antivirus, firewall or other software with kernel drivers
- A driver installed or updated shortly before the crashes
- New hardware that is not compatible with your Windows version
- Faulty RAM making a driver read bad data
Useful Windows tools
These commands open Windows tools. Review changes before applying them.
eventvwr.mscdevmgmt.mscmdsched.exeWas this helpful?
Your progress is saved on this device.