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: ffffcf88bbe9eb60, The address of the queue entry whose flink/blink field is NULL
Arg2: ffffcf88b7ebbe40, The address of the queue being references. Usually this is one
of the ExWorkerQueues.
Arg3: ffffcf88ad902a60, 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: 4953
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-1IBQR0U
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 13027
Key : Analysis.Memory.CommitPeak.Mb
Value: 86
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: ffffcf88bbe9eb60
BUGCHECK_P2: ffffcf88b7ebbe40
BUGCHECK_P3: ffffcf88ad902a60
BUGCHECK_P4: 502
WORK_ITEM: ffffcf88bbe9eb60
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: Discord.exe
STACK_TEXT:
ffffdf89`26052f48 fffff806`3a671335 : 00000000`00000096 ffffcf88`bbe9eb60 ffffcf88`b7ebbe40 ffffcf88`ad902a60 : nt!KeBugCheckEx
ffffdf89`26052f50 fffff806`3a4e26f8 : ffffcf88`b7ebbe40 00000000`00000000 ffffcf88`b89cd080 ffff8080`00000001 : nt!KeRemoveQueueEx+0x18e8d5
ffffdf89`26052ff0 fffff806`3a8f17ae : ffffcf88`bcc13a90 00000000`00989680 00000000`00000001 ffffcf88`bcc13a90 : nt!IoRemoveIoCompletion+0x98
ffffdf89`26053120 fffff806`3a606bb8 : 00000000`0000000a 00000000`00000019 00000000`00000032 00000000`00000000 : nt!NtRemoveIoCompletionEx+0xfe
ffffdf89`26053260 fffff806`3a5f9070 : fffffd19`32f3ceb8 fffffd3b`c71cf8a0 fffffd3b`c71cf8a0 ffffdf89`26053b80 : nt!KiSystemServiceCopyEnd+0x28
ffffdf89`26053468 fffffd19`32f3ceb8 : fffffd3b`c71cf8a0 fffffd3b`c71cf8a0 ffffdf89`26053b80 fffff806`3a4e16e4 : nt!KiServiceLinkage
ffffdf89`26053470 fffffd19`32f3b876 : fffffd3b`c71cf8a0 ffffdf89`26050000 00000000`00000001 fffffd3b`00000000 : win32kfull!xxxRealSleepThread+0x3d8
ffffdf89`26053590 fffffd19`32f3a062 : ffffdf89`26053a78 00000000`1034e801 00000000`00000000 00000000`00000000 : win32kfull!xxxRealInternalGetMessage+0x15d6
ffffdf89`26053a30 fffffd19`33646275 : ffffcf88`b89cd080 00007ffe`24d83970 00000000`00000020 00000000`0996d000 : win32kfull!NtUserGetMessage+0x92
ffffdf89`26053ac0 fffff806`3a606bb8 : 00000000`77083a10 00000000`00000000 00000000`00000000 00000000`1034e790 : win32k!NtUserGetMessage+0x15
ffffdf89`26053b00 00007ffe`24d90014 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`1034e7e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`24d90014
SYMBOL_NAME: win32kfull!xxxRealSleepThread+3d8
MODULE_NAME: win32kfull
IMAGE_NAME: win32kfull.sys
IMAGE_VERSION: 10.0.19041.631
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 3d8
FAILURE_BUCKET_ID: 0x96_win32kfull!xxxRealSleepThread
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {746db16b-421c-42f8-95da-7c29ad48484f}
Followup: MachineOwner
---------
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffed0a213edba0, memory referenced.
Arg2: 0000000000000011, value 0 = read operation, 1 = write operation.
Arg3: ffffed0a213edba0, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 6109
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-1IBQR0U
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 48827
Key : Analysis.Memory.CommitPeak.Mb
Value: 83
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: 50
BUGCHECK_P1: ffffed0a213edba0
BUGCHECK_P2: 11
BUGCHECK_P3: ffffed0a213edba0
BUGCHECK_P4: 2
WRITE_ADDRESS: fffff80114cfb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80114c0f340: Unable to get Flags value from nt!KdVersionBlock
fffff80114c0f340: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
ffffed0a213edba0
MM_INTERNAL_CODE: 2
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
TRAP_FRAME: ffffed0a213ed980 -- (.trap 0xffffed0a213ed980)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffed0a213edad0 rbx=0000000000000000 rcx=ffff9881df4e6180
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=ffffed0a213edba0 rsp=ffffed0a213edb10 rbp=ffffed0a213ede89
r8=0000000000000001 r9=0000000000000001 r10=0000000000000000
r11=ffff8878f7800000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
ffffed0a`213edba0 017262 add dword ptr [rdx+62h],esi ds:00000000`00000062=????????
Resetting default scope
STACK_TEXT:
ffffed0a`213ed6d8 fffff801`1447a665 : 00000000`00000050 ffffed0a`213edba0 00000000`00000011 ffffed0a`213ed980 : nt!KeBugCheckEx
ffffed0a`213ed6e0 fffff801`142ea4a0 : ffffed0a`00000000 00000000`00000011 ffffed0a`213eda00 00000000`00000000 : nt!MiSystemFault+0x172315
ffffed0a`213ed7e0 fffff801`1440335e : 00000000`00000000 00000000`00000000 00000000`00000000 fffff801`16df920a : nt!MmAccessFault+0x400
ffffed0a`213ed980 ffffed0a`213edba0 : fffff801`22b86890 ffffa98f`b66af030 fffff801`22b868a0 fffff801`22afaf1a : nt!KiPageFault+0x35e
ffffed0a`213edb10 fffff801`22b86890 : ffffa98f`b66af030 fffff801`22b868a0 fffff801`22afaf1a ffffa98f`b8a60dc0 : 0xffffed0a`213edba0
ffffed0a`213edb18 ffffa98f`b66af030 : fffff801`22b868a0 fffff801`22afaf1a ffffa98f`b8a60dc0 fffff801`22aa4aea : cfosspeed6+0x196890
ffffed0a`213edb20 fffff801`22b868a0 : fffff801`22afaf1a ffffa98f`b8a60dc0 fffff801`22aa4aea ffffa98f`b02593e0 : 0xffffa98f`b66af030
ffffed0a`213edb28 fffff801`22afaf1a : ffffa98f`b8a60dc0 fffff801`22aa4aea ffffa98f`b02593e0 ffffa98f`b66af030 : cfosspeed6+0x1968a0
ffffed0a`213edb30 ffffa98f`b8a60dc0 : fffff801`22aa4aea ffffa98f`b02593e0 ffffa98f`b66af030 00000000`00000000 : cfosspeed6+0x10af1a
ffffed0a`213edb38 fffff801`22aa4aea : ffffa98f`b02593e0 ffffa98f`b66af030 00000000`00000000 fffff801`22b87101 : 0xffffa98f`b8a60dc0
ffffed0a`213edb40 ffffa98f`b02593e0 : ffffa98f`b66af030 00000000`00000000 fffff801`22b87101 00000000`00000000 : cfosspeed6+0xb4aea
ffffed0a`213edb48 ffffa98f`b66af030 : 00000000`00000000 fffff801`22b87101 00000000`00000000 fffff801`22aa6cf8 : 0xffffa98f`b02593e0
ffffed0a`213edb50 00000000`00000000 : fffff801`22b87101 00000000`00000000 fffff801`22aa6cf8 ffffed0a`213edba0 : 0xffffa98f`b66af030
SYMBOL_NAME: cfosspeed6+196890
MODULE_NAME: cfosspeed6
IMAGE_NAME: cfosspeed6.sys
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 196890
FAILURE_BUCKET_ID: AV_INVALID_cfosspeed6!unknown_function
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {2a193c8d-232a-853e-b4eb-0538df41ee22}
Followup: MachineOwner
---------
4: kd> !sysinfo machineid
Machine ID Information [From Smbios 2.8, DMIVersion 0, Size=2634]
BiosMajorRelease = 5
BiosMinorRelease = 17
BiosVendor = American Megatrends Inc.
BiosVersion = 2.41
BiosReleaseDate = 09/29/2020
SystemManufacturer = Micro-Star International Co., Ltd.
SystemProductName = MS-7C95
SystemFamily = To be filled by O.E.M.
SystemVersion = 1.0
SystemSKU = To be filled by O.E.M.
BaseBoardManufacturer = Micro-Star International Co., Ltd.
BaseBoardProduct = B550M PRO-VDH WIFI (MS-7C95)
BaseBoardVersion = 1.0
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8063a4097fd, The address that the exception occurred at
Arg3: ffff810164806098, Exception Record Address
Arg4: ffff8101648058d0, Context Record Address
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : AV.Fault
Value: Write
Key : Analysis.CPU.mSec
Value: 5483
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-1IBQR0U
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 8765
Key : Analysis.Memory.CommitPeak.Mb
Value: 79
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: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff8063a4097fd
BUGCHECK_P3: ffff810164806098
BUGCHECK_P4: ffff8101648058d0
EXCEPTION_RECORD: ffff810164806098 -- (.exr 0xffff810164806098)
ExceptionAddress: fffff8063a4097fd (FLTMGR!FltReleaseContext+0x000000000000000d)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 000000000001002e
Attempt to write to address 000000000001002e
CONTEXT: ffff8101648058d0 -- (.cxr 0xffff8101648058d0)
rax=000000000000ffde rbx=ffffb00526e090f8 rcx=000000000001003e
rdx=00000000ffffffff rsi=ffffb00526e090f8 rdi=0000000000000001
rip=fffff8063a4097fd rsp=ffff8101648062d0 rbp=0000000000000000
r8=00000000ffffffff r9=7fffb0051d1fa828 r10=fffff8063a4097f0
r11=ffff810164806398 r12=ffffb00526e09090 r13=ffff8101648065d0
r14=ffff810164806438 r15=0000000010000004
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050282
FLTMGR!FltReleaseContext+0xd:
fffff806`3a4097fd f00fc15050 lock xadd dword ptr [rax+50h],edx ds:002b:00000000`0001002e=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: svchost.exe
WRITE_ADDRESS: fffff8063befb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8063be0f340: Unable to get Flags value from nt!KdVersionBlock
fffff8063be0f340: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
000000000001002e
ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek u olamaz %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000001
EXCEPTION_PARAMETER2: 000000000001002e
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
ffff8101`648062d0 fffff806`4e79cb61 : ffffb005`26e090f8 00000000`00000000 00000000`00000000 ffff8101`00000240 : FLTMGR!FltReleaseContext+0xd
ffff8101`64806310 fffff806`3a40608b : 00000000`00000000 ffffb005`26e090f8 ffff9c08`00000000 ffffb005`24755400 : bindflt!BfPreFsControl+0x311
ffff8101`648063a0 fffff806`3a405b37 : ffff8101`64806500 ffffb005`24991a0d ffffb005`26a6fe00 00000000`00000000 : FLTMGR!FltpPerformPreCallbacksWorker+0x36b
ffff8101`648064c0 fffff806`3a404b46 : ffff8101`64807000 ffff8101`64801000 00000000`00000000 ffff8101`648065e0 : FLTMGR!FltpPassThroughInternal+0xc7
ffff8101`64806510 fffff806`3a43caaf : 00000000`00000000 ffffb005`24991aa8 00000000`000000e0 ffffb005`1d07e050 : FLTMGR!FltpPassThrough+0x1d6
ffff8101`648065b0 fffff806`3b4cd6c5 : 00000000`0000000a ffffb005`25aec010 00000000`00000002 00000000`00000000 : FLTMGR!FltpFsControl+0xbf
ffff8101`64806610 fffff806`3b8c2528 : ffffb005`25aec010 00000000`00000000 00000000`00000000 ffffb005`26ce1080 : nt!IofCallDriver+0x55
ffff8101`64806650 fffff806`3b8c1df5 : 00000000`00090120 ffff8101`64806990 00000000`00440005 ffff8101`64806990 : nt!IopSynchronousServiceTail+0x1a8
ffff8101`648066f0 fffff806`3b89a0f8 : 00000000`00000000 ffffffff`80005a14 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x5e5
ffff8101`64806830 fffff806`3ba41c33 : ffff9c08`b676b0b8 ffffffff`80002f6c ffff8101`648069b1 ffff9c08`b74ee188 : nt!PfSnPrefetchFileMetadata+0xe8
ffff8101`648068d0 fffff806`3b9078b5 : 00000000`0000006c ffff8101`64806b00 ffff9c08`b74f1258 ffff9c08`00000000 : nt!PfSnGetSectionObject+0x13a0fb
ffff8101`64806a00 fffff806`3b5034b5 : ffffb005`2375d040 ffffb005`2375d040 ffffb005`1a0efa60 00000000`00000600 : nt!PfSnPopulateReadList+0x2b5
ffff8101`64806b70 fffff806`3b4a29a5 : ffffb005`2375d040 00000000`00000080 ffffb005`1a092040 000f8067`b4bbbdff : nt!ExpWorkerThread+0x105
ffff8101`64806c10 fffff806`3b5fc868 : fffff806`39297180 ffffb005`2375d040 fffff806`3b4a2950 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff8101`64806c60 00000000`00000000 : ffff8101`64807000 ffff8101`64801000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: bindflt!BfPreFsControl+311
MODULE_NAME: bindflt
IMAGE_NAME: bindflt.sys
IMAGE_VERSION: 10.0.19041.292
STACK_COMMAND: .cxr 0xffff8101648058d0 ; kb
BUCKET_ID_FUNC_OFFSET: 311
FAILURE_BUCKET_ID: AV_bindflt!BfPreFsControl
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {c5df67ac-dd81-d64e-979b-0c0100e4ecbf}
Followup: MachineOwner
---------
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: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000008, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ExceptionRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ContextRecord ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3592
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-1IBQR0U
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 3601
Key : Analysis.Memory.CommitPeak.Mb
Value: 76
Key : Analysis.System
Value: CreateObject
Key : Dump.Attributes.InsufficientDumpfileSize
Value: 1
Key : Dump.Attributes.RequiredDumpfileSize
Value: 0xe5c98cd6
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
DUMP_FILE_ATTRIBUTES: 0xc
Insufficient Dumpfile Size
Kernel Generated Triage Dump
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: 0
BUGCHECK_P3: 8
BUGCHECK_P4: 0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: HD-Player.exe
TRAP_FRAME: ffff800000000000 -- (.trap 0xffff800000000000)
Unable to read trap frame at ffff8000`00000000
STACK_TEXT:
ffff9a8e`8503d1a8 fffff804`37830d05 : 00000000`0000001e ffffffff`c0000005 00000000`00000000 00000000`00000008 : nt!KeBugCheckEx
ffff9a8e`8503d1b0 fffff804`378072ac : 00000000`00001000 ffff9a8e`8503da50 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x1df4e5
ffff9a8e`8503d870 fffff804`37803443 : 00000000`00f8004c ffffb906`5597dd00 00000000`00000000 ffff9a8e`8503dd18 : nt!KiExceptionDispatch+0x12c
ffff9a8e`8503da50 00000000`00000000 : ffffa88d`4f9a4b80 00000000`00000000 ffff9a8e`8503dd18 ffffffff`800000d0 : nt!KiPageFault+0x443
SYMBOL_NAME: nt!KiDispatchException+1df4e5
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.630
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 1df4e5
FAILURE_BUCKET_ID: 0x1E_nt!KiDispatchException
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {4c003660-11e1-3fb7-2474-3522eb7ee67b}
Followup: MachineOwner
---------
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: fffff80300000000, memory referenced.
Arg2: 0000000000000010, value 0 = read operation, 1 = write operation.
Arg3: fffff80300000000, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 4202
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-1IBQR0U
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 71985
Key : Analysis.Memory.CommitPeak.Mb
Value: 80
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: 50
BUGCHECK_P1: fffff80300000000
BUGCHECK_P2: 10
BUGCHECK_P3: fffff80300000000
BUGCHECK_P4: 2
READ_ADDRESS: fffff803442fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8034420f340: Unable to get Flags value from nt!KdVersionBlock
fffff8034420f340: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
fffff80300000000
MM_INTERNAL_CODE: 2
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: aow_exe.exe
TRAP_FRAME: fffff2810977fdb0 -- (.trap 0xfffff2810977fdb0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff28109780050
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80300000000 rsp=fffff2810977ff40 rbp=ffff8181abce6180
r8=0000000000000020 r9=0000000000000001 r10=0000000000000144
r11=0000000000000003 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
fffff803`00000000 ?? ???
Resetting default scope
FAILED_INSTRUCTION_ADDRESS:
+0
fffff803`00000000 ?? ???
STACK_TEXT:
fffff281`0977fb08 fffff803`43a7a665 : 00000000`00000050 fffff803`00000000 00000000`00000010 fffff281`0977fdb0 : nt!KeBugCheckEx
fffff281`0977fb10 fffff803`438ea4a0 : 00000000`00000000 00000000`00000010 fffff281`0977fe30 00000000`00000000 : nt!MiSystemFault+0x172315
fffff281`0977fc10 fffff803`43a0335e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x400
fffff281`0977fdb0 fffff803`00000000 : ffff0ab2`d9315609 ffffb809`ef6fcd90 fffff281`09780050 00000000`00000001 : nt!KiPageFault+0x35e
fffff281`0977ff40 ffff0ab2`d9315609 : ffffb809`ef6fcd90 fffff281`09780050 00000000`00000001 ffffb809`ecc361f0 : 0xfffff803`00000000
fffff281`0977ff48 ffffb809`ef6fcd90 : fffff281`09780050 00000000`00000001 ffffb809`ecc361f0 ffffb809`ecc361f0 : 0xffff0ab2`d9315609
fffff281`0977ff50 fffff281`09780050 : 00000000`00000001 ffffb809`ecc361f0 ffffb809`ecc361f0 00000000`00000000 : 0xffffb809`ef6fcd90
fffff281`0977ff58 00000000`00000001 : ffffb809`ecc361f0 ffffb809`ecc361f0 00000000`00000000 00000000`00000000 : 0xfffff281`09780050
fffff281`0977ff60 ffffb809`ecc361f0 : ffffb809`ecc361f0 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1
fffff281`0977ff68 ffffb809`ecc361f0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffb809`ecc361f0
fffff281`0977ff70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffb809`ecc361f0
SYMBOL_NAME: nt!MiSystemFault+172315
MODULE_NAME: nt
IMAGE_VERSION: 10.0.19041.630
STACK_COMMAND: .thread ; .cxr ; kb
IMAGE_NAME: ntkrnlmp.exe
BUCKET_ID_FUNC_OFFSET: 172315
FAILURE_BUCKET_ID: AV_INVALID_BAD_IP_nt!MiSystemFault
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {48ad9531-e3f8-1044-fc5f-d917677674c7}
Followup: MachineOwner
---------
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff801439041ab, The address that the exception occurred at
Arg3: fffffb0298315558, Exception Record Address
Arg4: fffffb0298314d90, Context Record Address
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : AV.Dereference
Value: NullClassPtr
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 6280
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-1IBQR0U
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 39352
Key : Analysis.Memory.CommitPeak.Mb
Value: 85
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: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff801439041ab
BUGCHECK_P3: fffffb0298315558
BUGCHECK_P4: fffffb0298314d90
EXCEPTION_RECORD: fffffb0298315558 -- (.exr 0xfffffb0298315558)
ExceptionAddress: fffff801439041ab (dxgmms2!VIDMM_GLOBAL::RemoveAllocationFromDecommitList+0x0000000000000093)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 000000000000000a
Attempt to read from address 000000000000000a
CONTEXT: fffffb0298314d90 -- (.cxr 0xfffffb0298314d90)
rax=ffff870836604f38 rbx=ffff8708308e0cc8 rcx=0000000000000002
rdx=0000000000000002 rsi=ffff8708308e0cb0 rdi=ffff870836604da0
rip=fffff801439041ab rsp=fffffb0298315790 rbp=fffffb02983158c0
r8=00000000ffffffff r9=7fff8708308e0cb0 r10=fffff801332dbb10
r11=ffffae050eb27860 r12=0000000000000000 r13=fffffb0298315b40
r14=ffffae051d039210 r15=ffff870836604da0
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050286
dxgmms2!VIDMM_GLOBAL::RemoveAllocationFromDecommitList+0x93:
fffff801`439041ab 48394208 cmp qword ptr [rdx+8],rax ds:002b:00000000`0000000a=????????????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: fffff80133cfb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80133c0f340: Unable to get Flags value from nt!KdVersionBlock
fffff80133c0f340: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
000000000000000a
ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek u olamaz %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 000000000000000a
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
fffffb02`98315790 fffff801`438e9198 : ffffae05`158dcc20 ffffae05`158d3000 ffffae05`00000000 ffffae05`158d3000 : dxgmms2!VIDMM_GLOBAL::RemoveAllocationFromDecommitList+0x93
fffffb02`983157c0 fffff801`438d9ce8 : ffffae05`158d3000 ffffae05`158dcc10 ffffae05`158d3000 ffffae05`158d3000 : dxgmms2!VIDMM_GLOBAL::ProcessDeferredCommand+0x344c8
fffffb02`98315a00 fffff801`438e3e99 : ffff8708`29c82b50 ffffae05`144c2000 00000000`00000000 00000000`04e1f000 : dxgmms2!VIDMM_WORKER_THREAD::Run+0xb78
fffffb02`98315be0 fffff801`332a29a5 : ffffae05`144c2080 fffff801`438e3e90 ffff8708`29c82b50 000f8067`b4bbbdff : dxgmms2!VidMmWorkerThreadProc+0x9
fffffb02`98315c10 fffff801`333fc868 : ffffc000`19ae6180 ffffae05`144c2080 fffff801`332a2950 ffffffff`ffffffff : nt!PspSystemThreadStartup+0x55
fffffb02`98315c60 00000000`00000000 : fffffb02`98316000 fffffb02`98310000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: dxgmms2!VIDMM_GLOBAL::RemoveAllocationFromDecommitList+93
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.19041.1124
STACK_COMMAND: .cxr 0xfffffb0298314d90 ; kb
BUCKET_ID_FUNC_OFFSET: 93
FAILURE_BUCKET_ID: AV_dxgmms2!VIDMM_GLOBAL::RemoveAllocationFromDecommitList
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {6c59b4be-29a7-a7bc-e0e2-8ae2ed2665e1}
Followup: MachineOwner
---------
