Ryzen 5 2600 RX 570 Bilgisayar birden kapandı

HardPlayer

Kilopat
Katılım
15 Kasım 2014
Mesajlar
1.161
Çözümler
5
Yer
İstanbul
Daha fazla  
Cinsiyet
Erkek
Meslek
Graphic Designer
• Ryzen 5 2600 (OC ile 4.0 GHz)
• masterliquid ml240l
• MSI RX 570 Armor 4G
• Asus TUF B450 plus gaming
• Gskill Ripjaws 8x2 3000 MHz
• Cougar turret v2 rgb kasadaki psu 750W

Oyun oynuyordum bilgisayarda ve birden kapandı sistem. Anakartımın ışıkları yanmaya devam etti. Güç düğmesine birkaç kez bastım bilgisayar tepki vermedi. Arkadan tuşu kapadım, 10 saniye sonra açtım ve tekrardan güç tuşuna bastım bilgisayar açıldı. Prime95 ile low ve medium testleri yaptım 15 dk boyunca ama kapanmadı. OCCT ile de power testi, ve diğer testleri de yaptım temiz. Sebebi ne olabilir? Minidump dosyasını paylaşıyorum buraya.
 
Ekran kartı sürücüsü problem çıkarmış DDU ile kaldır tekrar yükle hata tekrarlanırsa AMD 2019 sürücüsü yükle.

Hatanın geçtiğine emin olana kadar Ryzen Master'ı kaldır.
Kod:
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. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff80617773358, 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 atikmdag.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


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  System manufacturer

SYSTEM_PRODUCT_NAME:  System Product Name

SYSTEM_SKU:  SKU

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  1820

BIOS_DATE:  09/12/2019

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  TUF B450-PLUS GAMING

BASEBOARD_VERSION:  Rev X.0x

DUMP_TYPE:  2

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff80617773358

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

CPU_COUNT: c

CPU_MHZ: f03

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 8

CPU_STEPPING: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x133

PROCESS_NAME:  ShadowOfWar.exe

CURRENT_IRQL:  d

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  01-29-2020 17:54:14.0252

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff806173ee8c1 to fffff806173c1220

STACK_TEXT: 
ffff8a80`44773b08 fffff806`173ee8c1 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff806`17773358 : nt!KeBugCheckEx
ffff8a80`44773b10 fffff806`1721f5dc : 000017cf`befd5df7 ffff8a80`44800180 00000000`0006a4e2 00000000`0006a4e2 : nt!KeAccumulateTicks+0x1cbea1
ffff8a80`44773b70 fffff806`1715e4b7 : fffff001`2b387720 fffff001`2b387400 fffff001`2b387480 00000000`00000002 : nt!KeClockInterruptNotify+0x98c
ffff8a80`44773f30 fffff806`172029e5 : 0000000f`d75ca2ca ffffbc8f`528b3600 ffffbc8f`528b36b0 00000000`00000000 : hal!HalpTimerClockInterrupt+0xf7
ffff8a80`44773f60 fffff806`173c2cba : fffff001`2b387480 ffffbc8f`528b3600 ffffbc8f`58eb7a48 ffffbc8f`528b3600 : nt!KiCallInterruptServiceRoutine+0xa5
ffff8a80`44773fb0 fffff806`173c3227 : fffff001`2b3875f0 fffff001`2b387480 ffffbc8f`528b3600 fffff806`173c32b4 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff001`2b387400 fffff806`1721b9eb : 00000000`00000010 00000000`00040202 fffff001`2b3875b8 00000000`00000018 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff001`2b387590 fffff806`17205e2a : 00000000`00000000 00000000`00000000 ffffbc8f`a0218080 00000000`00900000 : nt!KeYieldProcessorEx+0x1b
fffff001`2b3875c0 fffff806`1723ee7d : 00000000`5379bb14 00000000`00000000 00000000`00000000 00000000`00000008 : nt!KxWaitForLockOwnerShip+0x2a
fffff001`2b3875f0 fffff806`2538a327 : ffffbc8f`5940f4b0 00000000`00000000 00000000`00000001 fffff806`172377a7 : nt!KeAcquireInStackQueuedSpinLock+0x7d
fffff001`2b387620 ffffbc8f`5940f4b0 : 00000000`00000000 00000000`00000001 fffff806`172377a7 00000000`00000000 : atikmdag+0xca327
fffff001`2b387628 00000000`00000000 : 00000000`00000001 fffff806`172377a7 00000000`00000000 ffffbc8f`58eb7a91 : 0xffffbc8f`5940f4b0


THREAD_SHA1_HASH_MOD_FUNC:  71177e0a5e6dab3f9f8e9010ab29d8279bb091a8

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  859674ab42725ecc8067562cb7a470f91e867871

