THREAD_STUCK_IN_DEVICE_DRIVER_M mavi ekran hatası

Orheyn

Hectopat
Katılım
15 Şubat 2020
Mesajlar
91
Çözümler
1
Gom Player'dan video izlerken mavi ekran aldım. Bilgisayarım daha 15 günlük ve 10 gün önce en güncel driverları yükledim, BIOS sürümü son sürüm. Dediğim gibi video izliyordum, bilgisayar 5 saattir falan açık ve hiç yormadım, powerpointte takılıp video izledim sadece.
minidump dosyam

WhatsApp Image 2020-02-23 at 18.31.26 (1).jpeg


WhatsApp Image 2020-02-23 at 18.31.26.jpeg
 
Son düzenleme:
BIOS sürümü son sürüm.
BIOS güncel değil, neden güncel diyorsun anlamıyorum, güncelle.
BIOS_VERSION: FX505DT.308

DDU ile dahili AMD sürücüsünü kaldır tekrar yükle.

ASUS, Ryzen Master yazılımlarını kaldır.
Kod:
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: ffff9a837ce88080, 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


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  ASUSTeK COMPUTER INC.

SYSTEM_PRODUCT_NAME:  TUF Gaming FX505DT_FX505DT

SYSTEM_VERSION:  1.0

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  FX505DT.308

BIOS_DATE:  09/19/2019

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  FX505DT

BASEBOARD_VERSION:  1.0

DUMP_TYPE:  2

BUGCHECK_P1: ffff9a837ce88080

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD:  ffff9a837ce88080

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CPU_COUNT: 8

CPU_MHZ: 830

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 18

CPU_STEPPING: 1

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xEA

PROCESS_NAME:  atieclxx.exe

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  02-23-2020 18:43:43.0595

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff80736060db5 to fffff80728dc14e0

STACK_TEXT: 
ffffd507`2db44618 fffff807`36060db5 : 00000000`000000ea ffff9a83`7ce88080 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffd507`2db44620 fffff807`36060e8e : ffffd507`2db44700 fffff807`3603beab ffffd507`2db44700 fffff807`400c3954 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
ffffd507`2db44690 fffff807`4002db00 : 000003f5`8dcdfb36 fffff807`400c3954 00000000`00000000 ffff9a83`6a80c000 : dxgkrnl!TdrTimedOperationDelay+0xce
ffffd507`2db446d0 000003f5`8dcdfb36 : fffff807`400c3954 00000000`00000000 ffff9a83`6a80c000 00000000`00989680 : atikmdag+0x6db00
ffffd507`2db446d8 fffff807`400c3954 : 00000000`00000000 ffff9a83`6a80c000 00000000`00989680 00000000`00000001 : 0x000003f5`8dcdfb36
ffffd507`2db446e0 00000000`00000000 : ffff9a83`6a80c000 00000000`00989680 00000000`00000001 00000000`00000028 : atikmdag+0x103954


STACK_COMMAND:  .thread 0xffff9a837ce88080 ; kb

THREAD_SHA1_HASH_MOD_FUNC:  72fdf9c2701b15ee3875c8d84432bb6f4f878992

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  8733c7833060fb02ce8c6a0258e1674615927de1

THREAD_SHA1_HASH_MOD:  7711aec31f9092c0b1e7c4bf053e92961bf05370

FOLLOWUP_IP:
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45
fffff807`36060db5 cc              int     3

FAULT_INSTR_CODE:  cccccccc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  3b77b364

IMAGE_VERSION:  10.0.18362.628

FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys

BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys

PRIMARY_PROBLEM_CLASS:  0xEA_IMAGE_dxgkrnl.sys

TARGET_TIME:  2020-02-23T14:59:07.000Z

OSBUILD:  18362

OSSERVICEPACK:  628

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE: 

USER_LCID:  0

OSBUILD_TIMESTAMP:  1991-11-30 08:21:39

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  12474

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xea_image_dxgkrnl.sys

FAILURE_ID_HASH:  {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}

Followup:     MachineOwner
---------
 
BIOS güncel değil, neden güncel diyorsun anlamıyorum, güncelle.


DDU ile dahili AMD sürücüsünü kaldır tekrar yükle.

ASUS, Ryzen Master yazılımlarını kaldır.
Kod:
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: ffff9a837ce88080, 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


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  ASUSTeK COMPUTER INC.

SYSTEM_PRODUCT_NAME:  TUF Gaming FX505DT_FX505DT

SYSTEM_VERSION:  1.0

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  FX505DT.308

BIOS_DATE:  09/19/2019

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  FX505DT

BASEBOARD_VERSION:  1.0

DUMP_TYPE:  2

BUGCHECK_P1: ffff9a837ce88080

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD:  ffff9a837ce88080

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CPU_COUNT: 8

CPU_MHZ: 830

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 18

CPU_STEPPING: 1

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xEA

