R5 5600 RX 580 sistemde oyun oynarken mavi ekran hatası

İşletim sistemi
Windows 11

arzeNNN

Femtopat
Katılım
18 Ağustos 2022
Mesajlar
17
Daha fazla  
Cinsiyet
Erkek
RAM
Adata XPG Gammix 8GB 3600 MHz DDR4 CL18 Ram (2 tane var)
SSD veya HDD modeli
Samsung 970 Evo Plus
Ekran kartı
RX 580 4GB
Anakart
Msi pro b550m-p gen3
İşlemci
Ryzen 5 5600
Arkadaşlar oyun oynarken bir anda mavi ekran hatası aldım aşağıya hata dosyasını ve sistem bilgilerimi bırakıyorum.

Ryzen 5 5600.
RX 580 4 GB.
Samsung 970 EVO Plus.
MSI Pro B550M-P gen 3
16 GB RAM.

 
Rich (BB code):
CPU#0
--------------------------------------------------
Current DPC: No Active DPC

Pending DPCs:
----------------------------------------
CPU Type      KDPC       Function
 0: Normal  : 0xffffde0f2599ddb8 0xfffff807c3ef1010 HDAudBus!HdaController::NotificationDpc
 0: Normal  : 0xffffde0f258f53f8 0xfffff8076c477800 ndis!ndisInterruptDpc
 0: Normal  : 0xfffff8076823bc20 0xfffff807678b1b40 nt!PpmCheckPeriodicStart
 0: Normal  : 0xfffff80768242240 0xfffff80767977070 nt!KiBalanceSetManagerDeferredRoutine
 0: Normal  : 0xffffde0f1b9fc278 0xfffff807679eb870 nt!EtwpLoggerDpc
 0: Threaded: 0xfffff807648d0758 0xfffff80767b6bfc0 nt!KiDpcWatchdog

Name:HDAudBus.sys
Info:High Definition Audio Bus Driver
Source:Windows Update

* İlk etapta ses sürücüsünde bir problem görüyorum.
* Kullandığınız anakarttaki ses çipinin sürücüsüne güncelleme gelmiş. Sizdeki eski.
* Eskisini silip yenisini kurabilirsiniz.
msedge_NN7F4D0XTc.png



* Aygıt yöneticisinde sarı ünlemli herhangi bir aygıt var mı bu arada?

* Bunun dışında, araya kaynamış bir AMD sürücüsü var.
Rich (BB code):
STACK_TEXT:
nt!KeBugCheckEx
nt!KeAccumulateTicks+0x23f
nt!KiUpdateRunTime+0xf4
nt!KiUpdateTime+0x13e3
nt!KeClockInterruptNotify+0x3de
nt!HalpTimerClockInterrupt+0x10a
nt!KiCallInterruptServiceRoutine+0x19e
nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
nt!KiInterruptDispatchNoLockNoEtw+0x37
nt!KxWaitForSpinLockAndAcquire+0x26
nt!KiCallInterruptServiceRoutine+0x15b
nt!KiInterruptSubDispatch+0x11f
nt!KiInterruptDispatch+0x37
amdkmdag+0xc6ab3
0xffffde0f`25175070
0xffffde0f`25fb7860

amdkmdag.sys =AMD kernel sürücüsü - AMD grafik sürücüsü

* Sorun yüksek ihtimalle ses sürücüsündendi, ama her ihtimale karşı DDU yardımıyla AMD ekran kartı sürücülerinizi temizleyip güncelini yükleyebilirsiniz.

- Güncel sürücüyü indirin: Radeon™ RX 580 Drivers & Support
- İnterneti kesin.
- Daha sonra DDU ile Sürücü Kaldırma rehberini takip edin.
- Sürücüyü kaldırdıktan sonra bilgisayar yeniden başlayacak.
- Bilgisayar açılınca indirdiğiniz sürücüyü kurun.
- İşlemler bitince interneti bağlayın.


