Computer does not reliably enter Standby/S3 mode

maxseven · 27 Feb 2015

Funny you would mention Driver Verifier--I found it yesterday and tried it briefly until I realized it was keeping TOff from sleeping the computer. Given that today again I had another failure (yet still no minidump) I will disable TOff and use Windows Power Options with DV turned on.

A last gasp before abandoning S3 for me.

Arc said:

maxseven said:

OK Arc I've appreciated your input here. I do believe you were correct from the beginning to suspect the storage drivers so thanks anyway for giving me some focus.

I had forgotten already that the NVIDIA drivers don't TRIM, so reverted again to the MS Standard Dual Channel PCI IDE Controller drivers so that TRIM again works.

It does seem like my Standby woes started with the installation of the SSD last year, and my best guess at this point is that this motherboard is too old to work gracefully with modern controllers for it (no AHCI for example). So I either revert to a spinner and Sleep again, or stay with the SSD and Shut-Down instead...

The two alternatives that you have decided are all inclusive. Yes, it is somehow true that there is always a possibility of non-compatibility between old (technically old) and new (technically new) hardware components. It is also a very widely noticed scenario that a good lot of SSDs are not for the sleep configurations, in whichever machine they are attached to.

If the SSD is not configured to go to sleep, then the unsuccessful sleep-wakeup power transitions might not be due to the disc only. Some other PnP devices also needed to be watched thoroughly. That is why I referred you to some expert of that very field.

One very common way to determine which driver is causing an issue is to enable driver verifier. If you are interested, you may use it, just to be sure that if it is anything else other than the disc that is playing in there.

enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

When DV is enabled, put the computer to sleep and wake it up. That means, force it to BSOD. If anything other than the storage drivers are playing any role there, DV will be able to discover those.

maxseven · 28 Feb 2015

Arc I suffered another crash when going into Standby yesterday and this time I did get a dump file and a WER also. If you would take a quick look I would sure appreciate it.

Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 2/28/2015 7:15:36 AM
Event ID: 1001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Quadcore
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0xffffffffffd1ac19, 0x0000000000000002, 0x0000000000000001, 0xfffff800038458b5). A dump was saved in: C:\Windows\Minidump\022815-23946-01.dmp. Report Id: 022815-23946-01.

I'm guessing this mobo doesn't like the Microsoft Standard Dual Channel PCI IDE Controller driver but will try Driver Verifier today and see what that might turn-up.

Arc · 28 Feb 2015

Code:

BugCheck A, {ffffffffffd1ac19, 2, 1, fffff800038458b5}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

A memory corruption during power transition means some sort of problem with page files.

Code:

fffff880`08ade8a0  fffff880`010ed12c PCIIDEX!BmReceiveScatterGatherList

PCIIDE and PCIIDEX are good for any board. It depends on storage controller configuration only, nothing serious.

It appears that you may not try standby/hibernation on this SSD.

For overnight, power off will be ok; but for short time of non-usage, those are not of any good use for desktop computers. Sleep/hibernation etc are mainly for the portable computers running using stored battery power.

maxseven · 02 Mar 2015

Arc said:

It appears that you may not try standby/hibernation on this SSD.

I hate giving-up on a problem such as this, but now I've decided I must. Thanks for your help Arc, I am abandoning the use of an SSD and going back to a spinner. A lot slower, but also a lot less trouble for this motherboard.

Arc · 02 Mar 2015

maxseven said:

Arc said:

It appears that you may not try standby/hibernation on this SSD.

I hate giving-up on a problem such as this, but now I've decided I must. Thanks for your help Arc, I am abandoning the use of an SSD and going back to a spinner. A lot slower, but also a lot less trouble for this motherboard.

Hope everything will go well, mate.