Error encountered during BSOD DPC Watchdog violation.
Error encountered during BSOD DPC Watchdog violation.
Hello,
For several months I've had a problem with recurring DPG Watchdog Violation blue screens, without understanding the cause. They had largely calmed down for several months, but resumed, which led me to completely reinstall Windows. However, shortly after installation, everything started up again as before.
I started collecting the dmp files, and underneath you have all the drivers implicated by the Windbg analysis.
My first thought was a hardware cause, but I ran all the hardware tests proposed in the bios. I also ran long stress tests on the chipset, processor and dedicated graphics card, with no apparent anomaly.
Impossible to find a precise cause for the problem, it happens just as easily on a PDF reader, Word, Firefox or even without software running.
At first, I thought it might be an interaction between the graphics card drivers (see my configuration below). However, I don't think there's any connection in the end. I've disabled the Nvidia graphics card in the BIOS and uninstalled its driver with DDU, but the problem still persists.
For your information, here's the list of drivers incriminated by WinDbg, as well as the windbg analysis results:
https://www.swisstransfer.com/d/788b9dd9...4018e7972f
All drivers are up to date.
I know it's a lot, but if anyone has any ideas, I'd love to hear from you. Of course I'm at your disposal if you need more info.
Many thanks in advance!
--------------------------
Configuration
Windows 11 24H2
Lenovo Yoga Pro 7
Ryzen 7 7840HS with AMD 780M
Nvidia GeForce 3050 6GB
28/02/25
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
01/03/25
MODULE_NAME: msgpioclx
IMAGE_NAME: msgpioclx.sys
07/03/25
MODULE_NAME: amdgpio2
IMAGE_NAME: amdgpio2.sys
03/17/25: nvidia GPU disabled from Lenovo control panel
MODULE_NAME: amdgpio2
IMAGE_NAME: amdgpio2.sys
03/21/25: nvidia GPU disabled from Lenovo control panel
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
03/22/25: nvidia GPU disabled from BIOS, chipset version given by Lenovo reinstalled.
MODULE_NAME: msgpioclx
IMAGE_NAME: msgpioclx.sys
24/03/25: nvidia GPU disabled from BIOS, chipset version given by Lenovo reinstalled.
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
30/03/25: uninstall Lenovo drivers and install AMD WHQL recommend drivers, nvidia disabled in bios
MODULE_NAME: amdgpio2
IMAGE_NAME: amdgpio2.sys
if i had to suggest a solution, i’d believe the issue stems from a motherboard sound driver interfering with a GPU video HD sound driver, leading to stack overflow and causing the GPU driver to crash due to a timeout. the recommended approach would be to update the motherboard sound driver and disable any unused sound devices—such as motherboard HD sound, gpu hd sound, and cpu hd sound. i’m specifically looking for an older realtek hd sound driver.
note: there are instances where attaching android phones via the GPU USB has caused similar problems.
Here’s a revised version of your text:
I wanted to thank you very much for your prompt response!
To recap the actions I took:
- Removed all graphics card drivers completely and reinstalled them with the latest updates
- Removed the Realtek sound driver and reinstalled it at the most recent available version (refer to the screenshot here)
- Disabled AMD HD audio and the AMD streaming Audio Device
- Changed the DMP type to kernel mode
Regarding USB devices, I’m using a laptop and don’t often rely on USB peripherals. Occasionally I connect it to an external monitor and use an external keyboard or mouse, plus an Ethernet/USB-C adapter. However, I haven’t observed many issues in these setups, so I’m not sure if bugs are more frequent.
I didn’t find any duplicate drivers installed, and I don’t overclock my graphics card. The lmiftsm results are available here for reference:
https://www.swisstransfer.com/d/c2004440...a2ce8b0b69
I followed the commands you requested, but unfortunately interpreting them is beyond my capabilities. Sorry if this wasn’t clear.
Thanks again!
P.S.: BSODs typically occur about once a week; after two weeks without any issues it seems like a positive sign, but I’ll update you if anything changes.
it seems the issue originates directly from the motherboard itself. Update the bios and drivers from the vendor's website. Check for firmware updates. After applying the updates, disable hardware devices in bios that you don’t use. Turn off any special bios tuning settings in bios. A file might be running from outside a driver at kernel address FFFFF80776E372E6 (firmware or bios program). For instance, an ASUS Armory Crate could create a file on your drive before Windows boots, leading to various problems.
your system has a lot of new amd drivers that I have never seen before.
generally I don't like seeing this driver installed
AtihdWT6.sys Tue Apr 30 16:51:17 2024
you might go into windows device manager and find this sound device and see if you can change the driver to the microsoft generic driver. This is just a guess as a fix to your problem.
the bugcheck was in general purpose input output drivers that handle slow devices on your motherboard. sound and microphone would be such a device.
you also need to make sure your bios was updated to match the drivers that are installed.
you can look here and see if you can find the updated amd gpio package:
https://www.amd.com/en/support/download/drivers.html
your version looks pretty current Aug 20 08:25:33 2024
note: look in bios and see if there is some setting for HDMI chipset configuration. you might disable it.
(sorry, this is just another guess would be using the IO on the motherboard and be corrupting the stack)
I searched for AtihdWT6.sys, which is used by AMD High Definition Audio Service. I disabled it and will check the drivers. The available BIOS settings are limited, and there’s no mention of an HDMI chipset. I enabled the “bios self-healing” feature and turned off bios blackflash. I considered the possibility of using UMA Graphics memory, which I set to 1 GB instead of the default 2 GB to free up RAM for more demanding graphics. If possible, I’d prefer to leave it unchanged, but I’m wondering if this might be the cause of the issue. Given the risks of updating BIOS, should we wait to see if the bug is resolved naturally, or will we need to proceed regardless?
Generally, refreshing the bios isn’t as challenging today as it once was. The bios must align with the drivers you installed; mismatches can lead to stack corruption and buffer overflows. It’s best to perform updates together—firmware, then bios, followed by motherboard drivers, and finally disable unused bios features. This approach works well because fixing bugs often requires this same sequence.
Newer systems handle much of the motherboard traffic via the PCI/e bus. Consequently, issues like a faulty usb driver causing video delays can occur even in systems that were previously unrelated.
I’ve also tested a setup where a quick mouse shake could trigger a video timeout if the video driver was bugged. The mouse would move, but without control for two seconds, the video would fail. This happened when a Windows drive was swapped into a new system without reinstalling Windows.
Wow, it's amazing how everything is connected! Thanks a lot, I'll proceed and then either wait for the next BSOD or be glad they stop appearing. I'll update you on the outcome.
Regarding the integrated graphics memory, should we increase it or not?
Thanks again!
things become quite problematic now that windows sleep functions preserve the states of everything in the pagefile.sys and restore them when the system restarts.
it is ideal for everything to function properly, but it creates significant issues for bugs and malware.
many people ask how to delete the pagefile on reboot, and modifying the registry can greatly improve stability.
poor RAM or faulty drivers often require hours of troubleshooting before any corruption is saved to disk and reloaded, which ultimately leads to bugs or failures.