drive.google.com
*******************************************************************************
* *
* 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: 1890
Key : Analysis.Elapsed.mSec
Value: 6539
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: 389
Key : Analysis.Init.Elapsed.mSec
Value: 22446
Key : Analysis.Memory.CommitPeak.Mb
Value: 94
Key : Bugcheck.Code.LegacyAPI
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: 120323-7609-02.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 2
PROCESS_NAME: System
STACK_TEXT:
ffffca0a`8fe7f9f8 fffff802`5a413780 : 00000000`00000020 00000000`00000000 00000000`0000ffff 00000000`00000000 : nt!KeBugCheckEx
ffffca0a`8fe7fa00 fffff802`5a2ab283 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PspExitThread+0x187848
ffffca0a`8fe7fb00 fffff802`5a2a96d4 : ffff9389`49308080 00000000`00000080 fffff802`5a36fcd0 ffff9389`34ece200 : nt!PspTerminateThreadByPointer+0x53
ffffca0a`8fe7fb40 fffff802`5a36fd18 : 00000000`00000000 00000000`00000000 00000000`00002000 00008e10`002070f6 : nt!PsTerminateSystemThread+0x24
ffffca0a`8fe7fb70 fffff802`59f078e5 : ffff9389`49308080 fffff802`5a36fcd0 ffffe704`c90d3ec0 00000000`00000000 : nt!IopThreadStart+0x48
ffffca0a`8fe7fbd0 fffff802`5a006368 : ffff8000`0fc40180 ffff9389`49308080 fffff802`59f07890 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffca0a`8fe7fc20 00000000`00000000 : ffffca0a`8fe80000 ffffca0a`8fe79000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: nt!PspExitThread+187848
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.3693
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 187848
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
---------
