What is the SYSTEM_SERVICE_EXCEPTION stop code and what does 0x0000003B mean?

Stop code 0x0000003B (SYSTEM_SERVICE_EXCEPTION) means a kernel-mode service or driver attempted an illegal operation — such as accessing invalid memory or violating processor privilege levels. Windows treats this as an unrecoverable kernel error and halts the system to prevent data corruption. The hex code 0x0000003B is logged in the minidump file for diagnostic purposes. The specific driver responsible is usually appended in parentheses (e.g., nvlddmkm.sys), but when Windows cannot identify it, only the stop code is shown.

Why does SYSTEM_SERVICE_EXCEPTION only happen during gaming or when I open a browser?

Crashes triggered by specific activities usually point to the driver handling that activity. Gaming crashes that name nvlddmkm.sys or dxgkrnl.sys indicate a GPU driver issue — update or clean-install your NVIDIA or AMD drivers using DDU. Browser crashes that name win32kbase.sys or win32kfull.sys suggest a Windows UI kernel issue often caused by a recent Windows Update or a GPU driver interaction with hardware acceleration. Try disabling GPU hardware acceleration in your browser settings as a temporary workaround while you update drivers.

How do I fix SYSTEM_SERVICE_EXCEPTION in Windows 10 when it keeps restarting and I cannot log in?

Boot into Safe Mode: power off the PC abruptly three times during the Windows logo to trigger Windows Recovery Environment, then go to Troubleshoot > Advanced Options > Startup Settings > Restart and press 4. In Safe Mode, open Device Manager and roll back or uninstall the most recently changed driver. Run 'sfc /scannow' from an elevated command prompt. If Safe Mode also BSODs, boot from a Windows 10 USB installer, choose 'Repair your computer,' and use Startup Repair or a command-prompt-based SFC scan. As a last resort, use System Restore from the recovery options to revert to a known-good state.

What causes SYSTEM_SERVICE_EXCEPTION fltmgr.sys specifically on Windows 10?

fltmgr.sys (Filter Manager) crashes are almost always caused by third-party filesystem filter drivers installed by antivirus software, backup agents (e.g., Acronis, Carbonite), encryption tools, or cloud storage clients (e.g., OneDrive, Dropbox). These tools attach themselves to the Windows filesystem filter stack, and a bug or version incompatibility in their kernel-mode component crashes fltmgr.sys. Fix: uninstall the suspect application using its dedicated removal tool, not just the standard uninstaller, then reboot and reinstall only the latest version. If you cannot identify which application is responsible, use Autoruns (Sysinternals) to inspect all registered filesystem filter drivers.

Why does SYSTEM_SERVICE_EXCEPTION appear in Windows 10 running inside VMware?

When Windows 10 runs as a VMware guest and shows this BSOD, the most common causes are: (1) outdated VMware Tools — the guest additions package that installs kernel-mode drivers; always keep VMware Tools current. (2) NIC driver mismatch — switch the VM's NIC type to VMXNET3 in VMware Workstation settings. (3) Host-level conflict — if the Windows 10 host machine has both Hyper-V and VMware installed, they conflict because both try to install hypervisor-level kernel components. Disable Hyper-V on the host with 'bcdedit /set hypervisorlaunchtype off' and reboot. (4) Hardware compatibility settings — in the VM's .vmx file, ensure 'virtualHW.version' is compatible with your VMware Workstation version.

SYSTEM_SERVICE_EXCEPTION Windows 10 Blue Screen (BSOD): Complete Fix Guide

Fix the SYSTEM_SERVICE_EXCEPTION BSOD on Windows 10. Step-by-step guide covering dxgkrnl.sys, nvlddmkm.sys, ntfs.sys, fltmgr.sys causes and proven fixes.

Last updated: March 1, 2026

Last verified: March 1, 2026

2,325 words

Key Takeaways

SYSTEM_SERVICE_EXCEPTION (Stop Code 0x0000003B) is triggered when a system service or driver violates kernel-mode memory protection rules, most commonly caused by outdated or corrupt GPU drivers (nvlddmkm.sys, dxgkrnl.sys), filesystem filter drivers (fltmgr.sys, ntfs.sys), or network stack components (netio.sys).
Faulty RAM, corrupt system files, incompatible third-party antivirus software, and VMware/Hyper-V virtualization conflicts are secondary but common root causes, especially when no specific .sys file is named in the crash dump.
Quick fix path: (1) Identify the offending .sys file in the minidump using WinDbg or WhoCrashed, (2) update or roll back the associated driver, (3) run SFC /scannow and DISM to repair system files, (4) test RAM with Windows Memory Diagnostic, and (5) if the PC keeps restarting in a loop, boot into Safe Mode first to perform repairs safely.

