Şu
konuyu bir inceleyin hocam.
Ben şahsen PSU'dan şüpheleniyorum ama belirttiğim üzere ilgili konuyu bir araştırın mavi ekran hatasını hangi parça yaşatıyor kesin bulalım ona göre çözüm yöntemi araştırırız.
İlgili konu da yazdığı gibi yaptım fakat çıkan sonuçtan hiç bir şey anlamadım desem yeridir..
Bir de siz bakar mısınız hocam?
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : false
AllowNugetExeUpdate : false
AllowNugetMSCredentialProviderInstall : false
AllowParallelInitializationOfLocalRepositories : true
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.031 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 36
Microsoft (R) Windows Debugger Version 10.0.25877.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\CwP\Desktop\093023-5843-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22621 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22621.1928.amd64fre.ni_release_svc_prod3.230622-0951
Kernel base = 0xfffff801`6c800000 PsLoadedModuleList = 0xfffff801`6d4130a0
Debug session time: Sat Sep 30 00:18:07.604 2023 (UTC + 3:00)
System Uptime: 0 days 3:45:46.243
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
...............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`6cc12670 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffa804`0638e820=0000000000000116
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffff858f7734d010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8018daf5b70, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc0000001, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000003, Optional internal context dependent data.
Debugging Details:
------------------
Unable to load image \SystemRoot\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_d70f42719281945b\igdkmdnd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmdnd64.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2734
Key : Analysis.Elapsed.mSec
Value: 12627
Key : Analysis.IO.Other.Mb
Value: 31
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 38
Key : Analysis.Init.CPU.mSec
Value: 296
Key : Analysis.Init.Elapsed.mSec
Value: 53630
Key : Analysis.Memory.CommitPeak.Mb
Value: 113
Key : Bugcheck.Code.LegacyAPI
Value: 0x116
Key : Failure.Bucket
Value: 0x116_IMAGE_igdkmdnd64.sys
Key : Failure.Hash
Value: {7eb0cc99-c85b-4092-6430-8f1db059b7c1}
Key : WER.OS.Branch
Value: ni_release_svc_prod3
Key : WER.OS.Version
Value: 10.0.22621.1928
BUGCHECK_CODE: 116
BUGCHECK_P1: ffff858f7734d010
BUGCHECK_P2: fffff8018daf5b70
BUGCHECK_P3: ffffffffc0000001
BUGCHECK_P4: 3
FILE_IN_CAB: 093023-5843-01.dmp
VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffff858f7734d010
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.
PROCESS_OBJECT: 0000000000000003
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffa804`0638e818 fffff801`7b2d1a0e : 00000000`00000116 ffff858f`7734d010 fffff801`8daf5b70 ffffffff`c0000001 : nt!KeBugCheckEx
ffffa804`0638e820 fffff801`7b2781da : fffff801`8daf5b70 ffff858f`617de000 ffff858f`617de0f8 00000000`00000000 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffffa804`0638e860 fffff801`7b279216 : ffff858f`00000101 00000000`00000080 ffff858f`617de000 00000000`00000080 : dxgkrnl!DXGADAPTER::PrepareToReset+0x222
ffffa804`0638e8e0 fffff801`7b2d1165 : 00000000`00000100 ffff858f`722cc040 00000000`00000000 ffff858f`75fd6570 : dxgkrnl!DXGADAPTER::Reset+0x346
ffffa804`0638e990 fffff801`7b2d12c2 : 00000000`00000000 fffff801`6d413c00 00000000`00000200 fffff801`6d549ac0 : dxgkrnl!TdrResetFromTimeout+0x15
ffffa804`0638e9c0 fffff801`6cb052e5 : ffff858f`722cc040 ffff858f`5c337bb0 ffff858f`00000000 ffff858f`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x22
ffffa804`0638ea00 fffff801`6cb00687 : ffff858f`722cc040 00000000`00000510 ffff858f`722cc040 fffff801`6cb05190 : nt!ExpWorkerThread+0x155
ffffa804`0638ebf0 fffff801`6cc175d4 : ffffd501`a0731180 ffff858f`722cc040 fffff801`6cb00630 224e82a5`8b572c37 : nt!PspSystemThreadStartup+0x57
ffffa804`0638ec40 00000000`00000000 : ffffa804`0638f000 ffffa804`06389000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34
SYMBOL_NAME: igdkmdnd64+15b70
MODULE_NAME: igdkmdnd64
IMAGE_NAME: igdkmdnd64.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x116_IMAGE_igdkmdnd64.sys
OS_VERSION: 10.0.22621.1928
BUILDLAB_STR: ni_release_svc_prod3
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {7eb0cc99-c85b-4092-6430-8f1db059b7c1}
Followup: MachineOwner
---------Hastamızın durumu ne?
