Computer switches off when attempting to come out of sleep

[HawkinsT]

Hi, I've just built a new PC, with the following specs:

MSI Z170-A Pro
i7-6700K
AMD HD 6850
2 x 16GB Corsair DDR4 2400MHz Vengeance LPX
500GB Samsung 850 EVO SSD
2 x 2TB Hitachi Ultrastar
EVGA SuperNova 650W S2 (80+/Gold efficiency)

Everything works completley fine for me, except for trying to get sleep working. Whenever the computer enters sleep, upon trying to resume, I hear the fans spin up, and see the front fan led come on, then within about 3 seconds, the PC shutsdown and must be restarted. I've seen a few similar threads to this, but with no working solution (for me).

I am running Windows 10 Professional x64 (I've run chkdk /F, sfc/scannow, Windows Memory Diagnostic, MemTest86 (6 passes), Prime95 + Folding@Home (run for over 48 hours straight with 100% cpu and gpu)), and everything is completley stable with no issues. I have updated to the latest drivers and have even flashed my bios to the latest version (and when that didn't work, the latest beta version).

The 850 evo and the HD 6850 I had in my previous windows 10 pc, which would sleep fine.

I've disabled hyprid sleep and hibernation. I've tried disabling the 'turn off hard disk' setting. Both my mouse and keyboard have 'allow this device to wake the computer' selected from device manager, and 'allow the computer to turn off this device to save power' disabled. In the BIOS I have disabled the option to turn off the computer to protect from unusual power surges.

When I was first trying to get the computer to sleep I had it set in the BIOS to let the OS handle wake up actions, but I was finding neither the keyboard nor mouse would wakeup the system. Pressing the power button would give the result I have described (start waking up, then shutdown). I switched this option to let the BIOS handle wakeup actions and selected 'usb devices'. Now keyboard and mouse input have the same result as hitting the power button.

This is my third install of windows 10. I have tried both home and professional (both x64), and have used different ISOs (all downloaded from microsoft) each time.

In event viewer there doesn't seem to be anything useable (at least to my knowledge), but in chronological order I get these on each failed wakeup attempt:

Error: The previous system shutdown at 15:47:03 on ‎01/‎08/‎2016 was unexpected.

Critical: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Error: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0xfffff680577763e8, 0x0000000000000002, 0x0000000000000000, 0xfffff8014f535182). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 46680a7a-dff5-4f49-8fe9-a4a06faee9f7.

I have tried debugging the dump file with windbg, but didn't see anything of relevance (I'm fairly sure the error occurs before here). My knowledge on debugging windows drivers is somewhat limited though, but there was nothing immediately apparent. I have however included the detailed debugging information below (the DMP file itself is about 1.6GB):

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff680577763e8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8014f535182, address which referenced memory

Debugging Details:
------------------

Page 5f4e1 not present in the dump file. Type ".hh dbgerr004" for details

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  10586.494.amd64fre.th2_release_sec.160630-1736

SYSTEM_MANUFACTURER:  MSI

SYSTEM_PRODUCT_NAME:  MS-7971

SYSTEM_SKU:  Default string

SYSTEM_VERSION:  1.0

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  1.B0

BIOS_DATE:  05/11/2016

BASEBOARD_MANUFACTURER:  MSI

BASEBOARD_PRODUCT:  Z170-A PRO (MS-7971)

BASEBOARD_VERSION:  1.0

DUMP_TYPE:  1

BUGCHECK_P1: fffff680577763e8

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8014f535182

READ_ADDRESS:  fffff680577763e8 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiAgeWorkingSet+302
fffff801`4f535182 498b1e          mov     rbx,qword ptr [r14]

CPU_COUNT: 8

CPU_MHZ: fa8

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R)  SIG: 84'00000000 (cache) 84'00000000 (init)

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

PROCESS_NAME:  MpCmdRun.exe

ANALYSIS_SESSION_HOST:  TOBY-DESKTOP

ANALYSIS_SESSION_TIME:  08-01-2016 17:27:07.0523

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

TRAP_FRAME:  ffffd00090dcf220 -- (.trap 0xffffd00090dcf220)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000800000000000 rbx=0000000000000000 rcx=ffffe00200dcfd40
rdx=0000000fffffffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff8014f535182 rsp=ffffd00090dcf3b0 rbp=ffffd00090dcf4b0
 r8=8000000000000000  r9=0000007ffffffff8 r10=0000098000000000
r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
nt!MiAgeWorkingSet+0x302:
fffff801`4f535182 498b1e          mov     rbx,qword ptr [r14] ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8014f5d74e9 to fffff8014f5cc940

STACK_TEXT:  
ffffd000`90dcf0d8 fffff801`4f5d74e9 : 00000000`0000000a fffff680`577763e8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffd000`90dcf0e0 fffff801`4f5d5cc7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffd000`90dcf220 fffff801`4f535182 : ffffd000`90dcf4c0 fffff801`4f51af80 00000000`00000000 00000000`00000146 : nt!KiPageFault+0x247
ffffd000`90dcf3b0 fffff801`4f540d9a : ffffe002`00dcfd40 ffffe001`e7a192a0 ffffe002`00dcfd40 00000000`00000000 : nt!MiAgeWorkingSet+0x302
ffffd000`90dcf700 fffff801`4f5407eb : 00000000`00000000 ffffd000`90dcf980 ffffd000`90dcf8b0 00000000`00000000 : nt!MiTrimOrAgeWorkingSet+0x15a
ffffd000`90dcf7b0 fffff801`4f4909d3 : fffff801`4f785c80 00000000`00000001 00000000`00000106 00000000`00000002 : nt!MiProcessWorkingSets+0x1fb
ffffd000`90dcf960 fffff801`4f5b0545 : 00000000`00000002 00000000`00000002 00000000`ffffffff 00000000`00000001 : nt!MiWorkingSetManager+0xa7
ffffd000`90dcfa20 fffff801`4f4d0a45 : ffffe001`e7b64040 00000000`00000080 fffff801`4f5b02f8 be2d59a1`ae394a08 : nt!KeBalanceSetManager+0x24d
ffffd000`90dcfb10 fffff801`4f5d1ae6 : ffffd000`90bc0180 ffffe001`e7b64040 fffff801`4f4d0a04 088e9a1a`3f3275d1 : nt!PspSystemThreadStartup+0x41
ffffd000`90dcfb60 00000000`00000000 : ffffd000`90dd0000 ffffd000`90dc9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  0b7fd279f8f08595961e6b53af24434648d2999c

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  68d24624aa1f97a727dfa4af87fc093683ce0427

