Repeated BSOD warnings about watchdog violations
Repeated BSOD warnings about watchdog violations
Hey everyone, I'm experiencing these DPC_Watchdog_Violation BOSD errors regularly—about every couple of days. My device is a Yoga 14ARB7 with a Windows 11 install that's only a year old. The drivers are up to date with Lenovo Vantage. When I checked the DMP files, I didn't find anything obvious that matches the issue. I'm unsure what triggers this BSOD—no app, process, time, location, power mode, USB devices, or charging state seems to fit. Thanks in advance for any advice! Marius 051023-14500-01.zip
You can use software such as BlueScreenView for a clearer overview of errors and their reasons. Often, the DPC_Watchdog_Violation screen appears due to Windows corruption or memory issues. You might try performing a Windows Repair Install or an in-place upgrade with the Windows 11 Media Creation Tool. If that fails, testing various memory modules could be helpful.
Thanks for the advice. It looks like Ntoskrnl.exe might be causing the problem. It's hard to say exactly what it does, but reinstalling Windows could help fix it. The laptop has its memory built in, so I'll look into troubleshooting steps from error logs. These steps may not always solve such issues, but a clean install might work better. Appreciate your support!
Performing an in-place upgrade with Windows Media Creation Tool is basically a complete reinstall while preserving your files and programs. It’s quite straightforward, though the time may vary depending on your system. If this doesn’t resolve the issue, consider a full reinstall of Windows; whether it’s hardware-related depends on that. If you still encounter blue screens after switching to a brand new OS, it usually points to a hardware problem—often memory is the culprit. If the Ntoskrnl.exe error persists and no specific software or driver is listed as the cause, it likely indicates a hardware fault. If your memory is built into the motherboard, repairing it would be difficult, possibly requiring a full board replacement.
BluescreenView and Whocrashed aren’t reliable tools. They’re simple to operate, yet they lack precision. These crashes don’t seem linked to ntoskrnl.exe. The Windows kernel file is usually unrelated to these issues. Since DPCs behave unpredictably, it can be hard for the OS to pinpoint the exact driver responsible. The crash reports aren’t very consistent, which reduces the reliability of the analysis. Most probable culprits appear to be the PPM, GPU driver, and chipset driver. Updating your BIOS might help—check if the automatic updater works. You’re currently on version 34, while the latest is 40, so you’re fairly up-to-date. Perform a scan here and review the results; it looks like no chipset driver was found in the manual list. Apply any available updates. If problems persist, proceed to the manual update page and download the AMD and Nvidia GPU drivers, but don’t install them immediately. Use DDU and follow the provided instructions. Before rebooting to safe mode, disable internet access so Windows updates won’t install unwanted versions. In safe mode, uninstall both AMD and Nvidia GPU drivers. After restarting, reinstall the AMD driver first, then the Nvidia driver. On laptops, it’s often better to remove both at once since some devices react negatively. Reinstalling Windows can resolve the issue by resetting all drivers, though it may require more effort.
Okay, I will have a new os Install as the last option. My device has some months of warranty left, which hopefully will cover if it is a hardware error. Thank you for your detailed answer! The automatic scan now comes up as all drivers installed, only the Intelligent thermal solution (ITS) driver might have been missing (I dont know for sure, i went into the chpset driver and installed it before running an automated scan). I also updated the BIOS. I plan on waiting until the crash happens again and then proceed with the next step, until i dont BSOD anymore. I will report if anything changes/problem seems to be resolved. Thank you both for helping me out!
Lenovo has encountered problems on other devices with DPC_Watchdog_Violation crashes when using their Nvidia driver (likely during the first installation, though updates may be uncertain). There were at least three such incidents, with two occurring on desktops—most notably the Legion T5. It’s possible these issues stem from compatibility between Lenovo’s OEM software and certain Nvidia driver versions.
The laptop features an internal AMD GPU of 680MHz. However, when using an external GPU like the GTX 1660, NVIDIA drivers are required. These were automatically installed during setup. I didn’t locate any Lenovo drivers for this model with a NVIDIA GPU, as it doesn’t list a discrete card in its specifications. The crashes happen whether or not the EGPU is connected.
I wasn't expecting an external GPU to be involved. It seems the chipset and bus issues are more relevant here. Updating the chipset and BIOS is crucial, especially on laptops where manufacturers often delay driver updates. You might want to check the AMD chipset listed for your motherboard. The graphics crashes were attributed to either DirectX or the AMD GPU itself. For DDU users, use the AMD driver. Make sure you install the newest Nvidia driver as recommended.