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

Yep I keet verifier running since #166.
I just notice the memtest in #2 is Passmark Memtest86
I will run the memtest86+ tomorrow.

Quote:
Wait until it reaches at least 8 passes or until an error appears.
This test could take few hours.
Added by Philc43: as an example, on some systems with 32GB RAM could take 1-2 days.
In this case it can be an advantage to breakdown the testing into steps of one or two modules at a time and run the tests overnight.

My RAM is not removable (LPDDR), does it mean I may be forced to run it overnight? I am worried of overheating
 
If it's present in the UEFI/BIOS, set the temperature limit to shutdown the laptop at 85/90°C.

If it's not present, you can consider to try hcidesign memtest (see hardware tutorials).
32GB RAM / 8 CPU cores = 4 GB (4096MB) for each instance of hcidesign memtest (i.e., you need to open it eight times).
The last instance will not probably allow 4096 as number.. Try 3096 (or 2048, 1536, 1024, 768, 512).

I have 10GB, 4 CPU cores: 2.5GB (2560MB).
After a bit of tries, I set 1728 for each instance:

hcidesign-memtest.webp


The advantage of this test is that you can continue to use the PC (for light things, such as surfing the internet) and monitor the temperature.
(One pass is 100%, 8 passes are 800%)
 
Last edited:
It seems the following setting (core isolation - memory integrity AKA hypervisor-protected code integrity - HVCI OR hypervisor enforced code integrity - HECI) is involved in virtualization (when it is enabled in the UEFI/BIOS):

1736186991421.webp

This is another setting you could try (turned off) after the memtest.
 
1736223801093.webp
I am running 10 instances of hcimemtest (3501MB each) is that ok? It does not allow me to run more than 3501MB for each instances.
I tried running memtest86+ but all my usb is not detected even after I turn off secure boot and fast boot.
 

Attachments

I know I've said this before but from those recent dumps (the January ones) this still looks much more like a RAM problem than anything else. It's a long thread and I've not the time to trawl back through it, but have you tried removing a pair of those RAM cards? That would be my suggestion. Run on just two RAM cards for a few days, or until you get a BSOD, and then swap the cards over and run on the other two for a few days.

Those most recently uploaded dumps are all over the place, the failures happen in different operations and in different modules. That's why I think bad RAM may well be the root cause.
 
You can stop verifier since after four days we only got this bsod (and 0x133_VRF_ISR_Npfs!NpFsdRead).
This is the minidump:
Read More:
The driver (SpbCx.sys? Or amdi2c.sys?) has completed a framework request, but has written more bytes to the output buffer than are specified in the IRP.
The information length is hex 0x56 (dec 86), the output buffer (max) length (accepted) is hex 0x2b (dec 43 - which is half of the provided information length).
That is, the error is that this driver tried to send back (to wdf01000.sys) more data than allowed (buffer overflow?).
It could be this one that trigger the 0x133 BSOD (without verifier).

AMD I2C is part of the chipset.
Speccy shows that it has to do with these devices (four groups):
Read More:
Check in device manager if you are able to try different amd i2c (older) drivers.

Blackboxpnp seems to suggest the problem could (also) be USB\VID_30FA&PID_0302\6&7d52dcf&0&2 that shows PnpProblemCode: 24.
It seems it is FUJITSU L1010 (USB Optical Mouse) connected through a USB port.
Microsoft says:
Read More:
It might be there just because the BSOD occurred...
Are you using an old fujitsu mouse?
Have you tried using just the touchpad without the mouse?
 
Last edited:
Screenshot 2025-01-08 120954.webp
Btw this is the result of hcimemtest (11 instances of 3158MB).

xilolee said:
Are you using an old fujitsu mouse?
Have you tried using just the touchpad without the mouse?
Click to expand...
No, my current mouse is called weibo optical mouse. I can't find its exact model on the mouse but that is the place I bought it.
I always disconnect the mouse and use touchscreen (rarely use touchpad) when trying to trigger BSOD.
But yesterday when the BSOD(#215) happen the mouse is connected.
xilolee said:
Check in device manager if you are able to try different amd i2c (older) drivers.
Click to expand...
We already roll back to the older driver in #81. There is only that driver and the current one available.
 
Let's recap:
- prime95 CPU/RAM test passed (2-3 hours per test and verifier enabled)
- furmark GPU test passed (2 hours and verifier enabled)
- (hcidesign) memtest passed (4 to 12 passes)
- passmark memtest86 passed (4 passes)
- seatools SSD test(s) passed
- verifier tests... Passed (four days)
- amd-v off: the PC works without bsods
- amd-on: bsods caused by AMD drivers (most likely AMDI2C.sys and AMDGPIO2.sys, but also the other ones)

Correct?
Am i forgetting any other tests?
 
Last edited:

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

Back
Top