GTX 285 sistemde mavi ekran hatası

İşletim sistemi
Windows 10
Katılım
23 Temmuz 2018
Mesajlar
82
Öncelikle merhabalar herkese. Ben bu sistemde GTA 5, CS:GO ve benzer oyunları oynamaktayım. Ancak sadece CS:GO'da vıdeo_tdr_faılure mavi ekran, ya da direkt 1 dk donduktan sonra ekran kartının performansını düşürerek beni zor duruma sokuyor. Sizce PSU'dan mı kaynaklıdır yoksa ekran kartından mı bilemedim. Bilen varsa fikirlerini paylaşsın lütfen. GTA 5'i saatlerce oynuyorum tık yok ancak CS:GO'da 30 dk falan oynayınca gidiyor. Eğer kesin olarak PSU'dan kaynaklı ise PB Fury 650W düşünüyorum. Son sürüm driver ve BIOS kullanmaktayım. Ekran kartı için de geçerli.
Sistemim i3 4150 + HyperX Fury 1600MHz + Gigabyte GTX 285 1GB + Xigmatek 400W 80Plus.
Minidump: Minidump.rar
wdas.gif
 
Son düzenleyen: Moderatör:
Lütfen Dump dosyanızı paylaşınız, söylemekten artık dilimde tüy bitti 😁
 
Lütfen dump dosyanızı paylaşınız, söylemekten artık dilimde tüy bitti 😁

Paylaştım sol altta olması gerek.
 
Görmemişim özür dilerim, inceliyorum şimdi.
Sevgili dostum bütün hataların ekran kartı sürücünden kaynaklı oluşmuş. Ekran kartı sürücünü DDU ile kaldırıp yeniden yüklemen gerekiyor. İşletim sistemin güncel değilse 20H2 sürümüne güncelle. BIOS güncel değilse güncelle. Ama önceliğimiz ekran kartı sürücüsü.
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\hazar\AppData\Local\Temp\7zOC8C353DF\020421-49968-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff802`5e800000 PsLoadedModuleList = 0xfffff802`5f42a4b0
Debug session time: Thu Feb 4 16:19:46.301 2021 (UTC + 3:00)
System Uptime: 0 days 5:12:57.313
Loading Kernel Symbols
...............................................................
................................................................
..............................................
Loading User Symbols
Loading unloaded module list
........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`5ebf5a80 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffad81`932a7790=0000000000000116
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffc00901be3010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8026d8c3400, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc00000b5, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000a, Optional internal context dependent data.

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

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 6327

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on VOSTRO-5468

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 11451

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

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

BUGCHECK_P1: ffffc00901be3010

BUGCHECK_P2: fffff8026d8c3400

BUGCHECK_P3: ffffffffc00000b5

BUGCHECK_P4: a

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffad81`932a7788 fffff802`6b26197e : 00000000`00000116 ffffc009`01be3010 fffff802`6d8c3400 ffffffff`c00000b5 : nt!KeBugCheckEx
ffffad81`932a7790 fffff802`6b26103c : fffff802`6d8c3400 ffffc009`01be3010 ffffad81`932a7899 00000000`00000000 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffffad81`932a77d0 fffff802`6e8b5ba6 : ffffc009`01be3010 00000000`0012540b ffffad81`932a7899 00000000`0012540b : dxgkrnl!TdrIsRecoveryRequired+0x20c
ffffad81`932a7800 fffff802`6e8de2cf : ffffad81`932a7ab0 ffffc008`fe10c000 ffffad81`932a7ab0 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x662
ffffad81`932a7900 fffff802`6e8a65fd : 00000000`00000001 ffffad81`932a7a08 00000000`00000000 ffffc008`f24d8c18 : dxgmms1!VidSchWaitForCompletionEvent+0x29f
ffffad81`932a79c0 fffff802`6e8dff9b : ffffc009`002ba010 ffffc008`fe10c000 ffffc009`002ba010 ffffc008`00000000 : dxgmms1!VidSchiScheduleCommandToRun+0x62d
ffffad81`932a7b90 fffff802`6e9068bf : 00000000`00000080 ffffc008`fe10c000 ffffc008`f0878040 00000000`00000000 : dxgmms1!VidSchiRun_PriorityTable+0x2b
ffffad81`932a7bd0 fffff802`5eb17e25 : ffffc008`fdf220c0 fffff802`6e906820 ffffc008`fe10c000 000fa425`bd9bbfff : dxgmms1!VidSchiWorkerThread+0x9f
ffffad81`932a7c10 fffff802`5ebfd0d8 : ffffd601`883db180 ffffc008`fdf220c0 fffff802`5eb17dd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffad81`932a7c60 00000000`00000000 : ffffad81`932a8000 ffffad81`932a2000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nvlddmkm+153400

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

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

