ERRORBlue screen0x0000003B
SYSTEM_SERVICE_EXCEPTIONStop code 0x0000003B
SYSTEM_SERVICE_EXCEPTION (stop code 0x0000003B) means an exception occurred while a system routine was running, almost always because of a faulty, outdated or incompatible driver. Graphics, audio and third-party kernel drivers are frequent culprits. Updating or rolling back the driver named in the dump usually resolves it.
What it means
SYSTEM_SERVICE_EXCEPTION, bug check 0x0000003B, fires when an exception occurs while the processor is executing a system service routine in kernel mode. Because kernel code runs with no safety net, an unhandled exception there stops the system. The code that misbehaves is almost always a driver rather than Windows itself.
Most likely causes
- Graphics drivers, especially after an update or a new GPU; these also produce VIDEO_TDR_FAILURE.
- Audio and network drivers.
- Third-party kernel software: VPN clients, antivirus, virtualisation, overclocking or RGB utilities that install low-level drivers.
- Corrupted system files, less often.
Fixes
1. Identify the driver from the dump. Open C:\Windows\Minidump with BlueScreenView, or run !analyze -v in WinDbg. The faulting .sys module points at the responsible device or application.
2. Update or roll back that driver. Get graphics, chipset and storage drivers from the vendor, not only Windows Update. If the crashes began right after a driver update, roll it back in Device Manager (device → Properties → Driver → Roll Back Driver).
3. Remove suspect third-party kernel software temporarily: a recently installed VPN, antivirus or system utility. If the crashes stop, that software is the cause.
4. Repair system files if no driver stands out:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannowGeneral blue-screen approach
Most stop codes are caused by drivers, hardware faults, or corrupted system files, in that order of likelihood. The efficient path is:
- Note what changed. A new driver, a Windows update, new hardware, or an overclock immediately before the crashes began is the prime suspect. Roll it back or remove it.
- Boot to Safe Mode if Windows will not stay up: hold Shift and restart, or interrupt boot three times to reach the recovery environment, then Troubleshoot → Advanced options → Startup Settings → Safe Mode.
- Update or roll back drivers, especially graphics, storage and chipset, from the vendor rather than only Windows Update.
- Repair system files from an elevated prompt:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow- Test hardware: Windows Memory Diagnostic for RAM, the drive vendor's tool and chkdsk for storage, and check temperatures.
- Read the dump. The minidump in
C:\Windows\Minidumpnames the faulting driver when analysed with WinDbg or a tool like BlueScreenView.
Frequently asked questions
What causes SYSTEM_SERVICE_EXCEPTION?
An exception raised while running kernel-level code, nearly always from a driver that is buggy, outdated or incompatible with the current Windows version. Graphics drivers, audio drivers and third-party tools that install kernel components (VPNs, antivirus, virtualisation) are common sources.
How do I find which driver caused it?
The minidump names it. Open C:\Windows\Minidump with BlueScreenView or analyse it in WinDbg with !analyze -v; the faulting module is usually a .sys file you can trace to a device or application. Update or roll back that driver.