THREAD_STUCK_IN_DEVICE_DRIVER_M mavi ekran hatası

Katılım
12 Temmuz 2014
Mesajlar
1.078
Çözümler
18
Bilgisayarım bazen oyun oynarken alttan müzik veya başka bir program açtığımda siyah ekranda kalıyor ve klavye mouse de gidiyor. Reset atmadan düzelmiyor. Kasayı açıp kabloları çıkarıp taktıktan sonra düzeliyor. 2-3 ayda bir tekrar ediyor. Minidump dosyasını paylaşıyorum. Yardımcı olur musunuz?

Sistemim:
  • RAM 4x2 1600 MHz
  • R9 380 2 GB
  • FX 8320 3.5GHz
  • Windows 8.1
 
Ekran kartı sürücüsünü güvenli mod da DDU ile eski sürücüyü silip yeni ve en güncel olanını yükleyin, dikkat edin internetiniz kapalı olsun siz yeni sürücüyü kurar iken Windows arka da eski tarihten kalma bir sürücüyü yükler ve sizde sürücüyü yükleyince üst üste sürücü kurmuş olursunuz.

Eğer hala devam ediyor ise kart donanım arızası problemli olabilir.
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: ffffe000b5816880, 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
GetUlongPtrFromAddress: unable to read from fffff80296d6b308

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:  9600.19538.amd64fre.winblue_ltsb_escrow.191014-1700

SYSTEM_MANUFACTURER:  To be filled by O.E.M.

SYSTEM_PRODUCT_NAME:  To be filled by O.E.M.

SYSTEM_SKU:  SKU

SYSTEM_VERSION:  To be filled by O.E.M.

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  2701

BIOS_DATE:  03/24/2016

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  M5A97 LE R2.0

BASEBOARD_VERSION:  Rev 1.xx

DUMP_TYPE:  2

BUGCHECK_P1: ffffe000b5816880

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD:  ffffe000b5816880

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CPU_COUNT: 8

CPU_MHZ: db8

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 2

CPU_STEPPING: 0

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xEA

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  01-21-2020 23:47:28.0524

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff80070ceea7d to fffff80296b5c4a0

STACK_TEXT:
ffffd000`f5884f78 fffff800`70ceea7d : 00000000`000000ea ffffe000`b5816880 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffd000`f5884f80 fffff800`70ce80fe : ffffd000`f5885078 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x4d
ffffd000`f5884ff0 fffff800`71322be0 : 00000000`00000000 ffffe000`b4e0c000 ffffd000`f5885181 00000000`00000064 : dxgkrnl!TdrTimedOperationDelay+0x7f42
ffffd000`f5885050 00000000`00000000 : ffffe000`b4e0c000 ffffd000`f5885181 00000000`00000064 00000000`00002710 : atikmdag+0x4dbe0


STACK_COMMAND:  .thread 0xffffe000b5816880 ; kb

THREAD_SHA1_HASH_MOD_FUNC:  260988b723f057138fe45b239c381c934e8a7f90

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  1f8bc9554cdcfca0949a06ad9979b6bf1958a00a

THREAD_SHA1_HASH_MOD:  b9a6b0a1888ce93becee46671d601e0839dd0b94

FOLLOWUP_IP:
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+4d
fffff800`70ceea7d cc              int     3

FAULT_INSTR_CODE:  40cccccc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+4d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5d51bd9e

IMAGE_VERSION:  6.3.9600.19457

FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys

BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys

PRIMARY_PROBLEM_CLASS:  0xEA_IMAGE_dxgkrnl.sys

TARGET_TIME:  2020-01-21T20:22:31.000Z

OSBUILD:  9600

OSSERVICEPACK:  19538

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 8.1

OSEDITION:  Windows 8.1 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID:  0

OSBUILD_TIMESTAMP:  2019-10-15 05:04:17

BUILDDATESTAMP_STR:  191014-1700

BUILDLAB_STR:  winblue_ltsb_escrow

BUILDOSVER_STR:  6.3.9600.19538.amd64fre.winblue_ltsb_escrow.191014-1700

ANALYSIS_SESSION_ELAPSED_TIME:  d35

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xea_image_dxgkrnl.sys

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

Followup:     MachineOwner
---------
 
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

Yeni konular

Geri
Yukarı