RX 570 mavi ekran hatası

Dostum dosyanı inceledim. THREAD STUCK IN DEVICE M hatası almışsın. dxgkrnl.sys adlı dosya hata vermiş. Bu DirectX Grafik Çekirdeğinde hata oluşmuş demek. Ekran kartı sürücün güncel mi?
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\hazar\Downloads\020421-12578-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 (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff802`7b600000 PsLoadedModuleList = 0xfffff802`7c22a2f0
Debug session time: Thu Feb 4 07:00:33.832 2021 (UTC + 3:00)
System Uptime: 0 days 2:26:49.505
Loading Kernel Symbols
...............................................................
................................................................
....................................................
Loading User Symbols
Loading unloaded module list
..............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`7b9f5780 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8388`b2ec3740=00000000000000ea
8: 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: ffffe1073eed20c0, 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 checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 7983

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 68542

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

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

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD: ffffe1073eed20c0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff8388`b2ec3738 fffff802`8686289d : 00000000`000000ea ffffe107`3eed20c0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff8388`b2ec3740 fffff802`8686297e : ffff8388`b2ec3820 fffff802`8683727b ffff8388`b2ec3820 fffff802`8d6ca764 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
ffff8388`b2ec37b0 fffff802`8d590c00 : 00000014`83020da2 fffff802`8d6ca764 00000000`00000000 ffffe107`3e59c000 : dxgkrnl!TdrTimedOperationDelay+0xce
ffff8388`b2ec37f0 00000014`83020da2 : fffff802`8d6ca764 00000000`00000000 ffffe107`3e59c000 00000000`00989680 : amdkmdag+0x70c00
ffff8388`b2ec37f8 fffff802`8d6ca764 : 00000000`00000000 ffffe107`3e59c000 00000000`00989680 00000000`00000001 : 0x00000014`83020da2
ffff8388`b2ec3800 00000000`00000000 : ffffe107`3e59c000 00000000`00989680 00000000`00000001 00000000`00000028 : amdkmdag+0x1aa764


STACK_COMMAND: .thread 0xffffe1073eed20c0 ; kb

SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

IMAGE_VERSION: 10.0.19041.746

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

8: kd> lmvm dxgkrnl
Browse full module list
start end module name
fffff802`86820000 fffff802`86bc3000 dxgkrnl # (pdb symbols) C:\ProgramData\Dbg\sym\dxgkrnl.pdb\36668E7AF9553FF10B4ED8E50E156C841\dxgkrnl.pdb
Loaded symbol image file: dxgkrnl.sys
Mapped memory image file: C:\ProgramData\Dbg\sym\dxgkrnl.sys\670B3B6A3a3000\dxgkrnl.sys
Image path: \SystemRoot\System32\drivers\dxgkrnl.sys
Image name: dxgkrnl.sys
Browse all global symbols functions data
Image was built with /Brepro flag.
Timestamp: 670B3B6A (This is a reproducible build file hash, not a timestamp)
CheckSum: 003A21BD
ImageSize: 003A3000
File version: 10.0.19041.746
Product version: 10.0.19041.746
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
Information from resource tables:
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: dxgkrnl.sys
OriginalFilename: dxgkrnl.sys
ProductVersion: 10.0.19041.746
FileVersion: 10.0.19041.746 (WinBuild.160101.0800)
FileDescription: DirectX Graphics Kernel
LegalCopyright: © Microsoft Corporation. All rights reserved.
 
Cool Whine olması zaten garantilik direkt.

Ekstradan ekran kartı sürücün güncel değil ise güncellemen gerekiyor.

Eğer güncellediğin halde mavi ekran alıyorsan garantiye gönder. Ek olarak hem Cool Whine var.

Yani garantiye gitmesi gerekiyor gibi.
 
Uyarı! Bu konu 5 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.

Technopat Haberler

Yeni konular

Geri
Yukarı