BSOD after wake up from sleep/hibernate

Hi,

I've bought new laptop, installed fresh windows but get many bsod.

I run disk check (Check your hard disk for errors in Windows 7) and memory check (Diagnosing memory problems on your computer), every thing is OK.

All dump file are in this archive:
https://skydrive.live.com/redir?resi...75804A53F8!107
+ 2 first file (061213-7082-01, 061413-7862-01): I go away more than 15 minutes, my laptop goes to sleep, when I come back and turn it on, it shows bsod.
+ 3 next files: I checked my drivers with verifier.exe, After some test, I detect that bluetooth driver has error, it causes bsod each time my laptop restart (with verifier.exe). I removed this driver.
+ last file (061613-11481-01): happended 5 minutes ago, it alo crashes after waking up from sleep. The chrome is up to date (Version 27.0.1453.110 m).

More Info: I install windows on the second drive (SSD).

Update: I run SF_Diagnostic_Tool and upload result here.

When storage and network fail together, we must to see more information before conclude anything. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

From the next time, dont alter the original post. Supply files in the subsequent posts. :)

Make it sure that the KINGSTON SV300S3 SSD is running with an up-to date firmware.
Tech Support Search | Kingston Technology

Get rid of intel rapid storage. First uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.

1. Right click on "my computer" icon and click "manage" on the context menu.
2. It will open the "computer management" window.
3. Select "Device Manager" in the left pane, It will list all the existing devices up.
4. Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
5. Select one Intel device item under it, right click, uninstall.
6. Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
7. Now restart the computer. At restart, windows will auto configure the appropriate native system driver.

Update the Intel HD Graphics Driver, either from our forum link, Latest Intel HD Graphics Driver for Windows 7, or You may get it from Intel Download Center.
Moreover, you may run the Intel (R) Driver Update Utility to auto detect the appropriate driver for your computer.

You need to update Dell Wireless 1901 802.11a/b/g/n (2.4GHz and 5GHz) driver (athrx.sys), too. Search it in Dell's site using your service tag.

And, Disable USB Selective Suspense too.
USB Selective Suspend - Turn On or Off

Also, which antivirus do you use?
_________________________________________________________________________________________
BSOD ANALYSIS:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff6fc4000b7d0, ffffffffc000000e, 2756db860, fffff880016fa648}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc4000b7d0, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 00000002756db860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff880016fa648, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c000000e

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to 0000000000000000

STACK_TEXT:  
00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  INVALID_KERNEL_CONTEXT

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

Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Download, install and update those, and then run full system scans with both of them, one by one.

It is not a typical sleep related BSOD, as I am seeing.

Make it sure that the Kingston SSD is running with the up to date firmware.

Scan the system for possible virus infection with the following programs.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Do some Disc checks.

1. Re-seat the sata and power. Try a new SATA cable, and try the free SATA ports on the motherboard to plug the discs in.
   
2. Run chkdsk /f/r, following the option two of the tutorial Disk Check
3. Seatool for dos: SeaTools | Seagate download
   Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

Disable Bluetooth.

Update Dell Wireless 1901 802.11a/b/g/n (2.4GHz and 5GHz) from Dell's site, using your service tag.

And, Disable USB Selective Suspense too.
USB Selective Suspend - Turn On or Off

Let us know the results.
________________________________________________________________________
BSOD ANALYSIS:

Code:

.............................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffff80000003, fffff80002cb6f40, fffff88009e41538, fffff88009e40d90}

Probably caused by : Wdf01000.sys ( Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+53 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffff80000003, The exception code that was not handled
Arg2: fffff80002cb6f40, The address that the exception occurred at
Arg3: fffff88009e41538, Exception Record Address
Arg4: fffff88009e40d90, Context Record Address

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


EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

FAULTING_IP: 
nt!DbgBreakPoint+0
fffff800`02cb6f40 cc              int     3

EXCEPTION_RECORD:  fffff88009e41538 -- (.exr 0xfffff88009e41538)
ExceptionAddress: fffff80002cb6f40 (nt!DbgBreakPoint)
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 1
   Parameter[0]: 0000000000000000

CONTEXT:  fffff88009e40d90 -- (.cxr 0xfffff88009e40d90)
rax=0000000000000000 rbx=0000057ff14493a8 rcx=30e3f801338c0000
rdx=0000000000000008 rsi=fffffa800d0a69c0 rdi=fffff88000f6d210
rip=fffff80002cb6f40 rsp=fffff88009e41778 rbp=fffffa800ebb6f88
 r8=0000000000000001  r9=fffff80002cfbec0 r10=fffff80002c4d000
r11=fffff88009e41778 r12=0000000000000001 r13=0000000000000000
r14=0000000000000000 r15=0000000000000007
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00000202
nt!DbgBreakPoint:
fffff800`02cb6f40 cc              int     3
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x7E

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION}  Breakpoint  A breakpoint has been reached.

