Sorun çıkartan bir Radeon VII, aşağıdaki mavi ekran hatalarına sebep olabilir.
Kod:
KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffb98e65764190, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffb98e657640e8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for atikmdag.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 4
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-HH6FM2D
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 55
Key : Analysis.Memory.CommitPeak.Mb
Value: 76
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: 139
BUGCHECK_P1: 3
BUGCHECK_P2: ffffb98e65764190
BUGCHECK_P3: ffffb98e657640e8
BUGCHECK_P4: 0
TRAP_FRAME: ffffb98e65764190 -- (.trap 0xffffb98e65764190)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff9680068e55e8 rbx=0000000000000000 rcx=0000000000000003
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8017be48b10 rsp=ffffb98e65764320 rbp=ffff9a81a02ee0c0
r8=0000000000000001 r9=0000000000000000 r10=fffff8017be484f0
r11=ffffb98e65764530 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po cy
nt!KiExitDispatcher+0x160:
fffff801`7be48b10 cd29 int 29h
Resetting default scope
EXCEPTION_RECORD: ffffb98e657640e8 -- (.exr 0xffffb98e657640e8)
ExceptionAddress: fffff8017be48b10 (nt!KiExitDispatcher+0x0000000000000160)
ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
ExceptionFlags: 00000001
NumberParameters: 1
Parameter[0]: 0000000000000003
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: Adobe Premiere Pro.exe
ERROR_CODE: (NTSTATUS) 0xc0000409 - Sistem, bu uygulamada y n tabanl bir arabelle in ta t n alg lad . Bu ta ma, k t niyetli bir kullan c n n bu uygulaman n denetimini ele ge irmesine olanak verebilir.
EXCEPTION_CODE_STR: c0000409
EXCEPTION_PARAMETER1: 0000000000000003
DPC_STACK_BASE: FFFFB98E65764FB0
EXCEPTION_STR: 0xc0000409
STACK_TEXT:
ffffb98e`65763e68 fffff801`7bfd32e9 : 00000000`00000139 00000000`00000003 ffffb98e`65764190 ffffb98e`657640e8 : nt!KeBugCheckEx
ffffb98e`65763e70 fffff801`7bfd3710 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffb98e`65763fb0 fffff801`7bfd1aa5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiFastFailDispatch+0xd0
ffffb98e`65764190 fffff801`7be48b10 : 00000000`00000000 33333333`33333333 00000000`00000008 fffff801`7be42497 : nt!KiRaiseSecurityCheckFailure+0x325
ffffb98e`65764320 fffff801`7be485a3 : ffff9680`068e55e0 00000000`00000000 ffff9a81`a05f5960 00000000`00000000 : nt!KiExitDispatcher+0x160
ffffb98e`65764380 fffff801`87002ef5 : 00000000`00000000 ffffb98e`657645b0 ffff928f`76bcf000 ffffb98e`657645b0 : nt!KeSetEvent+0xb3
ffffb98e`65764410 fffff801`87002be0 : ffff928f`76bcf570 fffff801`86ff81fa ffff928f`76bcf570 ffff928f`76bcf000 : dxgmms2!VidSchiProcessPresentHistoryToken+0x175
ffffb98e`657644d0 fffff801`86ff7cad : 00000000`00000000 00000000`00000002 ffffb98e`65764660 00000000`00000000 : dxgmms2!VidSchiSubmitPresentHistoryToken+0xb0
ffffb98e`65764560 fffff801`86ff70fe : ffff928f`76bf6802 ffff928f`00000000 ffff9680`00000000 ffff9680`00000000 : dxgmms2!VidSchiProcessCompletedQueuePacketInternal+0x7ed
ffffb98e`65764710 fffff801`86ff479b : ffff928f`76bf6802 00000000`00000001 ffffb98e`65764969 ffff9a81`00000000 : dxgmms2!VidSchiProcessDpcCompletedPacket+0x6ee
ffffb98e`65764870 fffff801`85224711 : ffffb98e`65764969 ffff928f`76bcf000 ffff9a81`95c0db50 00000000`00000000 : dxgmms2!VidSchDdiNotifyDpc+0x22b
ffffb98e`65764920 fffff801`8bbcef99 : ffff928f`76887000 fffff801`00000000 ffff928f`76887000 ffff928f`76887000 : dxgkrnl!DxgNotifyDpcCB+0x91
ffffb98e`657649d0 ffff928f`76887000 : fffff801`00000000 ffff928f`76887000 ffff928f`76887000 00000000`00000000 : atikmdag+0xbef99
ffffb98e`657649d8 fffff801`00000000 : ffff928f`76887000 ffff928f`76887000 00000000`00000000 ffff928f`7688a050 : 0xffff928f`76887000
ffffb98e`657649e0 ffff928f`76887000 : ffff928f`76887000 00000000`00000000 ffff928f`7688a050 ffff928f`768ec9d0 : 0xfffff801`00000000
ffffb98e`657649e8 ffff928f`76887000 : 00000000`00000000 ffff928f`7688a050 ffff928f`768ec9d0 00000000`00000000 : 0xffff928f`76887000
ffffb98e`657649f0 00000000`00000000 : ffff928f`7688a050 ffff928f`768ec9d0 00000000`00000000 00000000`00000000 : 0xffff928f`76887000
SYMBOL_NAME: dxgmms2!VidSchiProcessPresentHistoryToken+175
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.18362.418
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 175
FAILURE_BUCKET_ID: 0x139_3_CORRUPT_LIST_ENTRY_dxgmms2!VidSchiProcessPresentHistoryToken
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {dcc96d7c-024c-0254-0f9d-a23e7df66f4f}
Followup: MachineOwner
---------
THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: ffffca8cf4253080, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 0000000000000000, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 0000000000000000, Pointer to offending driver name.
Arg4: 0000000000000000, Number of times "intercepted" bugcheck 0xEA was hit (see notes).
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for atikmdag.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 4
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-HH6FM2D
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 59
Key : Analysis.Memory.CommitPeak.Mb
Value: 75
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: ea
BUGCHECK_P1: ffffca8cf4253080
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FAULTING_THREAD: ffffca8cf4253080
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: Corsair.Service.DisplayAdapter.exe
STACK_TEXT:
fffffe8d`9da52548 fffff807`31060db5 : 00000000`000000ea ffffca8c`f4253080 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffffe8d`9da52550 fffff807`31060e8e : fffffe8d`9da52638 fffff807`3103beab fffffe8d`9da52638 fffffe8d`9da52680 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
fffffe8d`9da525c0 fffff807`371724ca : 0000002b`b3838a8d fffffe8d`9da52680 00000000`00000000 ffffd28d`3c575000 : dxgkrnl!TdrTimedOperationDelay+0xce
fffffe8d`9da52600 0000002b`b3838a8d : fffffe8d`9da52680 00000000`00000000 ffffd28d`3c575000 00000000`00000001 : atikmdag+0x724ca
fffffe8d`9da52608 fffffe8d`9da52680 : 00000000`00000000 ffffd28d`3c575000 00000000`00000001 00000000`00989680 : 0x0000002b`b3838a8d
fffffe8d`9da52610 00000000`00000000 : ffffd28d`3c575000 00000000`00000001 00000000`00989680 fffffe8d`00000000 : 0xfffffe8d`9da52680
STACK_COMMAND: .thread 0xffffca8cf4253080 ; kb
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
IMAGE_VERSION: 10.0.18362.449
FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}
Followup: MachineOwner
---------
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: ffff9980e09d4eb0
Arg3: ffffbf88b82d1f30
Arg4: fffff80185214592
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 4
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-HH6FM2D
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 6
Key : Analysis.Memory.CommitPeak.Mb
Value: 80
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: 7f
BUGCHECK_P1: 8
BUGCHECK_P2: ffff9980e09d4eb0
BUGCHECK_P3: ffffbf88b82d1f30
BUGCHECK_P4: fffff80185214592
TRAP_FRAME: ffff9980e09d4eb0 -- (.trap 0xffff9980e09d4eb0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff359e9791e6cd rbx=0000000000000000 rcx=fffffffffffffffe
rdx=000000000000002c rsi=0000000000000000 rdi=0000000000000000
rip=fffff80185214592 rsp=ffffbf88b82d1f30 rbp=ffffbf88b82d22b0
r8=ffffbf88b82d24c0 r9=0000000000000010 r10=0000fffff8018521
r11=ffffbf88b82d21b8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!NtQueryInformationThread+0x42:
fffff801`85214592 4c89bc24b8000000 mov qword ptr [rsp+0B8h],r15 ss:0018:ffffbf88`b82d1fe8=????????????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXSCM: 1 (!blackboxscm)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: conhost.exe
STACK_OVERFLOW: Stack Limit: ffffbf88b82d2000. Use (kF) and (!stackusage) to investigate stack usage.
STACKUSAGE_FUNCTION: The function at address 0xffff950cb6dcc41b was blamed for the stack overflow. It is using 7680 bytes of stack total in 32 instances (likely recursion).
STACK_COMMAND: .trap 0xffff9980e09d4eb0 ; kb
SYMBOL_NAME: win32kfull!CreateScaledFont+13b
MODULE_NAME: win32kfull
IMAGE_NAME: win32kfull.sys
IMAGE_VERSION: 10.0.18362.295
BUCKET_ID_FUNC_OFFSET: 13b
FAILURE_BUCKET_ID: 0x7f_8_STACK_USAGE_RECURSION_win32kfull!CreateScaledFont
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {96a1b123-d9c5-7fec-7675-5fa6edd206f3}
Followup: MachineOwner
---------
