Drivers · critical

How to fix SYSTEM_SERVICE_EXCEPTION (0x3B)

Drivers troubleshooting guide

What this error means

Windows stopped because code running in the system kernel hit an exception, usually a bad memory address, while handling a request from a normal program. In practice the faulty code almost always belongs to a driver: graphics, audio, webcam, network, antivirus or a virtual device installed by a tool. Less often, unstable memory or damaged system files are responsible. The blue screen often names the file that failed, which points to the driver to update or remove.

Updated

Applies to
Windows 11 and Windows 10
Difficulty
Beginner to intermediate
Before changes
Low for steps 1–6; Driver Verifier in step 7 can cause extra crashes until it is turned off

Reviewed by Matyáš Rada · Documentation checked: 2026-10-30 · Checked against Microsoft's bug check documentation; not tested on every configuration.

Before you begin

Photograph the blue screen, especially the "What failed" line. If the PC keeps crashing, start it in Safe Mode for the following steps. If Windows cannot start, see the startup guide.

Work through these checks

0 of 7 complete
01Find the file named on the blue screen

This stop code is almost always caused by a specific driver, and Windows often shows its file name.

  1. Look for "What failed: name.sys" on the blue screen photo and search that file name to find the device or program it belongs to.
  2. Open Event Viewer (Win + R, eventvwr.msc) > Windows Logs > System and look at the critical errors and warnings just before the restart.
  3. Open Device Manager (Win + R, devmgmt.msc) and look for devices marked with a yellow exclamation point.
What to expect

You know which driver or device is the most likely cause.

If it does not help

Examples: nvlddmkm.sys or amdkmdag.sys are graphics drivers, Netwtw*.sys is Intel Wi-Fi. If the named file is a Windows file such as ntoskrnl.exe or win32kfull.sys, the real cause is usually another driver; continue with step 2.

Browse related errors
02Undo the most recent driver or software change

Microsoft's first recommendation is to remove or update drivers and system services that were added recently.

  1. Think about what changed before the crashes started: a new driver, Windows update, antivirus, VPN, webcam or capture software, fan and RGB control, or a hardware monitoring tool.
  2. Uninstall that program in Settings > Apps > Installed apps, or roll back the driver in Device Manager > device Properties > Driver > Roll Back Driver.
  3. If you added hardware recently, disconnect it and test again.

Keep Microsoft Defender turned on when you remove another antivirus program.

What to expect

The crashes stop after the change is undone.

If it does not help

If you need the program, install its newest version later and check whether the crash returns.

Browse related errors
03Reinstall the graphics driver cleanly

Graphics drivers are the most common source of this crash, especially when it happens in games or when playing video.

  1. Download the current driver for your graphics card from NVIDIA, AMD or Intel, or the laptop maker's driver for laptops with switchable graphics.
  2. Run the installer and choose its clean installation or factory reset option, if it offers one.
  3. If the crash began after a driver update, install the previous version instead.
What to expect

The PC runs games and video without the blue screen.

If it does not help

If the named file was not a graphics driver, go straight to step 4.

Browse related errors
04Update the remaining drivers

Old chipset, audio, network and storage drivers can also trigger the exception.

  1. Run Windows Update, including Advanced options > Optional updates > Driver updates.
  2. Install the latest chipset, audio, network and Wi-Fi drivers from your PC, laptop or motherboard maker's support page for your exact model.
  3. Update the BIOS/UEFI if the maker lists a newer version for stability fixes.

Do not use driver updater programs; they often install wrong or unsigned drivers. Do not switch off the PC during a BIOS update.

What to expect

Drivers and firmware are current.

If it does not help

Use the PC normally for a day and watch for new crashes.

Browse related errors
05Repair Windows system files

Damaged system files can make a correct driver crash when it calls into Windows.

  1. Right-click Start and open Terminal (Admin).
  2. Run DISM /Online /Cleanup-Image /RestoreHealth and wait for it to finish.
  3. Run sfc /scannow, then restart.
What to expect

SFC reports no integrity violations, or that it repaired them.

If it does not help

If SFC cannot repair some files, run both commands once more after a restart.

Browse related errors
06Test the memory

Faulty or overclocked RAM corrupts data that drivers then read as invalid addresses.

  1. If XMP, EXPO or another memory or CPU overclock is enabled in the BIOS, turn it off for testing.
  2. Run Windows Memory Diagnostic (Win + R, mdsched.exe) and choose Restart now and check for problems.
  3. After the restart, find the result in Event Viewer > Windows Logs > System, source MemoryDiagnostics-Results.
What to expect

The memory test passes and the crashes stop or remain.

If it does not help

If the test reports errors, follow the memory test errors guide on this site.

Browse related errors
07Find the driver with Driver Verifier

When no file is named, Driver Verifier puts extra checks on drivers so the faulty one is named in the next crash.

  1. Create a restore point first (search "Create a restore point").
  2. Open Command Prompt (Admin), type verifier, choose Create standard settings, then Select driver names from a list, and tick only non-Microsoft drivers.
  3. Restart and use the PC until it crashes; the new blue screen and dump name the driver.
  4. Turn Driver Verifier off afterwards with verifier /reset and restart.

Driver Verifier deliberately crashes the PC when a driver misbehaves. Use it only after the earlier steps and turn it off when done.

What to expect

The crash names a specific third-party driver to update or remove.

If it does not help

If Windows no longer starts with Driver Verifier on, start in Safe Mode and run verifier /reset.

Browse related errors

Possible causes

  • A faulty or outdated driver, most often graphics, audio, webcam or network
  • Security, VPN, monitoring or RGB software that installs its own kernel drivers
  • A driver or service added or updated shortly before the crashes began
  • Damaged Windows system files
  • Unstable or faulty RAM

Useful Windows tools

These commands open Windows tools. Review changes before applying them.

eventvwr.msc
devmgmt.msc
mdsched.exe

Sources & further reading