Windows 7 Home Premium Crashes in Sleep Mode

Question

Over the last few days my Windows 7 PC refuses to wake up from sleep mode.  
My configuration is as follows:
Windows 7 Home Premium 64 bit 
Asus P8Z77-V-LE Plus Motherbaord (BIOS 0910)
Intel Core i7-3770 
Samsung 830 SSD
Corsair Vengence RAM (16 Gbytes)
EVGA GeForce GTX660 
I have not made any changes to the machine and I don't think the hardware is a problem as the system does not crash when I disable sleep mode.  I try to keep my drivers current and my system clean.  Virus scans using Avast, Malwarebytes (on demand)
and Microsoft's own Malicious Software Removal tool all come back clean.
Each crash is recorded in an event log entry that looks like this
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> 
  <EventID>41</EventID> 
  <Version>2</Version> 
  <Level>1</Level> 
  <Task>63</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x8000000000000002</Keywords> 
  <TimeCreated SystemTime="2014-05-30T03:08:32.089604600Z" /> 
  <EventRecordID>149206</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="4" ThreadID="8" /> 
  <Channel>System</Channel> 
  <Computer>Raven</Computer> 
  <Security UserID="S-1-5-18" /> 
  </System>
- <EventData>
  <Data Name="BugcheckCode">10</Data> 
  <Data Name="BugcheckParameter1">0xfffff8a000399818</Data> 
  <Data Name="BugcheckParameter2">0x2</Data> 
  <Data Name="BugcheckParameter3">0x0</Data> 
  <Data Name="BugcheckParameter4">0xfffff80002e8225b</Data> 
  <Data Name="SleepInProgress">true</Data> 
  <Data Name="PowerButtonTimestamp">0</Data> 
  </EventData>
  </Event>
And a tool called WhoCrashed generates this report.
On Fri 5/30/2014 5:58:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\053014-7129-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) 
Bugcheck code: 0xA (0xFFFFF8A0003954A8, 0x2, 0x0, 0xFFFFF80002EC225B)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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. 
I tried to analyze install the SDK to analyze the MiniDump files but the installation keeps failing.
My most recent mindump  - the last one before I tuned off sleep mode - is here 
https://dl.dropboxusercontent.com/u/8391385/053014-7129-01.dmp
My impression is that an analysis of the dump file will help me zero in on the fault.
hope I can get some help on this and please let me know if I left out anything
Thanks in advance.

Answer 1

The DMP file is inconclusive. You could run driver verifier to find the underlying issue but WPR is often easier.
In order to diagnose your problem you will need to download and install the below
Install the WPT (windows Performance Toolkit) 
http://www.microsoft.com/en-us/download/details.aspx?id=30652
Help with installation (if needed) is here
When you have, open an elevated command prompt and type the following 
WPRUI.exe (which is the windows performance recorder) and check off the boxes for the following:
First level triage, CPU usage, Disk IO.  
If you problem is not CPU or HD then check off the relevant box/s as well (for example networking or registry)  Please configure your as per the below snip
Click Start
It will reboot 3 t imes and record the data to a file and tell you its name and location.
Zip the file and upload to us on Onedrive (or any file sharing service) and give us a link to it in your next post.
These crashes were related to memory corruption (probably caused by a driver). 
Please run these tests to verify your memory and find which driver is causing the problem.  
If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't
know what it is you probably are not overclocking.
Since it is more likely to be a driver please run verifier first.
1-Driver verifier (for complete directions see our wiki here)
If verifier does not find the issue we can move on to this.
2-Memtest. (You can read more about running memtest here)
Co-Authored by  JMH3143
Wanikiya and Dyami--Team Zigzag