SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8071193f2f6, Address of the instruction which caused the bugcheck
Arg3: fffff50fe5459c60, 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: 7609
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on BORA
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 34345
Key : Analysis.Memory.CommitPeak.Mb
Value: 77
Key : Analysis.System
Value: CreateObject
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
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 3b
BUGCHECK_P1: c0000005
BUGCHECK_P2: fffff8071193f2f6
BUGCHECK_P3: fffff50fe5459c60
BUGCHECK_P4: 0
CONTEXT: fffff50fe5459c60 -- (.cxr 0xfffff50fe5459c60)
rax=0000000000000000 rbx=ffffffffffffd8f0 rcx=ffffe200baf55180
rdx=fffff50fe545a710 rsi=ffffb682cf00f980 rdi=0000000000000000
rip=fffff8071193f2f6 rsp=fffff50fe545a660 rbp=fffff50fe545a739
r8=0000000000000000 r9=ffffb682d0bd5ee0 r10=fffff807048173f0
r11=0000000000000099 r12=ffffb682d19025c0 r13=0000000000000001
r14=ffffb682d1b59830 r15=ffffb682d1b59910
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246
afd!AfdPoll32+0x38a:
fffff807`1193f2f6 488b7818 mov rdi,qword ptr [rax+18h] ds:002b:00000000`00000018=????????????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: Battle.net.exe
STACK_TEXT:
fffff50f`e545a660 fffff807`11926d9c : 00000000`00000000 00000000`00000000 00000000`00000000 ffffb682`00000001 : afd!AfdPoll32+0x38a
fffff50f`e545a7a0 fffff807`1192681c : ffffb682`cf00fb28 00000000`00000000 00000000`0000020c 00000000`00000000 : afd!AfdPoll+0x3c
fffff50f`e545a7d0 fffff807`048cd6c5 : ffffb682`cf00f980 00000000`00000000 fffff50f`20206f49 00000000`00000001 : afd!AfdDispatchDeviceControl+0x7c
fffff50f`e545a800 fffff807`04cc2528 : ffffb682`cf00f980 00000000`00000000 00000000`00000000 ffffb682`cf905080 : nt!IofCallDriver+0x55
fffff50f`e545a840 fffff807`04cc1df5 : 00000000`00012024 fffff50f`e545ab80 00000000`00000005 fffff50f`e545ab80 : nt!IopSynchronousServiceTail+0x1a8
fffff50f`e545a8e0 fffff807`04cc17f6 : 00000000`00000001 00000000`0000078c 00000000`00000001 00000000`00000000 : nt!IopXxxControlFile+0x5e5
fffff50f`e545aa20 fffff807`04a06bb8 : 00000000`00000000 00000000`00040246 fffff50f`00000000 ffffb682`d1d52e60 : nt!NtDeviceIoControlFile+0x56
fffff50f`e545aa90 00000000`773f1cfc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`05f3eb18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773f1cfc
SYMBOL_NAME: afd!AfdPoll32+38a
MODULE_NAME: afd
IMAGE_NAME: afd.sys
IMAGE_VERSION: 10.0.19041.488
STACK_COMMAND: .cxr 0xfffff50fe5459c60 ; kb
BUCKET_ID_FUNC_OFFSET: 38a
FAILURE_BUCKET_ID: 0x3B_c0000005_afd!AfdPoll32
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {a40f0e59-8bb1-5ab2-5da6-9983978c6186}
Followup: MachineOwner
---------
INVALID_WORK_QUEUE_ITEM (96)
This message occurs when KeRemoveQueue removes a queue entry whose flink
or blink field is null. This is almost always called by code misusing
worker thread work items, but any queue misuse can cause this. The rule
is that an entry on a queue may only be inserted on the list once. When an
item is removed from a queue, it's flink field is set to NULL. This bugcheck
occurs when remove queue attempts to remove an entry, but the flink or blink
field is NULL. In order to debug this problem, you need to know the queue being
referenced.
In an attempt to help identify the guilty driver, this bugcheck assumes the
queue is a worker queue (ExWorkerQueue) and prints the worker routine as
parameter 4 below.
Arguments:
Arg1: ffffc386450c9530, The address of the queue entry whose flink/blink field is NULL
Arg2: ffffc38645663c40, The address of the queue being references. Usually this is one
of the ExWorkerQueues.
Arg3: ffffc3863aa74a20, The base address of the ExWorkerQueue array. This will help determine
if the queue in question is an ExWorkerQueue and if so, the offset from
this parameter will isolate the queue.
Arg4: 0000000000000502, If this is an ExWorkerQueue (which it usually is), this is the address
of the worker routine that would have been called if the work item was
valid. This can be used to isolate the driver that is misusing the work
queue.
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 7046
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on BORA
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 8978
Key : Analysis.Memory.CommitPeak.Mb
Value: 84
Key : Analysis.System
Value: CreateObject
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
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 96
BUGCHECK_P1: ffffc386450c9530
BUGCHECK_P2: ffffc38645663c40
BUGCHECK_P3: ffffc3863aa74a20
BUGCHECK_P4: 502
WORK_ITEM: ffffc386450c9530
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 2
PROCESS_NAME: NVIDIA Share.exe
STACK_TEXT:
fffff500`a3d08ad8 fffff806`16471335 : 00000000`00000096 ffffc386`450c9530 ffffc386`45663c40 ffffc386`3aa74a20 : nt!KeBugCheckEx
fffff500`a3d08ae0 fffff806`162e26f8 : ffffc386`45663c40 00000000`00000000 00000000`00000000 00000000`00000001 : nt!KeRemoveQueueEx+0x18e8d5
fffff500`a3d08b80 fffff806`166f17ae : 00000000`00000000 fffff500`a3d08d61 ffffc386`4576b080 fffff806`162dec33 : nt!IoRemoveIoCompletion+0x98
fffff500`a3d08cb0 fffff806`16406bb8 : ffffc386`41abd9f0 ffffffff`ffb3b4c0 ffffc386`4576b080 00000000`00000004 : nt!NtRemoveIoCompletionEx+0xfe
fffff500`a3d08df0 fffff806`163f9070 : ffff8559`e72908ec 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
fffff500`a3d08ff8 ffff8559`e72908ec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiServiceLinkage
fffff500`a3d09000 ffff8559`e73253da : 00000000`00000000 00000000`00000000 00000000`00000000 fffff500`a3d090c0 : win32kfull!xxxRemoveQueueCompletion+0x5c
fffff500`a3d09070 ffff8559`e7227e0e : 00000000`00000000 ffff850e`867c53f0 00000000`00000004 00000000`00001cff : win32kfull!xxxMsgWaitForMultipleObjectsEx+0x126
fffff500`a3d09120 ffff8559`e61a6fcf : fffff500`a3d09aa8 00000000`00000000 000000f5`00000004 fffff500`00001cff : win32kfull!NtUserMsgWaitForMultipleObjectsEx+0x3fe
fffff500`a3d09a50 fffff806`16406bb8 : 000000f5`9a01fb50 00000000`00000108 00000000`00000040 000000f5`9a01f350 : win32k!NtUserMsgWaitForMultipleObjectsEx+0x1f
fffff500`a3d09a90 00007fff`59d5a104 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000f5`9a01f9d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`59d5a104
SYMBOL_NAME: win32kfull!xxxRemoveQueueCompletion+5c
MODULE_NAME: win32kfull
IMAGE_NAME: win32kfull.sys
IMAGE_VERSION: 10.0.19041.630
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 5c
FAILURE_BUCKET_ID: 0x96_win32kfull!xxxRemoveQueueCompletion
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {fac0df31-67c0-336e-3158-4c7b5cb400e0}
Followup: MachineOwner
---------
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 000000000000000d, Attempt to release quota on a corrupted pool allocation.
Arg2: ffff96812f1beb60, Address of pool
Arg3: 0000000020206f49, Pool allocation's tag
Arg4: c837cdec3935a869, Quota process pointer (bad).
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 5968
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on BORA
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 24094
Key : Analysis.Memory.CommitPeak.Mb
Value: 75
Key : Analysis.System
Value: CreateObject
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
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: c2
BUGCHECK_P1: d
BUGCHECK_P2: ffff96812f1beb60
BUGCHECK_P3: 20206f49
BUGCHECK_P4: c837cdec3935a869
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: Discord.exe
STACK_TEXT:
fffffa87`a272c838 fffff803`4446796e : 00000000`000000c2 00000000`0000000d ffff9681`2f1beb60 00000000`20206f49 : nt!KeBugCheckEx
fffffa87`a272c840 fffff803`449b1019 : 00000000`00000000 00000000`00000001 00000000`00000080 01000000`00100000 : nt!ExFreeHeapPool+0x1a0a6e
fffffa87`a272c920 fffff803`4483a92c : 00000000`00000000 00000000`000014ac 00000000`00000000 ffff9681`2e78e080 : nt!ExFreePool+0x9
fffffa87`a272c950 fffff803`44406bb8 : 00000000`00000000 fffffa87`a272cb80 00000000`00000000 fffffa87`a272cae8 : nt!NtRemoveIoCompletionEx+0x14927c
fffffa87`a272ca90 00007ffd`7094eb94 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`10e9e658 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`7094eb94
SYMBOL_NAME: nt!NtRemoveIoCompletionEx+14927c
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.630
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 14927c
FAILURE_BUCKET_ID: 0xc2_d_nt!NtRemoveIoCompletionEx
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {fa4dc538-781a-0719-8806-a75c4586722f}
Followup: MachineOwner
---------
MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed. This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened. Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it. The
first actually works, and the second fails. Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second. However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: ffffc5029284c550, Address of the IRP
Arg2: 0000000000001232
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 7812
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on BORA
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 9093
Key : Analysis.Memory.CommitPeak.Mb
Value: 76
Key : Analysis.System
Value: CreateObject
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
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 44
BUGCHECK_P1: ffffc5029284c550
BUGCHECK_P2: 1232
BUGCHECK_P3: 0
BUGCHECK_P4: 0
IRP_ADDRESS: ffffc5029284c550
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: Discord.exe
DEVICE_OBJECT: ffffc5028836bab0
DRIVER_OBJECT: ffffc5028a265740
IMAGE_NAME: Npfs.SYS
MODULE_NAME: Npfs
FAULTING_MODULE: fffff8001dd40000 Npfs
STACK_TEXT:
ffffbf0d`f71f7678 fffff800`10266442 : 00000000`00000044 ffffc502`9284c550 00000000`00001232 00000000`00000000 : nt!KeBugCheckEx
ffffbf0d`f71f7680 fffff800`100c2e97 : ffffc502`915d4080 00000000`00000002 ffffc502`90f37a20 ffffc502`00000000 : nt!IopfCompleteRequest+0x1a3592
ffffbf0d`f71f7770 fffff800`1dd4d834 : 00000000`00000000 00000000`14925d18 ffffc502`9284fa80 ffffc502`915d4080 : nt!IofCompleteRequest+0x17
ffffbf0d`f71f77a0 fffff800`100cd6c5 : ffffc502`8837fb40 ffffc502`8837fb40 00000000`00000001 ffffc502`9284fa80 : Npfs!NpFsdWrite+0x94
ffffbf0d`f71f7810 fffff800`0f374906 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000005 : nt!IofCallDriver+0x55
ffffbf0d`f71f7850 fffff800`100cd6c5 : ffffc502`9284fa80 ffff9c00`7c35e180 ffffc502`915d4080 fffff800`100df38f : FLTMGR!FltpDispatch+0xd6
ffffbf0d`f71f78b0 fffff800`104c2528 : ffffc502`9284fa80 00000000`00000000 ffffc502`9284fa80 00000000`00000000 : nt!IofCallDriver+0x55
ffffbf0d`f71f78f0 fffff800`104b8e7f : ffff870f`00000000 ffffbf0d`f71f7b80 00000000`0e34f668 ffffbf0d`f71f7b80 : nt!IopSynchronousServiceTail+0x1a8
ffffbf0d`f71f7990 fffff800`10206bb8 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`0e8524b8 : nt!NtWriteFile+0x66f
ffffbf0d`f71f7a90 00000000`76e61cfc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`0e24f278 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e61cfc
SYMBOL_NAME: Npfs!NpFsdWrite+94
IMAGE_VERSION: 10.0.19041.1030
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 94
FAILURE_BUCKET_ID: 0x44_Npfs!NpFsdWrite
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {947b2e94-712f-fbfc-7620-19ee913c5b76}
Followup: MachineOwner
---------
