Çözüldü Undervolt sonrası mavi ekran

AhmetEfee · 2 Temmuz 2023

Arkadaşlar undervolt yaptım dün. 2 Kere mavi ekran hatası oldu. Sistem tekrar açılınca AMD Software: Adrenelin Edition'dan yaptığım undervolt ayarları sıfırlandı. Ne yapmam lazım? Ekran kartı RX 580. İşlemci Ryzen 5 2600. Mimidump dosyaları: Google Drive: Sign-in

EgeN7 · 2 Temmuz 2023

Evet, undervolt sonrası böyle problemler oluşabiliyor. Undervolt stabil olmayabilir veya "silicon lottery" dediğimiz silikon kalitesi şansınıza iyi denk gelmemiş olabilir.

Örnek olarak;
- DPC_WATCHDOG_VIOLATION after Undervolt
- DPC_WATCHDOG_VIOLATION Mavi Ekran Hatası

Yalnız siz ekran kartınıza undervolt yapmışsınız galiba. Benim üstte bahsettiğim konu işlemci ile alakalıydı. Gerçi aşağı yukarı aynı şeyler ekran kartı için de geçerli.

Tavsiyem aşağıdaki kategoriye RX580 için nasıl undervolt yapılacağına dair bir konu açmanız, bilgisi olan arkadaşlar mutlaka yardımcı olacaktır. Veya generic, basic diye adlandırdığımız undervolt rehberlerini uygulayabilirsiniz. Ama tabii ki her ekran kartına uymayacaktır o yüzden size özel bir konu açın mutlaka. Çünkü mavi ekranın undervolt sonrasında gerçekleştiğini açıkça belirtmişsiniz. Mavi ekran ile alakalı yapılabilecek bir şey yok daha fazla.

Overclock ve Soğutma

Su, Hava ve LN2 soğutmanın yanında hız aşırma tutkunlarının buluşma noktası.

www.technopat.net

Döküm:

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: fffff8075a31c340, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
Arg4: 0000000000000000

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: 2327

    Key  : Analysis.Elapsed.mSec
    Value: 7097

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Failure.Bucket
    Value: 0x133_ISR_nt!KeAccumulateTicks

    Key  : Failure.Hash
    Value: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1


BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8075a31c340

BUGCHECK_P4: 0

FILE_IN_CAB:  070223-8828-01.dmp

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  ffffd7867a5250a0 -- (.trap 0xffffd7867a5250a0)
Unable to read trap frame at ffffd786`7a5250a0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffffb080`6addacc8 fffff807`598deed1     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff807`5a31c340 : nt!KeBugCheckEx
ffffb080`6addacd0 fffff807`598de74c     : 000033c3`2f71c38c ffffb080`6adc0180 00000000`003a1df1 00000000`00000202 : nt!KeAccumulateTicks+0x231
ffffb080`6addad30 fffff807`598dc801     : 00000000`00000000 00000000`00000000 ffffb080`6adc0180 00000000`00000000 : nt!KiUpdateRunTime+0xcc
ffffb080`6addaea0 fffff807`598dc219     : fffff807`5a25fe90 00000000`00000001 00000000`00000001 00000000`00000008 : nt!KeClockInterruptNotify+0xc1
ffffb080`6addaf40 fffff807`5991757c     : 0000008a`91ff3a6a ffff8003`e3f49c40 ffff8003`e3f49cf0 00000000`00000000 : nt!HalpTimerClockInterrupt+0x109
ffffb080`6addaf70 fffff807`59a2e3da     : ffffd786`7a525120 ffff8003`e3f49c40 00000000`ca62d346 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x9c
ffffb080`6addafb0 fffff807`59a2ec47     : ffffd786`7a5252f0 ffff8003`e3f49c40 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffd786`7a5250a0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37


SYMBOL_NAME:  nt!KeAccumulateTicks+231

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.1848

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  231

FAILURE_BUCKET_ID:  0x133_ISR_nt!KeAccumulateTicks

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

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


*******************************************************************************
*                                                                             *
*                        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: fffff8034e51c340, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
Arg4: 0000000000000000

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: 2250

    Key  : Analysis.Elapsed.mSec
    Value: 9493

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Failure.Bucket
    Value: 0x133_ISR_nt!KeAccumulateTicks

    Key  : Failure.Hash
    Value: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1


BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8034e51c340

BUGCHECK_P4: 0

FILE_IN_CAB:  070123-10234-01.dmp

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  ffff82059fb63810 -- (.trap 0xffff82059fb63810)
Unable to read trap frame at ffff8205`9fb63810

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffff8680`86900cc8 fffff803`4dadeed1     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff803`4e51c340 : nt!KeBugCheckEx
ffff8680`86900cd0 fffff803`4dade74c     : 00052679`b9208a18 ffff8680`868e6180 00000000`0554aa9c 00000000`00000202 : nt!KeAccumulateTicks+0x231
ffff8680`86900d30 fffff803`4dadc801     : 00000000`00000000 00000000`00000000 ffff8680`868e6180 00000000`00000000 : nt!KiUpdateRunTime+0xcc
ffff8680`86900ea0 fffff803`4dadc219     : fffff803`4e45fe00 00000000`00000001 00000000`00000001 00000000`00000008 : nt!KeClockInterruptNotify+0xc1
ffff8680`86900f40 fffff803`4db1757c     : 00000cb5`e098769a ffffd28f`43b2a500 ffffd28f`43b2a5b0 00000000`00000000 : nt!HalpTimerClockInterrupt+0x109
ffff8680`86900f70 fffff803`4dc2e3da     : ffff8205`9fb63890 ffffd28f`43b2a500 00000000`eb5f3ad3 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x9c
ffff8680`86900fb0 fffff803`4dc2ec47     : ffff8205`9fb63a60 ffffd28f`43b2a500 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff8205`9fb63810 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37


SYMBOL_NAME:  nt!KeAccumulateTicks+231

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.1848

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  231

FAILURE_BUCKET_ID:  0x133_ISR_nt!KeAccumulateTicks

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

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

Çözüldü Undervolt sonrası mavi ekran

Ayrıntılı düzenleme

AhmetEfee

Hectopat

EgeN7

Overclock ve Soğutma

EgeN7

Megapat

Overclock ve Soğutma

Benzer konular

Yeni konular

Yeni mesajlar

Gizliliğinize önem veriyoruz