[SOLVED] System crashed & unable to find the reason ?

Aug 26, 2021
2
0
10
Hi

I have been having system crashes lately and the log details have been mentioned below. Kindly help me find out the reason for the crash.

Thanks in advance

Microsoft (R) Windows Debugger Version 10.0.22415.1002 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


Path validation summary *
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff8067ac00000 PsLoadedModuleList = 0xfffff8067b82a190
Debug session time: Thu Aug 26 13:22:23.394 2021 (UTC + 5:30)
System Uptime: 0 days 0:10:57.006
Loading Kernel Symbols
...............................................................
.....Page 847528 not present in the dump file. Type ".hh dbgerr004" for details
...........................................................
................................................................
..................
Loading User Symbols

Loading unloaded module list
..........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff8067aff71d0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8600d2899160=000000000000001e

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Can't set dump file contexts
MachineInfo::SetContext failed - Thread: 000002BA30870600 Handle: 11 Id: 11 - Error == 0x8000FFFF

Path validation summary *
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff8067ac00000 PsLoadedModuleList = 0xfffff8067b82a190
Debug session time: Thu Aug 26 13:22:23.394 2021 (UTC + 5:30)
System Uptime: 0 days 0:10:57.006
Loading Kernel Symbols
...............................................................
.....Page 847528 not present in the dump file. Type ".hh dbgerr004" for details
...........................................................
................................................................
..................
Loading User Symbols

Loading unloaded module list
..........
nt!KeBugCheckEx:
fffff8067aff71d0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8600d2899160=000000000000001e

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Can't set dump file contexts
MachineInfo::SetContext failed - Thread: 000002BA330CFD00 Handle: 11 Id: 11 - Error == 0x8000FFFF

Path validation summary *
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff8067ac00000 PsLoadedModuleList = 0xfffff8067b82a190
Debug session time: Thu Aug 26 13:22:23.394 2021 (UTC + 5:30)
System Uptime: 0 days 0:10:57.006
Loading Kernel Symbols
...............................................................
.....Page 847528 not present in the dump file. Type ".hh dbgerr004" for details
...........................................................
................................................................
..................
Loading User Symbols

Loading unloaded module list
..........
nt!KeBugCheckEx:
fffff8067aff71d0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8600d2899160=000000000000001e
||2:16: kd> !analyze -v
***
  • *
  • Bugcheck Analysis *
  • *
***

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common BugCheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8067ae87f3d, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2202

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 9712

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

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

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

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8067ae87f3d

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

READ_ADDRESS: ffffffffffffffff

