How to fix blue BSoD "SYSTEM_SERVICE_EXEPTION" I'm not sure what to do

The SYSTEM_SERVICE_EXCEPTION (0x3B) blue screen indicates that code running in kernel mode raised an exception while transitioning from user mode to kernel mode. In this scenario, the crash is reported as caused by BEDaisy.sys (BattlEye’s kernel‑mode driver) when starting BattlEye‑protected games.

From the bug check definition:

• 0x3B occurs when executing code in a system thread hits an exception.
• Common causes include NULL pointer dereferences, invalid memory access, or data structure corruption in a driver.

For this stop code, the documented troubleshooting and resolution steps are:

1. Check what changed around the time the crashes started
   • If new device drivers or system services were added (for example, anti‑cheat, GPU drivers, or other low‑level tools), remove, reinstall, or update them.
   • Because the failure is in BEDaisy.sys, reinstall or update the affected BattlEye‑protected games so that BattlEye and its driver are refreshed.
2. Update or roll back drivers and firmware
   • Use Device Manager to look for any devices with a warning icon and update those drivers.
   • Update the display driver (GPU), chipset, and storage drivers from their vendors.
   • If the crashes started after a particular driver or firmware update, test by rolling that component back.
3. Check Event Viewer for correlated errors
   • Open Event Viewer and review the System log for critical or error events that occur at the same time as the blue screen. This can help confirm whether another driver or component is involved in the failure path.
4. Test memory and system files
   • Run Windows Memory Diagnostics to rule out RAM issues.
   • Run SFC /scannow to verify and repair system files, as corrupted system files can contribute to kernel‑mode exceptions.
5. Use Driver Verifier to isolate faulty drivers (advanced)
   • Driver Verifier can be used to stress and validate non‑Microsoft drivers (such as anti‑cheat or GPU drivers). It runs in real time and forces misbehaving drivers to fail in a way that is easier to diagnose.
   • Because Driver Verifier adds overhead and can itself trigger additional bug checks, enable it only for non‑Microsoft drivers and only while actively troubleshooting.
6. Analyze dump files with WinDbg (advanced)
   • If kernel debugging tools are available, load the memory dump and:
     • Use !error on parameter 1 of the 0x3B bug check to see the exact exception code (for example, STATUS_ACCESS_VIOLATION 0xC0000005).
     • Use kb to inspect the stack trace and confirm BEDaisy.sys is on the stack at the time of the crash.
     • Use lm t n to list loaded modules and check for other third‑party drivers that might be interacting with BattlEye.
   • If multiple dumps exist, compare them to see whether the same driver stack appears each time.
7. General blue screen troubleshooting
   • Ensure there is sufficient free disk space so that Windows can operate and create dumps.
   • If the problem started after a Windows update and persists after driver updates and integrity checks, consider using a restore point or Windows recovery options to revert to a stable state.

If, after updating/removing third‑party drivers (especially BattlEye‑related components and GPU drivers), verifying memory and system files, and checking Event Viewer, the issue persists only when BattlEye loads, the next step is typically to work with the game/BattlEye vendor, providing them with the crash dumps and system details so they can address the driver‑level fault.

References:

• Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION
• Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION – Resolution
• Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION – Remarks
• Advanced troubleshooting for stop code errors
• Bug Check 0x154: UNEXPECTED_STORE_EXCEPTION – Troubleshooting tips
• Bug Check 0x74: BAD_SYSTEM_CONFIG_INFO – Remarks