DPC_WATCHDOG_VIOLATION on new Lenovo Yoga Laptop

I have a new Lenovo Yoga 7 14ARB7 with a fresh Windows 11 install (22H2) and get a BSOD every few days. The error is always a "DPC_WATCHDOG_VIOLATION".
It seems to be a common problem, at least with some of these units: I have updated all the drivers and even installed the latest graphic card driver directly from AMD, nothing helped.

Here is the output of the v2 log collector: v2 logs (SwitchDrive is the cloud service for Swiss universities)
Can you take a look, please? That would be great. I am open for any suggestions.
Do you think it is a hardware problem?

Thank you in advance!
Kai

New laptops / notebooks should not have BSOD and live kernel events.

The computer manufacturer is responsible for the hardware and OEM operating system at the time of sale.

Please contact Lenovo for a Return Merchandise Authorization (RMA).

Compared to Windows 10, there has been a marked reduction in BSOD with the new hardware requirements and DCH drivers with Windows 11.

There were 2 misbehaving drivers seen so far in the debugging.

The uncertainty is is there an underlying hardware problem.

It's best to start with a computer without BSOD and live kernel events.

Thank you, zbook. You are absolutely right about Lenovo being responsible for delivering a fault free laptop. I can definitely go the RMA-route. Problem is, this can take weeks or months without any real result. On the reddit discussions linked above, other people have reported that they went back and forth with Lenovo for months, sending in their device for several “repairs” that didn’t fix anything.

This is the reason why I reached out for help in this forum to get an independent opinion and a competent look on the crash dumps.

My main question is: Do you think this is a hardware issue? If so, I am going to return the device for repair. Or do you see hints of a misbehaving driver or something else on the software side?

Since the last crash I have also updated the chipset drivers to the newest versions directly from AMD. No crashes after that – but that doesn’t mean a lot since it can take days for the next BSOD to arrive.

You were talking about “2 misbehaving drivers”. Did you see that in my log files? Which drivers?

The log files were in a foreign language and were not able to be scanned.

During the troubleshooting please use English as the default language so that event viewer and other files can be scanned and read.




There were two misbehaving drivers seen in the mini dump debugging::

amdkmdag.sys
amdi2c.sys

c:\windows\system32\driverstore\filerepository\u0386458.inf_amd64_e0283e9e7966f704\b386218\amdkmdag.sys

amdi2c AMD I2C Controller Service c:\windows\system32\drivers\amdi2c.sys


1) Uninstall the AMD GPU drivers using Display Driver Uninstaller (DDU).

2) Reinstall from the Lenovo website.



3) Reinstall the Lenovo Chipset drivers

Thank you very much, zbook.
I will follow your guide and report back what happens. This may take a while because the BSODs happen quite infrequently.
All the best
Kai

What should be emphasized is from the Lenovo website. Generic drivers from Windows Update are known to occasionally cause issues. Similar issue with periodic DPC Watchdog crashes. Mine was due to a generic Synaptics Touchpad driver. Reinstalling with the driver from the Acer's website resolved the issue.

CausticCharade said:

What should be emphasized is from the Lenovo website.

Click to expand...

Yeah, usually I would only install drivers directly from the manufacturer, at least for a new machine. I tried the (newer) generic AMD drivers in an attempt to solve the crashes I got with the Lenovo drivers.
Interesting that you mention the touchpad. I had another small issue with the laptop where the touchpad was sometimes becoming unresponsive or intermittend. But I dont think that has anything to do with the BSOD. We will see.

For any unexpected shutdowns and restarts > post a new V2 share link into the newest post

Use only the best tested drivers displayed on the Lenovo website.


Monitor the computer using Reliability Monitor:

zbook said:

Monitor the computer using Reliability Monitor:

Click to expand...

That's a great tool, never seen that before.
I am waiting for a new crash and will post a new v2 log by then. I am also going to change the language to English, sorry for that.