Thread stuck in device driver mavi ekran hatası

İşletim sistemi
Windows 10
N

nygaard99

Decapat
Katılım
21 Ekim 2020
Mesajlar
18
Daha fazla  
Cinsiyet
Erkek
Bilgisayar daha bir haftalık ama mavi ekran hatası alıyorum. Ekran kartını güncelledim ama sorun çözülmedi. Özellikle oyun sırasında oluyor.
Yardımlarınızı bekliyorum.
Yeni klasör
 
Tarihe göre sırala Puana göre sırala
  1. AMD'ye ait ekran kartınıza veya APU'nuza ait sürücüyü DDU ile kaldırın, en güncel sürüm yerine güncel olan WHQL sürüm yükleyin.

    Rehber: DDU ile Sürücü Kaldırma Rehberi

    Display Driver Uninstaller (DDU), zamanla bilgisayara takılan farklı monitörler, üst üste güncellenen sürücüler ve Windows güncellemeleri sonrası biriken kayıt defteri ve sürücü dosyalarını silerek temiz bir sürücü kurulumunun yolunu açan kullanışlı bir araçtır. Adım adım sürücü temizliği...
    www.technopat.net www.technopat.net

    Sorunun ekran kartınızdan kaynaklı olduğunu görüyorum.

  2. AMD sistemlerde BIOS güncellemesi de önemlidir. BIOS versiyonunuzu 3.70'ten 4.00'a yükseltin. *: Anakartınızın doğruluğunu teyit ettikten sonra işleme devam edin.
    www.asrock.com

    ASRock A320M-HDV R4.0

    AMD AM4 Socket; 2 DIMMs, Supports DDR4 3200+(OC)<span style=color:red;>*</span>; 1 PCIe 3.0 x16, 1 PCIe 2.0 x1; Graphics Output : HDMI, DVI-D, D-Sub; 7.1 CH HD Audio (Realtek ALC887/897 Audio Codec); 4 SATA3, 1 Ultra M.2 (PCIe Gen3 x4 & SATA3)<span style=color:red;>*</span>; 6 USB 3.2 Gen1 (2...
    www.asrock.com www.asrock.com


    Kod: 
    Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\CsHay\AppData\Local\Temp\Rar$DIa2852.20766\102120-8265-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff804`66400000 PsLoadedModuleList = 0xfffff804`6702a310
Debug session time: Wed Oct 21 00:41:21.624 2020 (UTC + 3:00)
System Uptime: 0 days 0:05:34.274
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
.......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`667f45a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9988`9029f7a0=00000000000000ea
4: kd> !analyze -v
*******************************************************************************
* *
* 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: ffffcf85ce8090c0, 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 win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4515

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-IPC9T25

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 50432

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: ea

BUGCHECK_P1: ffffcf85ce8090c0

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD: ffffcf85ce8090c0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: RadeonSoftware.exe

STACK_TEXT:
ffff9988`9029f798 fffff804`7502285d : 00000000`000000ea ffffcf85`ce8090c0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff9988`9029f7a0 fffff804`7502293e : ffff9988`9029f880 fffff804`74ff713b ffff9988`9029f880 fffff804`7a3730dc : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
ffff9988`9029f810 fffff804`7a23dd10 : 00000000`c754f8e7 fffff804`7a3730dc 00000000`00000000 ffffcf85`cb83e000 : dxgkrnl!TdrTimedOperationDelay+0xce
ffff9988`9029f850 00000000`c754f8e7 : fffff804`7a3730dc 00000000`00000000 ffffcf85`cb83e000 00000000`00989680 : amdkmdag+0x6dd10
ffff9988`9029f858 fffff804`7a3730dc : 00000000`00000000 ffffcf85`cb83e000 00000000`00989680 00000000`00000001 : 0xc754f8e7
ffff9988`9029f860 00000000`00000000 : ffffcf85`cb83e000 00000000`00989680 00000000`00000001 00000000`00000028 : amdkmdag+0x1a30dc


STACK_COMMAND: .thread 0xffffcf85ce8090c0 ; kb

SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

IMAGE_VERSION: 10.0.19041.572

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
---------

Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\CsHay\AppData\Local\Temp\Rar$DIa2852.5737\102120-8859-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff807`56000000 PsLoadedModuleList = 0xfffff807`56c2a310
Debug session time: Wed Oct 21 00:16:16.892 2020 (UTC + 3:00)
System Uptime: 0 days 0:03:30.543
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
.......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`563f45a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff607`d88d07a0=00000000000000ea
4: kd> !analyze -v
*******************************************************************************
* *
* 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: ffffd081e6322080, 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: 5703

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-IPC9T25

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 48424

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: ea

BUGCHECK_P1: ffffd081e6322080

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD: ffffd081e6322080

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: RadeonSoftware.exe

STACK_TEXT:
fffff607`d88d0798 fffff807`6111285d : 00000000`000000ea ffffd081`e6322080 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff607`d88d07a0 fffff807`6111293e : fffff607`d88d0880 fffff807`610e713b fffff607`d88d0880 fffff807`67e22ddc : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
fffff607`d88d0810 fffff807`67cedae0 : 00000000`7d950e56 fffff807`67e22ddc 00000000`00000000 ffffd081`e683e000 : dxgkrnl!TdrTimedOperationDelay+0xce
fffff607`d88d0850 00000000`7d950e56 : fffff807`67e22ddc 00000000`00000000 ffffd081`e683e000 00000000`00989680 : amdkmdag+0x6dae0
fffff607`d88d0858 fffff807`67e22ddc : 00000000`00000000 ffffd081`e683e000 00000000`00989680 00000000`00000001 : 0x7d950e56
fffff607`d88d0860 00000000`00000000 : ffffd081`e683e000 00000000`00989680 00000000`00000001 00000000`00000028 : amdkmdag+0x1a2ddc


STACK_COMMAND: .thread 0xffffd081e6322080 ; kb

SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

IMAGE_VERSION: 10.0.19041.572

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
---------
    [*]
 
Artı 0 Eksi
Önerdiğiniz işlemleri uygulamama rağmen sorun devam ediyor özellikle bazı oyunlarda hatayı alıyorum diğerlerinde hata çıkmıyor.Yeni klasör
ViooYa dedi:
  1. AMD'ye ait ekran kartınıza veya APU'nuza ait sürücüyü DDU ile kaldırın, en güncel sürüm yerine güncel olan WHQL sürüm yükleyin.

    Rehber: DDU ile Sürücü Kaldırma Rehberi

    Display Driver Uninstaller (DDU), zamanla bilgisayara takılan farklı monitörler, üst üste güncellenen sürücüler ve Windows güncellemeleri sonrası biriken kayıt defteri ve sürücü dosyalarını silerek temiz bir sürücü kurulumunun yolunu açan kullanışlı bir araçtır. Adım adım sürücü temizliği...
    www.technopat.net www.technopat.net

    Sorunun ekran kartınızdan kaynaklı olduğunu görüyorum.

  2. AMD sistemlerde BIOS güncellemesi de önemlidir. BIOS versiyonunuzu 3.70'ten 4.00'a yükseltin. *: Anakartınızın doğruluğunu teyit ettikten sonra işleme devam edin.
    www.asrock.com

    ASRock A320M-HDV R4.0

    AMD AM4 Socket; 2 DIMMs, Supports DDR4 3200+(OC)<span style=color:red;>*</span>; 1 PCIe 3.0 x16, 1 PCIe 2.0 x1; Graphics Output : HDMI, DVI-D, D-Sub; 7.1 CH HD Audio (Realtek ALC887/897 Audio Codec); 4 SATA3, 1 Ultra M.2 (PCIe Gen3 x4 & SATA3)<span style=color:red;>*</span>; 6 USB 3.2 Gen1 (2...
    www.asrock.com www.asrock.com


    Kod: 
    Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\CsHay\AppData\Local\Temp\Rar$DIa2852.20766\102120-8265-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff804`66400000 PsLoadedModuleList = 0xfffff804`6702a310
Debug session time: Wed Oct 21 00:41:21.624 2020 (UTC + 3:00)
System Uptime: 0 days 0:05:34.274
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
.......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`667f45a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9988`9029f7a0=00000000000000ea
4: kd> !analyze -v
*******************************************************************************
* *
* 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: ffffcf85ce8090c0, 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 win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4515

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-IPC9T25

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 50432

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: ea

BUGCHECK_P1: ffffcf85ce8090c0

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD: ffffcf85ce8090c0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: RadeonSoftware.exe

STACK_TEXT:
ffff9988`9029f798 fffff804`7502285d : 00000000`000000ea ffffcf85`ce8090c0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff9988`9029f7a0 fffff804`7502293e : ffff9988`9029f880 fffff804`74ff713b ffff9988`9029f880 fffff804`7a3730dc : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
ffff9988`9029f810 fffff804`7a23dd10 : 00000000`c754f8e7 fffff804`7a3730dc 00000000`00000000 ffffcf85`cb83e000 : dxgkrnl!TdrTimedOperationDelay+0xce
ffff9988`9029f850 00000000`c754f8e7 : fffff804`7a3730dc 00000000`00000000 ffffcf85`cb83e000 00000000`00989680 : amdkmdag+0x6dd10
ffff9988`9029f858 fffff804`7a3730dc : 00000000`00000000 ffffcf85`cb83e000 00000000`00989680 00000000`00000001 : 0xc754f8e7
ffff9988`9029f860 00000000`00000000 : ffffcf85`cb83e000 00000000`00989680 00000000`00000001 00000000`00000028 : amdkmdag+0x1a30dc


STACK_COMMAND: .thread 0xffffcf85ce8090c0 ; kb

SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

IMAGE_VERSION: 10.0.19041.572

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
---------

Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\CsHay\AppData\Local\Temp\Rar$DIa2852.5737\102120-8859-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff807`56000000 PsLoadedModuleList = 0xfffff807`56c2a310
Debug session time: Wed Oct 21 00:16:16.892 2020 (UTC + 3:00)
System Uptime: 0 days 0:03:30.543
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
.......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`563f45a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff607`d88d07a0=00000000000000ea
4: kd> !analyze -v
*******************************************************************************
* *
* 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: ffffd081e6322080, 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: 5703

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-IPC9T25

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 48424

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: ea

BUGCHECK_P1: ffffd081e6322080

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD: ffffd081e6322080

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: RadeonSoftware.exe

STACK_TEXT:
fffff607`d88d0798 fffff807`6111285d : 00000000`000000ea ffffd081`e6322080 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff607`d88d07a0 fffff807`6111293e : fffff607`d88d0880 fffff807`610e713b fffff607`d88d0880 fffff807`67e22ddc : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
fffff607`d88d0810 fffff807`67cedae0 : 00000000`7d950e56 fffff807`67e22ddc 00000000`00000000 ffffd081`e683e000 : dxgkrnl!TdrTimedOperationDelay+0xce
fffff607`d88d0850 00000000`7d950e56 : fffff807`67e22ddc 00000000`00000000 ffffd081`e683e000 00000000`00989680 : amdkmdag+0x6dae0
fffff607`d88d0858 fffff807`67e22ddc : 00000000`00000000 ffffd081`e683e000 00000000`00989680 00000000`00000001 : 0x7d950e56
fffff607`d88d0860 00000000`00000000 : ffffd081`e683e000 00000000`00989680 00000000`00000001 00000000`00000028 : amdkmdag+0x1a2ddc


STACK_COMMAND: .thread 0xffffd081e6322080 ; kb

SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

IMAGE_VERSION: 10.0.19041.572

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
---------
    [*]
Genişletmek için tıkla...
nygaard99 dedi:
Önerdiğiniz işlemleri uygulamama rağmen sorun devam ediyor özellikle bazı oyunlarda hatayı alıyorum diğerlerinde hata çıkmıyor.Yeni klasör
Genişletmek için tıkla...
Yeni minidump dosyamı kontrol edebilirmisiniz başka ne yapmam gerekiyor.
 
Son düzenleme:
Artı 0 Eksi
HWMonitor, AMD RyzenMaster, MSI Afterburner tarzı bir program var ise kaldır.

DDU ile ekran akrtı sürücüsünü kaldır ve WYQL indir.

İlk defa denedim şansımı bir hatam var ise düzeltin.
 
Artı 0 Eksi

Benzer konular

waxy34
  • Soru
THREAD STUCK IN DEVICE Driver mavi ekran hatası
2 3
Mesaj
27
Görüntüleme
4B
perseid78
perseid78
RealtimeUfuk
  • Soru
"Thread Stuck in Device Driver" Mavi Ekran Hatası
Mesaj
1
Görüntüleme
2B
Talha Ertürk
Talha Ertürk
wintry
  • Çözüldü
Çözüldü  Thread Stuck In Device Driver mavi ekran hatası
2
Mesaj
19
Görüntüleme
2B
283156
2
W
  • Çözüldü
Çözüldü  THREAD STUCK IN DEVICE DRIVER mavi ekran hatası
2
Mesaj
13
Görüntüleme
4B
waspote
W
Ssouvenirs
  • Soru
Çözüldü  "Thread Stuck In Driver Device" Mavi Ekran Hatası
2
Mesaj
19
Görüntüleme
1B
claus
claus

Yeni konular

Yeni mesajlar

Geri
Yukarı