Lenovo Yoga 7 Gen 7 14ARB7 82QF: DPC Watchdog Violation (Bugcheck code: 0x133). WORKAROUND: Disabling AMD-V in UEFI/BIOS stops blue screens of death.

Attachments

The only new warnings visible in the event log are about disk: 6 January, 16 January, 2 February.
System, level Warning, source disk, event ID 51: An error was detected on device \Device\Harddisk1\DR2 during a paging operation.
The other messages say DR4, DR5, DR6 and \Device\Harddisk2\DR9.
 
The dumps in that last upload are all a similar bugcheck (0x133) but they apparently fail for different reasons. TBH I think sending it back is the best option, this looks like some sort of systemic hardware failure. I would do so ASAP.
 
Did amd send you a reply?
If they didn't, did you "update this service request" like Santosh wrote?

This service request will automatically close if we do not receive a response within 10 days and cannot be reopened.
If it is not feasible to respond within 10 days, feel free to open a new service request and reference this ticket for continued support.
Click to expand...
 
xilolee said:
Maybe you should specify this and send them the 0x10D minidump (010725-21250-01.dmp).
Click to expand...
I just did that using AMD Bug Report Tools.


By the way, I just had a BSOD? with WIN32K_POWER_WATCHDOG_TIMEOUT (19c) while trying to wake the laptop from hibernation the screen never light up(just the power button light up) so I force restart it. I am running driver verifier for 2 days already with virtualization off.
I am trying to see whether verifier can find out why #249 happens when virtualization is off, so I select these extra drivers (ntfs.sys, ntoskrnl.exe, spbcx.sys, hidclass.sys, hidi2c.sys, dxgkrnl.sys, dxgmms2.sys) other than the usual ones in #30.
Do you want the dump files and sysnative file collection app log?
 
Btw 5 BSOD happens today. First time the bsod occurs so frequently in a day
1 win32k and the rest is dpc watchdog as I turn on virtualization but verifier is off since that win32k bsod.
Several times the BSOD occurs when I didn't even sleep or hibernate the laptop once.

I am not sure but it seems that using windows sandbox can speed up the BSOD triggering process which I will experiment more with this.
 
User Of Inspiron 1420 said:
I just did that using AMD Bug Report Tools.


By the way, I just had a BSOD? with WIN32K_POWER_WATCHDOG_TIMEOUT (19c) while trying to wake the laptop from hibernation the screen never light up(just the power button light up) so I force restart it. I am running driver verifier for 2 days already with virtualization off.
I am trying to see whether verifier can find out why #249 happens when virtualization is off, so I select these extra drivers (ntfs.sys, ntoskrnl.exe, spbcx.sys, hidclass.sys, hidi2c.sys, dxgkrnl.sys, dxgmms2.sys) other than the usual ones in #30.
Do you want the dump files and sysnative file collection app log?
Click to expand...
All dump files links:
BSOD (MEMORY DDMMYYYY HHMM) - Google Drive
BSOD (MEMORY DDMMYYYY HHMM) - Google Drive
BSOD (MEMORY DDMMYYYY HHMM) - Google Drive (MEMORY 1322025 935)
 

Attachments

Running Windows Sandbox in the background seems to be able to speed up BSOD from occurring (letting it BSOD several times in a day instead of taking several days to BSOD)
But I am not sure is it because it is easier to trigger a BSOD after a BSOD occur.
 
Whilst I still think that this is a hardware issue, one of the five most recent dumps is interesting. It's a Driver Verifier detected BSOD (0xC9)...
Code: 
 DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000000000228, A driver's completion routine has not marked the IRP pending if the
    PendingReturned field was set in the IRP passed to it. This may cause the OS
    to hang, especially if an error is returned by the stack.
Arg2: fffff80397c30e70, The address in the driver's code where the error was detected.
Arg3: ffff9487218facf0, IRP address.
Arg4: 0000000000000000
You can see there that the problem here was that a driver has messed up its use of the IRP structure (the Interrupt Request Packet that manages interrupts).

By examining the IRP we can see the driver causing the problem...
Rich (BB code): 
15: kd> !irp ffff9487218facf0
Irp is active with 6 stacks 5 is current (= 0xffff9487218faee0)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  Pending has been returned
     cmd  flg cl Device   File     Completion-Context
 [IRP_MJ_PNP(1b), IRP_MN_START_DEVICE(0)]
            0 10 ffff94870082c060 00000000 fffff803295efcd0-ffff94870d3101d0 
           Name paged out    ACPI!ACPIIrpGenericFilterCompletionHandler
            Args: 00000000 00000000 00000000 00000000
 [IRP_MJ_PNP(1b), IRP_MN_START_DEVICE(0)]
            0 10 ffff94870080ddf0 00000000 fffff80398462430-ffffcb84def5ec30 
          ffff94870080ddf0: Could not read device object or _DEVICE_OBJECT not found
    nt!ViFilterGenericCompletionRoutine
            Args: 00000000 00000000 00000000 00000000
 [IRP_MJ_PNP(1b), IRP_MN_START_DEVICE(0)]
            0 10 ffff948707ad6c90 00000000 fffff80329467840-ffffcb84def5ed20 
           \DRIVER\VERIFIER_FILTER    Wdf01000!FxIrp::_IrpSynchronousCompletion
            Args: 00000000 00000000 00000000 00000000
 [IRP_MJ_PNP(1b), IRP_MN_START_DEVICE(0)]
            0 10 ffff9487008d8910 00000000 00000000-00000000 
           \Driver\GlPciSD
            Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_PNP(1b), IRP_MN_QUERY_CAPABILITIES(9)]
            0 e0 ffff9487008d8910 00000000 fffff80398462430-ffffcb84def5f0b0 Success Error Cancel
           \Driver\GlPciSD    nt!ViFilterGenericCompletionRoutine
            Args: ffffcb84def5f230 00000000 00000000 00000000
 [IRP_MJ_PNP(1b), IRP_MN_QUERY_CAPABILITIES(9)]
            0 e0 ffff948707acbc90 00000000 fffff80329467840-ffffcb84def5f1b0 Success Error Cancel
           \DRIVER\VERIFIER_FILTER    Wdf01000!FxIrp::_IrpSynchronousCompletion
            Args: ffffcb84def5f230 00000000 00000000 00000000
It's the GlPciSD.sys driver, a PCIe card reader driver from Gensys Logic. The version you have installed is old but not ancient...
Code: 
15: kd> lmvm GlPciSD
Browse full module list
start             end                 module name
fffff80d`83db0000 fffff80d`83dea000   GlPciSD  T (no symbols)        
    Loaded symbol image file: GlPciSD.sys
    Image path: \SystemRoot\System32\drivers\GlPciSD.sys
    Image name: GlPciSD.sys
    Browse all global symbols  functions  data  Symbol Reload
    Timestamp:        Mon Dec  5 03:33:12 2022 (638D4A58)
    CheckSum:         0003E00C
    ImageSize:        0003A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:
It might be worth looking for an update for that driver or, if you can, disable the card reader in Device Manager and reboot. See whether the problems disappear.

TBH I rather think this is just another manifestation of whatever hardware issue is afflicting your laptop.

FWIW of the other four dumps, three are 0x133 apparently caused by amdi2c.sys, an AMD chipset driver, and the other is apparently caused by some sort of networking failure, but your graphics driver (amdkmdag.sys) is bang up to date. These too I suspect are also symptoms rather than causes.
 

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

Back
Top