Lenovo Yoga 7 Gen 7: DPC Watchdog Violation (Bugcheck code: 0x133)

1732611167246.webp

"These could have been merged in the last one:
C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1fae5d30-2f46-449f-9b9d-2ffa6e6ce9f3.tmp.WERInternalMetadata.xml
C:\ProgramData\Microsoft\Windows\WER\Temp\WER.48e99073-27c1-46f4-85a4-79460bdc6b45.tmp.csv
C:\ProgramData\Microsoft\Windows\WER\Temp\WER.187462b4-7771-496f-983b-8026d307b307.tmp.txt
C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a82e4096-7d8a-41e8-bbdf-06345dea9663.tmp.xml"
This path is empty.

The rest of the available attachment is down below.
 

Attachments

I lost hope on Lenovo already lol
They simply ignore this issue even though many owners reported it since 2022.
I guess all yoga 7 gen 7 laptops face this issue as I always thought my laptop doesn't have this issue until I started to use touchscreen/touchpad/tablet mode frequently 😅
But hey let's hope they really manage to issue a fix this time
 
In the meanwhile, you could check (and clean) the disk(s).
Code:
dism /online /cleanup-image /checkhealth
sfc /scannow
dism /online /cleanup-image /startcomponentcleanup /resetbase
chkdsk c: /v /perf
cleanmgr /sageset:1
(select all options)
cleanmgr /sagerun:1
Post the result(s) of each command (except cleanmgr: it only cleans).

Try passmark diskcheckup or gsmartcontrol tests (or both), here at 4th post (third reply): Hard Drive (HDD) Diagnostics (Sea Tools for DOS) & SSD Test.
You can also try SeaTools bootable and/or SeaTools for windows.
 
You could try to stop AMD Crash Defender Service and change its startup type to disabled, given that it seems part of the problem.
You can stop the service from start, services.msc.
This will open the services window.
Double-right-click on amd crash defender service, left-click stop, click startup type, select disabled, click ok.

To stop the driver amdfendr.sys: sc config amdfendr start= disabled

My PC rebooted normally without them.
 
If the machine does not BSOD, in two (What was the frequency of BSODs?) days, enable half of them (marking down the ones you re-enable).

Then two(?) more days and enable all the items.
 
Sorry I am getting confused here
I still get BSOD when I already disabled all 3rd party services(which includes AMD Crash Defender) and auto-start apps (see #39)
Now I should disable half of the 3rd party services(including AMD Crash Defender) and auto-start apps?
 
Your question was:
Should I leave the other 3rd party services and auto-startup apps disabled? or just the AMD Crash Defender Service disabled?

But in the previous message I gave you instructions to stop also a driver.

My reply was: if you in next 2 days (or a week) won't get a bsod, enable half of the services you disabled before (marking down the ones you re-enable); and see if you still get bsods.
Then, after another reasonable amount of time, enable another half (marking down the ones you re-enable).
Then, after another reasonable amount of time, enable another half (marking down the ones you re-enable).
Until you re-enabled all of them.
This is the method used to identify the service responsible for the bsods suggested by ubuysa.
 
In Device Manager there is another driver called "amdfendrmgr.sys" should be disabled too right?
1732704191184.webp
I already run the command line but the picture above didn't show the driver being disabled until I disabled it.
1732704219916.webp
 
I can't find amdfendrmgr.sys in my pc:

Code:
dir c:\amdfend*.* /a /b /s

c:\Windows\System32\amdfendrsr.exe
c:\Windows\System32\drivers\amdfendr.sys
c:\Windows\System32\DriverStore\FileRepository\amdfendr.inf_amd64_d769a8c3fe3072f4
c:\Windows\System32\DriverStore\FileRepository\amdfendr.inf_amd64_d769a8c3fe3072f4\amdfendr.cat
c:\Windows\System32\DriverStore\FileRepository\amdfendr.inf_amd64_d769a8c3fe3072f4\amdfendr.inf
c:\Windows\System32\DriverStore\FileRepository\amdfendr.inf_amd64_d769a8c3fe3072f4\amdfendr.PNF
c:\Windows\System32\DriverStore\FileRepository\amdfendr.inf_amd64_d769a8c3fe3072f4\amdfendr.sys
c:\Windows\System32\DriverStore\FileRepository\amdfendr.inf_amd64_d769a8c3fe3072f4\amdfendrsr.exe
 
Sorry its my own fault
I mistook the service (amdfendrmgr) as a driver
It doesn't explain why the AMD Crash Defender is not disabled after running the command line but it should be disabled right(AMD Crash Defender in Device Manager)?
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top