0: kd> lmvm nvlddmkm
Browse full module list
start end module name
fffff802`6d770000 fffff802`6e40d000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
Image name: nvlddmkm.sys
Browse all global symbols functions data
Timestamp: Mon Nov 14 12:42:35 2016 (5829870B)
CheckSum: 00C5E4C4
ImageSize: 00C9D000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:

Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\hazar\AppData\Local\Temp\7zOC8C8C2DF\020421-38156-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff800`53200000 PsLoadedModuleList = 0xfffff800`53e2a4b0
Debug session time: Thu Feb 4 16:30:15.207 2021 (UTC + 3:00)
System Uptime: 0 days 0:09:43.875
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`535f5a80 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffae80`ff4e6790=0000000000000116
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffc70757e72010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80060fd3400, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc00000b5, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000a, Optional internal context dependent data.

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

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 6499

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on VOSTRO-5468

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 24487

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

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

BUGCHECK_P1: ffffc70757e72010

BUGCHECK_P2: fffff80060fd3400

BUGCHECK_P3: ffffffffc00000b5

BUGCHECK_P4: a

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffae80`ff4e6788 fffff800`5e99197e : 00000000`00000116 ffffc707`57e72010 fffff800`60fd3400 ffffffff`c00000b5 : nt!KeBugCheckEx
ffffae80`ff4e6790 fffff800`5e99103c : fffff800`60fd3400 ffffc707`57e72010 ffffae80`ff4e6899 00000000`00000000 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffffae80`ff4e67d0 fffff800`5e585ba6 : ffffc707`57e72010 00000000`00008f88 ffffae80`ff4e6899 00000000`00008f88 : dxgkrnl!TdrIsRecoveryRequired+0x20c
ffffae80`ff4e6800 fffff800`5e5ae2cf : ffffae80`ff4e6ab0 ffffc707`58dce000 ffffae80`ff4e6ab0 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x662
ffffae80`ff4e6900 fffff800`5e5765fd : 00000000`00000001 ffffae80`ff4e6a08 00000000`00000000 ffffc707`58106628 : dxgmms1!VidSchWaitForCompletionEvent+0x29f
ffffae80`ff4e69c0 fffff800`5e5aff9b : ffffc707`4eaae5f0 ffffc707`58dce000 ffffc707`4eaae5f0 ffffc707`00000000 : dxgmms1!VidSchiScheduleCommandToRun+0x62d
ffffae80`ff4e6b90 fffff800`5e5d68bf : 00000000`00000080 ffffc707`58dce000 ffffc707`4149f040 00000000`00000000 : dxgmms1!VidSchiRun_PriorityTable+0x2b
ffffae80`ff4e6bd0 fffff800`53517e25 : ffffc707`58ad1080 fffff800`5e5d6820 ffffc707`58dce000 000fa425`bd9bbfff : dxgmms1!VidSchiWorkerThread+0x9f
ffffae80`ff4e6c10 fffff800`535fd0d8 : fffff800`50343180 ffffc707`58ad1080 fffff800`53517dd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffae80`ff4e6c60 00000000`00000000 : ffffae80`ff4e7000 ffffae80`ff4e1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nvlddmkm+153400

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

Followup: MachineOwner
Verdiğim linkten sürücüyü yeniden kur.
 
Son düzenleme:
Görmemişim özür dilerim, inceliyorum şimdi.
Sevgili dostum bütün hataların ekran kartı sürücünden kaynaklı oluşmuş. Ekran kartı sürücünü DDU ile kaldırıp yeniden yüklemen gerekiyor. İşletim sistemin güncel değilse 20H2 sürümüne güncelle. BIOS güncel değilse güncelle. Ama önceliğimiz ekran kartı sürücüsü.
Microsoft (r) Windows debugger version 10.0.20153.1000 AMD64.
Copyright (C) Microsoft corporation. All rights reserved.

