Adrenalin 2020 Edition 20.11.2 Recommended (WHQL) sürümlü sürücüyü indirin. Daha sonra DDU ile eski sürücünüzü kaldırıp bilgisayar yeniden başladığında bu indirdiğiniz sürücüyü kurun. DDU rehberi linki de aşağıda mevcuttur.*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: ffffb5012c2cc0c0, 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:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 10124
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-70T822T
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 121916
Key : Analysis.Memory.CommitPeak.Mb
Value: 82
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: ea
BUGCHECK_P1: ffffb5012c2cc0c0
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FAULTING_THREAD: ffffb5012c2cc0c0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: RadeonSoftware.exe
STACK_TEXT:
ffffa004`07f94798 fffff802`8f67289d : 00000000`000000ea ffffb501`2c2cc0c0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffa004`07f947a0 fffff802`8f67297e : ffffa004`07f94880 fffff802`8f64727b ffffa004`07f94880 fffff802`94e1a764 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
ffffa004`07f94810 fffff802`94ce0c00 : 000000b9`ee7626f4 fffff802`94e1a764 00000000`00000000 ffffb501`25bbe000 : dxgkrnl!TdrTimedOperationDelay+0xce
ffffa004`07f94850 000000b9`ee7626f4 : fffff802`94e1a764 00000000`00000000 ffffb501`25bbe000 00000000`00989680 : amdkmdag+0x70c00
ffffa004`07f94858 fffff802`94e1a764 : 00000000`00000000 ffffb501`25bbe000 00000000`00989680 00000000`00000001 : 0x000000b9`ee7626f4
ffffa004`07f94860 00000000`00000000 : ffffb501`25bbe000 00000000`00989680 00000000`00000001 00000000`00000028 : amdkmdag+0x1aa764
STACK_COMMAND: .thread 0xffffb5012c2cc0c0 ; kb
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
IMAGE_VERSION: 10.0.19041.685
FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: ffffb5012c2cc0c0, 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:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 10124
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-70T822T
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 121916
Key : Analysis.Memory.CommitPeak.Mb
Value: 82
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: ea
BUGCHECK_P1: ffffb5012c2cc0c0
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FAULTING_THREAD: ffffb5012c2cc0c0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: RadeonSoftware.exe
STACK_TEXT:
ffffa004`07f94798 fffff802`8f67289d : 00000000`000000ea ffffb501`2c2cc0c0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffa004`07f947a0 fffff802`8f67297e : ffffa004`07f94880 fffff802`8f64727b ffffa004`07f94880 fffff802`94e1a764 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
ffffa004`07f94810 fffff802`94ce0c00 : 000000b9`ee7626f4 fffff802`94e1a764 00000000`00000000 ffffb501`25bbe000 : dxgkrnl!TdrTimedOperationDelay+0xce
ffffa004`07f94850 000000b9`ee7626f4 : fffff802`94e1a764 00000000`00000000 ffffb501`25bbe000 00000000`00989680 : amdkmdag+0x70c00
ffffa004`07f94858 fffff802`94e1a764 : 00000000`00000000 ffffb501`25bbe000 00000000`00989680 00000000`00000001 : 0x000000b9`ee7626f4
ffffa004`07f94860 00000000`00000000 : ffffb501`25bbe000 00000000`00989680 00000000`00000001 00000000`00000028 : amdkmdag+0x1aa764
STACK_COMMAND: .thread 0xffffb5012c2cc0c0 ; kb
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
IMAGE_VERSION: 10.0.19041.685
FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}
Followup: MachineOwner
---------
Adrenalin 2020 Edition 20.11.2 Recommended (WHQL) sürümlü sürücüyü indirin. Daha sonra DDU ile eski sürücünüzü kaldırıp bilgisayar yeniden başladığında bu indirdiğiniz sürücüyü kurun. DDU rehberi linki de aşağıda mevcuttur.*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: ffffb5012c2cc0c0, 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:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 10124
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-70T822T
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 121916
Key : Analysis.Memory.CommitPeak.Mb
Value: 82
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: ea
BUGCHECK_P1: ffffb5012c2cc0c0
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FAULTING_THREAD: ffffb5012c2cc0c0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: RadeonSoftware.exe
STACK_TEXT:
ffffa004`07f94798 fffff802`8f67289d : 00000000`000000ea ffffb501`2c2cc0c0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffa004`07f947a0 fffff802`8f67297e : ffffa004`07f94880 fffff802`8f64727b ffffa004`07f94880 fffff802`94e1a764 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
ffffa004`07f94810 fffff802`94ce0c00 : 000000b9`ee7626f4 fffff802`94e1a764 00000000`00000000 ffffb501`25bbe000 : dxgkrnl!TdrTimedOperationDelay+0xce
ffffa004`07f94850 000000b9`ee7626f4 : fffff802`94e1a764 00000000`00000000 ffffb501`25bbe000 00000000`00989680 : amdkmdag+0x70c00
ffffa004`07f94858 fffff802`94e1a764 : 00000000`00000000 ffffb501`25bbe000 00000000`00989680 00000000`00000001 : 0x000000b9`ee7626f4
ffffa004`07f94860 00000000`00000000 : ffffb501`25bbe000 00000000`00989680 00000000`00000001 00000000`00000028 : amdkmdag+0x1aa764
STACK_COMMAND: .thread 0xffffb5012c2cc0c0 ; kb
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
IMAGE_VERSION: 10.0.19041.685
FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: ffffb5012c2cc0c0, 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:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 10124
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-70T822T
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 121916
Key : Analysis.Memory.CommitPeak.Mb
Value: 82
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: ea
BUGCHECK_P1: ffffb5012c2cc0c0
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FAULTING_THREAD: ffffb5012c2cc0c0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: RadeonSoftware.exe
STACK_TEXT:
ffffa004`07f94798 fffff802`8f67289d : 00000000`000000ea ffffb501`2c2cc0c0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffa004`07f947a0 fffff802`8f67297e : ffffa004`07f94880 fffff802`8f64727b ffffa004`07f94880 fffff802`94e1a764 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
ffffa004`07f94810 fffff802`94ce0c00 : 000000b9`ee7626f4 fffff802`94e1a764 00000000`00000000 ffffb501`25bbe000 : dxgkrnl!TdrTimedOperationDelay+0xce
ffffa004`07f94850 000000b9`ee7626f4 : fffff802`94e1a764 00000000`00000000 ffffb501`25bbe000 00000000`00989680 : amdkmdag+0x70c00
ffffa004`07f94858 fffff802`94e1a764 : 00000000`00000000 ffffb501`25bbe000 00000000`00989680 00000000`00000001 : 0x000000b9`ee7626f4
ffffa004`07f94860 00000000`00000000 : ffffb501`25bbe000 00000000`00989680 00000000`00000001 00000000`00000028 : amdkmdag+0x1aa764
STACK_COMMAND: .thread 0xffffb5012c2cc0c0 ; kb
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
IMAGE_VERSION: 10.0.19041.685
FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}
Followup: MachineOwner
---------
1) Easy Anti-Cheat kaldırın.
2) MSI Afterburner kaldırın.
3) CPU-Z kaldırın.
4) PUBG'nin Anti-Cheat yazılımını kaldırın. XIGNCODE olarak geçiyor.
5) Aşağıdaki websitedenAdrenalin 2020 Edition 20.11.2 Recommended (WHQL)sürümlü sürücüyü indirin. Daha sonra DDU ile eski sürücünüzü kaldırıp bilgisayar yeniden başladığında bu indirdiğiniz sürücüyü kurun. DDU rehberi linki de aşağıda mevcuttur.
Website: https://www.amd.com/en/support/apu/...processors-radeon-vega-graphics/amd-ryzen-3-1
Rehber: DDU ile Sürücü Kaldırma Rehberi
6) Aşağıdaki rehberi uygulayıp sonucun ekran alıntısını paylaşın.
Kod:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: ffffb5012c2cc0c0, 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: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 10124 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-70T822T Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 121916 Key : Analysis.Memory.CommitPeak.Mb Value: 82 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: ea BUGCHECK_P1: ffffb5012c2cc0c0 BUGCHECK_P2: 0 BUGCHECK_P3: 0 BUGCHECK_P4: 0 FAULTING_THREAD: ffffb5012c2cc0c0 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: RadeonSoftware.exe STACK_TEXT: ffffa004`07f94798 fffff802`8f67289d : 00000000`000000ea ffffb501`2c2cc0c0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx ffffa004`07f947a0 fffff802`8f67297e : ffffa004`07f94880 fffff802`8f64727b ffffa004`07f94880 fffff802`94e1a764 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45 ffffa004`07f94810 fffff802`94ce0c00 : 000000b9`ee7626f4 fffff802`94e1a764 00000000`00000000 ffffb501`25bbe000 : dxgkrnl!TdrTimedOperationDelay+0xce ffffa004`07f94850 000000b9`ee7626f4 : fffff802`94e1a764 00000000`00000000 ffffb501`25bbe000 00000000`00989680 : amdkmdag+0x70c00 ffffa004`07f94858 fffff802`94e1a764 : 00000000`00000000 ffffb501`25bbe000 00000000`00989680 00000000`00000001 : 0x000000b9`ee7626f4 ffffa004`07f94860 00000000`00000000 : ffffb501`25bbe000 00000000`00989680 00000000`00000001 00000000`00000028 : amdkmdag+0x1aa764 STACK_COMMAND: .thread 0xffffb5012c2cc0c0 ; kb SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45 MODULE_NAME: dxgkrnl IMAGE_NAME: dxgkrnl.sys IMAGE_VERSION: 10.0.19041.685 FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8} Followup: MachineOwner --------- ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: ffffb5012c2cc0c0, 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: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 10124 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-70T822T Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 121916 Key : Analysis.Memory.CommitPeak.Mb Value: 82 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: ea BUGCHECK_P1: ffffb5012c2cc0c0 BUGCHECK_P2: 0 BUGCHECK_P3: 0 BUGCHECK_P4: 0 FAULTING_THREAD: ffffb5012c2cc0c0 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: RadeonSoftware.exe STACK_TEXT: ffffa004`07f94798 fffff802`8f67289d : 00000000`000000ea ffffb501`2c2cc0c0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx ffffa004`07f947a0 fffff802`8f67297e : ffffa004`07f94880 fffff802`8f64727b ffffa004`07f94880 fffff802`94e1a764 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45 ffffa004`07f94810 fffff802`94ce0c00 : 000000b9`ee7626f4 fffff802`94e1a764 00000000`00000000 ffffb501`25bbe000 : dxgkrnl!TdrTimedOperationDelay+0xce ffffa004`07f94850 000000b9`ee7626f4 : fffff802`94e1a764 00000000`00000000 ffffb501`25bbe000 00000000`00989680 : amdkmdag+0x70c00 ffffa004`07f94858 fffff802`94e1a764 : 00000000`00000000 ffffb501`25bbe000 00000000`00989680 00000000`00000001 : 0x000000b9`ee7626f4 ffffa004`07f94860 00000000`00000000 : ffffb501`25bbe000 00000000`00989680 00000000`00000001 00000000`00000028 : amdkmdag+0x1aa764 STACK_COMMAND: .thread 0xffffb5012c2cc0c0 ; kb SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45 MODULE_NAME: dxgkrnl IMAGE_NAME: dxgkrnl.sys IMAGE_VERSION: 10.0.19041.685 FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8} Followup: MachineOwner ---------
Bu rehberi nasıl yapabilirim pek anlamadım1) Easy Anti-Cheat kaldırın.
2) MSI Afterburner kaldırın.
3) CPU-Z kaldırın.
4) PUBG'nin Anti-Cheat yazılımını kaldırın. XIGNCODE olarak geçiyor.
5) Aşağıdaki websitedenAdrenalin 2020 Edition 20.11.2 Recommended (WHQL)sürümlü sürücüyü indirin. Daha sonra DDU ile eski sürücünüzü kaldırıp bilgisayar yeniden başladığında bu indirdiğiniz sürücüyü kurun. DDU rehberi linki de aşağıda mevcuttur.
Website: https://www.amd.com/en/support/apu/...processors-radeon-vega-graphics/amd-ryzen-3-1
Rehber: DDU ile Sürücü Kaldırma Rehberi
6) Aşağıdaki rehberi uygulayıp sonucun ekran alıntısını paylaşın.
Kod:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: ffffb5012c2cc0c0, 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: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 10124 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-70T822T Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 121916 Key : Analysis.Memory.CommitPeak.Mb Value: 82 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: ea BUGCHECK_P1: ffffb5012c2cc0c0 BUGCHECK_P2: 0 BUGCHECK_P3: 0 BUGCHECK_P4: 0 FAULTING_THREAD: ffffb5012c2cc0c0 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: RadeonSoftware.exe STACK_TEXT: ffffa004`07f94798 fffff802`8f67289d : 00000000`000000ea ffffb501`2c2cc0c0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx ffffa004`07f947a0 fffff802`8f67297e : ffffa004`07f94880 fffff802`8f64727b ffffa004`07f94880 fffff802`94e1a764 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45 ffffa004`07f94810 fffff802`94ce0c00 : 000000b9`ee7626f4 fffff802`94e1a764 00000000`00000000 ffffb501`25bbe000 : dxgkrnl!TdrTimedOperationDelay+0xce ffffa004`07f94850 000000b9`ee7626f4 : fffff802`94e1a764 00000000`00000000 ffffb501`25bbe000 00000000`00989680 : amdkmdag+0x70c00 ffffa004`07f94858 fffff802`94e1a764 : 00000000`00000000 ffffb501`25bbe000 00000000`00989680 00000000`00000001 : 0x000000b9`ee7626f4 ffffa004`07f94860 00000000`00000000 : ffffb501`25bbe000 00000000`00989680 00000000`00000001 00000000`00000028 : amdkmdag+0x1aa764 STACK_COMMAND: .thread 0xffffb5012c2cc0c0 ; kb SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45 MODULE_NAME: dxgkrnl IMAGE_NAME: dxgkrnl.sys IMAGE_VERSION: 10.0.19041.685 FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8} Followup: MachineOwner --------- ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: ffffb5012c2cc0c0, 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: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 10124 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-70T822T Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 121916 Key : Analysis.Memory.CommitPeak.Mb Value: 82 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: ea BUGCHECK_P1: ffffb5012c2cc0c0 BUGCHECK_P2: 0 BUGCHECK_P3: 0 BUGCHECK_P4: 0 FAULTING_THREAD: ffffb5012c2cc0c0 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: RadeonSoftware.exe STACK_TEXT: ffffa004`07f94798 fffff802`8f67289d : 00000000`000000ea ffffb501`2c2cc0c0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx ffffa004`07f947a0 fffff802`8f67297e : ffffa004`07f94880 fffff802`8f64727b ffffa004`07f94880 fffff802`94e1a764 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45 ffffa004`07f94810 fffff802`94ce0c00 : 000000b9`ee7626f4 fffff802`94e1a764 00000000`00000000 ffffb501`25bbe000 : dxgkrnl!TdrTimedOperationDelay+0xce ffffa004`07f94850 000000b9`ee7626f4 : fffff802`94e1a764 00000000`00000000 ffffb501`25bbe000 00000000`00989680 : amdkmdag+0x70c00 ffffa004`07f94858 fffff802`94e1a764 : 00000000`00000000 ffffb501`25bbe000 00000000`00989680 00000000`00000001 : 0x000000b9`ee7626f4 ffffa004`07f94860 00000000`00000000 : ffffb501`25bbe000 00000000`00989680 00000000`00000001 00000000`00000028 : amdkmdag+0x1aa764 STACK_COMMAND: .thread 0xffffb5012c2cc0c0 ; kb SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45 MODULE_NAME: dxgkrnl IMAGE_NAME: dxgkrnl.sys IMAGE_VERSION: 10.0.19041.685 FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8} Followup: MachineOwner ---------
