Miracast Cihaza Bağlanırken Mavi Ekran

Selamlar, GPU sürücünüzü DDU ile kaldırıp kurmayı deneyip sonucu bildirirseniz sevinirim.


[CODE title="Dökümler"]*******************************************************************************
* *
* 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: ffff8603e2e0d080, 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:
------------------

*** WARNING: Unable to verify timestamp for amdkmdag.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 5046

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 9153

Key : Analysis.Init.CPU.mSec
Value: 1030

Key : Analysis.Init.Elapsed.mSec
Value: 12059

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


FILE_IN_CAB: 021222-9546-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: ea

BUGCHECK_P1: ffff8603e2e0d080

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD: ffff8603e2e0d080

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff402`2f628fe8 fffff805`708645ad : 00000000`000000ea ffff8603`e2e0d080 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff402`2f628ff0 fffff805`7086468e : fffff402`2f6290d0 fffff805`70836cfb fffff402`2f6290d0 fffff805`7cadc734 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
fffff402`2f629060 fffff805`7c9ace20 : 00000000`95150cb2 fffff805`7cadc734 00000000`00000000 ffff8603`dc636000 : dxgkrnl!TdrTimedOperationDelay+0xce
fffff402`2f6290a0 00000000`95150cb2 : fffff805`7cadc734 00000000`00000000 ffff8603`dc636000 00000000`00989680 : amdkmdag+0x6ce20
fffff402`2f6290a8 fffff805`7cadc734 : 00000000`00000000 ffff8603`dc636000 00000000`00989680 00000000`00000001 : 0x95150cb2
fffff402`2f6290b0 00000000`00000000 : ffff8603`dc636000 00000000`00989680 00000000`00000001 00000000`00000028 : amdkmdag+0x19c734


STACK_COMMAND: .thread 0xffff8603e2e0d080 ; kb

SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

IMAGE_VERSION: 10.0.19041.1466

FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

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

PnpActivityId : {00000000-0000-0000-0000-000000000000}
PnpActivityTime : 132891538016403787
PnpEventInformation: 3
PnpEventInProgress : 0
PnpProblemCode : 24
PnpVetoType : 0
DeviceId : DISPLAY\Default_Monitor\3&2dac7332&0&UID256
VetoString : [/CODE]