Fix Approaches Compared
Method	When to Use	Time	Risk
Update/Roll Back GPU Driver (nvlddmkm.sys, dxgkrnl.sys)	BSOD names a GPU-related .sys file or crashes during gaming/video	10-20 min	Low
SFC /scannow + DISM Repair	No specific .sys named; general corruption suspected; ntoskrnl.exe crashes	20-45 min	Very Low
Windows Memory Diagnostic / MemTest86	Random BSODs with no consistent .sys file; system keeps restarting	1-8 hrs	Very Low
Uninstall Third-Party Antivirus	fltmgr.sys or unknown .sys crashes after AV install	5 min	Low
Roll Back Windows Update	BSOD started after a Windows Update; win32kbase.sys or win32kfull.sys named	15-30 min	Medium
Update Network Driver (netio.sys)	Crashes happen during heavy network activity or VPN use	10-15 min	Low
VMware/Hyper-V Fix (vmware blue screen)	Running Windows 10 as a VM or with virtualization software installed	15-30 min	Medium
Startup Repair / Reset Windows	All else fails; system unbootable or crashes immediately on login	30-120 min	High (data risk)

Understanding SYSTEM_SERVICE_EXCEPTION on Windows 10

The full stop error message you see on the blue screen reads:

Your PC ran into a problem and needs to restart.
Stop Code: SYSTEM_SERVICE_EXCEPTION

Sometimes Windows appends the offending driver filename:

STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION (dxgkrnl.sys)
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION (nvlddmkm.sys)
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION (fltmgr.sys)
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION (netio.sys)
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION (ntfs.sys)
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION (win32kbase.sys)
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION (win32kfull.sys)
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION (ntoskrnl.exe)

This error means a routine running in kernel mode attempted an illegal operation — usually accessing a memory address it doesn't own or calling a privileged instruction incorrectly. Because this happens in the kernel, Windows has no choice but to crash entirely.

Step 1: Identify the Root Cause from the Minidump

Before applying any fix blindly, read the crash dump to know exactly which driver or file is responsible.

Option A — WhoCrashed (Easy, Free)

Download and install WhoCrashed from resplendence.com.
Launch it and click Analyze.
Look for the "Caused by driver" field — this tells you the exact .sys file.

Option B — WinDbg (Advanced)

Install WinDbg from the Microsoft Store or Windows SDK.
Open WinDbg, go to File > Open Crash Dump, and navigate to C:\Windows\Minidump\.
In the command window, type: !analyze -v
Read the MODULE_NAME and IMAGE_NAME fields.

Enable minidump creation if disabled:

Right-click This PC > Properties > Advanced system settings.
Under Startup and Recovery, click Settings.
Set "Write debugging information" to Small memory dump (256 KB).
Confirm the dump path is %SystemRoot%\Minidump.

Step 2: Driver-Specific Fixes

nvlddmkm.sys / dxgkrnl.sys (NVIDIA GPU)

These are the most common culprits. nvlddmkm.sys is the NVIDIA kernel-mode driver; dxgkrnl.sys is the DirectX Graphics Kernel.

Download DDU (Display Driver Uninstaller) from guru3d.com.
Boot into Safe Mode (hold Shift while clicking Restart > Troubleshoot > Advanced > Startup Settings > Safe Mode with Networking).
Run DDU and choose "Clean and restart."
After reboot, download the latest NVIDIA driver from nvidia.com and do a Custom / Clean install.
If crashes persist after updating, roll back: Device Manager > Display Adapters > Right-click NVIDIA card > Properties > Driver tab > Roll Back Driver.

For dxgkrnl.sys on AMD GPUs: Use AMD Cleanup Utility, then reinstall the latest AMD Adrenalin driver.

fltmgr.sys (Filter Manager — Often Antivirus)

fltmgr.sys is Windows' filesystem filter manager. Third-party antivirus products, backup agents, and encryption tools register as filter drivers and can corrupt this interface.

