Son düzenleme:
Ekran kartı, SSD/HDD, CPU sıcaklığıda normalse driver sürümünü değiştirmeyi deneyin hocam. Oda işe yaramazsa son kez ramlere memtest86 testi yaparız. Ondada sorun çıkmazsa PSU sorunludur yüksek ihtimalle.
İlgi ve alakan için çok teşekkür ederim. Bunları denedikten sonra tekrardan bilgi vereceğim ama birkaç gün sürebilir çünkü nerede, ne zaman, nasıl olacağı belli olmuyor, bazen 3 gün hiç kapanmıyor.
 
@Raphoras

Sisteminde .DMP dosyası içinde ekran kartı ile ilgili sorun görünüyor. Siz DDU ile kaldırıp yüklediğinizi söylediniz lakin sizden Furmark testi ve OCCT 3D / VRAM testi yapmanızı istiyorum herhangi bir kapanma olursa veya error code görürseniz OCCT üzerinde buradan bildirin şuan sorun tamamen ekran kartı.

İndirme Link:
Testleri yapın paylaşın görsel olarak.

Kod:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: fffff803d83c43b0, 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: 1984

    Key  : Analysis.Elapsed.mSec
    Value: 7377

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27871.1001

    Key  : Analysis.Version.Description
    Value: 10.2505.01.02 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2505.1.2

    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_ISR_nvlddmkm!unknown_function

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

    Key  : Stack.Pointer
    Value: ISR


BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff803d83c43b0

BUGCHECK_P4: 0

FILE_IN_CAB:  081225-12609-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008
  Kernel Generated Triage Dump

FAULTING_THREAD:  fffff803d83d1640

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
fffff803`6b2dcc28 fffff803`d77e4866     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff803`d83c43b0 : nt!KeBugCheckEx
fffff803`6b2dcc30 fffff803`d77e3d9a     : 00000000`00000000 ffffb600`7acd4400 fffff780`00000320 fffff803`65e17180 : nt!KeAccumulateTicks+0x596
fffff803`6b2dcca0 fffff803`d7755361     : 00000122`e788a8b3 fffff803`6b2cc100 fffff803`65e17180 fffff803`6b2cc200 : nt!KiUpdateRunTime+0xca
fffff803`6b2dce60 fffff803`d7755cbb     : fffff803`d8210bb0 00000000`00000000 fffff803`d8210c60 fffff803`d838e850 : nt!KeClockInterruptNotify+0x431
fffff803`6b2dcf50 fffff803`d7aa657e     : ffffa60b`455cf002 fffff803`d8210bb0 00013aac`25f64240 00000122`e84d78cd : nt!KiCallInterruptServiceRoutine+0x31b
fffff803`6b2dcfb0 fffff803`d7aa6d8c     : 00000000`00000000 00001fa0`00000200 00000000`00000025 00000000`00000002 : nt!KiInterruptSubDispatchNoLockNoEtw+0x4e
fffff803`6b2cc1d0 fffff803`7c0003f6     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x3c
fffff803`6b2cc360 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 ffffa60b`455cf000 : nvlddmkm+0x3003f6


SYMBOL_NAME:  nvlddmkm+3003f6

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND: .process /r /p 0xfffff803d83cef80; .thread 0xfffff803d83d1640 ; kb

BUCKET_ID_FUNC_OFFSET:  3003f6

FAILURE_BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

Followup:     MachineOwner
---------
 
Driver olarak 577 veya 576 sürümü kurun derim. Son sürümlerde absürt sıkıntılar var. Bir ara ısı sensörü yanlış okuduğuna dair bilgi okumuştum tam emin değilim.
 
@Raphoras

Sisteminde .DMP dosyası içinde ekran kartı ile ilgili sorun görünüyor. Siz DDU ile kaldırıp yüklediğinizi söylediniz lakin sizden Furmark testi ve OCCT 3D / VRAM testi yapmanızı istiyorum herhangi bir kapanma olursa veya error code görürseniz OCCT üzerinde buradan bildirin şuan sorun tamamen ekran kartı.

İndirme Link:
Testleri yapın paylaşın görsel olarak.

Kod:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: fffff803d83c43b0, 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: 1984

    Key  : Analysis.Elapsed.mSec
    Value: 7377

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27871.1001

    Key  : Analysis.Version.Description
    Value: 10.2505.01.02 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2505.1.2

    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_ISR_nvlddmkm!unknown_function

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

    Key  : Stack.Pointer
    Value: ISR


BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff803d83c43b0

BUGCHECK_P4: 0

FILE_IN_CAB:  081225-12609-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008
  Kernel Generated Triage Dump

FAULTING_THREAD:  fffff803d83d1640

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
fffff803`6b2dcc28 fffff803`d77e4866     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff803`d83c43b0 : nt!KeBugCheckEx
fffff803`6b2dcc30 fffff803`d77e3d9a     : 00000000`00000000 ffffb600`7acd4400 fffff780`00000320 fffff803`65e17180 : nt!KeAccumulateTicks+0x596
fffff803`6b2dcca0 fffff803`d7755361     : 00000122`e788a8b3 fffff803`6b2cc100 fffff803`65e17180 fffff803`6b2cc200 : nt!KiUpdateRunTime+0xca
fffff803`6b2dce60 fffff803`d7755cbb     : fffff803`d8210bb0 00000000`00000000 fffff803`d8210c60 fffff803`d838e850 : nt!KeClockInterruptNotify+0x431
fffff803`6b2dcf50 fffff803`d7aa657e     : ffffa60b`455cf002 fffff803`d8210bb0 00013aac`25f64240 00000122`e84d78cd : nt!KiCallInterruptServiceRoutine+0x31b
fffff803`6b2dcfb0 fffff803`d7aa6d8c     : 00000000`00000000 00001fa0`00000200 00000000`00000025 00000000`00000002 : nt!KiInterruptSubDispatchNoLockNoEtw+0x4e
fffff803`6b2cc1d0 fffff803`7c0003f6     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x3c
fffff803`6b2cc360 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 ffffa60b`455cf000 : nvlddmkm+0x3003f6