EXCEPTION_PARAMETER2: ffffffffffffffff

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
ffff8600d2899158 fffff8067b0f5a2e : 000000000000001e ffffffffc0000005 fffff8067ae87f3d 0000000000000000 : nt!KeBugCheckEx
ffff8600d2899160 fffff8067b00008f : fffff8067b0f5a0c 0000000000000000 0000000000000000 0000000000000000 : nt!HvlpVtlCallExceptionHandler+0x22
ffff8600d28991a0 fffff8067aee6dd7 : ffff8600d2899710 0000000000000000 ffffb307d571fb60 fffff8067affad3e : nt!RtlpExecuteHandlerForException+0xf
ffff8600d28991d0 fffff8067aee59c6 : ffffb307d571eca8 ffff8600d2899e20 ffffb307d571eca8 009d0000000017b0 : nt!RtlDispatchException+0x297
ffff8600d28998f0 fffff8067aff8062 : 4e4f495441434946 0d4552554c494146 000000200000000a 4e555f5245564153 : nt!KiDispatchException+0x186
ffff8600d2899fb0 fffff8067aff8030 : fffff8067b0092a5 0000000000000000 0000000000000000 0000000000000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
ffffb307d571eb68 fffff8067b0092a5 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiExceptionDispatchOnExceptionStackContinue
ffffb307d571eb70 fffff8067b004fe0 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiExceptionDispatch+0x125
ffffb307d571ed50 fffff8067ae87f3d : ffff8600d2840180 0000000000000000 ffffba0600000004 ffffb307d571ef1c : nt!KiGeneralProtectionFault+0x320
ffffb307d571eee0 fffff8067ae871b1 : ffff8600d2840180 000000000000000c ffffba06515bd1c0 fffff8067ae8221a : nt!KiDeferredReadySingleThread+0xacd
ffffb307d571f0d0 fffff8067aeb7bf8 : 0000000000000000 ffffba0600000000 ffffba06514c8180 ffffba064f099cd0 : nt!KiExitDispatcher+0x141
ffffb307d571f140 fffff8067af42998 : ffffba064f084570 0000000000000000 ffffba0669877f00 ffffba0600000000 : nt!ExpQueueWorkItem+0x1d8
ffffb307d571f1d0 fffff8067af4294b : 0000000000000001 0000000000000001 fffff806983de6d0 0000000000000000 : nt!ExQueueWorkItemFromIo+0x40
ffffb307d571f210 fffff806981b43f8 : ffffba0657a03a18 fffff806983df1cc 0000000000000112 000000003b9aca00 : nt!IoQueueWorkItemEx+0x1b
ffffb307d571f240 fffff806983df286 : ffffba06613c0000 ffffba0657d96000 ffffba0657823c70 ffffba0657823c70 : nvlddmkm+0x843f8
ffffb307d571f280 fffff806985dd5e0 : ffffba0661316000 169ecbef3535b6e0 0000000000000000 fffff8067b5b21c4 : nvlddmkm+0x2af286
ffffb307d571f2c0 fffff806986827ad : 0000000000000000 169ecbef35369200 ffffba0661316000 0000000000000001 : nvlddmkm+0x4ad5e0
ffffb307d571f2f0 fffff8069825733c : ffffba0657d96000 ffffba0657d9b790 ffffba0657d9b790 fffff80600000000 : nvlddmkm+0x5527ad
ffffb307d571f330 fffff80698257575 : 0000000000000000 0000000000000034 ffffba0668e606d8 ffffba0657b59010 : nvlddmkm+0x12733c
ffffb307d571f390 fffff80698258839 : 0000000000000001 ffffb307d571f5b0 0000000000000001 ffffba0657d96000 : nvlddmkm+0x127575
ffffb307d571f410 fffff8069867d386 : 0000000000000002 fffff806981db880 ffffba0657d96000 ffffba0657d9b790 : nvlddmkm+0x128839
ffffb307d571f470 fffff806981b8703 : ffffba0657d96000 ffffba0657d9b790 ffffba0664a0f080 ffffb307d571f559 : nvlddmkm+0x54d386
ffffb307d571f4b0 fffff8067ae9a3ae : ffff8600d2843240 ffffb307d571fa10 ffffb307d571fa20 ffff8600d2840180 : nvlddmkm+0x88703
ffffb307d571f760 fffff8067ae99694 : 0000000000000000 0000000000000000 0000000000140001 0000000000000000 : nt!KiExecuteAllDpcs+0x30e
ffffb307d571f8d0 fffff8067affad3e : ffffffff00000000 ffff8600d2840180 ffff8600d284b540 ffffba064f230140 : nt!KiRetireDpcList+0x1f4
ffffb307d571fb60 0000000000000000 : ffffb307d5720000 ffffb307d5719000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME: nvlddmkm+843f8

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 843f8

FAILURE_BUCKET_ID: 0x1E_c0000005_R_nvlddmkm!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {5d60e010-dfb5-f385-5e0f-7c104332ff0c}

Followup: MachineOwner
---------
 
Last edited by a moderator:
Solution
Hi

Thanks for the reply

My PC Specs

Windows 10 Pro - 21H1

NVIDIA RTX 3090 GPU

Intel COre i9-10900K CPU

Samsung 970 EVO SSD

Seagate 1TB HDD

RAM 32GB Gskill TridentZ

Asus ROG Maximus XIII Hero Motherboard

Please let me know if you need any more info.

My system again crashed and the DMP file detail is as follows. This time looks like another issue? Please check



Microsoft (R) Windows Debugger Version 10.0.22415.1002 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


Path validation summary *
Response Time (ms)...
Aug 26, 2021
2
0
10
Hi

Thanks for the reply

My PC Specs

Windows 10 Pro - 21H1

NVIDIA RTX 3090 GPU

Intel COre i9-10900K CPU

Samsung 970 EVO SSD

Seagate 1TB HDD

RAM 32GB Gskill TridentZ

Asus ROG Maximus XIII Hero Motherboard

Please let me know if you need any more info.

My system again crashed and the DMP file detail is as follows. This time looks like another issue? Please check



Microsoft (R) Windows Debugger Version 10.0.22415.1002 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


