How to Fix SYSTEM_SERVICE_EXCEPTION in Windows 11

•
Ankit Kumar
Windows 11BSODTroubleshootingFixDrivers

The Problem

Windows blue-screens with SYSTEM_SERVICE_EXCEPTION (technical code 0x0000003B). A driver or system service tried to do something only the kernel is allowed to do, and Windows stopped rather than let it continue.

This is a driver problem far more often than a hardware problem. Graphics, webcam, virtualisation, and third-party antivirus drivers are the repeat offenders. The blue screen usually names a .sys file — that name is the whole investigation.

Crash happens only in games? Check VIDEO_TDR_FAILURE too. Can't stay booted long enough to fix anything? Start in Safe Mode.

Symptoms

  • Blue screen reading SYSTEM_SERVICE_EXCEPTION, often naming a file such as win32kfull.sys, nvlddmkm.sys, dxgmms2.sys, or ks.sys.
  • Crashes when launching a game, joining a video call, or waking from sleep.
  • Started right after a Windows update or a driver install.

Step 1: Find the Named Driver

  1. Photograph the blue screen text, including the line under the stop code.
  2. Or open Event Viewer → Windows Logs → System, sort by time, and open the BugCheck entry.
  3. Translate the file:
    • nvlddmkm.sys / atikmdag.sys / igdkmd64.sys — graphics driver
    • dxgmms2.sys / win32kfull.sys — graphics subsystem, still usually the GPU driver
    • ks.sys / usbvideo.sys — webcam or capture device
    • vmm.sys / vmci.sys — virtualisation (Hyper-V, VMware, VirtualBox)
    • bd*.sys, avg*.sys, mbam*.sys — third-party antivirus

Step 2: Roll Back the Driver That Changed

If the crashes began after an update, undo it.

  1. Right-click Start → Device Manager.
  2. Right-click the device → Properties → Driver tab → Roll Back Driver.
  3. If the button is greyed out, choose Uninstall device, tick Attempt to remove the driver, then restart — Windows reinstalls a generic driver.
  4. For graphics, do it properly: clean install GPU drivers with DDU.

Step 3: Update the Remaining Drivers Properly

  1. Get chipset, storage, network, and audio drivers from your motherboard or laptop manufacturer's support page, not from a driver-updater app.
  2. Install chipset first, then graphics, then everything else, restarting between the big ones.
  3. Detailed method: how to update outdated drivers.

Step 4: Repair Windows System Files

  1. Right-click Start → Terminal (Admin).
  2. Run: 
    sfc /scannow
  3. Then: 
    DISM /Online /Cleanup-Image /RestoreHealth
  4. Restart and retest. See repair Windows 11 with SFC and DISM for what the output means.

Step 5: Uninstall Third-Party Antivirus

Security suites hook deep into the kernel and are a classic source of this stop code.

  1. Uninstall the suite with the vendor's official removal tool, not just Add/Remove Programs.
  2. Restart and run on Microsoft Defender for a day or two.
  3. If the crashes vanish, the suite was the cause. Reinstall it fresh or stay on Defender.

Step 6: Turn Off Virtualisation Features You Don't Use

  1. Press Win + R, type optionalfeatures, press Enter.
  2. Untick Hyper-V, Virtual Machine Platform, and Windows Hypervisor Platform if you do not run VMs or WSL.
  3. Restart. If you do use WSL or Docker, leave these on and update those tools instead.

Step 7: Roll Back a Bad Windows Update

  1. Settings → Windows Update → Update history → Uninstall updates.
  2. Remove the most recent quality update and restart.
  3. Full procedure, including pausing the update so it does not return immediately: roll back Windows 11 after a bad update.

Step 8: Run Driver Verifier (Advanced, Last Resort)

Driver Verifier deliberately stresses drivers so the guilty one crashes immediately with its name attached.

  1. Create a restore point first: create a system restore point.
  2. Run verifier from an admin Terminal, choose Create custom settings → Select individual settings from a full list, enable Special Pool, Force IRQL checking, and Pool Tracking.
  3. Choose Select driver names from a list and tick only non-Microsoft drivers.
  4. Restart. Expect crashes — the stop code will now name the bad driver.
  5. Turn it off when finished: run verifier /reset and restart. If the PC will not boot, enter Safe Mode and run the same command.

What Not to Do

  • Don't leave Driver Verifier running. It is a diagnostic; forgetting it turns your PC into a crash loop.
  • Don't use automatic "driver updater" tools. They install mismatched drivers and cause exactly this crash.
  • Don't reinstall Windows first. This stop code is fixable in almost every case without it.

Still Not Working?

If Verifier points at a driver with no newer version available, remove that device or use a different one. If it points at nothing and crashes continue, test RAM with the steps in MEMORY_MANAGEMENT, then consider reinstalling Windows without losing data.

Related stop codes: IRQL_NOT_LESS_OR_EQUAL, PAGE_FAULT_IN_NONPAGED_AREA, and KERNEL_SECURITY_CHECK_FAILURE.

Related guides