Windows 11 - Frequent BSOD (SYSTEM_SERVICE_EXCEPTION) after recent Update

snow day calculator 10 Reputation points
2026-05-19T12:59:09.5366667+00:00

After installing the latest Windows 11 update (May 2026), my PC started getting frequent Blue Screen of Death with error SYSTEM_SERVICE_EXCEPTION (win32kfull.sys).

What I have tried:

  • Ran SFC /scannow and DISM commands
  • Updated all drivers via Windows Update
  • Performed Clean Boot
  • Checked Memory with Windows Memory Diagnostic

System Info:

  • Windows 11 Pro 24H2
  • Latest BIOS installed
  • Hardware: [Your CPU + GPU model]

Issue happens mostly when using Chrome + multiple tabs.

Can anyone suggest next troubleshooting steps or if this is a known issue with recent update?

Thanks in advance!

Windows for home | Windows 11 | Performance and system failures
0 comments
Answer accepted by question author
Hendrix-V 19,300 Reputation points Microsoft External Staff Moderator
2026-05-20T01:47:22.54+00:00

Hi snow day calculator,

It appears the crashes started after a recent update, which helps narrow it down. A SYSTEM_SERVICE_EXCEPTION typically points to an issue with how a system service interacts with drivers or memory, rather than a problem with the core Windows files themselves.

Since you’ve already completed the common checks, the focus should now shift to identifying the specific component triggering the crash. Here are some recommended next steps that you can try:

1, Identify the exact driver from crash logs

  • Go to: C:\Windows\Minidump
  • Zip the latest .dmp file and review it (or share it if needed)

2, Use Driver Verifier to expose hidden conflicts

  • Press Win + R > type verifier
  • Select Create standard settings
  • Choose Automatically select all drivers
  • Restart the PC
  • If a crash occurs, note the driver name shown on the BSOD.

3, Check update vs driver interaction

  • Temporarily uninstall the most recent update
  • Then test stability
  • If the issue stops, it indicates a compatibility interaction with an existing driver setup.

4, Update critical OEM drivers (manual install)

  • Focus on:
    • Graphics (GPU)
    • Chipset
    • Storage controller
  • Install directly from your device manufacturer’s website rather than Windows Update.

5, Validate disk / storage layer - run: chkdsk C: /f /r in Command Prompt

At this stage, isolating the specific driver involved is the most effective way to reach a stable resolution. Once the faulting module is identified, the fix becomes much more targeted.

Let me know if you need further assistance, feel free to ask me by clicking "Add Comment" or "Add Answer" if you cannot add comment so your response will be visible. Thanks for your effort.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Was this answer helpful?

4 people found this answer helpful.
0 comments

2 additional answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-05-19T12:59:34.33+00:00

    SYSTEM_SERVICE_EXCEPTION (bug check 0x3B) indicates a system service or driver fault. The context shows general guidance for this stop code and for recurring blue screens after updates.

    Based on the provided information and what has already been tried (SFC, DISM, driver updates via Windows Update, clean boot, memory test), the next supported steps are:

    1. Roll back recent drivers or system services
      • Bug check 0x3B commonly appears after new or updated drivers or system services are installed.
      • Identify what changed around the May 2026 update:
        • In Device Manager (right-click Start > Device Manager), look for devices with a warning icon (!). For any such device:
          • Right-click > Update driver. If that does not help, disable or uninstall the device to test.
        • If a specific driver (e.g., display, input, or security software) was updated manually or via vendor tools, roll it back to the previous version and test.
    2. Check Event Viewer and system logs
      • Open Event Viewer (right-click Start > Event Viewer) and check Windows Logs > System for critical errors or driver/service failures that occur at the same time as the BSOD.
      • Use those entries (especially any driver or module names) to identify the faulty component and then update, roll back, or remove it.
    3. Remove or test recently added hardware
      • If any new hardware (USB devices, peripherals, internal cards, etc.) was added before the issue started, shut down the PC, disconnect/remove that hardware, and test.
      • If the BSODs stop, work with the hardware vendor for updated drivers or firmware.
    4. Ensure sufficient free disk space
      • Verify that the system drive has at least 10–15% free space. Low free space can cause instability and issues with paging and updates.
    5. Install all current Windows 11 updates
      • Go to Start > Settings > Windows Update and select Check for updates to ensure all post-May 2026 fixes and driver updates are installed. Some blue-screen issues are mitigated in later cumulative updates.
    6. Use Windows recovery options if the issue started immediately after the May update
      • If the BSODs began directly after that specific update and persist, use Recovery options to undo recent changes:
        • Use System Restore to revert to a restore point from before the update, or
        • Use the “Uninstall latest quality update” or “Uninstall latest feature update” options from the Windows recovery environment, as appropriate for the change that introduced the problem.
      • See Recovery options in Windows 11 for the supported recovery paths.
    7. Advanced analysis (for IT/advanced users)
      • For deeper debugging, use the advanced bug check analysis guidance for SYSTEM_SERVICE_EXCEPTION (0x3B). Focus on:
        • Recently added or updated drivers/services
        • Any driver or module names referenced in the crash dump (for example, win32kfull.sys plus any third-party filter or security drivers)
      • Remove, update, or replace any driver or hardware identified as the cause.

    If, after these steps, the issue persists and is clearly tied to the May 2026 update, collect the bug check details (including the stop code and any module names) and escalate through official support channels with those logs and Event Viewer entries.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

    2 people found this answer helpful.
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.