BSOD after waking from Sleep No Crash Dump

[finesthours]

I have an Asus G50VT-X5 and I just installed a new Intel 330 SSD 240GB and started with a fresh Windows 7 Pro install. I've installed all windows updates (including SP1) and all the latest driver updates from Intel, Nvidia and the Asus driver support site.

Every time I wake from sleep the computer freezes and then after a couple of seconds bsod's. I've uploaded a picture of the bsod and while in that picture it doesn't show it, I have seen that it proceeds to say something to the effect of "physical memory dump failed" or something like that.

I tried to use a program called WhoCrashed to give me information on the crash dump, but it doesn't seem to be detecting any crash dump files. The program has a feature to crash the computer to make sure it is recording crash dump files correctly and it turns out it does, just not when it bsod's from waking up.

Please let me know if you need any other information, and thank you all very much for your time and help.

 

[koolkat77]

Welcome To SevenForums.

Bcc F4 is usually storage related. Have you checked if the firmware of the SSD needs to be updated?

 

[finesthours]

Welcome To SevenForums.

Bcc F4 is usually storage related. Have you checked if the firmware of the SSD needs to be updated?

I have installed v3.1.2 of the Intel SSD Toolbox and according to that my firmware is up to date. According to Device Manager when I check for driver updates it says I have it up to date. The only thing I have seen that I might have to install is the Intel RST, but as far as I can tell that's only for RAID set ups and I'm sure I don't have that. Is there somewhere else I can check to see if I need to update anything? Also for future reference, where did you find the reference to BCC F4? Much thanks in advance.

 

[finesthours]

Also wanted to add I've performed chkdsk and sfc /scannow and both came with NO errors reported. Although I don't know much about those commands, I just ran the command prompt as admin and put in those commands, should I have added anything else or done something else with those commands?

 

[essenbe]

finesthours, Welcome to Seven Forums. If you would, please fill out your system specs. I will help us greatly to be able to help you. In the bottom left of your last post you will see 'my system specs', click on that, there you will see another link update system specs. Fill it out as completely as possible and click save at the bottom. If you would like to see what we like, click my system specs in the bottom left of my post and see mine.

As for IRST, I don't know if you are running an Intel or AMD system. If you have an AMD chipset, you can't install it. If you are running an Intel chipset, you can. You are correct that it is Intel's Raid driver. However, it contains a driver called, IaStor.sys. That is Intel's AHCI driver and you can only get it by installing IRST. On all my SSDs, I use it. It seems to perform better than Microsoft's MSAHCI AHCI driver. I assume you have your Sata controller in AHCI mode. By installing IRST, you do not have to run raid and you should notice no difference in the operation of your computer. It simply provides a driver to run raid if you decide you want to do so. If you have any further questions, don't hesitate to ask.

For your information, scannow is a system file checker which will verify system files and attempt to fix any that are missing or corrupted. Check Disk checks your hard drive for errors on the drive itself.

 

[finesthours]

finesthours, Welcome to Seven Forums. If you would, please fill out your system specs. I will help us greatly to be able to help you. In the bottom left of your last post you will see 'my system specs', click on that, there you will see another link update system specs. Fill it out as completely as possible and click save at the bottom. If you would like to see what we like, click my system specs in the bottom left of my post and see mine.

Thanks for the suggestion! I've filled it out as much as I could, let me know if I should try to dig up some more information.

As for IRST, I don't know if you are running an Intel or AMD system. If you have an AMD chipset, you can't install it. If you are running an Intel chipset, you can. You are correct that it is Intel's Raid driver. However, it contains a driver called, IaStor.sys. That is Intel's AHCI driver and you can only get it by installing IRST. On all my SSDs, I use it. It seems to perform better than Microsoft's MSAHCI AHCI driver. I assume you have your Sata controller in AHCI mode. By installing IRST, you do not have to run raid and you should notice no difference in the operation of your computer. It simply provides a driver to run raid if you decide you want to do so. If you have any further questions, don't hesitate to ask.

I am running an Intel system. I'm tempted to install this driver, even if it doesn't fix my current problem. Better to have the RAID functionality and not need it than need it and not have it in the future.

For your information, scannow is a system file checker which will verify system files and attempt to fix any that are missing or corrupted. Check Disk checks your hard drive for errors on the drive itself.

Thanks for that, now I'm sure my system files and hard drive are fine, looks like it might be a driver problem. It's not too late to reformat and install drivers one by one to see which is the culprit, but do you or anyone else have any clue as to what might be causing this?

Thanks.

 

[essenbe]

It can also be a hardware problem, but we won't go there quite yet. Please download AS SSD. It is an SSD benchmarking program. Just be careful not to install any junk programs that may come with it. As I recall, it does not install, extract it and run the exe program. It will open a window, in the top left make sure your SSD is selected. You do not need to run the program, there is some information in that window I would like to see. Just open it, select your SSD and post a screenshot of the window. Running the test is not necessary. You may also want to download CPUz. It will provide you and us a lot of information about your system. There probably is no regular on Seven Forums who does not use it. It is pretty much the standard most of us go by. But again, be careful of the junk programs they like to download with it. Just uncheck the boxes.

 

[finesthours]

I should mention that I just installed the Intel RST driver, but I have not tested if that has fixed my issue just yet. In the meantime, I've attached the screen shot of AS SSD without running the test as well as some CPU-Z info. Please let me know if you need anything else. Thanks!

 

[essenbe]

From everything I can see, it looks right.

 

[finesthours]

From everything I can see, it looks right.

This along with the fact that I just confirmed I'm still BSODing even with the RST driver is disheartening. Unless there are any other suggestions, tomorrow I plan to reformat and reinstall everything one by one to see what caused this problem. I will update once I hopefully fix it.

 

[essenbe]

Why not try this first http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html 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.

 

[finesthours]

Why not try this first http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html 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.

Thanks for the suggestion, I will look into it.

 

[koolkat77]

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.

 

[essenbe]

Thank you Steve for your input in this thread!

You're very welcome.

 

[finesthours]

Bad news: Ran 9 passes in memtest and no errors
(Good news?: No ram errors)
Any other ideas? Either way thank you guys so much for your prompt help, you guys are awesome.

 

[koolkat77]

Any BSOD-s?

 

[finesthours]

Any BSOD-s?

Yes

 

[koolkat77]

Please upload them

 

[finesthours]

Not sure if it wasn't necessary to run the whole application. Here's the SF Diag dump. Wanted to mention that it doesn't look like things are being completely written out. It never gets passed the initialize message on the BSOD.

 

[koolkat77]

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

[FONT="Lucida Console"]................................................................
...................................
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[/FONT]

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 rb:
  2. Type CMD on Search
  3. Left click and Run as Administrator
  4. Type SFC /scannow

Full tutorial here:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html