Computer does not reliably enter Standby/S3 mode

EDIT: For anyone surfing on this issue and arriving here, be advised I've decided simply that the ancient motherboard in this computer simply did not work reliably with my SSD and so I've abandoned the effort.
END EDIT
I'd love if someone here would help me out. This PC does not reliably go into S3 standby, such that while a WOL or keystroke will wake it, this means only that it powers-up but does not start the monitor nor show the keyboard LEDs resetting with Numlock ON as normal. I have to hit reset or power off/on and the I get a startup screen that says it didn't shut down cleanly and usually I Start Windows Normally and it boots fine. Later I do diskchecks and have never had any serious corruptions.

I tried S1 mode, where it seems to work reliably, and after setting BIOS to S3 again on Thursday afternoon it's worked fine i.e. go into Standby, wake automatically for backup to WHS2011 Server, sleep again, a couple of wake/sleeps yesterday by me, and this morning it awakened for Backup fine, and I awakened it from Standby after Backup fine, but then I put it to sleep with AFAIK the standard Windows API (via control gadget) and I got a bad start again about a half hour ago. This is a typical scenario, where it works some times but not (maddeningly) others, and I can't find the "why not".

What is most peculiar to me about these instances is that the System Log never records anything at the time it actually went into Standby--there are no status or error messages, e.g. this morning I had sent the PC into Standby at 09:11AM CST, and in the log is stated at 10:22AM when I woke it again that "The previous shutdown at 9:11:03 AM on 2/21/2015 was unexpected" but the last entry in the System log is at 8:58:32 AM!? Nothing after that at all, until I restarted some 10 minutes later. Also I almost *never* get a dmp file but this time I did, so....

My WhoCrashed says about the minidump only the following:

On Sat 2/21/2015 4:21:04 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022115-16099-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0xD1 (0xFFFFF80403885DA0, 0x2, 0x8, 0xFFFFF80403885DA0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

I hope someone here will find some clues in the attachment to help me!

Code:

BugCheck D1, {fffff80403885da0, 2, 8, fffff80403885da0}

Probably caused by : storport.sys ( storport!RaidpAdapterTimerDpcRoutine+5b )

Followup: MachineOwner
---------

Code:

    Image name: storport.sys
    Timestamp:        Tue Feb 04 07:06:50 2014 (52F04432)

Storport.sys is the generic storage port driver. It is not the actual cause of the BSOD, but it indicates about the storage controller elements of the chipset.

Your SATA/AHCI controller is the element of the nvidia nforce chipset. Which is too old.

Code:

    Image name: nvstor64.sys
    Timestamp:        Fri Apr 09 14:52:41 2010 (4BBEF1E1)

About nforce updates, what I see that nvidia is pretty out of the market of chipsets, nforce is almost obsolete nowadays. There is not a big scope of update to it.

Still, search for any possible Chipset/BIOS update for your MSI MS-7380. If you get any, apply it.

Please be aware that the BIOS update process is risky. If you dont have any prior experience with it, dont do it yourself. Take assistance of anybody who knows. (I am not aware of your skill levels. So please dont take this word otherwise.).

Let us know the situation.

The only problem is nforce is out of the market.

IMHO you may try to use the storage drivers via windows update and not the nforce one, by starting it from the scratch.
Clean Reinstall - Factory OEM Windows 7

Nothing very special ATM, just install the drivers via windows update only. Sometimes it is seen that those drivers are more stable than the drivers obtained from the device manufacturer.

Then we may wishfully expect that the BSODs will stop.

Some SSDs are not for standby or hibernation. :)

Keep it away from the power configuration and see how it goes. I guess you know how to do it ..... Power Plan Settings - Change ... point 5 (B) ... Hard disc > sleep time set to 0 or never.

If it works, then everything is alright.

maxseven said:

....... I found there were two instances of the nvstor driver still in the system. nvstor.sys and nvstor64.sys were hidden......

Please let me see the changed situation? Upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.