BSOD Crashing

I am currently having the same issue as many, with the "update your driver to a version outside of range: Adrenalin 25.10.2 - Adrenalin 25.12.1" popping up as I log in. Beside that, I am getting a full PC freeze leading into a BSOD every 30 minutes mentioning the following in the dump file:

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

I have had this issue on 3 different versions of AMD drivers, and I've only ever had the issue in POE2. This started with this update. I am running an XFX AMD RX 9070, and the drivers this occurred on were Adrenalin 25.9.1, Adrenalin 25.9.2, and Adrenalin 25.12.1. The 25.12.1 was my attempt to use drivers within the given range as a DPC_WATCHDOG_VIOLATION is usually outdated drivers. I also full wiped the drivers between each attempt.

Edit: I tested with 25.8.1 as well, still crashes. Weirdly, it seems like the Drivers outside of the non-recommended range give me like 3ish hours of playtime before a crash, while the ones inside the range give me less then 30 minutes of playtime before crashing.

Just wanted to reply that I'm having the exact same problem. I've tried GPU driver versions going back to 25.8 (and using DDU for clean installs of each version) with minimal effect. I've also tried clearing shader cache, completely reinstalling the game, trying with/without multithreading enabled in settings, and swapping between Vulkan/DirectX 12.

I'm using an AMD RX 9070XT and a Ryzen 7 7700X CPU. Haven't had any issues in other games or tasks - only when playing POE2 and the crash is pretty inconsistent. I haven't been able to intentionally reproduce it. It can happen while solo, party play, in hubs, or in multiple different maps.

It has happened a lot over the past several days while attempting to play and has required a hard shutdown every time.

Nvidea user here and my pc is constantly blue screening with the DPC watchdog violation error. exclusively happening when playing this game.

Same, to this day, only Path of Exile 1 and 2 keeps BSODing my PC. I have played many different games like Elden Ring, Factorio, Borderlands 3 etc, and only happens with PoE.

"

Death_Scyth31#1709 wrote:

Same, to this day, only Path of Exile 1 and 2 keeps BSODing my PC. I have played many different games like Elden Ring, Factorio, Borderlands 3 etc, and only happens with PoE.

You need to deal with BSOD. Here's an explanation of what BSOD is.

"

What causes stop errors?
When Windows encounters a condition that compromises safe system operation, the system stops. Examples include something failing that could compromise security or lead to corruption of the operating system (OS) and/or user data. When the machine stops in order to prevent the operating system from moving forward in these conditions, it is called a bug check (or bugcheck). It is also commonly referred to as a system crash, a kernel error, or a stop code error. On preview releases of Windows, the screen color can be green, leading to the green screen of death (GSOD).

There's no simple explanation for the cause of stop errors. Many different factors can be involved. Our analysis of the root causes of crashes indicates that:

70% are caused by third-party driver code.
10% are caused by hardware issues.
5% are caused by Microsoft code.
15% have unknown causes, because the memory is too corrupted to analyze.

Note

The root cause of stop errors is rarely a user-mode process. While a user-mode process (such as Notepad or Slack) may trigger a stop error, it's usually exposing the underlying issue in a driver, hardware, or operating system

https://learn.microsoft.com/en-us/troubleshoot/windows-client/performance/stop-code-error-troubleshooting


Here's a typical guide to troubleshooting system stability issues.

https://www.amd.com/en/resources/support-articles/faqs/TS-TIPS.html

Doubt this is helpful but maybe you didn't use AI, this is what it told me:

This specific error means your computer "timed out" because a driver or process stayed active for too long at a high priority level, essentially freezing the system's ability to multitask.

Since Arg1 is 0000000000000001, it indicates a cumulative timeout. This means several Deferred Procedure Calls (DPCs) were running back-to-back for so long that the "Watchdog" timer stepped in and pulled the plug to prevent hardware damage or a total system hang.

Common Culprits

Storage Drivers: Outdated firmware on SSDs or corrupted SATA/NVMe drivers are the most frequent cause.

Network/Wi-Fi Drivers: Faulty wireless drivers often "hog" the CPU at this priority level.

Third-party Antivirus: Sometimes these hook too deeply into the kernel and cause delays.

Quick Fixes to Try

Update SSD Firmware: Visit the manufacturer's site (Samsung, WD, Crucial, etc.) and check for updates.

Replace iastor.sys: If you use Intel Rapid Storage Technology, switching to the standard Microsoft SATA AHCI driver often stops this specific crash.

Check Hardware: Run a chkdsk /f /r in the Command Prompt to ensure your drive isn't failing.