THREAD_SHA1_HASH_MOD:  bc100a5647b828107ac4e18055e00abcbe1ec406

FOLLOWUP_IP: 
nt!MiAgeWorkingSet+302
fffff801`4f535182 498b1e          mov     rbx,qword ptr [r14]

FAULT_INSTR_CODE:  481e8b49

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiAgeWorkingSet+302

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  5775e2f5

IMAGE_NAME:  memory_corruption

BUCKET_ID_FUNC_OFFSET:  302

FAILURE_BUCKET_ID:  AV_nt!MiAgeWorkingSet

BUCKET_ID:  AV_nt!MiAgeWorkingSet

PRIMARY_PROBLEM_CLASS:  AV_nt!MiAgeWorkingSet

TARGET_TIME:  2016-08-01T14:48:23.000Z

OSBUILD:  10586

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2016-07-01 04:26:45

BUILDDATESTAMP_STR:  160630-1736

BUILDLAB_STR:  th2_release_sec

BUILDOSVER_STR:  10.0.10586.494.amd64fre.th2_release_sec.160630-1736

ANALYSIS_SESSION_ELAPSED_TIME: 661

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_nt!miageworkingset

FAILURE_ID_HASH:  {a2dd9c19-c4fc-761b-f40a-b8172b183d05}

Followup:     MachineOwner
---------

If anyone has any suggestions as to how I can rectify this, it'd be most appreciated! Alternatively, if you would like any more information on anything, please let me know.

Edit: I forgot to mention, the CPU idles at 37'C in a 21'C room, and doesn't tend to get very hot. The hottest I've managed to get it is 70'C after several hours of stress testing Prime95's maximum heat test at 100% usage. Also, all my stress testing was done at a 4.4GHz overclock with stock voltages and the memory running an XMP profile (to meet its 2400MHz specification), however for the purposes of solving this I have reverted all settings back to stock, so my CPU is running at 4GHz, and the memory is actually underclocked at 2133MHz.

 

[HawkinsT]

To give an update; since updating to Windows 10 Anniversary Edition yesterday I tried sleeping again; on first attempt my monitors turned on and I could see the login screen and move the mouse for a couple of seconds. Then I got a BSOD reading CRITICAL_PROCESS_DIED. On reboot and further tried to sleep, the behaviour is back to how it was before (the monitors don't turn on, and the computer turns itself off after 2-10 seconds).

I also forgot to mention before, but I have tried a selective startup with msconfig (only loading system services), and the error still occurs; although I suspected this already, given that it happens on all three clean installs I've done to try to fix this problem.

 

[Colif]

I can't read all that but this can.. Download and run http://www.resplendence.com/whocrashed
it reads the memory dump and spits out a summary

copy/paste results here

It might show what cause is so we can stop guessing in that other thread

 

[HawkinsT]

I can't read all that but this can.. Download and run http://www.resplendence.com/whocrashed
it reads the memory dump and spits out a summary

copy/paste results here

It might show what cause is so we can stop guessing in that other thread

Thanks (again) for responding. Unfortunately the condensed version from WhoCrashed isn't overly helpful:

On Tue 02/08/2016 19:22:41 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\080216-11375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1F4DD8) 
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80009885DD8, 0xFFFF8980137632E8, 0xFFFF898013762B10)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Tue 02/08/2016 19:22:41 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF80009885DD8, 0xFFFF8980137632E8, 0xFFFF898013762B10)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Tue 02/08/2016 18:33:59 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\080216-19265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90) 
Bugcheck code: 0xEF (0xFFFF9288060FF180, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[Colif]

true., sometimes it shows the driver name, other times it just points at windows

Sleep problems with your board

another one

follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step belowo: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c/windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share a link here.

Some one who can read these things will help you more. I will add a tag to post.

 

[HawkinsT]

I already created a minidump through this method. I would upload it (1.6GB), but I've just read through the two threads you mentioned. It seems, that MSI lists my ram as 'overclock compatible' but not 'compatible' (whatever that means). The bios has a profile for my exact ram, but according to many owners of the motherboard with the same issue, the board is incredibly picky with ram and MSI won't acknowledge this as a problem; apparently I should have gone g.skill instead of corsair if I wanted to use 16GB modules.

This is a shame as it's my first experience with MSI, and I went with them specifically because of their reputation. Nevertheless, I shall contact them directly and see if they can offer a solution (other than buy different ram), but between this and their broken english in the bios and manual, I'm not sure I'll rush back to using them again anytime soon.

Thanks again for your assistance; I've picked your previous answer as the solution.

 

[HawkinsT]

Update:
I was writing to MSI to report the issue and noticed they've added a new BIOS today, so I flashed my bios and now the computer resumes from sleep fine! I won't get back the several hours I've spent trying to fix this, but good to know the issue wasn't with my operating system and it's now fixed!

 

[Colif]

Yay!