* BIOS'a güncelleme gelmiş. Güncelleyebilirsiniz.

* Bu arada, chipset sürücülerinizi nereden yüklüyorsunuz bilmiyorum ama anakartın kendi destek sayfasındaki sürücüler biraz geriden geliyor, özellikle MSI tarafında gördüğüm kadarıyla böyle. AMD sitesinden yüklemenizi tavsiye ederim.



* Tüm bunlar sonucunda tekrar mavi ekran alırsanız yeni döküm dosyalarınızı paylaşırsınız.


* Bu arada RAM'ler A2 ve B2'de takılı değil mi? 2. ve 4. slotlara, yani aralıklı şekilde?


msedge_xUPMRV0Mbb.png




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: fffff8076831c340, 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: 1734

    Key  : Analysis.Elapsed.mSec
    Value: 4725

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Dump.Attributes.AsUlong
    Value: 1008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    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_nt!KeAccumulateTicks

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


BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8076831c340

BUGCHECK_P4: 0

FILE_IN_CAB:  060223-10453-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
fffff807`6cdd3738 fffff807`678bb8ff     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff807`6831c340 : nt!KeBugCheckEx
fffff807`6cdd3740 fffff807`678ba744     : 00001593`46acb32e 0000000f`bda57b66 00000000`00069a26 00000000`00000000 : nt!KeAccumulateTicks+0x23f
fffff807`6cdd37a0 fffff807`678ba623     : 00000000`0000000c 00000000`00000000 fffff807`648c8180 0000000f`bda1e201 : nt!KiUpdateRunTime+0xf4
fffff807`6cdd3960 fffff807`678b884e     : 00000000`00000000 fffff807`648c8180 ffffffff`ffffffff 00000000`00000006 : nt!KiUpdateTime+0x13e3
fffff807`6cdd3c20 fffff807`678b805a     : fffff807`6825ff60 fffff807`6830dfa0 fffff807`6830dfa0 00000000`00000000 : nt!KeClockInterruptNotify+0x3de
fffff807`6cdd3cd0 fffff807`6794b3be     : 0000000f`bde84e08 fffff807`6830def0 fffff807`648c8180 fffff807`67a2d7eb : nt!HalpTimerClockInterrupt+0x10a
fffff807`6cdd3d00 fffff807`67a2da4a     : fffff807`6cdd3e10 fffff807`6830def0 ffffde0f`2216d270 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x19e
fffff807`6cdd3d40 fffff807`67a2e2b7     : 00000000`00000000 fffff807`be13c758 ffffde0f`20ee3000 fffff807`6cdd3e69 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff807`6cdd3d90 fffff807`678b24d6     : ffffa801`abdbd8c0 00000000`00000002 ffffde0f`2c992f01 fffff00d`8a84e290 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff807`6cdd3f20 fffff807`6794b37b     : ffffa801`abdbd8c0 fffff807`6789407c ffffde0f`25175070 ffffa801`abdbd8c0 : nt!KxWaitForSpinLockAndAcquire+0x26
fffff807`6cdd3f50 fffff807`67a2d7cf     : fffff00d`8a84e290 ffffa801`abdbd8c0 00000000`00003255 ffffde0f`2cb0a000 : nt!KiCallInterruptServiceRoutine+0x15b
fffff807`6cdd3f90 fffff807`67a2da97     : 00000000`00000000 fffff807`be0d9005 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatch+0x11f
fffff00d`8a84e210 fffff807`bdfc6ab3     : ffffde0f`25175070 ffffde0f`25fb7860 00000000`00000000 fffff00d`8a84e6c0 : nt!KiInterruptDispatch+0x37
fffff00d`8a84e3a0 ffffde0f`25175070     : ffffde0f`25fb7860 00000000`00000000 fffff00d`8a84e6c0 fffff807`be5e4000 : amdkmdag+0xc6ab3
fffff00d`8a84e3a8 ffffde0f`25fb7860     : 00000000`00000000 fffff00d`8a84e6c0 fffff807`be5e4000 fffff00d`8a846a18 : 0xffffde0f`25175070
fffff00d`8a84e3b0 00000000`00000000     : fffff00d`8a84e6c0 fffff807`be5e4000 fffff00d`8a846a18 ffffde0f`25175078 : 0xffffde0f`25fb7860


