Çözüldü THREAD_STUCK_IN_DEVICE_DRIVER_M mavi Ekran Hatası

Berrkay dedi:

DDU rehberini uygula buradan.

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

AMD'nin sitesinden ekran kartın için son çıkan Recommended WHQL sürücüyü kur.

AMD Drivers and Support for Radeon, Radeon Pro, FirePro, APU, CPU, Ryzen, desktops, laptops

www.amd.com

Geçebiliyorsan Windows 8, 8.1 veya 10'a geç. 10 desteklemiyorsa 8 veya 8.1'i dene.

Kod:Panoya kopyala

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: fffffa8007a89b50, 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 amdkmdag.sys
fffff80002e020e8: Unable to get Flags value from nt!KdVersionBlock
GetUlongPtrFromAddress: unable to read from fffff80002ebd300

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2749

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 8688

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 64

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: win7sp1_ldr_escrow

    Key  : WER.OS.Timestamp
    Value: 2020-04-16T14:36:00Z

    Key  : WER.OS.Version
    Value: 7.1.7601.24553


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  ea

BUGCHECK_P1: fffffa8007a89b50

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD:  fffffa8007a89b50

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  wmplayer.exe

STACK_TEXT:
fffff880`09232718 fffff880`03c6ff63     : 00000000`000000ea fffffa80`07a89b50 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`09232720 fffff880`03c70112     : fffff880`09232800 fffff880`03c7001f fffff880`09232800 fffff880`0f1f1764 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x37
fffff880`09232790 fffff880`0f0b7c00     : 00000001`8a1f99a7 fffff880`0f1f1764 00000000`00000000 fffffa80`0500b000 : dxgkrnl!TdrTimedOperationDelay+0xbe
fffff880`092327d0 00000001`8a1f99a7     : fffff880`0f1f1764 00000000`00000000 fffffa80`0500b000 00000000`002540b4 : amdkmdag+0x70c00
fffff880`092327d8 fffff880`0f1f1764     : 00000000`00000000 fffffa80`0500b000 00000000`002540b4 00000000`00000001 : 0x00000001`8a1f99a7
fffff880`092327e0 00000000`00000000     : fffffa80`0500b000 00000000`002540b4 00000000`00000001 00000000`00000028 : amdkmdag+0x1aa764


STACK_COMMAND:  .thread 0xfffffa8007a89b50 ; kb

SYMBOL_NAME:  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

IMAGE_VERSION:  6.1.7601.24546

FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys

OS_VERSION:  7.1.7601.24553

BUILDLAB_STR:  win7sp1_ldr_escrow

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 7

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

Followup:     MachineOwner
--------

Genişletmek için tıkla...

Ajan_47 dedi:

Öncelikle teşekkürler hocam. Nedir bu AMD'den çektiğimiz ya. Sosyale açtığım tüm mavi ekran hatalarında bu çözümü öneriyorlar. Windows 8.1, 10 farketmiyor. Bir süre sonra o hatayı alıyorum. Acaba donanımsal bir problem olabilir mi?

Genişletmek için tıkla...