EXCEPTION_PARAMETER1:  0000000000000000

LAST_CONTROL_TRANSFER:  from fffff88000f43a8b to fffff80002cb6f40

STACK_TEXT:  
fffff880`09e41778 fffff880`00f43a8b : fffff880`00f6e308 fffffa80`0e03fb60 fffff880`00f6d210 0000057f`f14493a8 : nt!DbgBreakPoint
fffff880`09e41780 fffff880`00f31243 : 0000057f`f14493a8 fffffa80`0ebb6fc8 fffffa80`0ebb6c60 fffffa80`0ebb6fc8 : Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+0x53
fffff880`09e417d0 fffff880`00f50044 : 00000000`00000000 fffff880`09e41800 00000000`00000000 fffffa80`10547dc8 : Wdf01000!FxPkgIo::StopProcessingForPower+0x3a7
fffff880`09e41850 fffff880`00f50481 : fffff880`00f64250 00000000`00000000 00000000`00000000 00000000`00000307 : Wdf01000!FxPkgPnp::PowerGotoDx+0x64
fffff880`09e41890 fffff880`00f4f6eb : 00000000`0000031a 00000000`00000002 fffff880`00f644c0 fffffa80`10a2e488 : Wdf01000!FxPkgPnp::PowerGotoDxArmedForWakeNP+0x9
fffff880`09e418c0 fffff880`00f4f38e : fffffa80`0ffe0130 00000000`00000002 fffff880`00f644c0 00000000`00000002 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x1db
fffff880`09e419f0 fffff880`00f4f06c : 00000000`00000000 00000000`00000002 00000000`00000000 fffffa80`0ffe0130 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0x13e
fffff880`09e41a60 fffff880`00f5c07f : 00000000`00000000 fffffa80`0ffe0130 00000000`00000000 00000000`00000000 : Wdf01000!FxPkgPnp::PowerProcessEvent+0x1d4
fffff880`09e41af0 fffff880`00f5bc91 : 00000000`00000002 fffff880`09e41bb8 00000000`00000004 00000000`00000000 : Wdf01000!FxPkgFdo::DispatchDeviceSetPower+0x117
fffff880`09e41b40 fffff880`00f4af38 : fffffa80`0d0a69c0 00000000`00000000 fffffa80`0d403b40 fffffa80`0dfc0010 : Wdf01000!FxPkgFdo::_DispatchSetPower+0x21
fffff880`09e41b70 fffff880`00f1a245 : fffffa80`0dfc0010 fffffa80`0dfc0010 fffffa80`0d403b40 fffff880`09e41d00 : Wdf01000!FxPkgPnp::Dispatch+0x314
fffff880`09e41be0 fffff880`00f1a14b : fffffa80`0dfc0010 fffffa80`0dfc0010 00000000`00000000 fffffa80`0d403b40 : Wdf01000!FxDevice::Dispatch+0xa9
fffff880`09e41c10 fffff800`02dd8e55 : 00000000`00000001 00000000`00000000 fffffa80`0d403b40 fffffa80`0dfc00b8 : Wdf01000!FxDevice::DispatchWithLock+0x93
fffff880`09e41c50 fffff800`02f62166 : ffffffff`fa0a1f00 fffffa80`0e03fb60 00000000`00000080 fffff800`02cb6d87 : nt!PopIrpWorker+0x3c5
fffff880`09e41d00 fffff800`02c9d486 : fffff800`02e37e80 fffffa80`0e03fb60 fffff800`02e45c40 fffff880`01239534 : nt!PspSystemThreadStartup+0x5a
fffff880`09e41d40 00000000`00000000 : fffff880`09e42000 fffff880`09e3c000 fffff880`09e414d0 00000000`00000000 : nt!KiStartSystemThread+0x16


FOLLOWUP_IP: 
Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+53
fffff880`00f43a8b 488d442430      lea     rax,[rsp+30h]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+53

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Wdf01000

IMAGE_NAME:  Wdf01000.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc19f

STACK_COMMAND:  .cxr 0xfffff88009e40d90 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+53

BUCKET_ID:  X64_0x7E_Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+53

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