SYMBOL_NAME:  nt!KeAccumulateTicks+23f

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.1702

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  23f

FAILURE_BUCKET_ID:  0x133_ISR_nt!KeAccumulateTicks

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

Followup:     MachineOwner
---------
 
Son düzenleme:
Rich (BB code):
CPU#0
--------------------------------------------------
Current DPC: No Active DPC.

Pending DPCs:
----------------------------------------
CPU Type KDPC Function.
 0: Normal : 0xffffde0f2599ddb8 0xfffff807c3ef1010 HDAudBus!HdaController::NotificationDpc
 0: Normal : 0xffffde0f258f53f8 0xfffff8076c477800 ndis!ndisInterruptDpc
 0: Normal : 0xfffff8076823bc20 0xfffff807678b1b40 nt!PpmCheckPeriodicStart
 0: Normal : 0xfffff80768242240 0xfffff80767977070 nt!KiBalanceSetManagerDeferredRoutine
 0: Normal : 0xffffde0f1b9fc278 0xfffff807679eb870 nt!EtwpLoggerDpc
 0: Threaded: 0xfffff807648d0758 0xfffff80767b6bfc0 nt!KiDpcWatchdog

Name:HDAudBus.sys
Info:High Definition Audio Bus Driver
Source:Windows Update

* İlk etapta ses sürücüsünde bir problem görüyorum.
* Kullandığınız anakarttaki ses çipinin sürücüsüne güncelleme gelmiş. Sizdeki eski.
* Eskisini silip yenisini kurabilirsiniz.
Eki Görüntüle 1803902

* Aygıt yöneticisinde sarı ünlemli herhangi bir aygıt var mı bu arada?

* Bunun dışında, araya kaynamış bir AMD sürücüsü var.
Rich (BB code):
STACK_TEXT:
nt!KeBugCheckEx
nt!KeAccumulateTicks+0x23f
nt!KiUpdateRunTime+0xf4
nt!KiUpdateTime+0x13e3
nt!KeClockInterruptNotify+0x3de
nt!HalpTimerClockInterrupt+0x10a
nt!KiCallInterruptServiceRoutine+0x19e
nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
nt!KiInterruptDispatchNoLockNoEtw+0x37
nt!KxWaitForSpinLockAndAcquire+0x26
nt!KiCallInterruptServiceRoutine+0x15b
nt!KiInterruptSubDispatch+0x11f
nt!KiInterruptDispatch+0x37
amdkmdag+0xc6ab3
0xffffde0f`25175070
0xffffde0f`25fb7860

amdkmdag.sys =AMD kernel sürücüsü - AMD grafik sürücüsü.

* Sorun yüksek ihtimalle ses sürücüsündendi, ama her ihtimale karşı DDU yardımıyla AMD ekran kartı sürücülerinizi temizleyip güncelini yükleyebilirsiniz.

- Güncel sürücüyü indirin: Radeon™ RX 580 Drivers & Support
- İnterneti kesin.
- Daha sonra DDU ile Sürücü Kaldırma rehberini takip edin.
- Sürücüyü kaldırdıktan sonra bilgisayar yeniden başlayacak.
- Bilgisayar açılınca indirdiğiniz sürücüyü kurun.
- İşlemler bitince interneti bağlayın.

* BIOS'a güncelleme gelmiş. Güncelleyebilirsiniz.

