Home build: crash after waking up from "sleep mode"

Greetings All,

First off, thank you for helping with these issues - I think what you guys (and gals) do is awesome and I wish I had the same troubleshooting skills.

I have recently completed a new home build with the following specs:

Processor: i7-6700k
Motherboard: Gigabyte GA Z170X Gaming GT
Memory: Corsair Vengence LPX DDR4, 2666
GPU: Sapphire Radeon R9 Fury
SSD: Intel 750 Series, 1.2 TB
PSU: Corsair RM Series 750 Watt
Case: Corsair Carbide Series Air 540
OS: Windows 10 Home

The build went fairly well and the computer seems rather stable (and very, very quiet). But the main problem I am having is that after the computer wakes up from sleep mode, it crashes a few seconds later and re-boots. The event log will be riddled with entries upon reboot, but one critical event in particular catches my attention:

Event ID: 41, Kernel-Power

There are also a number of Errors that show up; not sure if they are normal or not but I suspect errors should not typically occur. I've updated all of my device drives but that didn't really seem to help the issue. I also tried changing the power settings and un-selecting "Fast Startup" as per a recommendation I read on a different forum but that had no effect. To prevent the system crash, I've simply been shutting down my computer after I am done using it which isn't a bad thing, but I'd like to have the option of using sleep mode. Attached below is a screen shot of my event log:



Also, for what it's worth, I remember having a bitch of a time with sleep mode with RAID 0 on my old computer, so perhaps Windows does not yet adequately support "sleep mode" with PCI-E controllers.

Thanks again,

Michael

Double posting? Not nice. You also posted in the proper section called BSOD Crashes and Debugging.

Berton said:

Double posting? Not nice. You also posted in the proper section called BSOD Crashes and Debugging.

Did you read the response I had in BSOD section from axe0? Clearly not as it instructed me to post in Performance and Maintenance.

Although technically it is a double post, if you look through his other thread, you will see that he doesn't actually get a BSOD, so the "double post" was because he didn't post it in the right section the first time.

I can only go with what I got chastised for doing some time back, once scolded I tend to believe the scolder and assume others should abide by the same.