* Path validation summary **
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff8062e400000 PsLoadedModuleList = 0xfffff8062f02a190
Debug session time: Thu Aug 26 13:50:45.373 2021 (UTC + 5:30)
System Uptime: 0 days 0:27:57.984
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..................
Loading User Symbols
PEB is paged out (Peb.Ldr = 0000009d6afc0018). Type ".hh dbgerr001" for details Loading unloaded module list .......... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff8062e7f71d0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9f853e200250=000000000000003b 12: kd> !analyze -v ******************************************************************************* [LIST] [*]* [*]Bugcheck Analysis * [*]* [/LIST] ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the BugCheck Arg2: fffff8062e68a2a0, Address of the instruction which caused the BugCheck Arg3: ffff9f853e200b50, 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: 2593 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 20877 Key : Analysis.Init.CPU.mSec Value: 343 Key : Analysis.Init.Elapsed.mSec Value: 11382 Key : Analysis.Memory.CommitPeak.Mb Value: 81 Key : Memory.System.Errors.BadPageCount Value: 5 Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1 BUGCHECK_CODE: 3b BUGCHECK_P1: c0000005 BUGCHECK_P2: fffff8062e68a2a0 BUGCHECK_P3: ffff9f853e200b50 BUGCHECK_P4: 0 CONTEXT: ffff9f853e200b50 -- (.cxr 0xffff9f853e200b50) rax=00de000000000000 rbx=00de000000000000 rcx=0000000000110001 rdx=0000000000110000 rsi=0000000000000023 rdi=ffff8986ba7cded0 rip=fffff8062e68a2a0 rsp=ffff9f853e201550 rbp=ffff9f853e2015c8 r8=4cbeead10dbfe268 r9=0000000000000000 r10=0000000000000001 r11=0000000000000001 r12=0000000000000c13 r13=ffff8986ba7ca000 r14=ffff8986a9000280 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050206 nt!RtlpHpVsChunkSplit+0x590: fffff8062e68a2a0 8b4bf8 mov ecx,dword ptr [rbx-8] ds:002b:00ddfffffffffff8=???????? Resetting default scope BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 PROCESS_NAME: TiWorker.exe STACK_TEXT: ffff9f853e201550 fffff8062e689b3a : 0000001100000011 ffff8986ba7cdca0 0000000000000011 0000000000000000 : nt!RtlpHpVsChunkSplit+0x590 ffff9f853e201610 fffff8062e6dbfdd : ffff8986ba7a2d90 fffff80600000220 ffff8986a9000280 ffff8986ba7cda80 : nt!RtlpHpVsContextAllocateInternal+0x1fa ffff9f853e201670 fffff8062e68d2a0 : fffff8062f057e40 ffff9f853e2017d1 0000000000000001 0000000000063e7a : nt!RtlpHpVsContextMultiAlloc+0x69 ffff9f853e2016f0 fffff8062edb21c4 : 0000000000000000 fffff8062adfd4a6 ffffa08f6e664d46 0000000000000000 : nt!ExAllocateHeapPool+0xa70 ffff9f853e201830 fffff8062ae1b4f8 : 0000000000000000 0000000000000000 ffffa08f7292f7b0 0000000000000000 : nt!ExAllocatePoolWithTag+0x64 ffff9f853e201880 fffff8062ae1b09f : 0000000000000000 ffffa08f7292f7b0 0000000000000000 0000000000000000 : FLTMGR!FltGetFileNameInformationUnsafe+0xfc8 ffff9f853e2018b0 fffff8062ade23f4 : ffffa08f6eab2000 ffffa08f57cfc370 0000000000000000 ffffa08f5e0ac130 : FLTMGR!FltGetFileNameInformationUnsafe+0xb6f ffff9f853e201930 fffff8062ade3194 : 0000000000000000 ffffa08f5e0ac138 0000000000000000 ffffa08f7292f7b0 : FLTMGR!FltSetStreamHandleContext+0x174 ffff9f853e201970 fffff8062ade3d31 : 0000000000000000 ffff9f853e201ae8 0000000000000000 0000000000000000 : FLTMGR!FltAllocateCallbackData+0x864 ffff9f853e201a20 fffff806468fd2b0 : ffffa08f7292f7b0 ffffa08f7292b5d0 ffffa08f6f63f4a0 ffffa08f6ad5a001 : FLTMGR!FltGetFileNameInformation+0x101 ffff9f853e201ab0 fffff8062ae1b04f : 0000000000000000 0000000000000000 ffffa08f7292b5d0 fffff8062adef0bc : luafv!LuafvGenerateFileName+0x60 ffff9f853e201ae0 fffff8062ade23f4 : ffffa08f6eab2000 ffffa08f57cfc370 0000000000000000 ffffa08f5e0ac130 : FLTMGR!FltGetFileNameInformationUnsafe+0xb1f ffff9f853e201b60 fffff8062ade3194 : ffffa08f6ad5aae0 ffffa08f6ad5a020 0000000000000000 ffffa08f7292b5d0 : FLTMGR!FltSetStreamHandleContext+0x174 ffff9f853e201ba0 fffff8062ade3d31 : 0000000000000000 ffff9f853e201e68 0000000000000000 ffffa08f6ad5a010 : FLTMGR!FltAllocateCallbackData+0x864 ffff9f853e201c50 fffff80646a296ed : ffffa08f7292b5d0 0000000000000000 ffff9f853e201d41 0000000000000000 : FLTMGR!FltGetFileNameInformation+0x101 ffff9f853e201ce0 fffff80646a29cdb : ffffa08f6b5d3608 ffff9f853e201ea0 ffffa08f6f63f4a0 0000000000000004 : bindflt!BfGetPreCreateFileName+0x45d ffff9f853e201da0 fffff8062ade601c : 0000000000000000 0000000000000000 ffffa08f6b5d3520 ffffa08f6f63f6d0 : bindflt!BfPreCreate+0x40b ffff9f853e202140 fffff8062ade5c55 : 0000000000000000 fffff8062ade7800 0000000000000000 fffff80600000000 : FLTMGR!FltDecodeParameters+0x213c ffff9f853e202260 fffff8062ae1c270 : ffff9f853e203000 ffff9f853e1fc000 0000000000000000 0000000000000000 : FLTMGR!FltDecodeParameters+0x1d75 ffff9f853e2022b0 fffff8062e68f855 : 0000000000000000 ffffa08f5e10ac40 0000000000000000 0000000000000000 : FLTMGR!FltAddOpenReparseEntry+0x560 ffff9f853e202360 fffff8062e690e44 : 0000000000000003 ffffa08f71aad010 ffffa08f6d4e6f49 fffff8062e690a73 : nt!IofCallDriver+0x55 ffff9f853e2023a0 fffff8062ea76bcd : ffff9f853e202660 ffffa08f5e10ac40 ffffa08f74210378 0000000000000000 : nt!IoCallDriverWithTracing+0x34 ffff9f853e2023f0 fffff8062e9f23ce : ffffa08f5e10ac40 00000000000000ac ffffa08f56e1c010 ffffa08f56e1c001 : nt!IopParseDevice+0x117d ffff9f853e202560 fffff8062ea9428a : ffffa08f56e1c000 ffff9f853e2027c8 0000000000000040 ffffa08f56d24820 : nt!ObpLookupObjectName+0x3fe ffff9f853e202730 fffff8062ea15c8f : ffffffff00000000 0000009d6b1fab38 0000000000000000 0000000000000001 : nt!ObOpenObjectByNameEx+0x1fa ffff9f853e202860 fffff8062ea15869 : 0000009d6b1faaf8 0000000000000000 0000009d6b1fab38 0000009d6b1fab00 : nt!IopCreateFile+0x40f ffff9f853e202900 fffff8062e808bb5 : 0000000000000318 0000000000000000 0000000000000000 0000000000000000 : nt!NtCreateFile+0x79 ffff9f853e202990 00007ffdb61cd8c4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25 0000009d6b1faa78 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffdb61cd8c4


