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

VENGEANCE ANGEL

Üstün
Katılım
2 Ocak 2024
Mesajlar
1.033
Makaleler
1
Çözümler
30
Beğeniler
598
Yer
ANKARA
  • Anakart: MSI B150 Gaming M3
  • İşlemci: Intel i5-6500
  • Ekran Kartı: 1660 Super
  • İşletim Sistemi: Windows 10 Home Single Language

Herkese merhaba.
Bilgisayarımı tamamen kapattığımda fişten çekiyorum, akşam eve geldiğimde fişi takıp açıyorum. Son zamanlarda ilk açılışta masaüstüne geliyor, sonra ekran gidiyor, bilgisayar kendini resetliyor sonra açılıyor. Meğerse mavi ekran hatası oluşuyormuş ama ekrana mavi ekran hiç düşmedi.

0x116 VIDEO_TDR_FAILURE ve 0x133 DPC_WATCHDOG_VIOLATION hatası vermiş. Ben minidumpları inceledim, 0x133 hatası da ekran kartı kaynaklı.
Gözümden belki bir şey kaçmıştır düşüncesiyle sizinle paylaşmak istedim. Yardımcı olabilir misiniz?

3 ihtimal var tahminimce. Ya anakart, ya PCI-e yuvası, ya da ekran kartı.
FurMark 76 derece.
DDU yapıldı.
551.23 güncel sürüm.


@480 @claus @Enes3078 @Yener K
 
Son düzenleme:
Çözüm
Hatalar ekran kartına işaret ediyor lakin RAM yüzünden de ekran kartının çöktüğü durumlara şahit oldum. RAM'leri söktükten sonra bağlantı noktalarını silgiyle silip geri takar mısın?

Kod:
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffff810a798ca050, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80087cbf600, 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: 2843

    Key  : Analysis.Elapsed.mSec
    Value: 10203

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x116

    Key  : Dump.Attributes.AsUlong
    Value: c

    Key  : Dump.Attributes.InsufficientDumpfileSize
    Value: 1

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.RequiredDumpfileSize
    Value: 0x3f535792

    Key  : Failure.Bucket
    Value: 0x116_IMAGE_nvlddmkm.sys

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


BUGCHECK_CODE:  116

BUGCHECK_P1: ffff810a798ca050

BUGCHECK_P2: fffff80087cbf600

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

FILE_IN_CAB:  020924-9593-01.dmp

DUMP_FILE_ATTRIBUTES: 0xc
  Insufficient Dumpfile Size
  Kernel Generated Triage Dump

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

PROCESS_OBJECT: 0000000000000004

BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffffbe84`3606f918 fffff800`796c555e     : 00000000`00000116 ffff810a`798ca050 fffff800`87cbf600 ffffffff`c000009a : nt!KeBugCheckEx
ffffbe84`3606f920 fffff800`79675b04     : fffff800`87cbf600 ffff810a`7984e6e0 00000000`00002000 ffff810a`7984e7a0 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffffbe84`3606f960 fffff800`7966e63c     : ffff810a`7983f000 00000000`01000000 00000000`00000004 00000000`00000004 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffffbe84`3606f990 fffff800`796c4c85     : 00000000`00000100 ffff810a`7983fa70 00000000`79bd4040 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x4dc
ffffbe84`3606fa10 fffff800`796c4df7     : fffff800`59925440 00000000`00000000 00000000`00000000 00000000`00000b00 : dxgkrnl!TdrResetFromTimeout+0x15
ffffbe84`3606fa40 fffff800`58e50545     : ffff810a`75c79140 fffff800`796c4dd0 ffff810a`70498c60 00000000`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffffbe84`3606fa70 fffff800`58f0e6f5     : ffff810a`75c79140 00000000`00000080 ffff810a`704b7240 000fa4ef`bd9bbfff : nt!ExpWorkerThread+0x105
ffffbe84`3606fb10 fffff800`59006278     : ffff9d80`dc7dc180 ffff810a`75c79140 fffff800`58f0e6a0 06650020`05370000 : nt!PspSystemThreadStartup+0x55
ffffbe84`3606fb60 00000000`00000000     : ffffbe84`36070000 ffffbe84`36069000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nvlddmkm+148f600

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c89bfe8c-ed39-f658-ef27-f2898997fdbd}
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff807232fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
Arg4: 0000000000000000

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

*** WARNING: Unable to verify timestamp for nvlddmkm.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: 2671

    Key  : Analysis.Elapsed.mSec
    Value: 13012

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Dump.Attributes.AsUlong
    Value: c

    Key  : Dump.Attributes.InsufficientDumpfileSize
    Value: 1

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.RequiredDumpfileSize
    Value: 0x38cb6892

    Key  : Failure.Bucket
    Value: 0x133_ISR_nvlddmkm!unknown_function

    Key  : Failure.Hash
    Value: {f97493a5-ea2b-23ca-a808-8602773c2a86}


BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff807232fb320

BUGCHECK_P4: 0

FILE_IN_CAB:  020824-9875-01.dmp

DUMP_FILE_ATTRIBUTES: 0xc
  Insufficient Dumpfile Size
  Kernel Generated Triage Dump

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
fffff807`28464c88 fffff807`22a31864     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff807`232fb320 : nt!KeBugCheckEx
fffff807`28464c90 fffff807`22848dbd     : 000000b1`53c6bc85 fffff807`1fcad180 00000000`00000246 00000000`000036da : nt!KeAccumulateTicks+0x1ebcc4
fffff807`28464cf0 fffff807`2283fe41     : fffff807`1fcad100 00000000`000020b1 fffff807`1fcad180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
fffff807`28464d40 fffff807`228431d3     : fffff807`284551a0 00000000`00000000 fffff807`23231a80 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff807`28464e80 fffff807`2284aa62     : fffff807`284551a0 fffff807`28455220 fffff807`28455200 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
fffff807`28464f30 fffff807`228a7765     : 00000000`82dc2380 fffff807`232f3c20 fffff807`232f3cd0 ffff710d`130f00aa : nt!HalpTimerClockInterrupt+0xe2
fffff807`28464f60 fffff807`229ff5da     : fffff807`28455220 fffff807`232f3c20 000000b1`53c2b2ca ffffde08`94c03bf8 : nt!KiCallInterruptServiceRoutine+0xa5
fffff807`28464fb0 fffff807`229ffda7     : ffffde08`92a86920 ffffde08`944673f0 ffffde08`00000000 00001f80`00000c0b : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff807`284551a0 fffff807`4dfd1152     : fffff807`28455570 fffff807`28455ab0 ffffde08`94c03000 ffffb227`56652076 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff807`28455330 fffff807`28455570     : fffff807`28455ab0 ffffde08`94c03000 ffffb227`56652076 00000000`00000000 : nvlddmkm+0xf1152
fffff807`28455338 fffff807`28455ab0     : ffffde08`94c03000 ffffb227`56652076 00000000`00000000 fffff807`4df9e3ab : 0xfffff807`28455570
fffff807`28455340 ffffde08`94c03000     : ffffb227`56652076 00000000`00000000 fffff807`4df9e3ab ffffde08`94c03000 : 0xfffff807`28455ab0
fffff807`28455348 ffffb227`56652076     : 00000000`00000000 fffff807`4df9e3ab ffffde08`94c03000 00000000`00000001 : 0xffffde08`94c03000
fffff807`28455350 00000000`00000000     : fffff807`4df9e3ab ffffde08`94c03000 00000000`00000001 00000000`00000000 : 0xffffb227`56652076


SYMBOL_NAME:  nvlddmkm+f1152

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  f1152

FAILURE_BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f97493a5-ea2b-23ca-a808-8602773c2a86}

Followup:     MachineOwner
---------
Hatalar ekran kartına işaret ediyor lakin RAM yüzünden de ekran kartının çöktüğü durumlara şahit oldum. RAM'leri söktükten sonra bağlantı noktalarını silgiyle silip geri takar mısın?

Kod:
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffff810a798ca050, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80087cbf600, 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: 2843

    Key  : Analysis.Elapsed.mSec
    Value: 10203

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x116

    Key  : Dump.Attributes.AsUlong
    Value: c

    Key  : Dump.Attributes.InsufficientDumpfileSize
    Value: 1

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.RequiredDumpfileSize
    Value: 0x3f535792

    Key  : Failure.Bucket
    Value: 0x116_IMAGE_nvlddmkm.sys

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


BUGCHECK_CODE:  116

BUGCHECK_P1: ffff810a798ca050

BUGCHECK_P2: fffff80087cbf600

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

FILE_IN_CAB:  020924-9593-01.dmp

DUMP_FILE_ATTRIBUTES: 0xc
  Insufficient Dumpfile Size
  Kernel Generated Triage Dump

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

PROCESS_OBJECT: 0000000000000004

BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffffbe84`3606f918 fffff800`796c555e     : 00000000`00000116 ffff810a`798ca050 fffff800`87cbf600 ffffffff`c000009a : nt!KeBugCheckEx
ffffbe84`3606f920 fffff800`79675b04     : fffff800`87cbf600 ffff810a`7984e6e0 00000000`00002000 ffff810a`7984e7a0 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffffbe84`3606f960 fffff800`7966e63c     : ffff810a`7983f000 00000000`01000000 00000000`00000004 00000000`00000004 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffffbe84`3606f990 fffff800`796c4c85     : 00000000`00000100 ffff810a`7983fa70 00000000`79bd4040 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x4dc
ffffbe84`3606fa10 fffff800`796c4df7     : fffff800`59925440 00000000`00000000 00000000`00000000 00000000`00000b00 : dxgkrnl!TdrResetFromTimeout+0x15
ffffbe84`3606fa40 fffff800`58e50545     : ffff810a`75c79140 fffff800`796c4dd0 ffff810a`70498c60 00000000`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffffbe84`3606fa70 fffff800`58f0e6f5     : ffff810a`75c79140 00000000`00000080 ffff810a`704b7240 000fa4ef`bd9bbfff : nt!ExpWorkerThread+0x105
ffffbe84`3606fb10 fffff800`59006278     : ffff9d80`dc7dc180 ffff810a`75c79140 fffff800`58f0e6a0 06650020`05370000 : nt!PspSystemThreadStartup+0x55
ffffbe84`3606fb60 00000000`00000000     : ffffbe84`36070000 ffffbe84`36069000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nvlddmkm+148f600

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c89bfe8c-ed39-f658-ef27-f2898997fdbd}
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff807232fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
Arg4: 0000000000000000

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

