0xPC Error Codes Look up a code
One safety rule: if a message shows a phone number to call, it is a scam: Microsoft never does that. Check any warning in 5 questions.

Home › Blue and Black Screen Stop Codes › SYSTEM_SERVICE_EXCEPTION (0x3B): When a Windows Service Crashes Everything

0x3BStop Codes

SYSTEM_SERVICE_EXCEPTION (0x3B): When a Windows Service Crashes Everything

By Editorial Team · · 9 min read ✓ Checked against Microsoft documentation

In plain English

If you hit 0x3B with SYSTEM_SERVICE_EXCEPTION, Windows crashed while a system service was running code in the background. If you want the wider map of blue and black screen stop codes in plain English, start there, then come back here for this specific crash.

This stop code often starts after a recent driver install, app install, antivirus change, or Windows update.

First safe step

Think back to the last thing that changed, then roll back or remove that one change before you try deeper repairs: a new driver, an app install, an antivirus change, or a Windows update in the day or two before the crashes started.

Try these in order, cheapest first

One change at a time. Stop when the crashes stop.

1What changed last?Free
2Roll back that one changeFree
3Windows won't stay open: Safe ModeFree
4Rollback didn't fix it
5Repair or replacement

If you hit 0x3B with SYSTEM_SERVICE_EXCEPTION, Windows crashed while a system service was running code in the background. If you want the wider map of blue and black screen stop codes in plain English, start there, then come back here for this specific crash.

This stop code often starts after a recent driver install, app install, antivirus change, or Windows update. It is different from the 0x0A driver-IRQL page for the crash that names a driver problem, which points to a different kind of memory-access failure.

The safest first move is simple, roll back the last change before you try scans, repair commands, or part replacement. If your blue screen began right after patching, you may also need the first-30-minutes update rollback guide before going deeper.

What SYSTEM_SERVICE_EXCEPTION (0x3B) means

A SYSTEM_SERVICE_EXCEPTION crash means Windows hit a failure while a system service was running in the background. In plain English, part of Windows was doing normal system work and something it depended on, often a driver, app, or security tool, caused the session to break hard enough for a blue screen.

That is different from the 0x0A driver-IRQL page for the crash that names a driver problem. Both can involve drivers, but 0x3B points to a system-service crash path, not the specific driver-IRQL path covered there. If your blue screen actually shows a .sys file name, check the stop code page for crashes that name a .sys driver on screen as well.

A very common pattern is that SYSTEM_SERVICE_EXCEPTION starts soon after a change. That change might be a new graphics, audio, Wi-Fi, or printer driver, a fresh app install, antivirus, VPN software, or a recent Windows update.

First safe step: think back to the last thing that changed, then roll back or remove that one change before you try deeper repairs. If the timing lines up with a patch, the first-30-minutes update rollback guide is the best next read.

1 Check the recent change first Free

  1. Start with a simple timeline. Ask yourself what changed in the day or two before SYSTEM_SERVICE_EXCEPTION started: a new graphics, Wi-Fi, audio, chipset, or printer driver, a new app, a Windows update, a hardware utility, or a cleanup tool. Write down the change, when the first crash happened, and whether the blue screen appears on every boot or only during one task like gaming, printing, or opening a browser.
  2. If the timing lines up, undo the newest change first. Remove the newest app from Control Panel or roll back the newest driver in Device Manager. Security software is a common trigger here, especially third-party antivirus, VPN filters, motherboard tuning tools, RGB control apps, fan-control utilities, and registry or driver "cleaners."

If the crashes began right after Windows installed updates, focus on that before deeper repair work. Use the first-30-minutes update rollback guide, or go straight to uninstalling a bad recent update if you already know which patch started it. A recent change is still the best lead even if the stop code only appears once or twice a day.

Pay attention to what the blue screen actually shows. If the crash names a specific .sys file on screen, check the stop code page for crashes that name a .sys driver on screen. If you instead have a crash that clearly points to an IRQL driver fault, use the 0x0A driver-IRQL page for the crash that names a driver problem. If nothing obvious changed, keep going to the next checks on this page.

2 Roll back drivers and software safely Free

Roll back one suspect at a time, then restart and test. If you changed two or three things on the same day, start with the one most closely tied to graphics, audio, networking, storage, antivirus, or a hardware helper app. Changing several things at once makes it hard to tell which one stopped SYSTEM_SERVICE_EXCEPTION.

  1. For a driver, open Device Manager, find the device, open its properties, and check the driver tab. If Roll Back Driver is available, use it first. If it is grayed out, uninstall the device or its driver package only if you know Windows can reinstall a safe version after restart. If the blue screen actually names a .sys file, compare this page with the stop code page for crashes that name a .sys driver on screen.
  2. For a new app, utility, security suite, RGB tool, motherboard helper, VPN, overclocking tool, or backup filter, remove it from Control Panel or installed apps, then restart before you install anything else. If the crash began right after a Windows patch or optional driver update, use the first-30-minutes update rollback guide. If you specifically need help uninstalling a bad recent update, follow uninstalling a bad recent update.

