How to Fix BSOD SYSTEM_SERVICE_EXCEPTION (0x0000003B)

By ErrorFix · Updated October 14, 2026 · 8 min read

What error 0x0000003B means

Drivers live in the Windows kernel, the most privileged part of the operating system. When a driver's code does something illegal — reads memory it shouldn't, passes a bad parameter to a system service, or trips over another driver — Windows halts everything with SYSTEM_SERVICE_EXCEPTION (stop code 0x0000003B) to stop the corruption from spreading. The name says it plainly: a system service (a driver) threw an exception the system couldn't handle.

The encouraging news is that this blue screen is a software problem in the vast majority of cases. The top triggers are a buggy graphics driver update, an antivirus or firewall driver hooking into the kernel, corrupted Windows system files, or a driver conflict after a Windows update. Failing RAM can also produce it, because a bad memory cell makes good driver code read garbage — but hardware is the minority cause. That means most people fix this without buying anything, by working through drivers and system files in order.

Common causes

• Buggy graphics driver update: NVIDIA, AMD, and Intel driver updates are the single most common trigger — the crash often starts days after an update.
• Antivirus or firewall drivers: third-party security tools run in the kernel, and their drivers conflict with Windows more often than anything else.
• Corrupted Windows system files: a failed update or sudden shutdown can leave system files damaged, and drivers then trip over the damage.
• Failing RAM: defective memory cells corrupt data that drivers read, producing the exact "exception" this blue screen reports.
• Recent Windows update conflicts: a cumulative update can change kernel behavior that an older third-party driver doesn't expect.

How to fix error 0x0000003B — step by step

Work through these fixes in order. If the crashes started right after a driver or Windows update, step 2 alone usually ends them.

1. Boot into Safe Mode and identify what changed. Interrupt the boot process three times in a row (hold the power button during the Windows logo) to reach the Recovery screen. Go to Troubleshoot > Advanced options > Startup Settings > Restart, then press 4 for Safe Mode. Safe Mode loads only Microsoft's own drivers, so if the PC is stable here, a third-party driver is guilty. Think about what changed before the crashes started: a graphics driver update, a Windows update, or a newly installed program.
2. Roll back the most recently updated driver. Press Win + X and open Device Manager. Find the device whose driver changed most recently (Display adapters is the usual suspect). Right-click it, choose Properties, open the Driver tab, and click Roll Back Driver, choosing the most fitting reason. If the button is grayed out — meaning there's no previous version stored — use Uninstall device instead, tick "Attempt to remove the driver for this device" if offered, and restart. Windows will reinstall its stock driver, which is stable even if not the newest.
3. Clean-install the graphics driver with DDU. Partial driver installs are a classic 0x0000003B trigger, so a clean wipe matters. Download Display Driver Uninstaller (DDU) and the latest driver from NVIDIA, AMD, or Intel — not from Windows Update. Boot into Safe Mode, run DDU, select your GPU brand, and choose "Clean and restart." After rebooting normally, install the downloaded driver, pick Custom installation, and tick "Perform a clean installation." This removes every leftover file and registry entry from previous versions.
4. Repair system files with SFC and DISM. Open an admin Terminal (right-click Start > Terminal (Admin)). First run sfc /scannow and let it finish — it repairs protected Windows files. Then run DISM /Online /Cleanup-Image /RestoreHealth, which repairs the component store SFC relies on. If SFC reported unfixable corruption, run it again after DISM completes. Restart the PC and use it normally to see whether the crashes stop.
5. Test the RAM for errors. If driver work hasn't fixed it, hardware becomes a real suspect. Press Win + R, type mdsched.exe, and run the Windows Memory Diagnostic, choosing "Restart now and check for problems." Let it complete — any reported error means a memory stick is defective and needs replacing, because bad RAM makes good driver code read garbage and throw exactly this exception. For a deeper check, MemTest86 from a USB drive runs multiple passes.
6. Temporarily remove third-party security software. Go to Settings > Apps > Installed apps, uninstall any third-party antivirus or firewall, and restart. Antivirus drivers hook deep into the kernel and are a classic trigger of SYSTEM_SERVICE_EXCEPTION — even the built-in Windows Security is enough protection for testing. Use the PC for a day or two; if crashes stop, the security product's driver was the cause. Reinstall it only with the latest version, or switch to a different product.

Did this fix it? Quick checklist

• No more 0x0000003B crashes after normal use for a few days
• Graphics driver clean-installed or rolled back to a stable version
• SFC and DISM both completed without unrepairable corruption
• Memory diagnostic passed with zero errors

If crashes continue after all six steps, open Event Viewer (Win + X > Event Viewer), go to Windows Logs > System, and look for BugCheck entries — the parameters often name the faulting driver file, like nvlddmkm.sys or a security product's .sys file, which tells you exactly what to remove or replace. As a last resort before replacing hardware, try a clean Windows install: back up your files first, and choose the "Keep nothing" option so every driver starts from scratch.