SYMBOL_NAME: luafv!LuafvGenerateFileName+60

MODULE_NAME: luafv

IMAGE_NAME: luafv.sys

STACK_COMMAND: .cxr 0xffff9f853e200b50 ; kb

BUCKET_ID_FUNC_OFFSET: 60

FAILURE_BUCKET_ID: 0x3B_c0000005_luafv!LuafvGenerateFileName

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {528d35d3-ff80-5f65-e340-8b82fd9b5a30}

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

Thanks for the reply

My PC Specs

Windows 10 Pro - 21H1

NVIDIA RTX 3090 GPU

Intel COre i9-10900K CPU

Samsung 970 EVO SSD

Seagate 1TB HDD

RAM 32GB Gskill TridentZ

Asus ROG Maximus XIII Hero Motherboard

Please let me know if you need any more info.

My system again crashed and the DMP file detail is as follows. This time looks like another issue? Please check



Microsoft (R) Windows Debugger Version 10.0.22415.1002 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


Path validation summary *
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff8062e400000 PsLoadedModuleList = 0xfffff8062f02a190
Debug session time: Thu Aug 26 13:50:45.373 2021 (UTC + 5:30)
System Uptime: 0 days 0:27:57.984
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..................
Loading User Symbols
PEB is paged out (Peb.Ldr = 0000009d6afc0018). Type ".hh dbgerr001" for details Loading unloaded module list .......... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff8062e7f71d0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9f853e200250=000000000000003b 12: kd> !analyze -v ******************************************************************************* [LIST] [*]* [*]Bugcheck Analysis * [*]* [/LIST] ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the BugCheck Arg2: fffff8062e68a2a0, Address of the instruction which caused the BugCheck Arg3: ffff9f853e200b50, 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: 2593 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 20877 Key : Analysis.Init.CPU.mSec Value: 343 Key : Analysis.Init.Elapsed.mSec Value: 11382 Key : Analysis.Memory.CommitPeak.Mb Value: 81 Key : Memory.System.Errors.BadPageCount Value: 5 Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1 BUGCHECK_CODE: 3b BUGCHECK_P1: c0000005 BUGCHECK_P2: fffff8062e68a2a0 BUGCHECK_P3: ffff9f853e200b50 BUGCHECK_P4: 0 CONTEXT: ffff9f853e200b50 -- (.cxr 0xffff9f853e200b50) rax=00de000000000000 rbx=00de000000000000 rcx=0000000000110001 rdx=0000000000110000 rsi=0000000000000023 rdi=ffff8986ba7cded0 rip=fffff8062e68a2a0 rsp=ffff9f853e201550 rbp=ffff9f853e2015c8 r8=4cbeead10dbfe268 r9=0000000000000000 r10=0000000000000001 r11=0000000000000001 r12=0000000000000c13 r13=ffff8986ba7ca000 r14=ffff8986a9000280 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050206 nt!RtlpHpVsChunkSplit+0x590: fffff8062e68a2a0 8b4bf8 mov ecx,dword ptr [rbx-8] ds:002b:00ddfffffffffff8=???????? Resetting default scope BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 PROCESS_NAME: TiWorker.exe STACK_TEXT: ffff9f853e201550 fffff8062e689b3a : 0000001100000011 ffff8986ba7cdca0 0000000000000011 0000000000000000 : nt!RtlpHpVsChunkSplit+0x590 ffff9f853e201610 fffff8062e6dbfdd : ffff8986ba7a2d90 fffff80600000220 ffff8986a9000280 ffff8986ba7cda80 : nt!RtlpHpVsContextAllocateInternal+0x1fa ffff9f853e201670 fffff8062e68d2a0 : fffff8062f057e40 ffff9f853e2017d1 0000000000000001 0000000000063e7a : nt!RtlpHpVsContextMultiAlloc+0x69 ffff9f853e2016f0 fffff8062edb21c4 : 0000000000000000 fffff8062adfd4a6 ffffa08f6e664d46 0000000000000000 : nt!ExAllocateHeapPool+0xa70 ffff9f853e201830 fffff8062ae1b4f8 : 0000000000000000 0000000000000000 ffffa08f7292f7b0 0000000000000000 : nt!ExAllocatePoolWithTag+0x64 ffff9f853e201880 fffff8062ae1b09f : 0000000000000000 ffffa08f7292f7b0 0000000000000000 0000000000000000 : FLTMGR!FltGetFileNameInformationUnsafe+0xfc8 ffff9f853e2018b0 fffff8062ade23f4 : ffffa08f6eab2000 ffffa08f57cfc370 0000000000000000 ffffa08f5e0ac130 : FLTMGR!FltGetFileNameInformationUnsafe+0xb6f ffff9f853e201930 fffff8062ade3194 : 0000000000000000 ffffa08f5e0ac138 0000000000000000 ffffa08f7292f7b0 : FLTMGR!FltSetStreamHandleContext+0x174 ffff9f853e201970 fffff8062ade3d31 : 0000000000000000 ffff9f853e201ae8 0000000000000000 0000000000000000 : FLTMGR!FltAllocateCallbackData+0x864 ffff9f853e201a20 fffff806468fd2b0 : ffffa08f7292f7b0 ffffa08f7292b5d0 ffffa08f6f63f4a0 ffffa08f6ad5a001 : FLTMGR!FltGetFileNameInformation+0x101 ffff9f853e201ab0 fffff8062ae1b04f : 0000000000000000 0000000000000000 ffffa08f7292b5d0 fffff8062adef0bc : luafv!LuafvGenerateFileName+0x60 ffff9f853e201ae0 fffff8062ade23f4 : ffffa08f6eab2000 ffffa08f57cfc370 0000000000000000 ffffa08f5e0ac130 : FLTMGR!FltGetFileNameInformationUnsafe+0xb1f ffff9f853e201b60 fffff8062ade3194 : ffffa08f6ad5aae0 ffffa08f6ad5a020 0000000000000000 ffffa08f7292b5d0 : FLTMGR!FltSetStreamHandleContext+0x174 ffff9f853e201ba0 fffff8062ade3d31 : 0000000000000000 ffff9f853e201e68 0000000000000000 ffffa08f6ad5a010 : FLTMGR!FltAllocateCallbackData+0x864 ffff9f853e201c50 fffff80646a296ed : ffffa08f7292b5d0 0000000000000000 ffff9f853e201d41 0000000000000000 : FLTMGR!FltGetFileNameInformation+0x101 ffff9f853e201ce0 fffff80646a29cdb : ffffa08f6b5d3608 ffff9f853e201ea0 ffffa08f6f63f4a0 0000000000000004 : bindflt!BfGetPreCreateFileName+0x45d ffff9f853e201da0 fffff8062ade601c : 0000000000000000 0000000000000000 ffffa08f6b5d3520 ffffa08f6f63f6d0 : bindflt!BfPreCreate+0x40b ffff9f853e202140 fffff8062ade5c55 : 0000000000000000 fffff8062ade7800 0000000000000000 fffff80600000000 : FLTMGR!FltDecodeParameters+0x213c ffff9f853e202260 fffff8062ae1c270 : ffff9f853e203000 ffff9f853e1fc000 0000000000000000 0000000000000000 : FLTMGR!FltDecodeParameters+0x1d75 ffff9f853e2022b0 fffff8062e68f855 : 0000000000000000 ffffa08f5e10ac40 0000000000000000 0000000000000000 : FLTMGR!FltAddOpenReparseEntry+0x560 ffff9f853e202360 fffff8062e690e44 : 0000000000000003 ffffa08f71aad010 ffffa08f6d4e6f49 fffff8062e690a73 : nt!IofCallDriver+0x55 ffff9f853e2023a0 fffff8062ea76bcd : ffff9f853e202660 ffffa08f5e10ac40 ffffa08f74210378 0000000000000000 : nt!IoCallDriverWithTracing+0x34 ffff9f853e2023f0 fffff8062e9f23ce : ffffa08f5e10ac40 00000000000000ac ffffa08f56e1c010 ffffa08f56e1c001 : nt!IopParseDevice+0x117d ffff9f853e202560 fffff8062ea9428a : ffffa08f56e1c000 ffff9f853e2027c8 0000000000000040 ffffa08f56d24820 : nt!ObpLookupObjectName+0x3fe ffff9f853e202730 fffff8062ea15c8f : ffffffff00000000 0000009d6b1fab38 0000000000000000 0000000000000001 : nt!ObOpenObjectByNameEx+0x1fa ffff9f853e202860 fffff8062ea15869 : 0000009d6b1faaf8 0000000000000000 0000009d6b1fab38 0000009d6b1fab00 : nt!IopCreateFile+0x40f ffff9f853e202900 fffff8062e808bb5 : 0000000000000318 0000000000000000 0000000000000000 0000000000000000 : nt!NtCreateFile+0x79 ffff9f853e202990 00007ffdb61cd8c4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25 0000009d6b1faa78 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffdb61cd8c4


SYMBOL_NAME: luafv!LuafvGenerateFileName+60

MODULE_NAME: luafv

IMAGE_NAME: luafv.sys

STACK_COMMAND: .cxr 0xffff9f853e200b50 ; kb

BUCKET_ID_FUNC_OFFSET: 60

FAILURE_BUCKET_ID: 0x3B_c0000005_luafv!LuafvGenerateFileName

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {528d35d3-ff80-5f65-e340-8b82fd9b5a30}

Followup: MachineOwner
---------
Is this a new build? Try these:
  • Uninstall GPU Driver Using DDU
  • Uninstall all the processors in device manager like this, then boot up to bios:
unknown.png

Do it all without internet connection, download all the files needed first.
 
Last edited:
Solution