1) BIOS sürümünüzü
3405 sürümüne yükseltin.
2) Ekran kartı sürücünüzü DDU ile kaldırıp aşağıdan indireceğiniz sürücüyü kurun. DDU kullanım rehberi de aşağıda yer alıyor.
Sürücü:
Grafik Sürücüsü - GeForce Game Ready Driver | NVIDIA
Rehber:
DDU ile Sürücü Kaldırma Rehberi
3) Aşağıdaki sürücüyü indirip kurun. (Bluetooth)
4) Aşağıdaki rehberi uygulayıp sonucun ekran alıntısını paylaşın.
SFC /scannow nedir ve ne işe yarar?
www.technopat.net
[CODE title="Dökümler"]*******************************************************************************
* *
* 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: ffff95095d93c640, 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: 19499
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-5QPUIS0
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 108097
Key : Analysis.Memory.CommitPeak.Mb
Value: 84
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: ffff95095d93c640
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FAULTING_THREAD: ffff95095d93c640
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: AMDRSServ.exe
STACK_TEXT:
ffff920e`20fd5f58 fffff805`7ad0324d : 00000000`000000ea ffff9509`5d93c640 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff920e`20fd5f60 fffff805`7ad0332e : ffff920e`20fd6040 fffff805`7acd73bb ffff920e`20fd6040 fffff805`828dab74 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
ffff920e`20fd5fd0 fffff805`827a0d90 : 000002aa`402dee75 fffff805`828dab74 00000000`00000000 ffff9509`532a9000 : dxgkrnl!TdrTimedOperationDelay+0xce
ffff920e`20fd6010 000002aa`402dee75 : fffff805`828dab74 00000000`00000000 ffff9509`532a9000 00000000`00989680 : amdkmdag+0x70d90
ffff920e`20fd6018 fffff805`828dab74 : 00000000`00000000 ffff9509`532a9000 00000000`00989680 00000000`00000001 : 0x000002aa`402dee75
ffff920e`20fd6020 00000000`00000000 : ffff9509`532a9000 00000000`00989680 00000000`00000001 00000000`00000028 : amdkmdag+0x1aab74
STACK_COMMAND: .thread 0xffff95095d93c640 ; kb
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
IMAGE_VERSION: 10.0.19041.804
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
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CRITICAL_PROCESS_DIED (ef)
A critical system process died
Arguments:
Arg1: ffff8686d5685040, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
ETW minidump data unavailable
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 8530
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-5QPUIS0
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 29054
Key : Analysis.Memory.CommitPeak.Mb
Value: 75
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: ef
BUGCHECK_P1: ffff8686d5685040
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
PROCESS_NAME: smss.exe
CRITICAL_PROCESS: smss.exe
EXCEPTION_RECORD: ffff8686d5685780 -- (.exr 0xffff8686d5685780)
ExceptionAddress: 0000000000000000
ExceptionCode: 00000000
ExceptionFlags: 00000000
NumberParameters: 0
ERROR_CODE: (NTSTATUS) 0xd51fc340 - <Unable to get error code text>
CUSTOMER_CRASH_COUNT: 1
EXCEPTION_STR: 0x0
TRAP_FRAME: ffff800000000000 -- (.trap 0xffff800000000000)
Unable to read trap frame at ffff8000`00000000
STACK_TEXT:
ffff9988`91859d38 fffff806`05f068e2 : 00000000`000000ef ffff8686`d5685040 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff9988`91859d40 fffff806`05e49b39 : 00000000`00000001 fffff806`0595971d 00000000`00000002 fffff806`05958d37 : nt!PspCatchCriticalBreak+0x10e
ffff9988`91859de0 fffff806`05d09724 : ffff8686`00000000 00000000`00000000 ffff8686`d5685040 ffff8686`d5685478 : nt!PspTerminateAllThreads+0x140b4d
ffff9988`91859e50 fffff806`05d09a4c : ffff8686`d5685040 00000000`00000001 ffffffff`ffffffff 00000000`00000000 : nt!PspTerminateProcess+0xe0
ffff9988`91859e90 fffff806`05a071b8 : ffff8686`d5685040 ffff8686`d51fc340 ffff9988`91859f80 fffff806`05d1da92 : nt!NtTerminateProcess+0x9c
ffff9988`91859f00 fffff806`059f95e0 : fffff806`05a91307 ffff9988`9185aa18 ffff9988`9185aa18 ffffffff`ffffffff : nt!KiSystemServiceCopyEnd+0x28
ffff9988`9185a098 fffff806`05a91307 : ffff9988`9185aa18 ffff9988`9185aa18 ffffffff`ffffffff 00007ff8`beabe304 : nt!KiServiceLinkage
ffff9988`9185a0a0 fffff806`05a078ac : ffff8686`d5685780 fffff806`0580ecc6 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x166907
ffff9988`9185a8e0 fffff806`05a03a43 : ffff8686`00000000 00000000`00000001 00000000`00000800 ffff9988`9185ab40 : nt!KiExceptionDispatch+0x12c
ffff9988`9185aac0 00007ff8`be992344 : 00000000`00000000 00007ff8`be99444f 00007ff8`be9700e8 00007ff8`be9bbeb3 : nt!KiPageFault+0x443
00000060`1b2c10b0 00000000`00000000 : 00007ff8`be99444f 00007ff8`be9700e8 00007ff8`be9bbeb3 00000000`00000000 : 0x00007ff8`be992344
SYMBOL_NAME: nt!PspCatchCriticalBreak+10e
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.685
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 10e
FAILURE_BUCKET_ID: 0xEF_smss.exe_BUGCHECK_CRITICAL_PROCESS_d51fc340_nt!PspCatchCriticalBreak
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {895eff0e-7b0e-d32d-d288-95e75e082b45}
Followup: MachineOwner
---------[/CODE]
Sorun çözüldü mü? Yeni fark ettim çözüme kavuşmamış konular arasında.
drive.google.com
