BSOD after waking from Sleep No Crash Dump

Why not try this first RAM - Test with Memtest86+ make sure your laptop is plugged in. Run it for 7 complete passes. (quite a few hours) best to run it overnight. It tests you ram for errors.

Thank you Steve for your input in this thread! :)

Also for future reference, where did you find the reference to BCC F4? Much thanks in advance.

From the BSOD index BSOD Index F4 has no cause stated so it could be anything. But in most cases we experienced it is a driver, a system optimizer software, or back-up tools like acronis and then mainly related to storage (HDD/SSD).

Let us know the results from memtest and newer crash reports and we should continue diagnosing. :)

koolkat77 said:

Thank you Steve for your input in this thread! :)

You're very welcome.

Any BSOD-s?

Please upload them

Very weird. I don't seem to find such a thing in google either.

Code:

................................................................
...................................
Loading User Symbols
Loading unloaded module list
......
*** WARNING: Unable to verify timestamp for rspCrash64.sys
*** ERROR: Module load completed but symbols could not be loaded for rspCrash64.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck DEADDEAD, {0, 0, 189660af, 3c2a58ed}

Probably caused by : rspCrash64.sys ( rspCrash64+108b )

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

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

MANUALLY_INITIATED_CRASH1 (deaddead)
The user manually initiated this crash dump.
Arguments:
Arg1: 0000000000000000
Arg2: 0000000000000000
Arg3: 00000000189660af
Arg4: 000000003c2a58ed

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xDEADDEAD

PROCESS_NAME:  WhoCrashedEx.e

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff88008fe108b to fffff80002ae5fc0

STACK_TEXT:  
fffff880`0acd9838 fffff880`08fe108b : 00000000`deaddead 00000000`00000000 00000000`00000000 00000000`189660af : nt!KeBugCheckEx
fffff880`0acd9840 00000000`deaddead : 00000000`00000000 00000000`00000000 00000000`189660af 00000000`3c2a58ed : rspCrash64+0x108b
fffff880`0acd9848 00000000`00000000 : 00000000`00000000 00000000`189660af 00000000`3c2a58ed fffffa80`047086d0 : 0xdeaddead


STACK_COMMAND:  kb

FOLLOWUP_IP: 
rspCrash64+108b
fffff880`08fe108b ??              ???

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  rspCrash64+108b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: rspCrash64

IMAGE_NAME:  rspCrash64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50976856

FAILURE_BUCKET_ID:  X64_0xDEADDEAD_rspCrash64+108b

BUCKET_ID:  X64_0xDEADDEAD_rspCrash64+108b

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

1: kd> lmvm rspCrash64
start             end                 module name
fffff880`08fe0000 fffff880`08fe8000   rspCrash64 T (no symbols)           
    Loaded symbol image file: rspCrash64.sys
    Image path: \SystemRoot\system32\DRIVERS\rspCrash64.sys
    Image name: rspCrash64.sys
    Timestamp:        Mon Nov 05 13:18:46 2012 (50976856)
    CheckSum:         0001102E
    ImageSize:        00008000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Perform a system file check:
Run the System File Checker. It allows the user to scan for and restore corruptions in Windows system files.

• 1. Click on the
  2. Type CMD on Search
  3. Left click and Run as Administrator
  4. Type SFC /scannow

Full tutorial here:

• SFC /SCANNOW Command - System File Checker