SYMBOL_NAME:  nvlddmkm+3003f6

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND: .process /r /p 0xfffff803d83cef80; .thread 0xfffff803d83d1640 ; kb

BUCKET_ID_FUNC_OFFSET:  3003f6

FAILURE_BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

Followup:     MachineOwner
---------
Aslında dün volt değerlerini atarken yaptığım testler arasında OCCT testi vardı ve bir problem yaşamadım. Tekrardan çalıştırıp bakacağım ikisine de.

Driver olarak 577 veya 576 sürümü kurun derim. Son sürümlerde absürt sıkıntılar var. Bir ara ısı sensörü yanlış okuduğuna dair bilgi okumuştum tam emin değilim.
Tam olarak 5dk önce 576'yı kurdum ben de. Özellikle 580'i yükledikten sonra oyunlarda ciddi fps düşüşü gözlemledim.
 
Aslında dün volt değerlerini atarken yaptığım testler arasında OCCT testi vardı ve bir problem yaşamadım. Tekrardan çalıştırıp bakacağım ikisine de.

Tam olarak 5dk önce 576'yı kurdum ben de. Özellikle 580'i yükledikten sonra oyunlarda ciddi FPS düşüşü gözlemledim.
Zaten son sürümleri sıkıntılı vaziyette. Aklına gelecek ne varsa absürt sıkıntıları var. FPS düşüşü, sistem kararlığı bozulması, ekran kartını çökertmesi, ekran kararması gibi.
 
@Raphoras

Sisteminde .DMP dosyası içinde ekran kartı ile ilgili sorun görünüyor. Siz DDU ile kaldırıp yüklediğinizi söylediniz lakin sizden Furmark testi ve OCCT 3D / VRAM testi yapmanızı istiyorum herhangi bir kapanma olursa veya error code görürseniz OCCT üzerinde buradan bildirin şuan sorun tamamen ekran kartı.

İndirme Link:
Testleri yapın paylaşın görsel olarak.

Kod:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: fffff803d83c43b0, 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: 1984

    Key  : Analysis.Elapsed.mSec
    Value: 7377

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27871.1001

    Key  : Analysis.Version.Description
    Value: 10.2505.01.02 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2505.1.2

    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_ISR_nvlddmkm!unknown_function

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

    Key  : Stack.Pointer
    Value: ISR


BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff803d83c43b0

BUGCHECK_P4: 0

FILE_IN_CAB:  081225-12609-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008
  Kernel Generated Triage Dump

FAULTING_THREAD:  fffff803d83d1640

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
fffff803`6b2dcc28 fffff803`d77e4866     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff803`d83c43b0 : nt!KeBugCheckEx
fffff803`6b2dcc30 fffff803`d77e3d9a     : 00000000`00000000 ffffb600`7acd4400 fffff780`00000320 fffff803`65e17180 : nt!KeAccumulateTicks+0x596
fffff803`6b2dcca0 fffff803`d7755361     : 00000122`e788a8b3 fffff803`6b2cc100 fffff803`65e17180 fffff803`6b2cc200 : nt!KiUpdateRunTime+0xca
fffff803`6b2dce60 fffff803`d7755cbb     : fffff803`d8210bb0 00000000`00000000 fffff803`d8210c60 fffff803`d838e850 : nt!KeClockInterruptNotify+0x431
fffff803`6b2dcf50 fffff803`d7aa657e     : ffffa60b`455cf002 fffff803`d8210bb0 00013aac`25f64240 00000122`e84d78cd : nt!KiCallInterruptServiceRoutine+0x31b
fffff803`6b2dcfb0 fffff803`d7aa6d8c     : 00000000`00000000 00001fa0`00000200 00000000`00000025 00000000`00000002 : nt!KiInterruptSubDispatchNoLockNoEtw+0x4e
fffff803`6b2cc1d0 fffff803`7c0003f6     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x3c
fffff803`6b2cc360 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 ffffa60b`455cf000 : nvlddmkm+0x3003f6


SYMBOL_NAME:  nvlddmkm+3003f6

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND: .process /r /p 0xfffff803d83cef80; .thread 0xfffff803d83d1640 ; kb

BUCKET_ID_FUNC_OFFSET:  3003f6

FAILURE_BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

Followup:     MachineOwner
---------
OCCT de yaptığım 3d testinin 12. dakikasında siyah ekran akabinde reset atma problemini yaşadım. Crash sonrası ise programda bir error gözükmüyor ama PCI girişinin voltaj değeri gözüme çarptı. Furmark da bir problem çıkmadı.
 

Dosya Ekleri

  • OCCT.webp
    OCCT.webp
    105,3 KB · Görüntüleme: 48