Solved BSOD on wakeup, Error, 0x::f4

[kevdlandrig]

I just upgraded my system with a solid state drive, and installed a fresh copy of windows 7 pro x64 on the computer. The problem is, every time i wake the computer up, there it freezes, shortly followed by a random blue screen. I've seen Kernal Data inpage error, and the one about a system process exiting. When the bluescreen happens, I noticed that it doesn't collect the data from the hard drive. it just says initializing disk for dump or something like that. There aren't any records of bluescreens in the minidump file.

Upon restart of the computer ( i press the reset button on the case) it will successfully resume windows as if i never woke it up. (the startup icon says "resuming windows" not "Starting windows").

I am thinking this may be along the lines that the disks are not initializing after the computer wakes up, and the login screen is just loading from the RAM, but I don't know what to do to fix it.

I have attached the sf grabber file.

 

[Arc]

Hi kevdlandrig.

Make it sure that your sandisk SSD is running with the latest firmware.

• How to Upgrade SanDisk SSD Firmware | StorageReview.com - Storage Reviews
• Solid State Drive support information

BTW, the zip you uploaded does not contain any crash dump.

Follow it: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

 

[kevdlandrig]

The ssd has the latest firmware.

I don't think my system is capable of creating the dumps, because the bluescreen hangs at "initializing disk for crash dump..."

I am posting the picture of the most recent blue screen.
View attachment 318750

once I see the screen, it hangs for several minutes (to several hours), and then the computer either turns off or restarts, or someone resets it. The disk doesn't initialize until restart.

 

[Arc]

Next .... post a screenshot of your all HDDs and SSD uning CrystalDiskInfo - Software - Crystal Dew World

 

[kevdlandrig]

View attachment 318860
View attachment 318861
Is this what you wanted?

 

[Arc]

That's it.

And, SMART data looks good.

The next thing that you need to try is to re-seat the sata and power.

• 

Also check that the discs are properly tightened in the slots. Changing the SATA cables and applying those in the unused ports of the motherboard is also a worthy try.

 

[kevdlandrig]

The power and sata couplings are properly seated, and the hard drives are secure. I've already tried changing the sata ports, to no avail. Could it be something to do with ahci init?

 

[Arc]

Could it be something to do with ahci init?

Storage controllers? They can cause BSODs. But in your case it is msahci.sys..... which is windows system native AHCI controller, and it literally does not fail or cause a BSOD.

It would be really helpful if we could get a crash dump to analyze.

 

[kevdlandrig]

Okay so I know my system pretty well, so let's theorize here. Let's say that the system spins/powers down the drives when it goes into s3 sleep. When I wake the computer, the drives fail to spin up/power on for whatever reason. Windows calls up the login screen from RAM, and when it tries to grab a file from one of the disks, they aren't there and the system bluescreens. In the bluescreen, the system retries activating a drive, but fails again. The system reboots without being capable of recording any information about the failure, or deleting the restoration data. The restoration data is marked as active on the hard drive, and resumes windows to where I was when I put it to sleep. That would be my best guess, anyway.

At this point, I think it might be important to list my motherboard model, a gigabyte GA-MA790x-UD4P, revision 1.0. this may have something to do with it, but I don't know.

 

[Arc]

Yes, you definitely know your system, even much more than an advanced user.

Can you try this setting, as a test?

View attachment 318978

The theory that you developed is not just a theory, but it happens a lot of times. But usually it results a stop 0x9F, probably caused by partmgr.sys or disk.sys or atapi.sys. There is no reason that it will cause a stop 0xF4, but this is uncommon to me.

During S3, only RAM remains powered. And the disks are failing to get the power back during the wake up.

 

[kevdlandrig]

okay. the setting didn't seem to do anything when I had it running for about an hour this morning. I put it to sleep then awakened the computer, and it bluescreened as usual. the error was different though, Kernel data inpage error, 0x7a.

I'm adjusting my theory a little here. I noticed that my motherboard spends a significant amount of time doing ahci init on startup, about 10-15 seconds. If the computer truly powers down everything but the ram and USB ports in s3 sleep, then the storage controller could be going offline. If this is the case, then the computer would probably have to go through the ahci init steps again before the drives can be seen. My guess would be that this is a specific problem associated with my motherboard model.

 

[Arc]

okay. the setting didn't seem to do anything when I had it running for about an hour this morning. I put it to sleep then awakened the computer, and it bluescreened as usual. the error was different though, Kernel data inpage error, 0x7a.

Very good news. It is going to follow another working theory in that case. Which is enough to minimize the issue.

Can you get a crash dump in this case? If so, it would be better to explain the situation.

If not, I will try it otherwise. So let me now.

 

[kevdlandrig]

Unfortunately, I did not have a crash dump as of yet. Just FYI, I think I may have also seen that error before we tried adjusting the hard drive power down timer, but I was unable to record it because I had thought it was just a fluke at the time.