Question Computer randomly restarts, here is the bugcheck dump

[NotGreg]

For some reason at least once a month, my computer will randomly restart. The screen freezes then restarts. I was able to pull this dump from the bugcheck but I don't know how to read it. What steps should I take to fix this issue?



8: kd> !analyze -v
*******************************************************************************
* *
* 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: fffff802218101e4, Address of the instruction which caused the BugCheck
Arg3: fffff60076368fd0, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2592

Key : Analysis.Elapsed.mSec
Value: 3377

Key : Analysis.IO.Other.Mb
Value: 1

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 6

Key : Analysis.Init.CPU.mSec
Value: 640

Key : Analysis.Init.Elapsed.mSec
Value: 8623

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x3b

Key : Bugcheck.Code.TargetModel
Value: 0x3b

Key : Dump.Attributes.AsUlong
Value: 8

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Failure.Bucket
Value: AV_Ntfs!NtfsCompareLcbTableEntriesCaseInsensitive

Key : Failure.Hash
Value: {ef023714-65b8-6d79-d94e-3851ff98c5d4}


BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff802218101e4

BUGCHECK_P3: fffff60076368fd0

BUGCHECK_P4: 0

FILE_IN_CAB: 060124-42468-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

CONTEXT: fffff60076368fd0 -- (.cxr 0xfffff60076368fd0)
rax=ffffc00f59fbd000 rbx=0000000000010000 rcx=bfffc00f82d14ad2
rdx=0000000000000000 rsi=ffffc00f703bba50 rdi=0000000000000000
rip=fffff802218101e4 rsp=fffff600763699d0 rbp=0000000000000008
r8=ffffc00f703bba50 r9=0000000000000030 r10=0000000000000000
r11=0000000000000012 r12=0000000000000024 r13=0000000000000000
r14=fffff60076369b20 r15=0000000000000024
iopl=0 nv up ei ng nz ac po cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050297
Ntfs!NtfsCompareLcbTableEntriesCaseInsensitive+0x64:
fffff802`218101e4 440fb70c0a movzx r9d,word ptr [rdx+rcx] ds:002b:bfffc00f`82d14ad2=????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: chrome.exe

STACK_TEXT:
fffff600`763699d0 fffff802`217f25d6 : ffffc00f`703bba50 fffff600`76369b20 ffffc00f`63741ad8 fffff600`7636a070 : Ntfs!NtfsCompareLcbTableEntriesCaseInsensitive+0x64
fffff600`76369a00 fffff802`218c614d : fffff600`7636a070 ffffc00f`63741840 ffffd482`af01cca8 fffff600`7636a070 : Ntfs!FsLibLookupFirstMatchingElementGenericTableAvl+0x46
fffff600`76369a30 fffff802`218dfc88 : fffff600`7636a070 ffffc00f`637416e0 fffff600`76369d40 fffff802`21857000 : Ntfs!NtfsFindPrefix+0x2ed
fffff600`76369b90 fffff802`218e0ab0 : ffffd482`af01cca8 ffffd482`b622ba20 0005c71b`c310ffff fffff600`76369e30 : Ntfs!NtfsFindStartingNode+0x4d8
fffff600`76369c80 fffff802`218dbf5b : ffffd482`b622ba20 fffff600`7636a070 ffffd482`b622ba20 00000000`00000000 : Ntfs!NtfsCommonCreate+0x580
fffff600`76369f60 fffff802`1c82d835 : ffffd482`9faa9030 ffffd482`b622ba20 fffff600`7636a200 ffffd482`c6e90e90 : Ntfs!NtfsFsdCreate+0x1db
fffff600`7636a1e0 fffff802`1aaa710f : ffffd482`c6e90f00 fffff600`7636a2d0 fffff600`7636a2d9 fffff802`1aaa5f7a : nt!IofCallDriver+0x55
fffff600`7636a220 fffff802`1aadaee4 : fffff600`7636a2d0 ffffd482`c6e90ee8 ffffd482`9fa24d90 00000000`00000000 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x28f
fffff600`7636a290 fffff802`1c82d835 : 00000000`00000000 ffffd482`9f75c8f0 00000000`00000000 00000000`00000000 : FLTMGR!FltpCreate+0x324
fffff600`7636a340 fffff802`1c844604 : 00000000`00000003 ffffd482`b622ba20 ffffd482`6d4e6f49 fffff802`1c844573 : nt!IofCallDriver+0x55
fffff600`7636a380 fffff802`1cc3f72b : fffff600`7636a640 ffffd482`9f75c8f0 ffffd482`c6e90f28 00000000`00000000 : nt!IoCallDriverWithTracing+0x34
fffff600`7636a3d0 fffff802`1cc33887 : ffffd482`9f75c8f0 ffffd482`9f75c8c0 ffffd482`b62dfa20 ffffc00f`59c89f01 : nt!IopParseDevice+0x11bb
fffff600`7636a540 fffff802`1cc3be2a : ffffd482`b62dfa01 fffff600`7636a7a8 ffff8281`00000040 ffffd482`9cbf3140 : nt!ObpLookupObjectName+0x1117
fffff600`7636a710 fffff802`1cc2b1eb : 00000000`00000000 000000d8`4a9fe9c0 00000000`00000001 00000000`00000000 : nt!ObOpenObjectByNameEx+0x1fa
fffff600`7636a840 fffff802`1cc29319 : 000000d8`4a9fe960 fffff802`c0100080 000000d8`4a9fe9c0 000000d8`4a9fe968 : nt!IopCreateFile+0x132b
fffff600`7636a900 fffff802`1ca11b05 : 00000000`00000000 00000000`00000001 00000000`00000000 ffffd482`b98a95e0 : nt!NtCreateFile+0x79
fffff600`7636a990 00007ffb`9ab0db54 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000d8`4a9fe8d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`9ab0db54


STACK_COMMAND: .process /r /p 0xc3e0000000000000; .cxr 0xfffff60076368fd0 ; kb

SYMBOL_NAME: Ntfs!NtfsCompareLcbTableEntriesCaseInsensitive+64

MODULE_NAME: Ntfs

IMAGE_NAME: Ntfs.sys

IMAGE_VERSION: 10.0.19041.4412

BUCKET_ID_FUNC_OFFSET: 64

FAILURE_BUCKET_ID: AV_Ntfs!NtfsCompareLcbTableEntriesCaseInsensitive

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ef023714-65b8-6d79-d94e-3851ff98c5d4}

Followup: MachineOwner
---------

 

[kerberos_20]

so windows tryed to create file on your drive and failed to do so, got no access on lcb table
maybe your drive has hardware issue
check s.m.a.r.t. record and also run full disc scan including bad sectors

 

[NotGreg]

so windows tryed to create file on your drive and failed to do so, got no access on lcb table
maybe your drive has hardware issue
check s.m.a.r.t. record and also run full disc scan including bad sectors

Thank you for this. Do you think it's likely that the hardware issue is on my C drive? It's an SSD but only 2 years old. Kind of surprised to see it going back this early