New
#21
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.
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.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...
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.
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.enable Driver Verifier to monitor the drivers.Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
InformationWhy 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.
WarningBefore 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.
Let us know the results, with the subsequent crash dumps, if any.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.