*** WARNING: Unable to verify timestamp for nvlddmkm.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: 2671

    Key  : Analysis.Elapsed.mSec
    Value: 13012

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Dump.Attributes.AsUlong
    Value: c

    Key  : Dump.Attributes.InsufficientDumpfileSize
    Value: 1

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.RequiredDumpfileSize
    Value: 0x38cb6892

    Key  : Failure.Bucket
    Value: 0x133_ISR_nvlddmkm!unknown_function

    Key  : Failure.Hash
    Value: {f97493a5-ea2b-23ca-a808-8602773c2a86}


BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff807232fb320

BUGCHECK_P4: 0

FILE_IN_CAB:  020824-9875-01.dmp

DUMP_FILE_ATTRIBUTES: 0xc
  Insufficient Dumpfile Size
  Kernel Generated Triage Dump

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
fffff807`28464c88 fffff807`22a31864     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff807`232fb320 : nt!KeBugCheckEx
fffff807`28464c90 fffff807`22848dbd     : 000000b1`53c6bc85 fffff807`1fcad180 00000000`00000246 00000000`000036da : nt!KeAccumulateTicks+0x1ebcc4
fffff807`28464cf0 fffff807`2283fe41     : fffff807`1fcad100 00000000`000020b1 fffff807`1fcad180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
fffff807`28464d40 fffff807`228431d3     : fffff807`284551a0 00000000`00000000 fffff807`23231a80 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff807`28464e80 fffff807`2284aa62     : fffff807`284551a0 fffff807`28455220 fffff807`28455200 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
fffff807`28464f30 fffff807`228a7765     : 00000000`82dc2380 fffff807`232f3c20 fffff807`232f3cd0 ffff710d`130f00aa : nt!HalpTimerClockInterrupt+0xe2
fffff807`28464f60 fffff807`229ff5da     : fffff807`28455220 fffff807`232f3c20 000000b1`53c2b2ca ffffde08`94c03bf8 : nt!KiCallInterruptServiceRoutine+0xa5
fffff807`28464fb0 fffff807`229ffda7     : ffffde08`92a86920 ffffde08`944673f0 ffffde08`00000000 00001f80`00000c0b : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff807`284551a0 fffff807`4dfd1152     : fffff807`28455570 fffff807`28455ab0 ffffde08`94c03000 ffffb227`56652076 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff807`28455330 fffff807`28455570     : fffff807`28455ab0 ffffde08`94c03000 ffffb227`56652076 00000000`00000000 : nvlddmkm+0xf1152
fffff807`28455338 fffff807`28455ab0     : ffffde08`94c03000 ffffb227`56652076 00000000`00000000 fffff807`4df9e3ab : 0xfffff807`28455570
fffff807`28455340 ffffde08`94c03000     : ffffb227`56652076 00000000`00000000 fffff807`4df9e3ab ffffde08`94c03000 : 0xfffff807`28455ab0
fffff807`28455348 ffffb227`56652076     : 00000000`00000000 fffff807`4df9e3ab ffffde08`94c03000 00000000`00000001 : 0xffffde08`94c03000
fffff807`28455350 00000000`00000000     : fffff807`4df9e3ab ffffde08`94c03000 00000000`00000001 00000000`00000000 : 0xffffb227`56652076


