BSOD when resume from sleep (+1 hour)

Hello,

I have the problem with my new setup that it gives me a bluescreen when i wake it up from Sleep mode that's approximately +1 hour long sleep mode. When i set the pc to sleep and almost immediately wake it up by keyboard I get no bluescreen.

I can't get it fixed. Mayby someone can get this clear?

I tried the following already:
Memtest - 13 cycles, 28 hours (http://i60.tinypic.com/24m9o9d.jpg)
CPU test Intel
CPU stress test
GPU stress test
SSD check Samsung Magician
Bios update to newest version
WhoCrashed logs
Install Windows 7 & 8.1 on another SSD (M4 Crucial 128 GB )


Setup:
MB: Gigabyte Z97X Gaming 3
CPU: Intel Core i7 4790
CPU koeler: Scythe Mugen 4 PCGH Edition
RAM: Crucial Ballistix Sport 16GB DDR3-1600 CL9 kit
GPU: MSI GeForce GTX 970 Gaming 4GB
HDD: Samsung 850 Evo 500GB
PSU: Corsair RM650
On this moment installed Windows 7 x64 - Build 7601 SP1 (+all updates)

I have included the zip file in this post.

The versatility of the crash dumps are strongly indicating something going extremely odd there. The first notion goes to the RAM, which you nullified, the camera snap does the job.

Then we have to dig the deep for the root of the issue. At first I would like to ask you one thing. What is the purpose of this program in your system?

Start Menu\Programs\KMSpico

Let us know.

KMSPico is used for counterfeit activation of windows. So it alters the system codes with some heavy moderated codes. In such a situation, all sort of issues are possible, and troubleshooting is worthless by virtue of this program.

If you opt for a genuine software, it will help you to get the reliable error data at least, with which troubleshooting will be possible.

Till you get a legit OS installed and activate it using a legit key, there will not be a scope of troubleshooting.

OK, let us wet and see.

When I wake up my pc this morning it starts, but gives me no screen activity. But I didn't hear it reset either.
So i quickly disconnect my 2 external harddrives out of the USB 3.0 ports and hit the reset button.

It resets, give me on the screen: "Resuming Windows" and it starts in the same state I left it the night before, without BSOD :).

In the logs I found the following entry 5 times:
An error was detected on device \Device\Harddisk2\DR2

I have both SSD's plugged in (harddisk0 & harddisk1) en the external harddrivers connected via USB 3.0. I think they cause the boot failure when I resume from sleep?

Edit:
I use: Intel Usb3.0 version 3.0.4.65 (from the Gigabyte website)

On the Intel website the newest version is: 3.0.5.69 (https://downloadcenter.intel.com/dow...Chipset-Family)

Maybe an driver update will fix the issue?

Yesterday I installed the new USB 3.0 driver and set my pc to sleep in the evening.
In the morning I resume it from sleep without a problem but after a couple of minutes I get the following BSOD:

I also use the DM collector again and added the zip as a Attachment.

Code:

Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\070115-5397-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18869.amd64fre.win7sp1_gdr.150525-0603
Machine Name:
Kernel base = 0xfffff800`03253000 PsLoadedModuleList = 0xfffff800`0349a730
Debug session time: Wed Jul  1 09:30:02.583 2015 (UTC + 2:00)
System Uptime: 0 days 10:05:10.363
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
..................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa800498ae30, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+338a4 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
	contains the address of the PFN for the corrupted page table page.
	On a 32 bit OS, parameter 2 contains a pointer to the number of used
	PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa800498ae30
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  WerFault.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER:  from fffff80003337810 to fffff800032c78c0

STACK_TEXT:  
fffff880`0add56e8 fffff800`03337810 : 00000000`0000001a 00000000`00041790 fffffa80`0498ae30 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0add56f0 fffff800`032fb1b9 : 00000000`00000000 000007fe`f355cfff fffffa80`00000000 fffff880`00960000 : nt! ?? ::FNODOBFM::`string'+0x338a4
fffff880`0add58b0 fffff800`035dfb71 : fffffa80`10d8ce20 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`0add59d0 fffff800`035dff7f : 0000007f`00000000 000007fe`f3240000 fffffa80`00000001 fffffa80`1034ddc0 : nt!MiUnmapViewOfSection+0x1b1
fffff880`0add5a90 fffff800`032c6b53 : 00000000`00000000 000007fe`f354800c fffffa80`105d3b10 000007fe`f3240000 : nt!NtUnmapViewOfSection+0x5f
fffff880`0add5ae0 00000000`7713de5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0028a448 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7713de5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+338a4
fffff800`03337810 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+338a4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  556356e8

IMAGE_VERSION:  6.1.7601.18869

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+338a4

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+338a4

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x1a_41790_nt!_??_::fnodobfm::_string_+338a4

FAILURE_ID_HASH:  {b7b6e799-20a2-a8ed-3529-d30731685de0}

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