Tablet BSOD while sleeping

Page 5 of 6 FirstFirst ... 3456 LastLast

  1. axe0
    Posts : 14,903
    Windows 10 Pro
       New #41

    I have to correct you on a few things.

    This also seems just to happen in connected standby, so scanning the disk wont show any errors.
    Incorrect, hardware errors can be very specific and very 'wild'. I've seen it happen that playing a game for a specific time crashed the system as a result of a disk error which was beyond repair.

    This says, DisablePagingExecutive is just for keeping drivers and kernel modules in memory, this is not for user space apps, so why should it grow over time?
    Several programs use drivers, both kernel mode and user mode. A tiny bug, which is always there, could hang on to memory even when the program closes or perform a loop of infinite calls consuming memory.

    It seems to me the problem is related to Windows 10's memory compression feature, in combination with it storing drivers on disk, then in combination of this power saving of the SSD in connected standby. Windows somhow cant reach the SSD or wake it up, wants to load something from disk, and crashes.
    This sounds similar like a firmware bug in the Samsung 800 series from a long time ago. Many systems with a samsung 800 ssd couldn't wake up from sleep, either a firmware update or another SSD solved that problem.
      My Computers
    Quote Quote

  3. gorgor
    Posts : 194
    Windows 10
    Thread Starter
       New #42

    I think you should maybe read the whole thread. I am totally sure my thesis is correct. It is related to AHCI LPM. It is related to a Windows 10 only (mostly up from anniversary update). It wont happen in normal use. It didnt happen in Windows 8, mostly because of changes to the connected standby (now modern standby). So you are incorrect of saying I am incorrect. It is not a hardware error.

    SDSSDA240G problems with LPM on Windows 10 anniver... - SanDisk Forums

    https://answers.microsoft.com/en-us/...73c25ea?page=2

    And I find other reports like this, that it began with Windows 10 anniversary update.

    Deactivating LPM seems to fix the crashes, but this is not an option for tablet users, because it drains the tablet literally in hours. It wont have no big effect on laptops or desktops having the issue.

    disablepagingexecutive seems to be a "fix" (more like a shabby workaround) too for this, because it wont crash Windows when it wants to load something from swap aka disk not ready in time.
      My Computer
    Quote Quote

  4. axe0
    Posts : 14,903
    Windows 10 Pro
       New #43

    Alright, I've reread the whole thread and done some reading about compressed memory.

    Compressed memory is memory that the Memory Management decides is long enough being untouched to move it to the so-called 'modified list' where it is being compressed to 40% of the original size. After compression and after the memory is moved to the pagefile, it is put on the 'standby list' where it can be reused through an I/O operation. Access is allowed by the process that was the rightful owner of the memory and by another process.
    When the rightful owner accesses the compressed memory from the pagefile it is called a 'softfault', if something else accesses the memory and the rightful owner accesses the memory later it is called a 'hardfault'.
    See Windows 10 Memory Compression - Windows 10 Forums

    After reading this I have a different opinion on what I think might have happened in the earlier BSOD.
    Going through the stack of the earlier BSOD, a driver caused a hardfault when trying to access its compressed memory which appeared to have already been called. I believe that the error handling by this driver is simply improper seeing the result of an unhandled exception in the call stack after the driver received its compressed page.

    Did you run driver verifier?
      My Computers
    Quote Quote

  6. gorgor
    Posts : 194
    Windows 10
    Thread Starter
       New #44

    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.
      My Computer
    Quote Quote

  7. axe0
    Posts : 14,903
    Windows 10 Pro
       New #45

    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.
      My Computers
    Quote Quote

  8. gorgor
    Posts : 194
    Windows 10
    Thread Starter
       New #46

    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?
      My Computer
    Quote Quote

  9. axe0
    Posts : 14,903
    Windows 10 Pro
       New #47

    I would suggest following below for driver verifier.



    Diagnostic Test

     DRIVER VERIFIER


    warning   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   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.
      My Computers
    Quote Quote

  10. gorgor
    Posts : 194
    Windows 10
    Thread Starter
       New #48

    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.
      My Computer
    Quote Quote

  12. axe0
    Posts : 14,903
    Windows 10 Pro
       New #49

    Have you run driver verifier?
      My Computers
    Quote Quote

  13. gorgor
    Posts : 194
    Windows 10
    Thread Starter
       New #50

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

 

  Related Discussions
Laptop started rebooting, seems it happens when it goes to sleep mode. Nothing suspicious in device manager, in event viewer: Any pointers on how to fix it please? No new hardware added recently.
Surface Pro 3 BSOD when Idle/Sleeping
in BSOD Crashes and Debugging

I have a Surface Pro 3 and it has an issue where when it sleeps, it will crash and power off. There is a critical Kernel-Power event (41) whenever this happens, and sometimes it's accompanied by a BSOD, other times it's not - The BSOD bugcheck...
A couple days ago when normally putting my PC to sleep at night it restarted. I then tried to put it to sleep again and watched as the screen went black and the pc just sat there on for like 10 seconds then began the process of rebooting. The next...
BSOD/Bugcheck while sleeping, AC plugged in
in BSOD Crashes and Debugging

Hello, I just bought a used Dell Latitude E7450 laptop (256GB SSD, 8GB RAM). Last night, I just upgraded to Windows 10 Pro, and downloaded all the official drivers from the Dell site and installed them. So I don't know if this was a problem while...
Greetings All: I installed Windows 10 on a fully compatible ASUS Transformer T100TA yesterday. All is working great except, whenever I remove the tablet from the dock I get the BSoD (kmode_exception_not_handled) and the tablet reboots. I have...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 09:09.
Find Us




Windows 10 Forums