F5F Stay Refreshed Hardware Desktop Repeated crashes and unclear issues

Repeated crashes and unclear issues

Repeated crashes and unclear issues

1
1Nuky22skin
Member
140
05-06-2022, 01:11 PM
#1
I began experiencing regular BSODs this week. Hardware hasn<|pad|>'s been stable. DPC_WATCHDOG_VIOLATION (133) indicates a long runtime at an IRQL of DISPATCH_LEVEL or higher. amdkmdag is the module involved. I've attempted driver updates, rolled back drivers, re-seated hardware, used image restores, and performed several clean installs. Still can't identify the problem. My PC specs: MB x670e, Asrock Taichi Carrara CPU, AMD ryzen 7700x, RAM G.SKILL Trident Z5 RGB Series 32GB (2 x 16GB), 288-Pin PC RAM DDR5 6000 (PC5 48000), PSU EVGA 1000 GQ NVME, Kingston FURY Renegade M.2 2280 1TB PCIe 4.0 x4 NVMe, 3D TLC SSD (SFYRS/1000G).
1
1Nuky22skin
05-06-2022, 01:11 PM #1

I began experiencing regular BSODs this week. Hardware hasn<|pad|>'s been stable. DPC_WATCHDOG_VIOLATION (133) indicates a long runtime at an IRQL of DISPATCH_LEVEL or higher. amdkmdag is the module involved. I've attempted driver updates, rolled back drivers, re-seated hardware, used image restores, and performed several clean installs. Still can't identify the problem. My PC specs: MB x670e, Asrock Taichi Carrara CPU, AMD ryzen 7700x, RAM G.SKILL Trident Z5 RGB Series 32GB (2 x 16GB), 288-Pin PC RAM DDR5 6000 (PC5 48000), PSU EVGA 1000 GQ NVME, Kingston FURY Renegade M.2 2280 1TB PCIe 4.0 x4 NVMe, 3D TLC SSD (SFYRS/1000G).

N
natsu40
Member
239
05-06-2022, 05:34 PM
#2
It occurs only under particular conditions, such as certain games or when the CPU is under heavy strain, not just during idle time. You’ve checked the RAM and tried using both sticks, different slots, and it still happens. This pattern suggests a hardware problem, with RAM being the most probable cause, though a failing drive could also be involved.
N
natsu40
05-06-2022, 05:34 PM #2

It occurs only under particular conditions, such as certain games or when the CPU is under heavy strain, not just during idle time. You’ve checked the RAM and tried using both sticks, different slots, and it still happens. This pattern suggests a hardware problem, with RAM being the most probable cause, though a failing drive could also be involved.