- Software and digital services
- Operating system
SYSTEM_SERVICE_EXCEPTION
SYSTEM_SERVICE_EXCEPTION (0x3B) on Windows: error while switching from normal to privileged code
Risk level
Medium
Proceed carefully and stop if the check is unclear.
Urgency
High
Quick answer
An exception happened while Windows ran a routine that moves from non-privileged to privileged code. Check which driver the screen names and what you installed most recently.
Safety first
Stop and check this first
- A 0x3B does not mean the graphics card or memory is faulty even when the named module is a graphics driver: the usual fix is a different driver version.
Safe checks you can perform
- Driver shown on screen
- Devices with an exclamation mark
- System File Checker
Leave these tasks to a qualified professional
- Do not attempt this professional task: Analyse the dump and identify the driver
- Do not attempt this professional task: Driver Verifier with pool options
What a technician must be able to justify
Technician visit
These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.
These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.
Analyse the dump and identify the driver
What they doIT support uses WinDbg with !analyze -v, checks KiBugCheckDriver, decodes the exception in parameter 1 with !error and applies .cxr with parameter 3 and kb.
They must show youthe output with the module, exception code and stack.
In writingwhich driver was updated or removed.
Driver Verifier with pool options
What they doIf a graphics driver is suspected, they enable Driver Verifier with the pool options on that driver.
They must show youthe settings and the dump obtained.
In writingthe result and that verification was turned off afterwards.
Before accepting a part or repair
Nothing has been shown yet. Do not accept a part swap based on the code alone.
Follow these steps
Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.
Driver shown on screen
- Who:
- you.
- How:
- photograph the blue screen and look for a .sys file name; note it with the time and what you were doing.
- Result that matters:
- whether a driver is named.
- If one is:
- update it from its maker's website and see if it repeats.
- If not:
- check devices and logs.
- Evidence to keep:
- photo with the .sys file.
Evidence: Bug Check 0x3B SYSTEM_SERVICE_EXCEPTION · Troubleshooting Windows unexpected restarts and stop code errors
Devices with an exclamation mark
- Who:
- you.
- How:
- open Device Manager, look for an exclamation mark and review the events in that driver's properties; choose Update driver.
- Result that matters:
- whether a device has a logged problem.
- If one does:
- it is the candidate to update or remove.
- If not:
- go to the System log.
- Evidence to keep:
- screenshot of the device properties.
Evidence: Bug Check 0x3B SYSTEM_SERVICE_EXCEPTION · Troubleshooting Windows unexpected restarts and stop code errors
System File Checker
- Who:
- you, as administrator.
- How:
- open Command Prompt as administrator, run sfc /scannow and restart when done.
- Result that matters:
- whether it reports repaired files.
- If it repaired files:
- watch whether the blue screen returns.
- If it found nothing:
- protected files are not the cause.
- Evidence to keep:
- screenshot of the SFC result.
Evidence: Stop code error or bug check troubleshooting (IT professionals)
Still not solved
If the error persists, stop here. See what the technician must do and show you.
Where this code applies
A code is meaningful only inside the right product and version context.
Primary scope
- System
- Software and digital services
- Brand
- Microsoft Windows
- Product type
- Operating system
Known code variants
- 0x0000003B
- 0x3B
- STOP 0x0000003B
- stop code SYSTEM_SERVICE_EXCEPTION
- SYSTEM SERVICE EXCEPTION
What it means
Microsoft defines 0x0000003B as an exception raised while running a routine that transitions from non-privileged to privileged code, on a system thread. It can come from a NULL pointer, a wrong address, memory freed too early or corrupted data structures; in the past it has been linked to graphics drivers passing bad data to the kernel. If a driver is identified, its name appears on screen. The code does not point to a part.
Warnings and stop conditions
- Mediumeditorial warning
A 0x3B does not mean the graphics card or memory is faulty even when the named module is a graphics driver: the usual fix is a different driver version.
Evidence: Bug Check 0x3B SYSTEM_SERVICE_EXCEPTION
Symptoms and causes
Probable causes · in order
- Recently added or updated driver or serviceCommon
Microsoft suggests removing or updating it and working out what changed before the code appeared.
Evidence: Bug Check 0x3B SYSTEM_SERVICE_EXCEPTION
- Graphics driver passing bad dataPossible
Microsoft has linked it to excessive paged pool use by graphics drivers. Suspected if the named module belongs to the graphics card.
Evidence: Bug Check 0x3B SYSTEM_SERVICE_EXCEPTION
- Damaged system filesPossible
For this code, Microsoft's IT guidance points to System File Checker.
Evidence: Stop code error or bug check troubleshooting (IT professionals)
Virtual technician
Does SYSTEM_SERVICE_EXCEPTION still appear after these checks?
Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.
Sources and technical references
- 1
Bug Check 0x3B SYSTEM_SERVICE_EXCEPTION
Microsoft · 2026 · official_doc
- 2
Stop code error or bug check troubleshooting (IT professionals)
Microsoft · 2026 · official_doc
- 3
Troubleshooting Windows unexpected restarts and stop code errors
Microsoft · 2026 · official_doc
Was this entry useful?