Tablet BSOD while sleeping

gorgor · 07 Aug 2017

Like I said... this looks to me, that the ssd "lost connection" aka, turned off / lost stable power, while the tablet was sleeping. An indicator to me is that Windows says E/A error and a device was not there which should be "Ein nicht vorhandenes Gerät wurde angegeben". I doubt the SSD is actually broken. I read in another thread somewhere, this might be related to "Link Power Managment" of AHCI/PCIe, which you can actually disable in the Intel tool. But when I do this, the Tablet drains the battery in sleep mode, and shows 0% HW sleep with powercfg. Should I maybe remove the Intel storage driver and use Windows default AHCI driver?

BSODHunter · 07 Aug 2017

adding stuff above, please wait till im done

axe0 · 07 Aug 2017

Hi gorgor,

I do not want to fight against you, but the dumps are not the only thing we need in order for us to properly troubleshoot your issue.

You mentioned "EXCEPTION_CODE: (NTSTATUS)" being irrelevant. The exception code gives us the reason why the BSOD was called, multiple exception codes that are the same point to something. It often means a memory violation occured, 0xc00005, which in result gives immediately 2 options, the RAM is bad or a driver is bad. If a driver is bad it is often mentioned somewhere in the dump, if not we know from the exception code where to start. This is the reason why it is relevant :)

Why do we need other information besides dumps?
- The eventlog, it contains a lot of information. For example, often we see hard drives that fail. Very often we can't say from dumps if a drive fails, because when hardware fails it often results in various of BSOD error codes. In such cases we use the eventlog to find anything relevant to connect to the BSOD error codes and identify the drive possibly failing.
- Files like msinfo32, installed, uninstalled, systeminfo, etc.
These files contain all different kind of information. Drivers are part of programs, like security programs or programs which help you control your mouse via the USB. Without files as drivers.txt, msinfo32, uninstalled.txt, dxdiag.txt or other files we cannot determine from which program the driver comes from that may be at fault.

I hope to have explained why we need not only dumps, but the other files as well :)

BSODHunter · 07 Aug 2017

Tablet BSOD while sleeping - Windows 10 Forums

gorgor · 07 Aug 2017

BSODHunter said:

Tablet BSOD while sleeping - Windows 10 Forums

Thank you very much for trying to help. The SSD already had the newest firmware. It could still be though, that the SSD still has bugs, Sandisk is a very shitty company actually for SSDs. I installed the driver, because of the first BSOD, before I dont know which was installed, I think the one, which came with the Chipset package, also one from Intel. The first one installed, was the default MS AHCI one I think. I could try to revert back to that maybe? I think the highest chance of the issue though is what I said, related to power state (incompatibilities). The Intel Chipset Device Software on the Dell site is form 2014 though, I had actually doubts if I should install it or not, or just use the default MS noname drivers, but then I wasnt sure if that was the worst decision of the two. I actually hate how bad Intel maintains their drivers, and stops supporting products older than 2 years usually.

philc43 · 07 Aug 2017

@BSODHunter Please note the dump_iaStorA.sys is not a problem - this driver is only used to record the crash and not part of normal operation.

BSODHunter · 07 Aug 2017

philc43 said:

@BSODHunter Please note the dump_iaStorA.sys is not a problem - this driver is only used to record the crash and not part of normal operation.

Yes I know, but in this case hardware_disk could be related to hardware OR driver?! Or not? Normally I dont look at this, but in this case....maybe its worth a try?!

philc43 · 07 Aug 2017

BSODHunter said:

Yes I know, but in this case hardware_disk could be related to hardware OR driver?! Or not? Normally I dont look at this, but in this case....maybe its worth a try?!

I would think it is worth uninstalling the Intel drivers and trying the default MS drivers - I think gorgor has said he intends to try this. Let's see if it helps.

gorgor · 07 Aug 2017

I just had to look into the event log myself now... and it is obvious, that the crash happened, like I assumed from the beginning, when Windows tried to switch from sleep to hibernate. The memcompress process actually was already indication for that.

2017-08-04 09:20:07 Warnung: Ein Zurücksetzen auf Gerät "\Device\RaidPort0" wurde ausgegeben.
2017-08-04 12:52:29 Warnung: Ein Zurücksetzen auf Gerät "\Device\RaidPort0" wurde ausgegeben.
2017-08-04 12:54:09 Warnung: Ein Zurücksetzen auf Gerät "\Device\RaidPort0" wurde ausgegeben.
2017-08-05 00:00:59 Warnung: Ein Zurücksetzen auf Gerät "\Device\RaidPort0" wurde ausgegeben.
2017-08-05 15:11:15 Warnung: Ein Zurücksetzen auf Gerät "\Device\RaidPort0" wurde ausgegeben.
2017-08-05 19:18:15 Warnung: Ein Zurücksetzen auf Gerät "\Device\RaidPort0" wurde ausgegeben.

all those events, the system had a few seconds later the log entry:

Das System wird in den Standbymodus versetzt.

Ursache: Vom Standbymodus in den Ruhezustand wechseln

and I guess, the two bsod also happened there. It more looks to me like a Windows bug in combination of power state and driver. Windows wants to switch to hibernate => wants to write to disk from inside sleep, but the SSD is not ready / still in sleep mode.

BSODHunter · 07 Aug 2017

yes Im thinking the same. There a direct connection between the error message and standby/hibernate:

Code:

Event[4273]:
  Log Name: System
  Source: iaStorA
  Date: 2017-08-06T03:42:20.725
  Event ID: 129
  Task: N/A
  Level: Warnung
  Opcode: N/A
  Keyword: Klassisch
  User: N/A
  User Name: N/A
  Computer: mkdr-V11
  Description: 
Ein Zurücksetzen auf Gerät "\Device\RaidPort0" wurde ausgegeben.

Code:

Event[4274]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2017-08-06T03:42:27.927
  Event ID: 42
  Task: N/A
  Level: Informationen
  Opcode: Info
  Keyword: N/A
  User: N/A
  User Name: N/A
  Computer: mkdr-V11
  Description: 
Das System wird in den Standbymodus versetzt.


Ursache: Vom Standbymodus in den Ruhezustand wechseln – vorhergesagte Benutzerabwesenheit