* Bu arada, chipset sürücülerinizi nereden yüklüyorsunuz bilmiyorum ama anakartın kendi destek sayfasındaki sürücüler biraz geriden geliyor, özellikle MSI tarafında gördüğüm kadarıyla böyle. AMD sitesinden yüklemenizi tavsiye ederim.


* Tüm bunlar sonucunda tekrar mavi ekran alırsanız yeni döküm dosyalarınızı paylaşırsınız.

* Bu arada RAM'ler A2 ve b2'de takılı değil mi? 2. ve 4. slotlara, yani aralıklı şekilde?

Eki Görüntüle 1803915

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: fffff8076831c340, 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: 1734.

 Key : Analysis.Elapsed.mSec
 Value: 4725.

 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: 6442.

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

 Key : Bugcheck.Code.LegacyAPI
 Value: 0x133.

 Key : Dump.Attributes.AsUlong
 Value: 1008.

 Key : Dump.Attributes.DiagDataWrittenToHeader
 Value: 1

 Key : Dump.Attributes.ErrorCode
 Value: 0

 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_nt!KeAccumulateTicks

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

BUGCHECK_CODE: 133.

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00.

BUGCHECK_P3: fffff8076831c340.

BUGCHECK_P4: 0

FILE_IN_CAB: 060223-10453-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008.
 Kernel Generated Triage Dump.

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System.

STACK_TEXT:
fffff807`6cdd3738 fffff807`678bb8ff : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff807`6831c340 : nt!KeBugCheckEx
fffff807`6cdd3740 fffff807`678ba744 : 00001593`46acb32e 0000000f`bda57b66 00000000`00069a26 00000000`00000000 : nt!KeAccumulateTicks+0x23f
fffff807`6cdd37a0 fffff807`678ba623 : 00000000`0000000c 00000000`00000000 fffff807`648c8180 0000000f`bda1e201 : nt!KiUpdateRunTime+0xf4
fffff807`6cdd3960 fffff807`678b884e : 00000000`00000000 fffff807`648c8180 ffffffff`ffffffff 00000000`00000006 : nt!KiUpdateTime+0x13e3
fffff807`6cdd3c20 fffff807`678b805a : fffff807`6825ff60 fffff807`6830dfa0 fffff807`6830dfa0 00000000`00000000 : nt!KeClockInterruptNotify+0x3de
fffff807`6cdd3cd0 fffff807`6794b3be : 0000000f`bde84e08 fffff807`6830def0 fffff807`648c8180 fffff807`67a2d7eb : nt!HalpTimerClockInterrupt+0x10a
fffff807`6cdd3d00 fffff807`67a2da4a : fffff807`6cdd3e10 fffff807`6830def0 ffffde0f`2216d270 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x19e
fffff807`6cdd3d40 fffff807`67a2e2b7 : 00000000`00000000 fffff807`be13c758 ffffde0f`20ee3000 fffff807`6cdd3e69 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff807`6cdd3d90 fffff807`678b24d6 : ffffa801`abdbd8c0 00000000`00000002 ffffde0f`2c992f01 fffff00d`8a84e290 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff807`6cdd3f20 fffff807`6794b37b : ffffa801`abdbd8c0 fffff807`6789407c ffffde0f`25175070 ffffa801`abdbd8c0 : nt!KxWaitForSpinLockAndAcquire+0x26
fffff807`6cdd3f50 fffff807`67a2d7cf : fffff00d`8a84e290 ffffa801`abdbd8c0 00000000`00003255 ffffde0f`2cb0a000 : nt!KiCallInterruptServiceRoutine+0x15b
fffff807`6cdd3f90 fffff807`67a2da97 : 00000000`00000000 fffff807`be0d9005 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatch+0x11f
fffff00d`8a84e210 fffff807`bdfc6ab3 : ffffde0f`25175070 ffffde0f`25fb7860 00000000`00000000 fffff00d`8a84e6c0 : nt!KiInterruptDispatch+0x37
fffff00d`8a84e3a0 ffffde0f`25175070 : ffffde0f`25fb7860 00000000`00000000 fffff00d`8a84e6c0 fffff807`be5e4000 : amdkmdag+0xc6ab3
fffff00d`8a84e3a8 ffffde0f`25fb7860 : 00000000`00000000 fffff00d`8a84e6c0 fffff807`be5e4000 fffff00d`8a846a18 : 0xffffde0f`25175070
fffff00d`8a84e3b0 00000000`00000000 : fffff00d`8a84e6c0 fffff807`be5e4000 fffff00d`8a846a18 ffffde0f`25175078 : 0xffffde0f`25fb7860

