SYSTEM_SERVICE_EXCEPTION Windows 10: Complete Fix Guide (BSOD Stop Code 0x0000003B)
Fix SYSTEM_SERVICE_EXCEPTION BSOD on Windows 10. Step-by-step solutions for dxgkrnl.sys, nvlddmkm.sys, ntfs.sys, fltmgr.sys & more. Stop code 0x0000003B resolve
- Root cause 1: Faulty, outdated, or incompatible device drivers (GPU, network, filter drivers) are the #1 trigger — specifically files like nvlddmkm.sys (NVIDIA), dxgkrnl.sys (DirectX kernel), fltmgr.sys (filter manager), netio.sys (network I/O), and win32kbase.sys/win32kfull.sys (Win32 subsystem).
- Root cause 2: Corrupted system files, bad Windows updates, conflicting antivirus software, or hardware faults (especially RAM and storage) can all generate the SYSTEM_SERVICE_EXCEPTION stop code 0x0000003B.
- Quick fix summary: Boot into Safe Mode, identify the offending .sys file from the crash dump, update or roll back the associated driver, run SFC and DISM to repair system files, test RAM with Windows Memory Diagnostic, and uninstall recent Windows updates if the BSOD started after a patch.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| Update/Roll Back GPU Driver | BSOD references nvlddmkm.sys or dxgkrnl.sys | 10–20 min | Low |
| Update/Roll Back Network Driver | BSOD references netio.sys | 5–10 min | Low |
| SFC /scannow + DISM | Suspected corrupted system files or after bad Windows Update | 15–30 min | Very Low |
| Windows Memory Diagnostic | Random BSODs, no consistent .sys file, system keeps restarting | 30–60 min | Very Low |
| Uninstall Recent Windows Update | BSOD started immediately after a cumulative update | 10–15 min | Low |
| Clean Boot / Disable Third-Party Software | Antivirus or third-party filter driver suspected (fltmgr.sys) | 10–20 min | Low |
| Check Disk (chkdsk) | BSOD references ntfs.sys or storage-related files | 20–60 min | Low |
| Reinstall VMware Tools | BSOD occurs inside or after running VMware on Windows 10 | 10–15 min | Low |
| In-place Upgrade Repair Install | All other methods fail, frequent BSODs, unbootable system | 60–90 min | Medium |
| Fresh Windows 10 Install | Hardware confirmed good, OS is severely corrupted | 90–120 min | High (data loss) |
Understanding the SYSTEM_SERVICE_EXCEPTION Error
The SYSTEM_SERVICE_EXCEPTION blue screen (stop code 0x0000003B) appears when a Windows kernel-mode component or device driver violates system service access rules — typically by executing privileged instructions from non-privileged code, dereferencing a null/invalid pointer, or causing an unhandled exception inside a system service routine.
The full error message you will see on the blue screen reads:
Your PC ran into a problem and needs to restart.
Stop code: SYSTEM_SERVICE_EXCEPTION
Failing file: <filename>.sys (or not shown)
Common failing files and their meaning:
- nvlddmkm.sys — NVIDIA display driver kernel module
- dxgkrnl.sys — DirectX Graphics Kernel (often GPU-related)
- fltmgr.sys — Windows Filter Manager (antivirus, backup, VPN filter drivers)
- netio.sys — Network I/O subsystem (network driver conflict)
- ntfs.sys — NTFS file system driver (disk corruption or failing drive)
- win32kbase.sys / win32kfull.sys — Win32 kernel base (often bad Windows Update or display driver)
- ntoskrnl.exe — Windows kernel itself (often RAM, bad driver, or severe OS corruption)
Step 1: Identify the Offending Driver via Crash Dump
Before applying any fix blindly, read the crash dump to know exactly which component failed.
1a. Enable crash dumps if not already on:
Press Win + R → type sysdm.cpl → Advanced → Startup and Recovery → Settings → set "Write debugging information" to Small memory dump (256 KB). Set the dump path to %SystemRoot%\Minidump.
1b. Read the minidump with WinDbg:
Download WinDbg from the Microsoft Store ("WinDbg Preview"). Open a minidump file from C:\Windows\Minidump\ and run:
!analyze -v
Look for the MODULE_NAME and IMAGE_NAME fields — these point directly to the guilty driver or executable.
1c. Use WhoCrashed (free tool) for a quick human-readable report: Download from https://www.resplendence.com/whocrashed, run it, and it will parse all minidumps and display the probable cause.
Step 2: Boot into Safe Mode (if Windows Won't Start)
If Windows keeps restarting and you cannot log in:
- Force-restart your PC 3 times during boot (hold power button) to trigger Automatic Repair.
- Choose Troubleshoot → Advanced Options → Startup Settings → Restart.
- Press 4 for Safe Mode or 5 for Safe Mode with Networking.
Alternatively, boot from Windows 10 installation media → Repair your computer → Troubleshoot → Advanced Options → Startup Settings.
Step 3: Fix nvlddmkm.sys / dxgkrnl.sys (GPU Driver)
This is the most common SYSTEM_SERVICE_EXCEPTION cause on systems with NVIDIA or AMD graphics.
Option A — Update GPU Driver:
- Press
Win + X→ Device Manager. - Expand Display Adapters → right-click your GPU → Update driver → Search automatically.
- Or download the latest driver directly from https://www.nvidia.com/Download/index.aspx or https://www.amd.com/en/support.
Option B — Roll Back GPU Driver:
- Device Manager → Display Adapters → right-click GPU → Properties.
- Driver tab → Roll Back Driver (if available).
Option C — Clean install with DDU (Display Driver Uninstaller):
- Boot into Safe Mode.
- Run DDU (https://www.guru3d.com/files-details/display-driver-uninstaller-download.html) and select "Clean and restart."
- After reboot, install the fresh driver package.
Step 4: Fix fltmgr.sys (Filter Manager / Antivirus)
fltmgr.sys errors almost always point to a third-party filter driver — typically antivirus software, VPN clients, backup agents, or cloud sync tools.
- Perform a Clean Boot: Press
Win + R→msconfig→ Services tab → check "Hide all Microsoft services" → Disable all → Restart. - If the BSOD stops, re-enable services in groups to isolate the culprit.
- Temporarily uninstall third-party antivirus (use vendor removal tools, not just Add/Remove Programs).
- Update or reinstall the offending application.
Step 5: Fix netio.sys (Network Driver)
- Device Manager → Network Adapters → right-click your adapter → Update driver.
- If recently updated, roll back the driver.
- Disable IPv6 temporarily:
Control Panel → Network and Sharing Center → adapter Properties → uncheck Internet Protocol Version 6 (TCP/IPv6). - Reset TCP/IP stack:
netsh int ip reset
netsh winsock reset
ipconfig /flushdns
Restart after each command set.
Step 6: Fix ntfs.sys (File System / Disk)
- Open Command Prompt as Administrator.
- Run Check Disk on your Windows drive:
chkdsk C: /f /r /x
- Restart to allow chkdsk to run before Windows loads.
- Check drive health with CrystalDiskInfo or:
wmic diskdrive get status
Step 7: Repair System Files (SFC + DISM)
Corrupted system files can trigger SYSTEM_SERVICE_EXCEPTION referencing ntoskrnl.exe, win32kbase.sys, or win32kfull.sys.
Run these in order in an elevated Command Prompt:
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
Restart after completion and monitor for BSODs.
Step 8: Test RAM
- Press
Win + R→ typemdsched.exe→ Restart now and check for problems. - For a more thorough test, use MemTest86 (https://www.memtest86.com/) — run at least 2 full passes.
- If errors are found, reseat RAM sticks, try them one at a time, or replace faulty module(s).
Step 9: Uninstall Problematic Windows Updates
If the BSOD started after a Windows Update:
Settings → Update & Security → View update history → Uninstall updates.- Sort by date, right-click the most recent cumulative update → Uninstall.
- After uninstall, go back to Windows Update settings and Pause updates for 7 days while waiting for Microsoft to release a fix.
Step 10: Fix SYSTEM_SERVICE_EXCEPTION in VMware
VMware-related BSODs (particularly after installing VMware Workstation or Player on Windows 10) are caused by VMware's kernel drivers conflicting with Hyper-V or the host OS.
- Update VMware Workstation to the latest version.
- Reinstall VMware Tools inside the guest VM.
- If Hyper-V is also installed, disable it or use VMware's compatibility mode:
bcdedit /set hypervisorlaunchtype off
Restart after running the command. To re-enable Hyper-V later:
bcdedit /set hypervisorlaunchtype auto
- Check VMware KB articles for Windows 10 version-specific patches.
Step 11: Last Resort — In-Place Repair Upgrade
If nothing else works and your system is severely corrupted:
- Download the Windows 10 ISO from https://www.microsoft.com/en-us/software-download/windows10.
- Mount the ISO and run
setup.exe. - Choose Keep personal files and apps — this reinstalls Windows without deleting your data.
- This replaces all system files and effectively resolves persistent BSOD issues caused by OS corruption.
Frequently Asked Questions
# ============================================================
# SYSTEM_SERVICE_EXCEPTION Diagnostic & Fix Script
# Run PowerShell as Administrator
# ============================================================
# --- Step 1: List recent minidump files ---
Write-Host "=== Recent Crash Dump Files ==="
Get-ChildItem -Path "$env:SystemRoot\Minidump" -Filter "*.dmp" -ErrorAction SilentlyContinue |
Sort-Object LastWriteTime -Descending |
Select-Object -First 10 Name, LastWriteTime, @{N='SizeMB';E={[math]::Round($_.Length/1MB,2)}}
# --- Step 2: Check Windows Event Log for BSODs (last 7 days) ---
Write-Host "`n=== BSOD Events (Last 7 Days) ==="
$since = (Get-Date).AddDays(-7)
Get-WinEvent -FilterHashtable @{LogName='System'; Id=41; StartTime=$since} -ErrorAction SilentlyContinue |
Select-Object TimeCreated, Message | Format-List
# --- Step 3: Run SFC scan ---
Write-Host "`n=== Running System File Checker ==="
sfc /scannow
# --- Step 4: Run DISM to repair Windows image ---
Write-Host "`n=== Running DISM RestoreHealth ==="
DISM /Online /Cleanup-Image /RestoreHealth
# --- Step 5: Check disk for errors (schedules on next boot) ---
Write-Host "`n=== Scheduling CHKDSK on Next Boot ==="
chkdsk C: /f /r /x
# Note: Press Y when prompted to schedule for next restart
# --- Step 6: Reset network stack ---
Write-Host "`n=== Resetting Network Stack ==="
netsh int ip reset
netsh winsock reset
ipconfig /flushdns
Write-Host "Network stack reset. Please restart your PC."
# --- Step 7: List recently installed drivers ---
Write-Host "`n=== Drivers Installed in Last 30 Days ==="
Get-WmiObject Win32_PnPSignedDriver |
Where-Object { $_.DriverDate -and [datetime]::ParseExact($_.DriverDate.Substring(0,8),'yyyyMMdd',$null) -gt (Get-Date).AddDays(-30) } |
Select-Object DeviceName, DriverVersion, DriverDate, Manufacturer |
Sort-Object DriverDate -Descending
# --- Step 8: List recent Windows Updates ---
Write-Host "`n=== Recent Windows Updates (Last 30 Days) ==="
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10
# --- Step 9: Launch Windows Memory Diagnostic ---
Write-Host "`n=== Launching Windows Memory Diagnostic ==="
$choice = Read-Host "Run Memory Diagnostic now? (requires restart) [Y/N]"
if ($choice -eq 'Y' -or $choice -eq 'y') {
mdsched.exe
}
# --- Step 10: Disable Hyper-V (for VMware BSOD fix) ---
# Uncomment the line below ONLY if you use VMware and NOT Hyper-V
# bcdedit /set hypervisorlaunchtype off
Write-Host "`n=== Diagnostic Complete. Review output above and restart your PC. ==="Error Medic Editorial
The Error Medic Editorial team consists of senior DevOps engineers, SRE practitioners, and Windows systems specialists with 10+ years of experience diagnosing kernel-level failures, BSOD stop codes, and OS-level instability across enterprise and consumer environments. Our guides prioritize actionable, command-driven troubleshooting backed by official Microsoft documentation and real-world incident data.
Sources
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x3b--system-service-exception
- https://support.microsoft.com/en-us/windows/windows-stop-errors-blue-screen-or-black-screen-aac96926-a72c-4703-9c98-2b6f04f5a51b
- https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/driver-verifier
- https://answers.microsoft.com/en-us/windows/forum/all/blue-screen-system-service-exception/c47b5318-1c98-4c74-8ac2-c1be4027d207
- https://www.memtest86.com/
- https://kb.vmware.com/s/article/2146361