If Windows does not stay open long enough to finish the rollback, move to Safe Mode when Windows will not stay up long enough to work and remove the same suspect there. If your crash points more toward a driver reaching the wrong memory level than a system-service failure, use the 0x0A driver-IRQL page for the crash that names a driver problem instead.

✓ Crashes gone? You can stop here.

3 If Windows will not stay open long enough Free

If the desktop crashes before you can remove the last change, use Safe Mode when Windows will not stay up long enough to work. The goal is simple: get Windows open long enough to uninstall the last app, utility, antivirus change, or driver package, then restart and test normally.

Once you are in Safe Mode, remove only the most recent suspect item. Do one change at a time, restart, and see whether SYSTEM_SERVICE_EXCEPTION comes back. If the crashes started right after Patch Tuesday or another Windows update, use uninstalling a bad recent update or the first-30-minutes update rollback guide instead of guessing.

If the blue screen shows a specific .sys file before the restart, that is a different clue path. Use the stop code page for crashes that name a .sys driver on screen. If the crash is the driver-IRQL type instead, go to the 0x0A driver-IRQL page for the crash that names a driver problem.

Keep this recovery step narrow. For 0x3B, the best use of recovery tools is to undo the last change and test again, not to jump through every repair option at once. If Windows stays stable after that rollback, you have likely found the trigger.

4 What to do if the rollback did not fix it

If the crashes kept happening after you rolled back the recent driver, app, or utility change, try to narrow Windows down to basic startup items. A clean boot can show whether a background service or startup program is still colliding with the system service that 0x3B was using. If the blue screen started right after Patch Tuesday or another install wave, use the first-30-minutes update rollback guide before you spend time on deeper repairs.

If you have a restore point from before the first crash, that is the next safe test. Pick a date before the problem began, let Windows restart, and then use the PC normally for a while. This is often faster than chasing several small changes one by one.

Only after the rollback path and restore point check should you move on to file and disk repairs. Run SFC first, then DISM if SFC reports corruption it cannot fix. If you also suspect storage trouble, check the disk for file-system errors. These steps can repair damaged Windows files, but they will not usually remove a bad driver conflict by themselves.

Stop here and change direction if the PC still throws SYSTEM_SERVICE_EXCEPTION during normal use after rollback, restore, and file checks. Repeated crashes at that point often mean Windows needs a repair install, or that the fault is being pushed by a specific driver path such as the one covered on the stop code page for crashes that name a .sys driver on screen or the 0x0A driver-IRQL page for the crash that names a driver problem.

5 When to move to repair or replacement

If SYSTEM_SERVICE_EXCEPTION keeps coming back after you cleanly removed the last driver, app, antivirus, or update change, the problem may be deeper than one bad install. At that point, think in two buckets: Windows itself may be damaged, or a hardware part such as memory or storage may be starting to fail. Repeated blue screens during ordinary tasks are the point where repair work or hands-on testing starts to make more sense than more guessing.

Watch the blue screen wording each time. If the pattern shifts and the crash starts to look like a driver access problem, use the 0x0A driver-IRQL page for the crash that names a driver problem. If the screen names a specific .sys file, use the stop code page for crashes that name a .sys driver on screen, because that clue usually gives you a narrower suspect list than a plain 0x3B stop code.

If the crashes began right after Patch Tuesday or another Windows update and you have not fully tested that path yet, go back to the first-30-minutes update rollback guide. If Windows becomes too unstable to stay open while you decide, use Safe Mode when Windows will not stay up long enough to work so you can reach your files and repair options more safely.

A calm rule works well here: if the recent change is gone, the crash still returns, and the screen does not point clearly to a single driver, move on to a repair install, hardware testing, or a local repair shop you trust. If your PC is older and also showing disk errors, failed updates, or random restarts, replacement can be the cheaper answer than chasing a stubborn 0x3B for weeks.

Frequently asked questions

What should I do if 0x3B happened only once?

Restart, save your work often for the next few days, and note what changed just before the crash. If it does not return, no repair is needed. If it returns, start with that note and the recent change it points to.

Does a 0x3B crash mean my files are gone?

Usually no. Work that was open and unsaved when Windows stopped may be lost, but files already saved to the drive usually stay in place. Check the files you were using after the restart, then make a backup.

The short version

For most readers, SYSTEM_SERVICE_EXCEPTION (0x3B) will end as a timing story. The crash arrived after something changed, and it stopped when that change was gone. Keep a short note of what you removed, and do not reinstall it just to check. That note will help if the crash returns weeks later.

If the blue screen comes back with a different code or a named driver, treat that as new information. Follow that clue instead, and if the crashes keep changing, stop swapping drivers and get the PC checked before your files are at risk. A single clear clue is easier to fix than a moving pattern.

Different number on screen?

Type it exactly as it appears and get the plain-English answer.

Look up a code

Pop-up telling you to call?

That is a scam. Microsoft never asks you to phone a number.

Check it in 5 questions