Photograph the blue screen and note any file name. If Windows crashes during startup, use Safe Mode (recovery menu > Troubleshoot > Advanced options > Startup Settings > Restart > 4) for the steps below. If Windows cannot start, see the startup guide.
Work through these checks
0 of 7 complete01Note the driver and when the crash happens
The named driver and the situation tell you which of the causes applies.
- Check the blue screen photo for a .sys file name and search it to find its device or program.
- Open Event Viewer (Win + R, eventvwr.msc) > Windows Logs > System and look at errors just before the BugCheck event (ID 1001).
- Note whether it happens during a Windows installation or upgrade, at startup, or during normal use.
You know the likely driver, or at least the situation.
If it does not helpDuring installation or an upgrade, start with step 4 (BIOS). Otherwise continue with step 2.
02Remove recently added drivers and services
Microsoft recommends disabling or removing drivers and services that were added recently.
- Uninstall programs you installed shortly before the crashes started, especially antivirus, VPN, virtual drive, RGB and monitoring tools, in Settings > Apps > Installed apps.
- Roll back a recently updated driver in Device Manager > device Properties > Driver > Roll Back Driver.
- If the crash happens at startup, do this in Safe Mode, where you can also disable the device in Device Manager.
Keep Microsoft Defender on when you remove another antivirus program.
Windows runs without the crash.
If it does not helpReinstall needed programs one at a time, using their latest versions, and test after each.
03Update or replace the named driver
When the blue screen names a driver, Microsoft's advice is to remove it or get an update from the maker.
- Download the latest driver for that device from its maker or your PC maker's support page, and install it.
- For graphics drivers, use the installer's clean installation option if it has one.
- If no newer driver exists and the device is not essential, disable it in Device Manager to confirm it is the cause.
Avoid third-party driver updater programs.
The PC runs normally with the updated driver.
If it does not helpIf the problem continues, update the BIOS in step 4.
04Update the BIOS
Microsoft says BIOS problems behind this stop code are resolved by upgrading the system BIOS version.
- Find your exact PC or motherboard model on the maker's support page.
- Install the latest BIOS/UEFI version using the maker's instructions.
- If the crash happened during a Windows upgrade, update the BIOS first and then run the upgrade again.
Do not switch off the PC during a BIOS update.
The PC runs or upgrades without the stop code.
If it does not helpAfter the update, check the BIOS settings, as some may be reset to defaults.
05Check hardware compatibility
Microsoft lists hardware that is incompatible with the installed Windows version as a cause.
- If you added hardware recently, remove it and test.
- Check the maker's website that each recently added device supports your Windows version, and install its latest driver.
- For older devices without Windows 11 drivers, consider replacing them.
Switch off and unplug the PC before removing internal parts.
You know whether a specific device is responsible.
If it does not helpIf the crash stops without the device, contact its maker about compatibility.
06Run the memory test and hardware diagnostics
Microsoft recommends the manufacturer's hardware diagnostics, especially the memory scanner.
- Turn off XMP, EXPO and any overclock in the BIOS for testing.
- Run Windows Memory Diagnostic (Win + R, mdsched.exe) > Restart now and check for problems.
- Run the hardware diagnostics from your PC or laptop maker, if available.
Memory and hardware tests pass.
If it does not helpIf the memory test reports errors, follow the memory test errors guide on this site.
07Repair system files
Damaged system files can cause kernel-mode components to fail.
- Open Terminal (Admin).
- Run DISM /Online /Cleanup-Image /RestoreHealth.
- Run sfc /scannow and restart.
SFC reports no integrity violations, or that it repaired them.
If it does not helpIf crashes continue, see the blue screen errors overview on this site for related stop codes, or use System Restore to return to a point before the problem.
Possible causes
- A faulty device driver or system service
- A driver or service added shortly before the crashes started
- BIOS incompatibility, especially during or after a Windows upgrade
- Hardware that does not support the installed Windows version
- Faulty RAM
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.