THREAD_SHA1_HASH_MOD:  fa9cf36acd85121dbaf6be6d6600bd3af5a6c56c

FOLLOWUP_IP:
atikmdag+ca327
fffff806`2538a327 33db            xor     ebx,ebx

FAULT_INSTR_CODE:  8d49db33

SYMBOL_STACK_INDEX:  a

SYMBOL_NAME:  atikmdag+ca327

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5d976fcf

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  ca327

FAILURE_BUCKET_ID:  0x133_ISR_atikmdag!unknown_function

BUCKET_ID:  0x133_ISR_atikmdag!unknown_function

PRIMARY_PROBLEM_CLASS:  0x133_ISR_atikmdag!unknown_function

TARGET_TIME:  2019-11-13T18:14:33.000Z

OSBUILD:  18362

OSSERVICEPACK:  418

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE: 

USER_LCID:  0

OSBUILD_TIMESTAMP:  unknown_date

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  a9c2

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x133_isr_atikmdag!unknown_function

FAILURE_ID_HASH:  {f4e621b5-c0d0-0526-442a-5fac58190602}

Followup:     MachineOwner
---------
 
Elektrik kesintisi olmuş olabilir düşük voltaj. Şebekeyle alakalı
Benlik bir durum mu bu? Bu arada elektrik gidip gelmedi çünkü öyle olsaydı pilsiz kardeşimin kullandığı laptop da kapanırdı diye düşünüyorum.
Ekran kartı sürücüsü problem çıkarmış DDU ile kaldır tekrar yükle hata tekrarlanırsa AMD 2019 sürücüsü yükle.

Hatanın geçtiğine emin olana kadar Ryzen Master'ı kaldır.
Kod:
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. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff80617773358, 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 atikmdag.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


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  System manufacturer

SYSTEM_PRODUCT_NAME:  System Product Name

SYSTEM_SKU:  SKU

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  1820

BIOS_DATE:  09/12/2019

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  TUF B450-PLUS GAMING

BASEBOARD_VERSION:  Rev X.0x

DUMP_TYPE:  2

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff80617773358

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

CPU_COUNT: c

CPU_MHZ: f03

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 8

CPU_STEPPING: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x133

PROCESS_NAME:  ShadowOfWar.exe

CURRENT_IRQL:  d

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  01-29-2020 17:54:14.0252

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff806173ee8c1 to fffff806173c1220

STACK_TEXT:
ffff8a80`44773b08 fffff806`173ee8c1 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff806`17773358 : nt!KeBugCheckEx
ffff8a80`44773b10 fffff806`1721f5dc : 000017cf`befd5df7 ffff8a80`44800180 00000000`0006a4e2 00000000`0006a4e2 : nt!KeAccumulateTicks+0x1cbea1
ffff8a80`44773b70 fffff806`1715e4b7 : fffff001`2b387720 fffff001`2b387400 fffff001`2b387480 00000000`00000002 : nt!KeClockInterruptNotify+0x98c
ffff8a80`44773f30 fffff806`172029e5 : 0000000f`d75ca2ca ffffbc8f`528b3600 ffffbc8f`528b36b0 00000000`00000000 : hal!HalpTimerClockInterrupt+0xf7
ffff8a80`44773f60 fffff806`173c2cba : fffff001`2b387480 ffffbc8f`528b3600 ffffbc8f`58eb7a48 ffffbc8f`528b3600 : nt!KiCallInterruptServiceRoutine+0xa5
ffff8a80`44773fb0 fffff806`173c3227 : fffff001`2b3875f0 fffff001`2b387480 ffffbc8f`528b3600 fffff806`173c32b4 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff001`2b387400 fffff806`1721b9eb : 00000000`00000010 00000000`00040202 fffff001`2b3875b8 00000000`00000018 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff001`2b387590 fffff806`17205e2a : 00000000`00000000 00000000`00000000 ffffbc8f`a0218080 00000000`00900000 : nt!KeYieldProcessorEx+0x1b
fffff001`2b3875c0 fffff806`1723ee7d : 00000000`5379bb14 00000000`00000000 00000000`00000000 00000000`00000008 : nt!KxWaitForLockOwnerShip+0x2a
fffff001`2b3875f0 fffff806`2538a327 : ffffbc8f`5940f4b0 00000000`00000000 00000000`00000001 fffff806`172377a7 : nt!KeAcquireInStackQueuedSpinLock+0x7d
fffff001`2b387620 ffffbc8f`5940f4b0 : 00000000`00000000 00000000`00000001 fffff806`172377a7 00000000`00000000 : atikmdag+0xca327
fffff001`2b387628 00000000`00000000 : 00000000`00000001 fffff806`172377a7 00000000`00000000 ffffbc8f`58eb7a91 : 0xffffbc8f`5940f4b0


THREAD_SHA1_HASH_MOD_FUNC:  71177e0a5e6dab3f9f8e9010ab29d8279bb091a8

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  859674ab42725ecc8067562cb7a470f91e867871

THREAD_SHA1_HASH_MOD:  fa9cf36acd85121dbaf6be6d6600bd3af5a6c56c

FOLLOWUP_IP:
atikmdag+ca327
fffff806`2538a327 33db            xor     ebx,ebx

