VIDEO_TDR_FAILURE Mavi Ekran hatası

aa12 · 8 Kasım 2020

@Assecreed @Bora Dere @Enes3078 İşimi garantiye alayım.

GTA 5 Oynarken oldu.

Minidump: 110820-22750-01.rar dosyasını indir - download

Assecreed · 8 Kasım 2020

Mavi ekrana yine ekran kartı sebep olmuş. @PanzerTR'in dediği sürücüyü yükleyiniz ve rehberi de uygulayınız.

Kod:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

THREAD_STUCK_IN_DEVICE_DRIVER (ea)
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 (OS builds <= 3790) 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: ffff920f17364080, 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 this error occurred.  If a debugger is attached,
    this error is not always fatal -- see DESCRIPTION below.  On the
    blue screen, this will always equal 1.

Debugging Details:
------------------KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4514

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 5645

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

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  ea

BUGCHECK_P1: ffff920f17364080

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD:  ffff920f17364080

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  RadeonSoftware

STACK_TEXT: 
ffff9008`ead717f8 fffff806`6ca026ad     : 00000000`000000ea ffff920f`17364080 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff9008`ead71800 fffff806`6ca0278e     : ffff9008`ead718e0 fffff806`6c9d6aeb ffff9008`ead718e0 fffff806`72a4396c : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
ffff9008`ead71870 fffff806`7290e5e0     : 00000008`86f996e0 fffff806`72a4396c 00000000`00000000 ffff920f`0ff55000 : dxgkrnl!TdrTimedOperationDelay+0xce
ffff9008`ead718b0 00000008`86f996e0     : fffff806`72a4396c 00000000`00000000 ffff920f`0ff55000 00000000`00989680 : amdkmdag+0x6e5e0
ffff9008`ead718b8 fffff806`72a4396c     : 00000000`00000000 ffff920f`0ff55000 00000000`00989680 00000000`00000001 : 0x00000008`86f996e0
ffff9008`ead718c0 00000000`00000000     : ffff920f`0ff55000 00000000`00989680 00000000`00000001 00000000`00000028 : amdkmdag+0x1a396c


STACK_COMMAND:  .thread 0xffff920f17364080 ; kb

SYMBOL_NAME:  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

IMAGE_VERSION:  10.0.19041.508

FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

Followup:     MachineOwner
---------

aa12 · 8 Kasım 2020

DDU kullanmak yerine, Factory reset yapsam?

PanzerTR · 8 Kasım 2020

aa12 dedi:
DDU kullanmak yerine, Factory reset yapsam?

Ayar sıfırlamak ile kaldırmak aynı şey değil.

aa12 · 8 Kasım 2020

Rehber benim işimi görmedi, sorun çözülemez galİba..
Çok üzdü bu PC beni..

2 sene önce İlk bilgisayarımı topladım.. Yaklaşık 4000 TL'ye, ilk başta i3 7100 - GTX 750 ti kullanıyordum. Sonra elime 500 TL geçti hemen RX 580 aldım. Sonra da İşlemcimi geri istediler babamın arkadaşın dan almıştık intel pentiuma geçmek zorunda kaldım bende tabii. Ondan bu yana 1 Kere düzgün oynıyamadım. Duygu sömürüsü değİl İçimi dökeyim dedim..

PanzerTR · 8 Kasım 2020

aa12 dedi:
Rehber benim işimi görmedi, sorun çözülemez galiba.

DDU ile kaldırıp yeni sürücüleri yükledikten sonra rehberi uyguladınız değil mi?

aa12 · 8 Kasım 2020

PanzerTR dedi:
DDU ile kaldırıp yeni sürücüleri yükledikten sonra rehberi uyguladınız değil mi?

Hayır

.
Rehberi 1 hafta önce uyguladım. Az önce DDU ile temizledim, şimdi yüklüyorum

PossibleTurco · 8 Kasım 2020

Allah hiçbir kuluna VIDEO_TDR_FAILURE hatasını göstermesin. Bu hata genellikle ekran kartı ile alakalı olup, ekran kartının artık hakka yürüdüğü anlamına geliyor olabilir.

claus · 9 Kasım 2020

Dediklerim değişmeyecek maalesef...

aa12 · 10 Kasım 2020

Son hız devam! (iki tane var içinde)

Minidump.rar dosyasını indir - download

Minidump.rar dosyasını indir, download. Dosya.tc .Dosya Upload. Dosya Paylaş. Dosya Yükle

www.dosya.tc

@claus @Assecreed @Bora Dere

Assecreed · 10 Kasım 2020

Bu rehberi uygulayınız.
[Çözüm] VIDEO TDR FAILURE, VIDEO TDR TIMEOUT DETECTED Mavi Ekran - Technopat Sosyal

Kod:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

THREAD_STUCK_IN_DEVICE_DRIVER (ea)
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 (OS builds <= 3790) 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: ffffd581c0716100, 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 this error occurred.  If a debugger is attached,
    this error is not always fatal -- see DESCRIPTION below.  On the
    blue screen, this will always equal 1.

Debugging Details:
------------------

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4905

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 9071

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

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  ea

BUGCHECK_P1: ffffd581c0716100

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD:  ffffd581c0716100

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffffd38a`b2faf788 fffff804`999326ad     : 00000000`000000ea ffffd581`c0716100 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffd38a`b2faf790 fffff804`9993278e     : ffffd38a`b2faf870 fffff804`99906aeb ffffd38a`b2faf870 fffff804`9e6f2ddc : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
ffffd38a`b2faf800 fffff804`9e5bdae0     : 00000003`9bc832ee fffff804`9e6f2ddc 00000000`00000000 ffffd581`be5b4000 : dxgkrnl!TdrTimedOperationDelay+0xce
ffffd38a`b2faf840 00000003`9bc832ee     : fffff804`9e6f2ddc 00000000`00000000 ffffd581`be5b4000 00000000`00989680 : amdkmdag+0x6dae0
ffffd38a`b2faf848 fffff804`9e6f2ddc     : 00000000`00000000 ffffd581`be5b4000 00000000`00989680 00000000`00000001 : 0x00000003`9bc832ee
ffffd38a`b2faf850 00000000`00000000     : ffffd581`be5b4000 00000000`00989680 00000000`00000001 00000000`00000028 : amdkmdag+0x1a2ddc