SYMBOL_NAME: nt!KeAccumulateTicks+23f

MODULE_NAME: nt.

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.22621.1702

STACK_COMMAND: .cxr; .ecxr ; kb.

BUCKET_ID_FUNC_OFFSET: 23f.

FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

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

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

Dediklerinizi yaptım fakat bir daha mavi ekran yedim.

 
* Bir önceki mavi ekranda olan sorunlar yok.
* İşlemciye uygulanan bir undervolt veya overclock ile alakalı bir durum olabilir.
* BIOS'tan veya Ryzen Master'dan böyle bir işlem gerçekleştirdiniz mi?
* Stabil olmayabilir. Yaptıysanız geri çekin şimdilik.

* RAM'ler A2 ve B2'ye takılı değil mi?

* BIOS hala güncel değil, bir ara güncelleyin.

* RAM'leri XMP açık kullanıyorsunuz değil mi?

RAM'lere OC uygularken:
  • XMP profili ile mi seçim yaptınız?
  • Yoksa elle frekans seçimi/voltaj/timing vs. değişimi mi yaptınız?


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

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000010, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffff8200a5bc5180, The PRCB address of the hung processor.
Arg4: 0000000000000004, The index of the hung processor.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1530

    Key  : Analysis.Elapsed.mSec
    Value: 2460

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x101

    Key  : Dump.Attributes.AsUlong
    Value: 1008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

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

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

    Key  : Failure.Hash
    Value: {95498f51-33a9-903b-59e5-d236937d8ecf}


BUGCHECK_CODE:  101

BUGCHECK_P1: 10

BUGCHECK_P2: 0

BUGCHECK_P3: ffff8200a5bc5180

BUGCHECK_P4: 4

FILE_IN_CAB:  060423-10531-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump

FAULTING_PROCESSOR: 4

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Red Giant Serv

