[SOLVED] Trying to solve my nephews BSD issue - SYSTEM_SERVICE_EXCEPTION (3b)

[BSDMe]

Hello,

I helped my nephew build his first PC and all went well until the last few months when he's been getting BSDs randomly. No real pattern to them and maybe 1-3 per day, but not every day. I made sure he had all his drivers updated and ran the usual tests and they all came back fine. I had him uninstall his programs that he had put on the OS's drive and put then on the other drive and then repaired windows. Still getting the BSDs after updating all drivers again. Windows did find and repair a corrupted file when I ran the scans again and I was hopeful that had solved the issue, but he just emailed me his latest dmp file. Hoping someone can make sense of it for me so I can help him out. Thanks!

Spoiler: Dump File Results

***

• *
• Bugcheck Analysis *
• *

***

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8056fc143ad, Address of the instruction which caused the bugcheck
Arg3: fffff90e53acee50, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 3

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on ELLE

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 5

Key : Analysis.Memory.CommitPeak.Mb
Value: 78

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8056fc143ad

BUGCHECK_P3: fffff90e53acee50

BUGCHECK_P4: 0

CONTEXT: fffff90e53acee50 -- (.cxr 0xfffff90e53acee50)
rax=0000000000000000 rbx=00000000fffffff3 rcx=0000000000000000
rdx=fffff80570325c50 rsi=000000000000000d rdi=ffffde8490a95340
rip=fffff8056fc143ad rsp=fffff90e53acf850 rbp=fffff80570325c50
r8=fffff90e53acf860 r9=0000000000000000 r10=0000000000000000
r11=ffffab7e27c00000 r12=0000000000000000 r13=ffffde8488b65c00
r14=ffffde8464b07200 r15=ffffcb8c362e8080
iopl=0 nv up ei pl nz na po cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050207
nt!SeDefaultObjectMethod+0x18d:
fffff8056fc143ad 488b01 mov rax,qword ptr [rcx] ds:002b:0000000000000000=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: ServiceHub.Host.CLR.

STACK_TEXT:
fffff90e53acf850 fffff8056fbfb2a6 : ffffcb8c34a0a050 fffff90e53acfa39 ffffcb8c34a0a050 0000000000000000 : nt!SeDefaultObjectMethod+0x18d
fffff90e53acf8b0 fffff8056f861277 : 0000000000000000 0000000000000000 fffff90e53acfa39 ffffcb8c34a0a080 : nt!ObpRemoveObjectRoutine+0xd6
fffff90e53acf910 fffff8056fc28cbe : ffffcb8c202b0a60 0000000000000001 ffffffffffffffff ffffde846ee90fe0 : nt!ObfDereferenceObjectWithTag+0xc7
fffff90e53acf950 fffff8056fc2c93c : 00000000000013f8 0000000000000000 0000000000000000 ffffcb8c3808b8e0 : nt!ObCloseHandleTableEntry+0x29e
fffff90e53acfa90 fffff8056fa074b8 : ffffcb8c362e8000 0000000000000000 fffff90e53acfb80 fffffffffeced300 : nt!NtClose+0xec
fffff90e53acfb00 00007ffc8730c804 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28
00000024300ff4d8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffc`8730c804


SYMBOL_NAME: nt!SeDefaultObjectMethod+18d

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.804

STACK_COMMAND: .cxr 0xfffff90e53acee50 ; kb

BUCKET_ID_FUNC_OFFSET: 18d

FAILURE_BUCKET_ID: 0x3B_c0000005_nt!SeDefaultObjectMethod

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {0efa101b-e9d0-1362-a826-cbc49be172a8}

Followup: MachineOwner

 

[BSDMe]

Okay that is good to know. So it sounds like the order should be:
Update the driver mentioned in an earlier post
If still BSOD clean format the machine (This just needs to be the SSD that the OS is installed on, not any additional drives, or does this require all of them being formatted?)
If still BSOD, then try a new wifi card

Thanks again for your input, much appreciated!

 

[Hellfire13]

Okay that is good to know. So it sounds like the order should be:
Update the driver mentioned in an earlier post
If still BSOD clean format the machine (This just needs to be the SSD that the OS is installed on, not any additional drives, or does this require all of them being formatted?)
If still BSOD, then try a new wifi card

Thanks again for your input, much appreciated!

Just the OS drive.