STACK_COMMAND:  .thread 0xffffd581c0716100 ; kb

SYMBOL_NAME:  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

IMAGE_VERSION:  10.0.19041.508

FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

Followup:     MachineOwner
---------
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

THREAD_STUCK_IN_DEVICE_DRIVER (ea)
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 (OS builds <= 3790) 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: ffff8889461950c0, 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 this error occurred.  If a debugger is attached,
    this error is not always fatal -- see DESCRIPTION below.  On the
    blue screen, this will always equal 1.

Debugging Details:
------------------
KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4031

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 6040

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

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  ea

BUGCHECK_P1: ffff8889461950c0

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD:  ffff8889461950c0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  MSIAfterburner

STACK_TEXT:
ffffcc04`d4d3eb38 fffff800`516026ad     : 00000000`000000ea ffff8889`461950c0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffcc04`d4d3eb40 fffff800`5160278e     : ffffcc04`d4d3ec20 fffff800`515d6aeb ffffcc04`d4d3ec20 fffff800`57bd2ddc : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
ffffcc04`d4d3ebb0 fffff800`57a9dae0     : 00000001`e99ec413 fffff800`57bd2ddc 00000000`00000000 ffff8889`3f4db000 : dxgkrnl!TdrTimedOperationDelay+0xce
ffffcc04`d4d3ebf0 00000001`e99ec413     : fffff800`57bd2ddc 00000000`00000000 ffff8889`3f4db000 00000000`00989680 : amdkmdag+0x6dae0
ffffcc04`d4d3ebf8 fffff800`57bd2ddc     : 00000000`00000000 ffff8889`3f4db000 00000000`00989680 00000000`00000001 : 0x00000001`e99ec413
ffffcc04`d4d3ec00 00000000`00000000     : ffff8889`3f4db000 00000000`00989680 00000000`00000001 00000000`00000028 : amdkmdag+0x1a2ddc


STACK_COMMAND:  .thread 0xffff8889461950c0 ; kb

SYMBOL_NAME:  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

IMAGE_VERSION:  10.0.19041.508

FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

Followup:     MachineOwner
---------

Ekran kartı ile ilgili bir rehber olduğu için belki işe yarar diye attım.

VIDEO_TDR_FAILURE Mavi Ekran hatası

Ayrıntılı düzenleme

aa12

Hectopat

Assecreed

Megapat

aa12

Hectopat

PanzerTR

Megapat

aa12

Hectopat

PanzerTR

Megapat

aa12

Hectopat

PossibleTurco

Kilopat

claus

Zettapat

aa12

Hectopat

Minidump.rar dosyasını indir - download

Assecreed

Megapat

Benzer konular

Yeni konular

Yeni mesajlar

Gizliliğinize önem veriyoruz