Windows 10: Tablet BSOD while sleeping

See, it makes sense. I am sure the bug was introduced with the memory compress "feature", which was introduced with anniversary update. I am sure all is fine with the drivers, there are no other AHCI drivers available anyway. It happens with the Intel driver, it happens with the default MS AHCI driver.

It mostly didnt got triggered or was not relevant before the compressed memory feature, so it never came to a bluescreen before then. Because I can find the issue with the 129 event back before Windows 10, it mostly wasnt much relevant though before the memory compressing. But with the memory compressing, Windows seems to swap more and more happily, and if it does, and it can access the disk (for whatever reason), it seems to bluescreen like this.

Either there is a bug in Windows, how to handle disks who went sleep in sleep mode itself, or a bug in the SSDs firmware, or both. I can find posts about this issue though for a high range of disks, by Sandisk, Kingston Crucial, it is unliky they all have the same issue in their firmware. I am sure it is Windows fault.

 

Have you tried the Dell Intel chipset drivers? I noticed the current one is newer than the one from Dell.
Did you run driver verifier?

The issue is where a driver accessed compressed memory but fails to properly handle unexpected data.

 

I have used the procedure which suggest Dell for Windows 10 clean install, use the cab from there site which contains all drivers. The intel inf chipset driver, the current one, is newer, but doesnt contain anymore drivers for the 5th gen Core m series (the one in the tablet), same for the rapid store drivers, the current one isnt supporting the 5th gen core series anymore.

What shall I do with the driver verifier?

 

I would suggest following below for driver verifier.

Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

I actually found this blog entry which might give a hint: Event ID 129 s System Center Blog stating:

"PCI Express has "active-state" power management, which lowers power consumption when the bus is not active (that is, no data is being sent between components or peripherals). On a parallel interface such as PCI, no transitions occur on the interface until data needs to be sent.In contrast, high-speed serial interfaces such as PCI Express require that the interface be active at all times so that the transmitter and receiver can maintain synchronization. This is accomplished by continuously sending idle characters when there is no data to send. The receiver decodes and discards the idle characters. This process consumes additional power, which impacts battery life on portable and handheld computers.
To address this issue, the PCI Express specification creates two low-power link states and the active-state power management (ASPM) protocol. When the PCI Express link goes idle, the link can transition to one of the two low-power states. These states save power when the link is idle, but require a recovery time to resynchronize the transmitter and receiver when data needs to be transmitted. The longer the recovery time (or latency), the lower the power usage. The most frequent implementation will be the low-power state with the shortest recovery time."

Fun fact: powercfg /energy says as an error, that ASPM is disabled because of an "incompatibility". Do I understand this correctly, that ASPM is like a backup protocol to speak to the HDD when its in sleep mode? This might explain, why Windows cant reach it anymore, if ASPM isnt working too.

I had a few hangs actually too under normal usage, for example clicking on the start button and Windows would hang for about 30 seconds. This also happens a lot when turning the tablet on from sleep and I log in my PIN, then screen goes black and takes about 30 seconds to come back.

disablePagingExecutive = 1 didnt help btw. I had anther BSOD while testing it the other hour while charging the tablet.

 

Have you run driver verifier?

 

Yes it didnt produce any bsod. I let it run for about 12h, while having connected standby deactivated, so just having monitor turned off.

 

Please make sure that driver verifier runs for at least 48h.

 

No triggered bsod by driver verifier. I had deactivated connected standby via registry, and since then no bsod, no disk related event in the logs, no event 129. It is just when the tablet enters connected standby.