************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToV8JsProvider : false
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.016 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 41
Microsoft (R) Windows Debugger Version 10.0.27553.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidumps\060224-7921-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are 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 (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff803`7c600000 PsLoadedModuleList = 0xfffff803`7d22a7c0
Debug session time: Sun Jun 2 20:40:06.978 2024 (UTC + 3:00)
System Uptime: 0 days 0:03:56.622
Loading Kernel Symbols
...............................................................
................................................................
...............................................................
Loading User Symbols
Loading unloaded module list
........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`7c9fd8f0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffd88b`1e3bfa40=0000000000000020
6: kd> !analyze -v
*******************************************************************************
*
Bugcheck Analysis *
*
*******************************************************************************
KERNEL_APC_PENDING_DURING_EXIT (20)
The key data item is the thread's APC disable count.
If this is non-zero, then this is the source of the problem.
The APC disable count is decremented each time a driver calls
KeEnterCriticalRegion, FsRtlEnterFileSystem, or acquires a mutex. The APC
disable count is incremented each time a driver calls KeLeaveCriticalRegion,
FsRtlExitFileSystem, or KeReleaseMutex. Since these calls should always be in
pairs, this value should be zero when a thread exits. A negative value
indicates that a driver has disabled APC calls without re-enabling them. A
positive value indicates that the reverse is true.
If you ever see this error, be very suspicious of all drivers installed on the
machine -- especially unusual or non-standard drivers. Third party file
system redirectors are especially suspicious since they do not generally
receive the heavy duty testing that NTFS, FAT, RDR, etc receive.
This current IRQL should also be 0. If it is not, that a driver's
cancellation routine can cause this BugCheck by returning at an elevated
IRQL. Always attempt to note what you were doing/closing at the
time of the crash, and note all of the installed drivers at the time of
the crash. This symptom is usually a severe bug in a third party
driver.
Arguments:
Arg1: 0000000000000000, The address of the APC found pending during exit.
Arg2: 000000000000ffff, The thread's APC disable count
Arg3: 0000000000000000, The current IRQL
Arg4: 0000000000000001
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2234
Key : Analysis.Elapsed.mSec
Value: 2244
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 468
Key : Analysis.Init.Elapsed.mSec
Value: 5648
Key : Analysis.Memory.CommitPeak.Mb
Value: 91
Key : Bugcheck.Code.LegacyAPI
Value: 0x20
Key : Bugcheck.Code.TargetModel
Value: 0x20
Key : Dump.Attributes.AsUlong
Value: 8
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Failure.Bucket
Value: 0x20_NULLAPC_KAPC_NEGATIVE_nt!PspExitThread
Key : Failure.Hash
Value: {fcbbc787-b7cc-0ca4-c274-c788b86a9951}
BUGCHECK_CODE: 20
BUGCHECK_P1: 0
BUGCHECK_P2: ffff
BUGCHECK_P3: 0
BUGCHECK_P4: 1
FILE_IN_CAB: 060224-7921-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffd88b`1e3bfa38 fffff803`7ce0e064 : 00000000`00000020 00000000`00000000 00000000`0000ffff 00000000`00000000 : nt!KeBugCheckEx
ffffd88b`1e3bfa40 fffff803`7ccbfc13 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PspExitThread+0x18462c
ffffd88b`1e3bfb40 fffff803`7cd01064 : ffff9087`0f4b90c0 00000000`00000080 fffff803`7cd723c0 ffff9086`ffe79200 : nt!PspTerminateThreadByPointer+0x53
ffffd88b`1e3bfb80 fffff803`7cd72408 : 00000001`00000038 00000000`00000000 00000000`00000000 00000632`006080e6 : nt!PsTerminateSystemThread+0x24
ffffd88b`1e3bfbb0 fffff803`7c948c55 : ffff9087`0f4b90c0 fffff803`7cd723c0 ffffdb83`f98731f0 00000000`00000000 : nt!IopThreadStart+0x48
ffffd88b`1e3bfc10 fffff803`7ca068f8 : ffffb381`cd1c0180 ffff9087`0f4b90c0 fffff803`7c948c00 ffffa37c`3ec00000 : nt!PspSystemThreadStartup+0x55
ffffd88b`1e3bfc60 00000000`00000000 : ffffd88b`1e3c0000 ffffd88b`1e3ba000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: nt!PspExitThread+18462c
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.4474
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 18462c
FAILURE_BUCKET_ID: 0x20_NULLAPC_KAPC_NEGATIVE_nt!PspExitThread
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {fcbbc787-b7cc-0ca4-c274-c788b86a9951}
Followup: MachineOwner
---------