FAULT_INSTR_CODE:  8d49db33

SYMBOL_STACK_INDEX:  a

SYMBOL_NAME:  atikmdag+ca327

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5d976fcf

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  ca327

FAILURE_BUCKET_ID:  0x133_ISR_atikmdag!unknown_function

BUCKET_ID:  0x133_ISR_atikmdag!unknown_function

PRIMARY_PROBLEM_CLASS:  0x133_ISR_atikmdag!unknown_function

TARGET_TIME:  2019-11-13T18:14:33.000Z

OSBUILD:  18362

OSSERVICEPACK:  418

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID:  0

OSBUILD_TIMESTAMP:  unknown_date

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  a9c2

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x133_isr_atikmdag!unknown_function

FAILURE_ID_HASH:  {f4e621b5-c0d0-0526-442a-5fac58190602}

Followup:     MachineOwner
---------
İki sorun olacak:

1) Güncellesem olur mu?
2) AMD 2019 sürücüsünden kastınız chipset mi?
 
Benlik bir durum mu bu? Bu arada elektrik gidip gelmedi çünkü öyle olsaydı pilsiz kardeşimin kullandığı laptop da kapanırdı diye düşünüyorum.
Bazen internet kafedeyken oluyor. 3 5 pc kapaniyor digerleri kapanmiyor. Her pc de kapanma olmuyor, anlık olay. Muhtemelen bir daha tekrar etmez.
 
Bazen internet kafedeyken oluyor. 3 5 pc kapaniyor digerleri kapanmiyor. Her pc de kapanma olmuyor, anlık olay. Muhtemelen bir daha tekrar etmez.
Ama internet de kapanmadı yani. Mesela bizde elektrik gidip gelince anlık olarak ev telefonu "bip bip" diye ses çıkarıyor bu da olmadı.
 
Arkadaşın dedigi gibi yazilimla alakalı da olabilir. Bende de 1050 de olmustu. Guncellemistim. Oyunu her asagi aldigimda mavi ekran aliyordum. Sonraki guncellemeyi bekleyin ve ya eski surumu yukleyin sorun o ise
 
Şuan 2019 WHQL olan yüklü. DDU ile kaldırıp son sürümü kuruyorum. İleriki zamanlarda bir daha böyle bir sorun olursa konu açarım. Bu arada komple kapanmasının sebebi nasıl oluyor da driver oluyor dolaylı yoldan mı? Bir de minidump dosyasında hatanın oluş tarihi bugün mü acaba çünkü birkaç hafta önce de olmuştu.
 

Dosya Ekleri

  • Adsızz.jpg
    Adsızz.jpg
    69,1 KB · Görüntüleme: 33
• Ryzen 5 2600 (OC ile 4.0 GHz)
• masterliquid ml240l
• MSI RX 570 Armor 4G
• Asus TUF B450 plus gaming
• Gskill Ripjaws 8x2 3000 MHz
• Cougar turret v2 rgb kasadaki psu 750W

Oyun oynuyordum bilgisayarda ve birden kapandı sistem. Anakartımın ışıkları yanmaya devam etti. Güç düğmesine birkaç kez bastım bilgisayar tepki vermedi. Arkadan tuşu kapadım, 10 saniye sonra açtım ve tekrardan güç tuşuna bastım bilgisayar açıldı. Prime95 ile low ve medium testleri yaptım 15 dk boyunca ama kapanmadı. OCCT ile de power testi, ve diğer testleri de yaptım temiz. Sebebi ne olabilir? Minidump dosyasını paylaşıyorum buraya.
Aynı şey bana da 2 defa oldu hem de video izliyordum ağır yükte falan da değildi sistem. İşlemci ve anakartımız aynı ekran kartı olarak bende 1660ti var. Sorun neyden kaynaklanıyor anlayamadım.
 
Uyarı! Bu konu 5 yıl önce açıldı.
Muhtemelen daha fazla tartışma gerekli değildir ki bu durumda yeni bir konu başlatmayı öneririz. Eğer yine de cevabınızın gerekli olduğunu düşünüyorsanız buna rağmen cevap verebilirsiniz.

Yeni konular

Geri
Yukarı