Open Programs and Features and uninstall any recently installed antivirus or backup software.
Use the vendor's dedicated removal tool (e.g., ESET Uninstaller, Avast Clear, Norton Remove and Reinstall).
Reboot and test. If stable, reinstall the AV after updating it to the latest version.

netio.sys (Network I/O Subsystem)

Crashes naming netio.sys usually stem from VPN clients, network filter drivers, or outdated NIC drivers.

Update NIC driver: Device Manager > Network Adapters > Right-click your adapter > Update driver.
Uninstall VPN software temporarily to test.
Reset TCP/IP stack: Run the commands in the code block below.

ntfs.sys (NTFS Filesystem Driver)

ntfs.sys crashes often indicate disk errors or filesystem corruption.

Run chkdsk C: /f /r /x in an elevated command prompt (schedule for next reboot if the drive is in use).
Check drive health with CrystalDiskInfo or the manufacturer's diagnostic tool.
If S.M.A.R.T. data shows reallocated sectors or pending sectors, back up immediately — the drive may be failing.

win32kbase.sys / win32kfull.sys (Windows Kernel UI)

These usually appear after a Windows Update. The fix is to roll back the update.

Settings > Update & Security > View update history > Uninstall updates.
Identify the most recent cumulative update and uninstall it.
Alternatively, use DISM to revert: DISM /Online /Get-Packages then DISM /Online /Remove-Package /PackageName:<KB_NAME>.

ntoskrnl.exe (Windows Kernel — Usually RAM)

When ntoskrnl.exe is listed without another .sys file, the kernel itself crashed — most often due to bad RAM.

Press Win + R, type mdsched.exe, and press Enter to run Windows Memory Diagnostic.
For more thorough testing, create a bootable MemTest86 USB and run it overnight.
If errors are found, try reseating RAM sticks, testing them one at a time, or replacing them.

Step 3: Repair System Files (SFC + DISM)

Run these regardless of the specific .sys file — corrupt Windows system files can cause any BSOD variant.

Open Command Prompt as Administrator.
Run DISM first to repair the Windows image store:
```
DISM /Online /Cleanup-Image /RestoreHealth
```
Then run System File Checker:
```
sfc /scannow
```
Reboot and check if the BSOD recurs.

Step 4: VMware / Hyper-V Specific Fix

If you are running Windows 10 inside VMware Workstation or VirtualBox and see this BSOD:

Update VMware Tools to the latest version from within the VM.
In VMware Workstation settings, set the VM to use VMXNET3 NIC instead of E1000.
Ensure the host machine's virtualization extensions (VT-x / AMD-V) are enabled in BIOS.
Disable Hyper-V on the host if you are using VMware (they conflict): bcdedit /set hypervisorlaunchtype off — reboot after.
If running Windows 10 as the host with VMware installed, update VMware to the latest version; older VMware versions install kernel drivers that conflict with Windows security updates.

Step 5: If Windows Keeps Restarting (Boot Loop)

If the system crashes before you can log in:

Force the PC off three times in a row during the Windows logo to trigger Automatic Repair mode.
Go to Troubleshoot > Advanced Options > Startup Settings > Restart, then press 4 for Safe Mode.
In Safe Mode, perform driver rollbacks, SFC scans, and uninstall problematic software.
If Safe Mode also crashes, boot from a Windows 10 USB installation media and use Startup Repair or open a command prompt to run sfc /scannow and chkdsk from the recovery environment.

Step 6: Last Resort — Reset Windows 10

If all else fails and you have confirmed the hardware is healthy:

Settings > Update & Security > Recovery > Reset this PC.
Choose Keep my files to preserve personal data.
Select Cloud download for a fresh copy of Windows files.

This resolves virtually every software-caused SYSTEM_SERVICE_EXCEPTION instance.

Frequently Asked Questions

powershell

# ============================================================
# SYSTEM_SERVICE_EXCEPTION Diagnostic & Repair Script
# Run PowerShell as Administrator
# ============================================================

# --- 1. Check for recent BSODs in Event Log ---
Write-Host "`n[1] Recent BSOD Events (last 7 days):" -ForegroundColor Cyan
Get-WinEvent -FilterHashtable @{
    LogName = 'System'
    Id      = 1001
    StartTime = (Get-Date).AddDays(-7)
} -ErrorAction SilentlyContinue | Select-Object TimeCreated, Message | Format-List

