Windows 10: Windows blue screening when waking up from S3 sleep

Since changing my sleep mode from S0 modern standby to S3 classic sleep a month or two ago, my machine has blue screened 3 times, every time when waking up from sleep mode, with the unexpected store exception message. It happened on 23 December, 8 January and again today. I would love to find out what the cause of this is. As far as I know my system is up to date with the drivers etc. Is it possible to send the minidump files to somebody who is knowledgeable and can take a look at them?

:)

 

Windows 10 blue screens after waking from sleep.

Steps to that cause this problem:

• Allowing windows to sleep.
• Waking once, logging in.
• Allowing it to sleep once more.
• Wait for some time like 2 hours.
• Try to login again.

After all these steps my laptop Dell Vostro 3546, stops responding on the login screen, no inputs will be taken and then Blue screens by saying Critical_Store_Exception. I have collected some crash dumps and posted it here: CrashDumps.

Blue Screen View says that the BSOD happened because of something went wrong with the ntoskrnl.exe, address ntoskrnl+142760, file version of ntoskrnl.exe is "10.0.10586.306 (th2_release_sec.160422-1850)".

 

Windows 10 Pro ver. 1709 now crashes with a BSOD when waking from S3 sleep mode.

Hi John,

There is a possibility that a driver is failing to start when waking up the computer from an S3 sleep mode. Kindly access this
article. The article contains multiple ways on how to resolve blue screen errors. Once you've accessed
the page, select a scenario and do all of the steps found under that chosen scenario.

Keep us posted.

 

sleep problem with standby when both s1 and s3 shows under powercfg

My supermicro X9SRA board only have the option diable, s1, s3 under acpi.... but if i select s3 then under windows powercfg /a it would give standby (s1 s3)

and that seems to be the problem that i can't properly wake the computer after it goes to sleep and power down everything. a touch of the keyboard would wake up the fan but you just have a blank screen and an unresponsive computer...

conversely, i notice a few other computers i have where s3 sleep works properly, under powercfg /a, you only have standby (s3)

is there a way to tell windows to specifically only use s3 when both s1 and s3 standby are listed under powercfg /a ?