STACK_TEXT:
fffff802`447939a8 fffff802`40c9f258     : 00000000`00000101 00000000`00000010 00000000`00000000 ffff8200`a5bc5180 : nt!KeBugCheckEx
fffff802`447939b0 fffff802`40aba744     : 00000000`00000000 0000001a`8ab5d304 00000000`000b2468 00000000`00000000 : nt!KeAccumulateTicks+0x1e3b98
fffff802`44793a10 fffff802`40aba623     : 00000000`0000000c 00000000`00000000 fffff802`3c30e180 0000001a`90abf401 : nt!KiUpdateRunTime+0xf4
fffff802`44793bd0 fffff802`40ab884e     : 00000000`00000000 fffff802`3c30e180 ffffffff`ffffffff 00000000`0000000c : nt!KiUpdateTime+0x13e3
fffff802`44793e90 fffff802`40ab805a     : fffff802`4145fed0 fffff802`4150dfa0 fffff802`4150dfa0 00000000`00000000 : nt!KeClockInterruptNotify+0x3de
fffff802`44793f40 fffff802`40b4b3be     : 0000001a`90f22f70 fffff802`4150def0 fffff802`3c30e180 00000000`00000000 : nt!HalpTimerClockInterrupt+0x10a
fffff802`44793f70 fffff802`40c2da4a     : ffff9c04`66a66a90 fffff802`4150def0 fffff802`3c30e180 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x19e
fffff802`44793fb0 fffff802`40c2e2b7     : 00000000`264b7455 00000000`00000000 ffff9c04`66a66c28 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff9c04`66a66a10 fffff802`40ab0900     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff802`40baa000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff9c04`66a66ba0 fffff802`40ab1061     : 00000000`00000000 00000000`00000001 ffff9c04`66a66c28 ffff9c04`66a66c20 : nt!KiIpiStallOnPacketTargetsPrcb+0x10
ffff9c04`66a66bd0 fffff802`40f3449c     : 00000000`00000000 ffff9c04`66a67b20 00000000`00000000 00000000`00000001 : nt!KeFlushProcessWriteBuffers+0xd9
ffff9c04`66a66c20 fffff802`40eb3325     : ffffb504`cb31b080 00000000`00010000 fffff802`4150eb80 00000000`00000000 : nt!ExpGetProcessInformation+0x17c
ffff9c04`66a67230 fffff802`40eb24f9     : fffff802`40c27810 0000008e`e16ffae0 0000008e`e16ffac8 00000000`00000000 : nt!ExpQuerySystemInformation+0xcf5
ffff9c04`66a67a60 fffff802`40c406e8     : 0000024c`cae10000 ffffb504`cceb2080 00000000`00000000 0000024c`cad27ce0 : nt!NtQuerySystemInformation+0x79
ffff9c04`66a67aa0 00007ff8`8f7cf314     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
0000008e`e16feec8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`8f7cf314


SYMBOL_NAME:  nt!KeAccumulateTicks+1e3b98

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.1702

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1e3b98

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {95498f51-33a9-903b-59e5-d236937d8ecf}

Followup:     MachineOwner
---------
 
* Bir önceki mavi ekranda olan sorunlar yok.
* İşlemciye uygulanan bir undervolt veya overclock ile alakalı bir durum olabilir.
* BIOS'tan veya Ryzen Master'dan böyle bir işlem gerçekleştirdiniz mi?
* Stabil olmayabilir. Yaptıysanız geri çekin şimdilik.

* RAM'ler A2 ve b2'ye takılı değil mi?

* BIOS hala güncel değil, bir ara güncelleyin.

* RAM'leri XMP açık kullanıyorsunuz değil mi?

RAM'lere OC uygularken:
  • XMP profili ile mi seçim yaptınız?
  • Yoksa elle frekans seçimi/voltaj/timing vs. değişimi mi yaptınız?

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

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an.
MP system within the allocated interval. This indicates that the specified.
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000010, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffff8200a5bc5180, The PRCB address of the hung processor.
Arg4: 0000000000000004, The index of the hung processor.

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

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 1530.

 Key : Analysis.Elapsed.mSec
 Value: 2460.

 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: 217.

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

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

 Key : Bugcheck.Code.LegacyAPI
 Value: 0x101.

 Key : Dump.Attributes.AsUlong
 Value: 1008.

 Key : Dump.Attributes.DiagDataWrittenToHeader
 Value: 1

 Key : Dump.Attributes.ErrorCode
 Value: 0

 Key : Dump.Attributes.KernelGeneratedTriageDump
 Value: 1

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

 Key : Dump.Attributes.ProgressPercentage
 Value: 0

 Key : Failure.Bucket
 Value: CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

 Key : Failure.Hash
 Value: {95498f51-33a9-903b-59e5-d236937d8ecf}

BUGCHECK_CODE: 101.

BUGCHECK_P1: 10.

BUGCHECK_P2: 0

BUGCHECK_P3: ffff8200a5bc5180.

BUGCHECK_P4: 4

FILE_IN_CAB: 060423-10531-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008.
 Kernel Generated Triage Dump.

FAULTING_PROCESSOR: 4

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Red Giant Serv.

STACK_TEXT:
fffff802`447939a8 fffff802`40c9f258 : 00000000`00000101 00000000`00000010 00000000`00000000 ffff8200`a5bc5180 : nt!KeBugCheckEx
fffff802`447939b0 fffff802`40aba744 : 00000000`00000000 0000001a`8ab5d304 00000000`000b2468 00000000`00000000 : nt!KeAccumulateTicks+0x1e3b98
fffff802`44793a10 fffff802`40aba623 : 00000000`0000000c 00000000`00000000 fffff802`3c30e180 0000001a`90abf401 : nt!KiUpdateRunTime+0xf4
fffff802`44793bd0 fffff802`40ab884e : 00000000`00000000 fffff802`3c30e180 ffffffff`ffffffff 00000000`0000000c : nt!KiUpdateTime+0x13e3
fffff802`44793e90 fffff802`40ab805a : fffff802`4145fed0 fffff802`4150dfa0 fffff802`4150dfa0 00000000`00000000 : nt!KeClockInterruptNotify+0x3de
fffff802`44793f40 fffff802`40b4b3be : 0000001a`90f22f70 fffff802`4150def0 fffff802`3c30e180 00000000`00000000 : nt!HalpTimerClockInterrupt+0x10a
fffff802`44793f70 fffff802`40c2da4a : ffff9c04`66a66a90 fffff802`4150def0 fffff802`3c30e180 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x19e
fffff802`44793fb0 fffff802`40c2e2b7 : 00000000`264b7455 00000000`00000000 ffff9c04`66a66c28 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff9c04`66a66a10 fffff802`40ab0900 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff802`40baa000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff9c04`66a66ba0 fffff802`40ab1061 : 00000000`00000000 00000000`00000001 ffff9c04`66a66c28 ffff9c04`66a66c20 : nt!KiIpiStallOnPacketTargetsPrcb+0x10
ffff9c04`66a66bd0 fffff802`40f3449c : 00000000`00000000 ffff9c04`66a67b20 00000000`00000000 00000000`00000001 : nt!KeFlushProcessWriteBuffers+0xd9
ffff9c04`66a66c20 fffff802`40eb3325 : ffffb504`cb31b080 00000000`00010000 fffff802`4150eb80 00000000`00000000 : nt!ExpGetProcessInformation+0x17c
ffff9c04`66a67230 fffff802`40eb24f9 : fffff802`40c27810 0000008e`e16ffae0 0000008e`e16ffac8 00000000`00000000 : nt!ExpQuerySystemInformation+0xcf5
ffff9c04`66a67a60 fffff802`40c406e8 : 0000024c`cae10000 ffffb504`cceb2080 00000000`00000000 0000024c`cad27ce0 : nt!NtQuerySystemInformation+0x79
ffff9c04`66a67aa0 00007ff8`8f7cf314 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
0000008e`e16feec8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`8f7cf314

SYMBOL_NAME: nt!KeAccumulateTicks+1e3b98

MODULE_NAME: nt.

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.22621.1702

STACK_COMMAND: .cxr; .ecxr ; kb.

BUCKET_ID_FUNC_OFFSET: 1e3b98.

FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {95498f51-33a9-903b-59e5-d236937d8ecf}

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

RAM'ler A2 ve b2ye takılı ve XMP profile 1 olarak ayarlı.
BIOS'tan veya Ryzen Master'dan hiçbir şeye ellemedim.
 
BlueStacks var sistemde. Yeni bir sürümü gelmişse güncelleyin.

BlueStacks kullanmıyorsanız kaldırın. Kullanıyorsanız:
BIOS'ta SVM açık mı? Disabled ise Enabled yapın.

Tekrar hata alırsanız yenisini paylaşın.

Bu arada Samsung Magician güncel mi?

Bu sürede bir ara RAM testini aradan çıkartın. Şu an için gerekli olmayabilir, burada kalsın.
 
İlk etapta BlueStacks sizin için hayati öneme sahip değil ise kaldırın. Samsung Magician kaldırın.

BIOS güncelleyin.

 

Geri
Yukarı