Çözüldü VIDEO_TDR_FAILURE mavi ekran hatası

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.

safak123

Decapat
Katılım
14 Ocak 2023
Mesajlar
144
Çözümler
5
Daha fazla  
Cinsiyet
Erkek
Özellikle ekran kartım yük altındayken mavi ekran hatası alıyorum. Minidump analizinde sorunun ekran kartı sürücüsünden kaynaklandığı çıkıyor, ama sürücülerim güncel.

"VIDEO_TDR_FAILURE (0x116) hatası, ekran kartı sürücüsünün zamanında yanıt vermemesi veya çökmesi sonucu Windows'un grafik sürücüsünü sıfırlamaya çalışması ama başarısız olması durumunda oluşur."

 
Çözüm
Collavino dedi:
Tamamdır hocam. Sorun ekran kartının kendisinde gibi görünüyor. Haber verirsiniz. İyi akşamlar.
Genişletmek için tıkla...

Intel Chipset Driver, Intel Serial IO Software ve Management Engine Interface güncellemelerini yaptıktan sonra mavi ekran hataları ve WHEA hataları tamamen kesildi. Sorun bu üçünden biriyle ilgiliymiş. Benzer sorunları yaşayanlara yardımcı olur umarım.

Tarihe göre sırala Puana göre sırala
Minidump dosyasını paylaşır mısınız? Daha iyi yönlendirmeler yapabiliriz.

Minidump Dosyalarını Paylaşın

23.06.2025 tarihinde yapılan güncel rehbere aşağıdaki linkten erişebilirsiniz: https://www.technopat.net/sosyal/konu/minidump-nedir-nasil-paylasilir.3817531/ Minidump dosyaları, bilgisayarınız mavi ekran verdiğinde belleğin ufak bir dökümünü barındıran dosyalardır. Bunları analiz ederek mavi...
www.technopat.net
 
Artı 0 Eksi

Minidump.rar

drive.google.com
 
Artı 0 Eksi
İnceledim. VIDEO_TDR_FAILURE hatasının yanında bir de DPC_WATCHDOG_VIOLATION hatası da vardı.

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

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

Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1546

    Key  : Analysis.Elapsed.mSec
    Value: 2439

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 0

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27829.1001

    Key  : Analysis.Version.Description
    Value: 10.2503.24.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2503.24.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x116

    Key  : Bugcheck.Code.TargetModel
    Value: 0x116

    Key  : Dump.Attributes.AsUlong
    Value: 0x21008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0x116_IMAGE_nvlddmkm.sys

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff80250636ba0

    Key  : Failure.Exception.IP.Module
    Value: nvlddmkm

    Key  : Failure.Exception.IP.Offset
    Value: 0x1936ba0

    Key  : Failure.Hash
    Value: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}


BUGCHECK_CODE:  116

BUGCHECK_P1: ffffcb858d32e010

BUGCHECK_P2: fffff80250636ba0

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

FILE_IN_CAB:  050225-12109-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffcb857e068080

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffcb858d32e010
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_OBJECT: 0000000000000004

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
ffffc50d`ef5af808 fffff802`365515ad     : 00000000`00000116 ffffcb85`8d32e010 fffff802`50636ba0 ffffffff`c000009a : nt!KeBugCheckEx
ffffc50d`ef5af810 fffff802`367d657e     : fffff802`50636ba0 ffffcb85`741ec590 00000000`00002000 ffffcb85`741ec650 : dxgkrnl!TdrBugcheckOnTimeout+0x101
ffffc50d`ef5af850 fffff802`365603dd     : ffffcb85`78f81000 00000000`00000000 00000000`00000004 00000000`00000000 : dxgkrnl!ADAPTER_RENDER::Reset+0x12a
ffffc50d`ef5af880 fffff802`36596ac5     : fffff802`32a80180 ffffcb85`7e068080 ffffcb85`00000000 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x589
ffffc50d`ef5af910 fffff802`36596c22     : ffffcb85`73a88260 ffffcb85`6e686f10 00000000`00000000 ffffa704`c854ce00 : dxgkrnl!TdrResetFromTimeout+0x15
ffffc50d`ef5af940 fffff802`a473bf92     : ffffcb85`7e068080 ffffcb85`6e7a6600 fffff802`a5238800 00000000`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x22
ffffc50d`ef5af980 fffff802`a484d1fa     : ffffcb85`7e068080 ffffcb85`7e068080 fffff802`a473bde0 ffffcb85`6e7a6600 : nt!ExpWorkerThread+0x1b2
ffffc50d`ef5afb30 fffff802`a4a7ca94     : ffff8681`aac80180 ffffcb85`7e068080 fffff802`a484d1a0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
ffffc50d`ef5afb80 00000000`00000000     : ffffc50d`ef5b0000 ffffc50d`ef5a9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  nvlddmkm+1936ba0

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND: .process /r /p 0xffffcb856e6c8040; .thread 0xffffcb857e068080 ; kb

