Fix SYSTEM_SERVICE_EXCEPTION (0x3B): Drivers, RAM and Firmware

Q: It names ntoskrnl.exe — is that the cause?

No — ntoskrnl is just where the exception surfaced. The real culprit is a third-party driver in the stack; the dump's STACK_TEXT reveals it.

Sources linked 1 min read May 5, 2026 · by Ryan Bennett

Your PC blue-screens with SYSTEM_SERVICE_EXCEPTION (stop code 0x0000003B).

What it means: an exception occurred while code was transitioning into the kernel. A buggy driver or corrupted data structure can cause it. Check the crash details and drivers, then investigate RAM and firmware if the evidence points there.

Fix 1: Update or roll back the recent driver

Update graphics, network, audio and chipset drivers from the hardware vendor (not just Windows Update).
If it began after a driver change, roll it back (Device Manager → device → Driver → Roll Back).
Third-party AV/VPN/virtualization drivers are common triggers — update or temporarily remove to test.

Fix 2: Repair system files

Admin Command Prompt:

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

Fix 3: Test RAM and update firmware (the skipped steps)

Run Windows Memory Diagnostic (mdsched.exe) or MemTest86 — faulty RAM throws 0x3B.
Update your BIOS/UEFI firmware from the motherboard/PC maker; old firmware causes kernel-transition faults.

Fix 4: Read the dump to pinpoint the driver

The crash dump names the faulting module. Follow how to find the driver behind a Blue Screen and act on the .sys it names.

FAQ

It names ntoskrnl.exe — is that the cause? No — ntoskrnl is just where the exception surfaced. The real culprit is a third-party driver in the stack; the dump’s STACK_TEXT reveals it.

Sources: Microsoft Learn — Bug Check 0x3B SYSTEM_SERVICE_EXCEPTION