SYMBOL_NAME:  nvlddmkm+f1152

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  f1152

FAILURE_BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f97493a5-ea2b-23ca-a808-8602773c2a86}

Followup:     MachineOwner
---------
 
Çözüm
Hatalar ekran kartına işaret ediyor lakin RAM yüzünden de ekran kartının çöktüğü durumlara şahit oldum. RAM'leri söktükten sonra bağlantı noktalarını silgiyle silip geri takar mısın?
Hocam, ben de sizi etiketlemeyi düşünüyordum, sonra yoğunsunuzdur, başınız kalabalıktır diye etiketlememiştim. :D

RAM'leri söktüm, sildim tekrar taktım. Bir sorun olursa -ki inşallah olmaz- tekrar buraya yazarım.

Hatalar ekran kartına işaret ediyor lakin RAM yüzünden de ekran kartının çöktüğü durumlara şahit oldum. RAM'leri söktükten sonra bağlantı noktalarını silgiyle silip geri takar mısın?
Hocam iyi geceler. Dediğinizi yapmıştım. Az önce bilgisayarı açmak istediğimde Windows boot ederken ekran gitti bir süre gelmedi. Daha sonra klavyenin NumLock CapsLock gibi tuşlarının tepki verdiğini fark ettim. Yani sistem boot etmiş aslında ama görüntü yok. Power tuşundan sistemi kapattım tekrar açtım şimdi görüntü geldi ama yine 0x116 hatası almışım. Son minidump'u paylaşmak istiyorum. Farklı bir şey görebildiniz mi?

Son dosya:
021324-9312-01.dmp

Anakartımda 2 tane PCIe slotu var. Artık 2. slota takmayı düşünüyorum.
Hatalar ekran kartına işaret ediyor lakin RAM yüzünden de ekran kartının çöktüğü durumlara şahit oldum. RAM'leri söküp, bağlantı noktalarını silgiyle silip geri takar mısın?

Kod:
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffff810a798ca050, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80087cbf600, 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: 2843

    Key  : Analysis.Elapsed.mSec
    Value: 10203

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x116

    Key  : Dump.Attributes.AsUlong
    Value: c

    Key  : Dump.Attributes.InsufficientDumpfileSize
    Value: 1

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.RequiredDumpfileSize
    Value: 0x3f535792

    Key  : Failure.Bucket
    Value: 0x116_IMAGE_nvlddmkm.sys

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


BUGCHECK_CODE:  116

BUGCHECK_P1: ffff810a798ca050

BUGCHECK_P2: fffff80087cbf600

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

FILE_IN_CAB:  020924-9593-01.dmp

DUMP_FILE_ATTRIBUTES: 0xc
  Insufficient Dumpfile Size
  Kernel Generated Triage Dump

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

PROCESS_OBJECT: 0000000000000004

BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffffbe84`3606f918 fffff800`796c555e     : 00000000`00000116 ffff810a`798ca050 fffff800`87cbf600 ffffffff`c000009a : nt!KeBugCheckEx
ffffbe84`3606f920 fffff800`79675b04     : fffff800`87cbf600 ffff810a`7984e6e0 00000000`00002000 ffff810a`7984e7a0 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffffbe84`3606f960 fffff800`7966e63c     : ffff810a`7983f000 00000000`01000000 00000000`00000004 00000000`00000004 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffffbe84`3606f990 fffff800`796c4c85     : 00000000`00000100 ffff810a`7983fa70 00000000`79bd4040 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x4dc
ffffbe84`3606fa10 fffff800`796c4df7     : fffff800`59925440 00000000`00000000 00000000`00000000 00000000`00000b00 : dxgkrnl!TdrResetFromTimeout+0x15
ffffbe84`3606fa40 fffff800`58e50545     : ffff810a`75c79140 fffff800`796c4dd0 ffff810a`70498c60 00000000`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffffbe84`3606fa70 fffff800`58f0e6f5     : ffff810a`75c79140 00000000`00000080 ffff810a`704b7240 000fa4ef`bd9bbfff : nt!ExpWorkerThread+0x105
ffffbe84`3606fb10 fffff800`59006278     : ffff9d80`dc7dc180 ffff810a`75c79140 fffff800`58f0e6a0 06650020`05370000 : nt!PspSystemThreadStartup+0x55
ffffbe84`3606fb60 00000000`00000000     : ffffbe84`36070000 ffffbe84`36069000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nvlddmkm+148f600

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c89bfe8c-ed39-f658-ef27-f2898997fdbd}
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff807232fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
Arg4: 0000000000000000

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

*** WARNING: Unable to verify timestamp for nvlddmkm.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: 2671

    Key  : Analysis.Elapsed.mSec
    Value: 13012

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Dump.Attributes.AsUlong
    Value: c

    Key  : Dump.Attributes.InsufficientDumpfileSize
    Value: 1

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.RequiredDumpfileSize
    Value: 0x38cb6892

    Key  : Failure.Bucket
    Value: 0x133_ISR_nvlddmkm!unknown_function

    Key  : Failure.Hash
    Value: {f97493a5-ea2b-23ca-a808-8602773c2a86}


BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff807232fb320

BUGCHECK_P4: 0

FILE_IN_CAB:  020824-9875-01.dmp

DUMP_FILE_ATTRIBUTES: 0xc
  Insufficient Dumpfile Size
  Kernel Generated Triage Dump

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
fffff807`28464c88 fffff807`22a31864     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff807`232fb320 : nt!KeBugCheckEx
fffff807`28464c90 fffff807`22848dbd     : 000000b1`53c6bc85 fffff807`1fcad180 00000000`00000246 00000000`000036da : nt!KeAccumulateTicks+0x1ebcc4
fffff807`28464cf0 fffff807`2283fe41     : fffff807`1fcad100 00000000`000020b1 fffff807`1fcad180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
fffff807`28464d40 fffff807`228431d3     : fffff807`284551a0 00000000`00000000 fffff807`23231a80 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff807`28464e80 fffff807`2284aa62     : fffff807`284551a0 fffff807`28455220 fffff807`28455200 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
fffff807`28464f30 fffff807`228a7765     : 00000000`82dc2380 fffff807`232f3c20 fffff807`232f3cd0 ffff710d`130f00aa : nt!HalpTimerClockInterrupt+0xe2
fffff807`28464f60 fffff807`229ff5da     : fffff807`28455220 fffff807`232f3c20 000000b1`53c2b2ca ffffde08`94c03bf8 : nt!KiCallInterruptServiceRoutine+0xa5
fffff807`28464fb0 fffff807`229ffda7     : ffffde08`92a86920 ffffde08`944673f0 ffffde08`00000000 00001f80`00000c0b : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff807`284551a0 fffff807`4dfd1152     : fffff807`28455570 fffff807`28455ab0 ffffde08`94c03000 ffffb227`56652076 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff807`28455330 fffff807`28455570     : fffff807`28455ab0 ffffde08`94c03000 ffffb227`56652076 00000000`00000000 : nvlddmkm+0xf1152
fffff807`28455338 fffff807`28455ab0     : ffffde08`94c03000 ffffb227`56652076 00000000`00000000 fffff807`4df9e3ab : 0xfffff807`28455570
fffff807`28455340 ffffde08`94c03000     : ffffb227`56652076 00000000`00000000 fffff807`4df9e3ab ffffde08`94c03000 : 0xfffff807`28455ab0
fffff807`28455348 ffffb227`56652076     : 00000000`00000000 fffff807`4df9e3ab ffffde08`94c03000 00000000`00000001 : 0xffffde08`94c03000
fffff807`28455350 00000000`00000000     : fffff807`4df9e3ab ffffde08`94c03000 00000000`00000001 00000000`00000000 : 0xffffb227`56652076


SYMBOL_NAME:  nvlddmkm+f1152

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  f1152

FAILURE_BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f97493a5-ea2b-23ca-a808-8602773c2a86}

Followup:     MachineOwner
---------
Hocam ben bu konuyu unutmuşum, kusura bakmayın. RAM'leri ve ekran kartının pinlerini silgiyle silip temizledikten sonra düzelmişti.
 
Son düzenleyen: Moderatör: