Constant DPC_WATCHDOG_VIOLATION while playing certain games on W11 PC

Dilat3d 20 Reputation points
2026-04-13T22:48:10.0866667+00:00

Hi all

I'm at my wits end. I installed Diablo 4 off of Steam and almost immediately ran into the subject error. I attempted numerous fixes, finally decided to do a fresh install of Windows however my problems persist. Attached are links to my system and application dump files - seeking any/all guidance, thank you!

Application dump:
https://1drv.ms/u/c/ffccbf3ee6631c45/IQA-QRfPMJ_pTKXrXzdYkmJ6AWi9HkaMCP5-hLeVsRo8S1s?e=2K4h5t

System dump:
https://1drv.ms/u/c/ffccbf3ee6631c45/IQDBwws-TnFvT7jWk2DgL9zxAYyiJHMpHurc757SGuenuog?e=QdhkKu

Windows for home | Windows 11 | Performance and system failures

Answer accepted by question author
BryceSor 5,485 Reputation points Volunteer Moderator
2026-04-14T02:31:44.8+00:00

Hi Dilat3d,

I checked both dumps and what you have said about trying to fix your issue, I build my own computers and have a specific order of install, below is by OP but with my input to try and give you a clear picture, sorry its a bit long.

I analysed (x2) your crash dump, and the error is very specific:

This type of crash is not caused by game settings, DLL files, audio devices, SSDs, or background services. It’s a hardware‑timing issue involving the GPU, chipset, and PCIe stack.

Right now your system is in a bit of a mixed state after the Windows reinstall, and several things you mentioned are actually making the platform less stable. For example:

• You’re missing the AMD chipset drivers, which handle PCIe timing, power management, and interrupt routing.

• LAN, WiFi, and Bluetooth drivers are also missing, which means Windows is using fallback drivers.

• EXPO and PBO are enabled, which can destabilise the memory controller and SoC voltage.

• Resizable BAR is disabled, which AMD GPUs expect to be on for correct PCIe behaviour.

• The EFI partition being on a different drive is unusual, but not related to the crash.

None of this is your fault — it’s just the result of Windows Update not installing the correct motherboard drivers after the reinstall.

To get you back to a stable baseline, here’s the recovery path that actually addresses the root cause:

  1. Disable EXPO and PBO temporarily

These can cause timing instability even if MemTest passes.

  1. Re‑enable Resizable BAR

AMD GPUs on AM5 platforms expect it.

  1. Install ALL motherboard drivers from ASUS (not Windows Update)

From the ROG STRIX X870E‑E support page, install:

• AMD Chipset Driver

• LAN Driver

• WiFi Driver

• Bluetooth Driver

• Firmware/ME/AM5 platform drivers

• USB drivers

• Armoury Crate Service (optional but stabilises ACPI)

This restores proper PCIe, power, and interrupt behaviour.

  1. Clean‑install the AMD GPU driver

Use DDU or AMD Cleanup Utility, then install the latest WHQL driver.

  1. Ignore the EFI partition issue for now

It won’t cause GPU ISR crashes.

It can be fixed later once the system is stable.

Once these steps are done, you’ll be back on a clean, stable platform — and in most cases, this completely resolves the 0x133 ISR stall.

https://rog.asus.com/motherboards/rog-strix/rog-strix-x870e-e-gaming-wifi/helpdesk_download/ please check I have the right motherboard.

Which AMD video card are you using?

Was this answer helpful?

2 people found this answer helpful.

2 additional answers

Sort by: Most helpful
  1. Jonathan Deives 79,650 Reputation points Independent Advisor
    2026-04-13T23:27:22.4833333+00:00

    See if your computer is creating minidump files.

    To find these files, this is the path "C:\Windows\Minidump".

    First copy and paste all the minidump files you have to another folder and then zip it. Then upload the ZIP file to the cloud OneDrive.

    Choose to share or right click and get the share link.

    Please post the link to the ZIP file here so it can be reviewed.

    Was this answer helpful?

    1 person found this answer helpful.

  2. AI answer

    2026-04-13T22:48:56.9766667+00:00

    Bug check DPC_WATCHDOG_VIOLATION (0x133) is almost always caused by a faulty or misbehaving driver or hardware that does not complete its work within the allotted time. A clean Windows install rules out most OS corruption, so focus should be on drivers, hardware, and any vendor tuning/overclocking tools.

    Use these steps to narrow it down:

    1. Check which driver is failing (if visible)
      If the blue screen or dump analysis identifies a specific driver (for example a display, storage, or network driver), disable or update that driver from the device manufacturer. This is the first recommendation for 0x133:
      • If a driver is identified in the bug check message, disable it to isolate the issue and check with the manufacturer for updates.
    2. Update or roll back GPU and other key drivers
      Since the issue occurs in specific games (Diablo 4 via Steam):
      • Update graphics driver to the latest WHQL version from the GPU vendor.
      • If already on latest, try rolling back one version.
      • Update chipset, storage (SATA/NVMe), network, and audio drivers from the motherboard or OEM support site.
    3. Remove or disable OEM tuning/overclocking utilities
      Similar BSOD patterns have been resolved by removing OEM performance tools that change CPU/GPU frequencies or power profiles. For example, one user with repeated BSODs on a gaming laptop stabilized the system by doing a clean install and uninstalling the OEM control app that managed performance/overclocking profiles.
      • Uninstall any vendor tools that adjust clocks, voltages, or fan curves (gaming center, performance/OC suites, RGB tools that hook drivers, etc.).
      • Restore BIOS/UEFI to default (no overclock, XMP/EXPO off as a test).
    4. Check Event Viewer and dumps if no driver is obvious
      If the bug check does not clearly name a driver:
      • Check System log in Event Viewer around the time of the crash for driver or device errors.
      • If able to use WinDbg, follow the guidance for 0x133:
        • Use !analyze to get details.
        • For parameter 0, inspect the stack (k) to see which driver was running when the watchdog fired.
        • For parameter 1, use event tracing and !dpcs to see which DPCs are queued and which driver is exceeding its normal execution duration.
    5. Basic hardware and compatibility checks
      • Confirm any new hardware (SSD, RAM, USB devices, controllers) is compatible with Windows 11 and has current firmware.
      • Temporarily disconnect non-essential USB/peripherals and test the game.
      • If the issue started after adding a specific device (for example, external monitor, controller, USB hub), test without it.
    6. If still unstable, treat as driver/hardware fault
      In general, this stop code is caused by faulty driver code that, under certain conditions (like heavy GPU/IO load in a game), does not complete within the watchdog’s time limit. If no single driver stands out, continue systematically:
      • Test with only Microsoft-supplied drivers where possible.
      • Disable third‑party antivirus or overlay tools (recording/streaming, FPS overlays) as a test.
      • If a specific driver is consistently implicated, work with that vendor’s support or replace the associated hardware if no stable driver exists.

    If comfortable with debugging, the WinDbg crash-dump analysis articles in the references provide step‑by‑step commands to pinpoint the offending module.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.