PROCESS_NAME:  atieclxx.exe

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  02-23-2020 18:43:43.0595

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff80736060db5 to fffff80728dc14e0

STACK_TEXT:
ffffd507`2db44618 fffff807`36060db5 : 00000000`000000ea ffff9a83`7ce88080 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffd507`2db44620 fffff807`36060e8e : ffffd507`2db44700 fffff807`3603beab ffffd507`2db44700 fffff807`400c3954 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
ffffd507`2db44690 fffff807`4002db00 : 000003f5`8dcdfb36 fffff807`400c3954 00000000`00000000 ffff9a83`6a80c000 : dxgkrnl!TdrTimedOperationDelay+0xce
ffffd507`2db446d0 000003f5`8dcdfb36 : fffff807`400c3954 00000000`00000000 ffff9a83`6a80c000 00000000`00989680 : atikmdag+0x6db00
ffffd507`2db446d8 fffff807`400c3954 : 00000000`00000000 ffff9a83`6a80c000 00000000`00989680 00000000`00000001 : 0x000003f5`8dcdfb36
ffffd507`2db446e0 00000000`00000000 : ffff9a83`6a80c000 00000000`00989680 00000000`00000001 00000000`00000028 : atikmdag+0x103954


STACK_COMMAND:  .thread 0xffff9a837ce88080 ; kb

THREAD_SHA1_HASH_MOD_FUNC:  72fdf9c2701b15ee3875c8d84432bb6f4f878992

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  8733c7833060fb02ce8c6a0258e1674615927de1

THREAD_SHA1_HASH_MOD:  7711aec31f9092c0b1e7c4bf053e92961bf05370

FOLLOWUP_IP:
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45
fffff807`36060db5 cc              int     3

FAULT_INSTR_CODE:  cccccccc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  3b77b364

IMAGE_VERSION:  10.0.18362.628

FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys

BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys

PRIMARY_PROBLEM_CLASS:  0xEA_IMAGE_dxgkrnl.sys

TARGET_TIME:  2020-02-23T14:59:07.000Z

OSBUILD:  18362

OSSERVICEPACK:  628

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID:  0

OSBUILD_TIMESTAMP:  1991-11-30 08:21:39

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  12474

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xea_image_dxgkrnl.sys

FAILURE_ID_HASH:  {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}

Followup:     MachineOwner
---------
Aldığımda V308 idi ASUS'un paylaştığı son sürüm. Daha dün aklıma geldi kontrol ettim V308 idi benim sürümüm de. Daha dün doğruladığım için yeni baktığımı düşündüm fakat ASUS'un sitesine V310 gelmiş hemen güncelleyeyim teşekkürler. AMD sürücüsü hakkında da https://www.amd.com/en/support/apu/...processors-radeon-vega-graphics/amd-ryzen-5-2 bu siteden bulmaya çalıştım ama indirme yerini bulamadım. Nereden bulacağım bu driverı? ASUS'un sitesindeki son güncel sürüm müdür acaba? NVIDIA'nın güncel sürümünü vermemişti.

He bir de Ryzen Master ile ilgili bir program yok bilgisayarımda ama klavye aydınlatmasını düzenleyen TUF Aura Core ve fan çalışma hızı gibi birkaç detayı gösteren Armoury Create adlı programlar yüklü onların zararı mı oluyor kaldırayım mı? Ayrıca bir yerde MSI Afterburner kaldırın demişler onu da kaldırayım mı?
 
Bu sürüm.
Eki Görüntüle 505335

Evet iki dediğim programı da kaldır.
Ayrıca Ryzen Master adlı programı ben dosyada gördüm, bu program.
Yok hocam ben öyle bir program yüklemedim ki program ekle/kaldır da da yok zaten. Teşekkür ederim. Peki bu ASUS uygulamalarının nasıl bir parmağı var bilgisayarda? Ayrıca işlemci driverlarını bulamadım, DriverPack diye bir uygulama ile yüklemiştim driverların bazılarını. Onu kullansam yine olur mu acaba? Bir de son olarak MSI Afterburner'ı da kaldırayım mı?
 
Sürücü bulucu kullandıysan hiç uğraşma direk temiz kurulum yap, sonra gerekli tüm sürücüleri elle yükle.

ASUS ve MSI programları sistem kararlılığını bozuyor.
Temiz kurulumdan kastın format mı? Bütün bunları 1-2 hafta sonra yapsam bilgisayarıma kayda değer bi zarar gelir mi peki? KYKda kalıyorum internetim yok da yapamayacağım şimdilik hiçbir şey
 
Uyarı! Bu konu 6 yıl önce açıldı.
Muhtemelen daha fazla tartışma gerekli değildir ki bu durumda yeni bir konu başlatmayı öneririz. Eğer yine de cevabınızın gerekli olduğunu düşünüyorsanız buna rağmen cevap verebilirsiniz.

Bu konuyu görüntüleyen kullanıcılar

Technopat Haberler

Geri
Yukarı