BSOD on wakeup, Error, 0x::f4

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.

kevdlandrig said:

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.

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.