FAILURE_BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

Followup:     MachineOwner


Kod: 
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
Arg2: 0000000000000500, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff804d51c33b0, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding this single DPC timeout

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

*** WARNING: Unable to verify timestamp for ROGMS.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1578

    Key  : Analysis.Elapsed.mSec
    Value: 2239

    Key  : Analysis.IO.Other.Mb
    Value: 2

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 2

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27829.1001

    Key  : Analysis.Version.Description
    Value: 10.2503.24.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2503.24.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Bugcheck.Code.TargetModel
    Value: 0x133

    Key  : Dump.Attributes.AsUlong
    Value: 0x21008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0x133_DPC_mouclass!MouseClassServiceCallback

    Key  : Failure.Hash
    Value: {3fa01bd8-d2f7-df82-2794-89aa20021973}

    Key  : Stack.Pointer
    Value: ISR


BUGCHECK_CODE:  133

BUGCHECK_P1: 0

BUGCHECK_P2: 500

BUGCHECK_P3: 500

BUGCHECK_P4: fffff804d51c33b0

FILE_IN_CAB:  050525-12140-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffff980da32b5080

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  ArmourySwAgent

STACK_TEXT: 
fffff804`66bd5b48 fffff804`d452eec9     : 00000000`00000133 00000000`00000000 00000000`00000500 00000000`00000500 : nt!KeBugCheckEx
fffff804`66bd5b50 fffff804`d45a44a1     : fffff804`d51c33b0 00000000`00000002 00000000`00000000 00000000`000c98b9 : nt!KeAccumulateTicks+0x589
fffff804`66bd5bc0 fffff804`d45a4065     : 00000000`00078216 00000000`00000000 0000001e`0858e85d 00000000`0000000d : nt!KiUpdateRunTime+0xc9
fffff804`66bd5c40 fffff804`d448573e     : fffff804`d5010a40 00000000`00000000 fffff804`64ffa7c0 fffff804`d51207a8 : nt!KiUpdateTime+0x2b5
fffff804`66bd5dd0 fffff804`d44870ed     : fffff804`d5010a40 00000000`00000000 fffff804`d5010af0 fffff804`d518e0d8 : nt!KeClockInterruptNotify+0x66e
fffff804`66bd5f50 fffff804`d487dade     : 00000000`1db4b102 fffff804`d5010a40 fffff804`66bccde0 0000001e`0870a5d2 : nt!KiCallInterruptServiceRoutine+0x2ed
fffff804`66bd5fb0 fffff804`d487e2ec     : 00000000`00000001 fffff804`66bcce60 00000000`00000000 ffff4fba`3511a991 : nt!KiInterruptSubDispatchNoLockNoEtw+0x4e
fffff804`66bccde0 fffff804`d44c21fc     : ffff980d`962100b8 00000000`00000040 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x3c
fffff804`66bccf70 fffff804`d44c213a     : fffff804`66bcd0f4 00000000`00000103 00000000`00000001 fffff804`66bcd099 : nt!KxWaitForSpinLockAndAcquire+0x1c
fffff804`66bccfa0 fffff804`85db1910     : fffff804`64ff1180 00000000`00000002 fffff804`7ef6c008 00000000`00000103 : nt!KeAcquireSpinLockAtDpcLevel+0x1a
fffff804`66bccfd0 fffff804`7f0813d2     : ffff980d`9621dcb0 fffff804`66bcd0f4 fffff804`66bcd108 ffff980d`9623de80 : mouclass!MouseClassServiceCallback+0x70
fffff804`66bcd070 ffff980d`9621dcb0     : fffff804`66bcd0f4 fffff804`66bcd108 ffff980d`9623de80 ffff980d`9623dd20 : ROGMS+0x13d2
fffff804`66bcd078 fffff804`66bcd0f4     : fffff804`66bcd108 ffff980d`9623de80 ffff980d`9623dd20 ffff980d`92ff6260 : 0xffff980d`9621dcb0
fffff804`66bcd080 fffff804`66bcd108     : ffff980d`9623de80 ffff980d`9623dd20 ffff980d`92ff6260 ffff980d`9623dd20 : 0xfffff804`66bcd0f4
fffff804`66bcd088 ffff980d`9623de80     : ffff980d`9623dd20 ffff980d`92ff6260 ffff980d`9623dd20 fffff804`7f063848 : 0xfffff804`66bcd108
fffff804`66bcd090 ffff980d`9623dd20     : ffff980d`92ff6260 ffff980d`9623dd20 fffff804`7f063848 00000000`00000002 : 0xffff980d`9623de80
fffff804`66bcd098 ffff980d`92ff6260     : ffff980d`9623dd20 fffff804`7f063848 00000000`00000002 ffff980d`92ff6260 : 0xffff980d`9623dd20
fffff804`66bcd0a0 ffff980d`9623dd20     : fffff804`7f063848 00000000`00000002 ffff980d`92ff6260 00000000`00000000 : 0xffff980d`92ff6260
fffff804`66bcd0a8 fffff804`7f063848     : 00000000`00000002 ffff980d`92ff6260 00000000`00000000 ffff980d`962326e0 : 0xffff980d`9623dd20
fffff804`66bcd0b0 fffff804`d44dc4a4     : 00000000`00000000 ffff980d`96235000 ffff980d`9620e101 fffff804`00000000 : mouhid!MouHid_ReadComplete+0x7b8
fffff804`66bcd150 fffff804`d44dbfb3     : 00000000`00000000 ffff980d`96224050 ffff980d`9620e1d0 00000000`00000000 : nt!IopfCompleteRequest+0x4c4
fffff804`66bcd290 fffff804`7efb24ed     : ffff980d`9620e1d0 fffff804`d44ddf8b 00000000`00000001 00000000`0000000f : nt!IofCompleteRequest+0x13
fffff804`66bcd2c0 fffff804`7efb1815     : ffff980d`9620e1d0 00000000`d44f6d02 ffff980d`9620e1d0 00000000`00000008 : HIDCLASS!HidpDistributeInterruptReport+0x26d
fffff804`66bcd3e0 fffff804`d44dc4a4     : ffff980d`96224a60 ffff980d`9620e060 fffff804`66bcd620 00000000`00000000 : HIDCLASS!HidpInterruptReadComplete+0x455
fffff804`66bcd520 fffff804`d44dbfb3     : 00000000`00000000 00000000`00000000 ffff980d`92fd89c0 ffff980d`962170e0 : nt!IopfCompleteRequest+0x4c4
fffff804`66bcd660 fffff804`6679d2ce     : ffff980d`92fd8b22 00000000`00000000 ffff980d`96224a60 ffff980d`92fd89c0 : nt!IofCompleteRequest+0x13
(Inline Function) --------`--------     : --------`-------- --------`-------- --------`-------- --------`-------- : Wdf01000!FxIrp::CompleteRequest+0x13 [minkernel\wdf\framework\shared\inc\private\km\FxIrpKm.hpp @ 75]
fffff804`66bcd690 fffff804`667e8b07     : 00000000`00000029 fffff804`66bcd7c8 ffff980d`96224a60 ffff980d`92fd89c0 : Wdf01000!FxRequest::CompleteInternal+0x13e [minkernel\wdf\framework\shared\core\fxrequest.cpp @ 869]
(Inline Function) --------`--------     : --------`-------- --------`-------- --------`-------- --------`-------- : Wdf01000!FxRequest::Complete+0x35 [minkernel\wdf\framework\shared\inc\private\common\FxRequest.hpp @ 803]
fffff804`66bcd720 fffff804`7e89dd6a     : ffff980d`92fd8b60 ffff980d`92fd89c0 ffff980d`962174c0 ffff980d`92fd8b60 : Wdf01000!imp_WdfRequestComplete+0xa7 [minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 436]
fffff804`66bcd7a0 fffff804`7e89d6c0     : 00000000`00000001 ffff980d`92b548a0 00000000`00000000 ffff980d`96215820 : USBXHCI!Bulk_ProcessTransferEventWithED1+0x68a
fffff804`66bcd860 fffff804`7e8b01ee     : ffff980d`90cfeaf0 00000000`00000000 00000000`00000000 00000000`00000000 : USBXHCI!Bulk_EP_TransferEventHandler+0x10
fffff804`66bcd890 fffff804`7e8b00a6     : 00000000`00000004 fffff804`66bcd900 fffff804`7e8fa2a0 fffff804`66bcd9c8 : USBXHCI!Endpoint_TransferEventHandler+0x8e
fffff804`66bcd8f0 fffff804`7e8b5a18     : ffff980d`9128fec0 00000000`000004c0 00000000`00000000 000067f2`6e119fd8 : USBXHCI!UsbDevice_TransferEventHandler+0x56
fffff804`66bcd950 fffff804`7e8b541c     : 00000000`00000000 00000000`00000000 ffff980d`a00d1948 000026b5`c90279e7 : USBXHCI!Interrupter_DeferredWorkProcessor+0x5e8
fffff804`66bcda50 fffff804`667d6411     : fffff804`d51cff40 00000000`00000f44 fffff804`64ff1180 ffffbb81`5973c6f0 : USBXHCI!Interrupter_WdfEvtInterruptDpc+0xc
(Inline Function) --------`--------     : --------`-------- --------`-------- --------`-------- --------`-------- : Wdf01000!FxInterrupt::DpcHandler+0x69 [minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp @ 75]
fffff804`66bcda80 fffff804`d444000e     : 000026ad`848a8934 ffff980d`a867c080 ffff980d`9128fcc0 fffff804`64ffa2f8 : Wdf01000!FxInterrupt::_InterruptDpcThunk+0xb1 [minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp @ 405]
fffff804`66bcdad0 fffff804`d452ca0b     : fffff804`64ff1180 00000000`00000020 fffff804`64ff1180 00000000`0000000e : nt!KiExecuteAllDpcs+0x67e
fffff804`66bcdd20 fffff804`d48836e5     : 00000000`00000000 ffff980d`a34c78b0 ffffcc07`6193ec40 00000000`00000000 : nt!KiRetireDpcList+0x36b
fffff804`66bcdfb0 fffff804`d488368f     : ffffcc07`6193ed30 fffff804`d4420c65 fffff804`64ff1180 fffff804`d452fdcb : nt!KxSwapStacksAndRetireDpcList+0x5
ffffcc07`6193ec40 fffff804`d4420c65     : fffff804`64ff1180 fffff804`d452fdcb 00000000`00000000 fffff804`d44dd4ec : nt!KiPlatformSwapStacksAndCallReturn
ffffcc07`6193ec50 fffff804`d4882ebb     : 00000000`00000018 ffff980d`a34c7f20 ffffbb81`5973cdc0 ffffbb81`5973cdc0 : nt!KiDispatchInterrupt+0x65
ffffcc07`6193ec80 fffff804`d487db54     : 0000001d`fc866386 ffffcc07`6193ed30 0000001d`fc8663a6 000026ad`848a87ea : nt!KiDpcInterruptBypass+0x1b
ffffcc07`6193ecb0 fffff804`85db6c32     : fffff804`85db19e8 ffff980d`a34c78b0 ffff980d`9621de00 000067f2`59a86208 : nt!KiInterruptDispatch+0x64
ffffcc07`6193ee48 fffff804`85db19e8     : ffff980d`a34c78b0 ffff980d`9621de00 000067f2`59a86208 fffff804`667e97db : mouclass!memcpy+0x32
ffffcc07`6193ee50 fffff804`7f081235     : ffff980d`9621dcb0 00000000`00000000 00000000`00000000 000067f2`59a878c8 : mouclass!MouseClassServiceCallback+0x148
ffffcc07`6193eef0 ffff980d`9621dcb0     : 00000000`00000000 00000000`00000000 000067f2`59a878c8 ffff980d`92d97db0 : ROGMS+0x1235
ffffcc07`6193eef8 00000000`00000000     : 00000000`00000000 000067f2`59a878c8 ffff980d`92d97db0 fffff804`66843bb8 : 0xffff980d`9621dcb0


SYMBOL_NAME:  mouclass!MouseClassServiceCallback+70

MODULE_NAME: mouclass

IMAGE_NAME:  mouclass.sys

IMAGE_VERSION:  10.0.26100.1150

STACK_COMMAND: .process /r /p 0xffff980d9e2db080; .thread 0xffff980da32b5080 ; kb

BUCKET_ID_FUNC_OFFSET:  70

FAILURE_BUCKET_ID:  0x133_DPC_mouclass!MouseClassServiceCallback

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {3fa01bd8-d2f7-df82-2794-89aa20021973}

Followup:     MachineOwner

Hocam farenizin, klavyenizin sürücüsünü güncelleyin zira bir hata mouclass.sys yüzünden gerçekleşmiş. Ayrıca en güncel ekran kartı sürücüsü yerine bir önceki sürücüler veya WHQL onaylı sürücüleri yükleyin.

​

 
Artı 0 Eksi

Hocam, ben bu hatayı 1 aydan uzun süredir alıyorum 2 günde bir falan ve hep aynı şekilde ekran kararıyor, garip bir hata sesi geliyor, ardından sistem yeniden başlıyor. Bu sürede pek çok kez sürücülerimi güncelledim; sürücülerin güncel olmaması ya da yeni sürümlerde sorun olması olduğunu sanmıyorum.
 
Artı 0 Eksi
Hocam fare sürücünüzü güncelleyin eğer onu güncellemediyseniz. Ayrıca OCCT ile 30 dakika VRAM ve 3D Standard testi yapın, ekran kartınızda donanımsal sıkıntı olabilir.
 
Artı 0 Eksi

Bu şekilde başlattım error yazınca durdurdum, benmi yanlış birşey yaptım bir sorun mu var.

00:00:00 - Info - Test schedule started at 2025-05-11 15:24:25
00:00:00 - Info - Combined - Initializing (Duration : 01:00:00)
00:00:05 - Error - 3D Adaptive - 785808 error(s) found ( GPU #0 - NVIDIA GeForce RTX 3060 )
00:00:06 - Info - Combined - Started (Duration : 01:00:00)
00:00:07 - Error - 3D Adaptive - 785808 error(s) found ( GPU #0 - NVIDIA GeForce RTX 3060 )
00:00:08 - Error - 3D Adaptive - 785808 error(s) found ( GPU #0 - NVIDIA GeForce RTX 3060 )
00:00:09 - Error - 3D Adaptive - 785808 error(s) found ( GPU #0 - NVIDIA GeForce RTX 3060 )
00:00:10 - Error - 3D Adaptive - 785808 error(s) found ( GPU #0 - NVIDIA GeForce RTX 3060 )
00:00:11 - Error - 3D Adaptive - 785808 error(s) found ( GPU #0 - NVIDIA GeForce RTX 3060 )
00:00:12 - Error - 3D Adaptive - 785808 error(s) found ( GPU #0 - NVIDIA GeForce RTX 3060 )
00:00:13 - Error - 3D Adaptive - 785808 error(s) found ( GPU #0 - NVIDIA GeForce RTX 3060 )
00:00:14 - Error - 3D Adaptive - 785808 error(s) found ( GPU #0 - NVIDIA GeForce RTX 3060 )
00:00:15 - Error - 3D Adaptive - 785808 error(s) found ( GPU #0 - NVIDIA GeForce RTX 3060 )
00:00:16 - Error - 3D Adaptive - 785808 error(s) found ( GPU #0 - NVIDIA GeForce RTX 3060 )
00:00:17 - Error - 3D Adaptive - 785808 error(s) found ( GPU #0 - NVIDIA GeForce RTX 3060 )
00:00:18 - Error - 3D Adaptive - 785808 error(s) found ( GPU #0 - NVIDIA GeForce RTX 3060 )
00:00:19 - Error - 3D Adaptive - 785808 error(s) found ( GPU #0 - NVIDIA GeForce RTX 3060 )
00:00:19 - Info - Combined - Test stopped
00:00:19 - Info - Schedule stopped by user request
 
Artı 0 Eksi


Hocam 30 dk nin sonu böyle. Doğru yeri mi attım acaba?
 
Artı 0 Eksi
Doğru yer gibi görünüyor. Hocam 3D Standard ile VRAM seçiliydi değil mi bunda da? Öncekinde error vardı bunda temiz çıktı diye soruyorum.
 
Artı 0 Eksi
Mesaj yazmak için giriş yapmalı ya da kaydolmalısınız.

Benzer konular

  • Soru
"VIDEO_TDR_FAILURE" mavi ekran hatası
Mesaj
5
Görüntüleme
252
claus
  • Soru
VIDEO_TDR_FAILURE mavi ekran hatası
Mesaj
3
Görüntüleme
167
turko35408
  • Soru
VIDEO_TDR_FAILURE mavi ekran hatası
Mesaj
5
Görüntüleme
275
claus
  • Soru
VIDEO_TDR_FAILURE mavi ekran hatası
Mesaj
0
Görüntüleme
191
Lewis44
  • Soru
VIDEO_TDR_FAILURE mavi ekran hatası
Mesaj
2
Görüntüleme
249
vilgaxq
Menü
Giriş yap
Kaydol
Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…