I had hoped that the latest driver and firmware updates had fixed it, so I re-enabled the default hibernation after 120 minutes of sleep. That usually would put my surface book into the sleep of death where the screen wouldn't wake up, though the keyboard
backlighting would light up when pressing a key. The only thing that would recover my machine would be a forced shutdown. Note: when this would happen all that would be logged in the reliability monitor would be a "the computer unexpectedly shutdown". Anyways,
after the latest updates and reinstating the factory default 120 minute sleep to hibernation schedule I tried to test the machine after being asleep for a few hours, and happily it seemed to appear to come out of hibernation. However, it being difficult to
distinguish between a wake from hibernation and a full restart, I decided to check the reliability monitor to see if anything was logged, and to my horror there were several ugly and unusual events listed. There were 5 events that were all time-stamped at
the same instant @ 11:32PM. So, I would have to say definitely not fixed. More like made much worse, since before the updates I never would see all those events. It would only log the unexpected shutdown from me having to force a shutdown to recover from the
sleep of death state.
Here are those 5 events from the sleep of death, post 5/25/16 firmware updates.
#1.
Description
Faulting Application Path: C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe
Problem signature
Problem Event Name: MoAppCrash
Package Full Name: Microsoft.Windows.ShellExperienceHost_10.0.10586.0_neutral_neutral_cw5n1h2txyewy
Application Name: praid:App
Application Version: 10.0.10586.306
Application Timestamp: 571afaa5
Fault Module Name: QuickActionsDataModel.dll
Fault Module Version: 10.0.10586.122
Fault Module Timestamp: 56cc1a1b
Exception Code: c0000005
Exception Offset: 00000000000045ef
OS Version: 10.0.10586.2.0.0.256.48
Locale ID: 1033
Additional Information 1: f783
Additional Information 2: f783caecb2dd1b170710c0722cdfac4b
Additional Information 3: 5e84
Additional Information 4: 5e845f007f79d6d4b3c53d2dd1f15e86
Extra information about the problem
Bucket ID: 5f34d1aa912730a214f7ea46523ae718 (133326888755)
#2.
Windows was not properly shutdown
Description
The previous system shutdown at 11:23:39 PM on 5/31/2016 was unexpected.
#3.
Description
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffe0004fa05060, 0xffffd000e7670890, 0xffffe00051d95490). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 9e577e0d-f560-4217-b392-fe8bde255a5a.
#4.
Description
A problem with your hardware caused Windows to stop working correctly.
Problem signature
Problem Event Name: LiveKernelEvent
Code: 15f
Parameter 1: 1
Parameter 2: ffffd000f2a8ea28
Parameter 3: 493fe
Parameter 4: 0
OS version: 10_0_10586
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.10586.2.0.0.256.48
Locale ID: 1033
Extra information about the problem
Bucket ID: LKD_0x15F_DRIPS
#5.
Shutdown unexpectedly
Problem signature
Problem Event Name: BlueScreen
Code: 9f
Parameter 1: 3
Parameter 2: ffffe0004fa05060
Parameter 3: ffffd000e7670890
Parameter 4: ffffe00051d95490
OS version: 10_0_10586
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.10586.2.0.0.256.48
Locale ID: 1033
Extra information about the problem
Bucket ID: 0x9F_3_IMAGE_pci.sys