I've been getting repeated DPC_WATCHDOG_VIOLATION (0x133) blue screens since August and can't figure out what's causing them. My system has an RTX 4080 Super, 32GB of DDR4-2666 memory, a Gigabyte B760M DS3H AX DDR4 motherboard, an Intel Core i9-13900K, a 2TB Predator GM7000 SSD, and a 1TB SP PCIe Gen 3 M.2 SSD connected through a USB-C adapter.
I initially suspected the second SSD, but the crashes continue even when it's disconnected. There's also strange boot behavior: the primary SSD sometimes doesn't appear in the boot menu, but it becomes visible when I reconnect the second drive. The second SSD also isn't detected when installed directly in the motherboard by itself, although it does work through the adapter, and both drives have Windows installed.
My BIOS currently reports version F21 from June 19, 2025. Could a BIOS update, CPU issue, or failing SSD explain the crashes and inconsistent drive detection?
4 Answers
The CPU-degradation explanation is less convincing if you’ve been using F21, because the earlier BIOS versions that lacked the relevant microcode were the bigger concern. Still, updating the BIOS is reasonable. Don’t assume the processor is dead without checking crash dumps and hardware behavior first.
Check the BIOS version first. The 13th- and 14th-generation Intel stability problems were addressed through BIOS microcode updates, so make sure the board is running a current release. Since you’re already on F21, the major fix should be included, but updating to the newest stable BIOS, such as F24 if it’s the official release for your exact board revision, may still be worth trying.
For the BSOD itself, look in C:WindowsMinidump for crash dump files and analyze several of them rather than relying only on the stop code. Those logs can identify whether a storage controller, driver, or another component is triggering the watchdog timeout. If no dumps are being created, enable small memory dumps and reproduce the problem.
The storage detection problems point toward a drive, M.2 slot, motherboard configuration, or connection issue as well. Test each SSD separately, try the other M.2 slot if available, check the BIOS storage settings, and test the drives in another computer or with a known-good drive. Having Windows installed on both drives can also make boot selection confusing, so disconnect one drive while repairing or testing the other.
Do you think the checksum-listed F24 release could actually fix this? I just want to be sure before updating.