# --- 2. List minidump files ---
Write-Host "`n[2] Minidump files found:" -ForegroundColor Cyan
$dumpPath = "$env:SystemRoot\Minidump"
if (Test-Path $dumpPath) {
    Get-ChildItem $dumpPath -Filter *.dmp | Sort-Object LastWriteTime -Descending | Select-Object Name, LastWriteTime, Length
} else {
    Write-Host "No minidump folder found. Enable small memory dumps in System Properties > Startup and Recovery."
}

# --- 3. Repair Windows image with DISM ---
Write-Host "`n[3] Running DISM RestoreHealth (this may take 10-20 minutes)..." -ForegroundColor Cyan
DISM /Online /Cleanup-Image /RestoreHealth

# --- 4. System File Checker ---
Write-Host "`n[4] Running SFC /scannow..." -ForegroundColor Cyan
sfc /scannow

# --- 5. Check disk for errors (schedules for next boot if C: is busy) ---
Write-Host "`n[5] Scheduling CHKDSK on C: drive..." -ForegroundColor Cyan
echo Y | chkdsk C: /f /r /x

# --- 6. Reset TCP/IP stack (fixes netio.sys crashes) ---
Write-Host "`n[6] Resetting TCP/IP stack and Winsock (fixes netio.sys)..." -ForegroundColor Cyan
netsh int ip reset resetlog.txt
netsh winsock reset
netsh advfirewall reset

# --- 7. List all third-party kernel drivers (non-Microsoft) ---
Write-Host "`n[7] Third-party kernel drivers (potential BSOD sources):" -ForegroundColor Cyan
Get-WmiObject Win32_SystemDriver | Where-Object {
    $_.PathName -notmatch 'system32\\drivers' -or
    (Get-AuthenticodeSignature $_.PathName -ErrorAction SilentlyContinue).SignerCertificate.Subject -notmatch 'Microsoft'
} | Select-Object Name, DisplayName, State, PathName | Format-Table -AutoSize

# --- 8. Check GPU driver version ---
Write-Host "`n[8] Current Display Adapter Driver Info:" -ForegroundColor Cyan
Get-WmiObject Win32_VideoController | Select-Object Name, DriverVersion, DriverDate | Format-List

# --- 9. Check RAM for errors using Windows Memory Diagnostic ---
Write-Host "`n[9] Launching Windows Memory Diagnostic (choose 'Restart now'):" -ForegroundColor Cyan
# Uncomment the line below to auto-launch:
# Start-Process mdsched.exe

# --- 10. Disable Hyper-V (for VMware conflict scenarios) ---
# WARNING: Only run if you use VMware and NOT Hyper-V
# Uncomment the block below if needed:
# Write-Host "`n[10] Disabling Hyper-V hypervisor (VMware fix)..." -ForegroundColor Yellow
# bcdedit /set hypervisorlaunchtype off
# Write-Host "Reboot required for change to take effect."

Write-Host "`n[Done] Diagnostic complete. Review output above and reboot." -ForegroundColor Green
Write-Host "If crashes continue, open the latest .dmp file in WinDbg and run: !analyze -v" -ForegroundColor Yellow

Error Medic Editorial

The Error Medic Editorial team consists of senior DevOps engineers, Windows kernel specialists, and SRE professionals with combined decades of experience diagnosing Windows stop errors, driver conflicts, and system-level failures across enterprise and consumer environments. Our guides are based on hands-on lab testing, official Microsoft documentation, and analysis of thousands of real-world crash dumps.

Sources

Explore More windows Guides

Acer Aspire Blue Screen of Death Fix: How to Stop BSOD Crashes on Acer Laptops

Fix Acer Aspire Blue Screen of Death errors fast. Step-by-step guide covering driver updates, RAM checks, overheating, and Windows repair commands.

Acer Aspire Blue Screen of Death Fix: Step-by-Step Troubleshooting Guide (BSOD Errors Solved)

Fix Acer Aspire blue screen of death errors fast. Covers MEMORY_MANAGEMENT, DRIVER_IRQL, KERNEL_SECURITY_CHECK and more. Step-by-step commands included.

Acer Aspire Blue Screen of Death Fix: Stop Codes, Causes & Complete Solutions

Fix Acer Aspire Blue Screen of Death errors fast. Covers MEMORY_MANAGEMENT, DRIVER_IRQL, KERNEL_SECURITY_CHECK_FAILURE & more with exact commands.