📎 AI Summary:
The original poster, Jasonc126, reports experiencing a recurring System Service Exception BSOD, with crash analysis pointing to potential driver issues within the Windows kernel, but no specific hardware problems identified. They seek advice on how to resolve the issue. Responding later, Neemobeer suggests following standard troubleshooting instructions for BSOD problems to get help, indicating the need for more detailed diagnostic steps. The overall sentiment is a troubleshooting request with a recommended approach for diagnosis.

Jasonc126

Honorable Member
Joined
Oct 23, 2011
Messages
9
Thread Author #1
I keep getting this BSOD System Service Exception. I downloaded a program called WhoCrashed and here's what it read for the dump files:

On Mon 4/29/2019 3:02:02 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\042919-49515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B3730)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800238B0A18, 0xFFFFFC878A683D30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 4/29/2019 3:02:02 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x7DB9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800238B0A18, 0xFFFFFC878A683D30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

How do I fix this?