Loading dump file [C:\Users\hazar\AppData\Local\Temp\7zOC8C353DF\020421-49968-01.dmp]
Mini kernel dump file: Only registers and stack trace are available.

************* Path validation summary **************
Response Ti'me (ms) location.
Deferred srv*
Symbol Search path is: Srv*
Executable Search path is:
Windows 10 kernel version 19041 MP (4 procs) Free X64.
PROduct: Winnt, Suite: Terminalserver singleuserts.
Edition Build lab: 19041.1.AMD64fre. Vb_release. 191206-1406
Machine name:
Kernel base = 0xfffff802`5e800000 psloadedmodulelist = 0xfffff802`5f42a4b0
Debug session Ti'me: Thu feb 4 16:19:46.301 2021 (utc + 3:00)
System uptime: 0 days 5:12:57.313
Loading kernel symbols.



Loading user symbols.
Loading unloaded module list.

For analysis of this file, run! Analyze -v
Nt! Kebugcheckex:
Fffff802'5ebf5a80 48894C2408 mov qword ptr [rsp+8],rcx SS: Ffffad81'932A7790=0000000000000116
0: Kd>!analyze -v
*******************************************************************************
* *
* Bugcheck analysis *
* *
*******************************************************************************

Vıdeo_tdr_faılure (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: FffFC00901Be3010, optional pointer to internal tdr Recovery context (tdr_recovery_context).
Arg2: FffFF8026D8C3400, the pointer into responsible device driver module (e. G. Owner tag).
Arg3: FffffffFC00000B5, optional error code (ntstatus) of the last failed operation.
Arg4: 000000000000000A, optional internal context dependent data.

Debugging details:
------------------

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0N2.
*** Warnıng: Unable to verify timestamp for nvlddmkm.sys
*** Warnıng: Unable to verify checksum for win32k.sys

Key_values_strıng: 1

Key: Analysis. CPU. Msec.
Value: 6327.

Key: Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007E on Vostro-5468

Key: Analysis. Debugdata.
Value: Createobject.

Key: Analysis. Debugmodel.
Value: Createobject.

Key: Analysis. Elapsed. Msec.
Value: 11451.

Key: Analysis. Memory. Commitpeak. MB.
Value: 90.

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

Addıtıonal_xml: 1

Os_buıld_layers: 1

Bugcheck_code: 116.

Bugcheck_p1: FFFFC00901BE3010.

Bugcheck_p2: FFFFF8026D8C3400.

Bugcheck_p3: FffffffFC00000B5.

Bugcheck_p4: A

Blackboxbsd: 1 (!blackboxbsd)

Blackboxntfs: 1 (!blackboxntfs)

Blackboxpnp: 1 (!blackboxpnp)

Blackboxwınlogon: 1

Customer_crash_count: 1

Process_name: System.

Stack_text:
Ffffad81'932A7788 fffff802'6B26197E: 00000000'00000116 ffffc009'01be3010 fffff802'6D8C3400 ffffffff'C00000B5: Nt! Kebugcheckex.
Ffffad81'932A7790 fffff802'6B26103C: Fffff802'6D8C3400 ffffc009'01be3010 ffffad81'932A7899 00000000'00000000: Dxgkrnl! Tdrbugcheckontimeout+0xfe
Ffffad81'932A77D0 fffff802'6E8b5ba6: Ffffc009'01be3010 00000000'0012540B ffffad81'932A7899 00000000'0012540B: Dxgkrnl! Tdrısrecoveryrequired+0x20C
Ffffad81'932A7800 fffff802'6E8de2CF: Ffffad81'932a7ab0 ffffc008'FE10C000 ffffad81'932a7ab0 00000000'00000002: Dxgmms1! Vidschireporthwhang+0x662
Ffffad81'932A7900 fffff802'6E8A65fd: 00000000'00000001 ffffad81'932a7a08 00000000'00000000 ffffc008'F24D8C18: Dxgmms1! Vidschwaitforcompletionevent+0x29F
Ffffad81'932A79C0 fffff802'6E8dff9b: Ffffc009'002ba010 ffffc008'FE10C000 ffffc009'002ba010 ffffc008'00000000: Dxgmms1! Vidschischedulecommandtorun+0x62D
Ffffad81'932a7B90 fffff802'6E9068BF: 00000000'00000080 ffffc008'FE10C000 ffffc008'F0878040 00000000'00000000: Dxgmms1! Vidschirun_prioritytable+0x2B
Ffffad81'932a7bd0 fffff802'5eb17e25: Ffffc008'fdf220C0 fffff802'6E906820 ffffc008'FE10C000 000fa425'BD9bbfff: Dxgmms1! Vidschiworkerthread+0x9F
Ffffad81'932a7C10 fffff802'5ebfd0D8: Ffffd601'883dB180 ffffc008'fdf220C0 fffff802'5eb17dd0 00000000'00000000: Nt! Pspsystemthreadstartup+0x55
Ffffad81'932a7C60 00000000'00000000: Ffffad81'932a8000 ffffad81'932a2000 00000000'00000000 00000000'00000000: Nt! Kistartsystemthread+0x28

Symbol_name: Nvlddmkm+153400

Module_name: Nvlddmkm.

Image_name: nvlddmkm.sys

Stack_command: Thread. Cxr; KB.

Faılure_bucket_ıd: 0x116_IMAGE_nvlddmkm.sys

Os_versıon: 10.0.19041.1

Buıldlab_str: Vb_release.

Osplatform_type: X64.

Osname: Windows 10.

Faılure_ıd_hash: {C89BFE8C-ED39-F658-EF27-F2898997fdbd}

Followup: Machineowner.
---------

0: Kd> lmvm nvlddmkm.
Browse Full module list.
Start end module name.
Fffff802'6D770000 fffff802'6E40D000 nvlddmkm t (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
Image name: nvlddmkm.sys
Browse all global symbols functions data.
Timestamp: Mon nov 14 12:42:35 2016 (5829870B)
Checksum: 00C5E4C4.
Imagesize: 00C9D000.
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:

Microsoft (r) Windows debugger version 10.0.20153.1000 AMD64.
Copyright (C) Microsoft corporation. All rights reserved.

Loading dump file [C:\Users\hazar\AppData\Local\Temp\7zOC8C8C2DF\020421-38156-01.dmp]
Mini kernel dump file: Only registers and stack trace are available.

************* Path validation summary **************
Response Ti'me (ms) location.
Deferred srv*
Symbol Search path is: Srv*
Executable Search path is:
Windows 10 kernel version 19041 MP (4 procs) Free X64.
PROduct: Winnt, Suite: Terminalserver singleuserts.
Edition Build lab: 19041.1.AMD64fre. Vb_release. 191206-1406
Machine name:
Kernel base = 0xfffff800`53200000 psloadedmodulelist = 0xfffff800`53e2a4b0
Debug session Ti'me: Thu feb 4 16:30:15.207 2021 (utc + 3:00)
System uptime: 0 days 0:09:43.875
Loading kernel symbols.



Loading user symbols.
Loading unloaded module list.

For analysis of this file, run! Analyze -v
Nt! Kebugcheckex:
Fffff800'535F5a80 48894C2408 mov qword ptr [rsp+8],rcx SS:0018:ffffae80'FF4e6790=0000000000000116
0: Kd>!analyze -v
*******************************************************************************
* *
* Bugcheck analysis *
* *
*******************************************************************************

Vıdeo_tdr_faılure (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: FffFC70757E72010, optional pointer to internal tdr Recovery context (tdr_recovery_context).
Arg2: FffFF80060Fd3400, the pointer into responsible device driver module (e. G. Owner tag).
Arg3: FffffffFC00000B5, optional error code (ntstatus) of the last failed operation.
Arg4: 000000000000000A, optional internal context dependent data.

Debugging details:
------------------

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0N2.
*** Warnıng: Unable to verify timestamp for nvlddmkm.sys
*** Warnıng: Unable to verify checksum for win32k.sys

Key_values_strıng: 1

Key: Analysis. CPU. Msec.
Value: 6499.

Key: Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007E on Vostro-5468

Key: Analysis. Debugdata.
Value: Createobject.

Key: Analysis. Debugmodel.
Value: Createobject.

Key: Analysis. Elapsed. Msec.
Value: 24487.

Key: Analysis. Memory. Commitpeak. MB.
Value: 90.

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

Addıtıonal_xml: 1

Os_buıld_layers: 1

Bugcheck_code: 116.

Bugcheck_p1: FFFFC70757E72010.

Bugcheck_p2: FFFFF80060FD3400.

Bugcheck_p3: FffffffFC00000B5.

Bugcheck_p4: A

Blackboxbsd: 1 (!blackboxbsd)

Blackboxntfs: 1 (!blackboxntfs)

Blackboxpnp: 1 (!blackboxpnp)

Blackboxwınlogon: 1

Customer_crash_count: 1

Process_name: System.

Stack_text:
Ffffae80'FF4e6788 fffff800'5E99197E: 00000000'00000116 ffffc707'57e72010 fffff800'60fd3400 ffffffff'C00000B5: Nt! Kebugcheckex.
Ffffae80'FF4e6790 fffff800'5E99103C: Fffff800'60fd3400 ffffc707'57e72010 ffffae80'FF4e6899 00000000'00000000: Dxgkrnl! Tdrbugcheckontimeout+0xfe
Ffffae80'FF4e67D0 fffff800'5E585BA6: Ffffc707'57e72010 00000000'00008F88 ffffae80'FF4e6899 00000000'00008F88: Dxgkrnl! Tdrısrecoveryrequired+0x20C
Ffffae80'FF4e6800 fffff800'5E5ae2CF: Ffffae80'FF4e6ab0 ffffc707'58dce000 ffffae80'FF4e6ab0 00000000'00000002: Dxgmms1! Vidschireporthwhang+0x662
Ffffae80'FF4e6900 fffff800'5E5765FD: 00000000'00000001 ffffae80'FF4e6a08 00000000'00000000 ffffc707'58106628: Dxgmms1! Vidschwaitforcompletionevent+0x29F
Ffffae80'FF4e69C0 fffff800'5E5aff9b: Ffffc707'4eaae5F0 ffffc707'58dce000 ffffc707'4eaae5F0 ffffc707'00000000: Dxgmms1! Vidschischedulecommandtorun+0x62D
Ffffae80'FF4e6B90 fffff800'5E5D68BF: 00000000'00000080 ffffc707'58dce000 ffffc707'4149F040 00000000'00000000: Dxgmms1! Vidschirun_prioritytable+0x2B
Ffffae80'FF4e6bd0 fffff800'53517E25: Ffffc707'58ad1080 fffff800'5E5D6820 ffffc707'58dce000 000fa425'BD9bbfff: Dxgmms1! Vidschiworkerthread+0x9F
Ffffae80'FF4e6C10 fffff800'535fd0D8: Fffff800'50343180 ffffc707'58ad1080 fffff800'53517DD0 00000000'00000000: Nt! Pspsystemthreadstartup+0x55
Ffffae80'FF4e6C60 00000000'00000000: Ffffae80'FF4e7000 ffffae80'FF4e1000 00000000'00000000 00000000'00000000: Nt! Kistartsystemthread+0x28

Symbol_name: Nvlddmkm+153400

Module_name: Nvlddmkm.

Image_name: nvlddmkm.sys

Stack_command: Thread. Cxr; KB.

Faılure_bucket_ıd: 0x116_IMAGE_nvlddmkm.sys

Os_versıon: 10.0.19041.1

Buıldlab_str: Vb_release.

Osplatform_type: X64.

Osname: Windows 10.

Faılure_ıd_hash: {C89BFE8C-ED39-F658-EF27-F2898997fdbd}

Followup: Machineowner.
Verdiğim linkten sürücüyü yeniden kur.

Tamamdır çok teşekkürler dediklerinizi yapıp durumu tekrar bildireceğim.
 
Tamamdır, geri dönüş sağlarsınız bana.
@Burak Aziz Demirci

Windows Update kafasına göre sürücü güncelliyor 3 defa denedim pes ettim. Oyundayım problemsiz test ediyorum tak ekran gidip geliyor bir bakmışım sürücü güncellenmiş artık yarın bakarım. Sonucu tekrar yazarım buraya...
Tamamdır, geri dönüş sağlarsınız bana.
@Burak Aziz Demirci durum nedir halihazırda?

Merhabalar, bugün denedim dediklerinizi yaptım ancak mavi ekran yerine bu seferde oyun bahsettiğim gibi donup ekran kartının saat hızını düşürüyor. Var mıdır yapılabilecek başka bir şey?
 
Son düzenleme:
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

Geri
Yukarı