Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Computer does not reliably enter Standby/S3 mode

21 Feb 2015   #1
maxseven

Windows 7 Home Premium 64bit 6.1 Build 7601 (SP1)
 
 
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:

Quote:
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!


My System SpecsSystem Spec
.
23 Feb 2015   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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.
My System SpecsSystem Spec
23 Feb 2015   #3
maxseven

Windows 7 Home Premium 64bit 6.1 Build 7601 (SP1)
 
 

Thank you so much Arc for looking and commenting! Yes my BIOS for this now-ancient board is "latest" which means from 2011 iirc, and hopefully was done after W7 was released and tested as clearly no further BIOS will be made available for this old mobo.

I've been trying to eradicate from my system (i.e. drivers) anything non-Windows, which is not easy to do, and while I have tried in the past to replace the storage drivers with any/all chipset-appropriate versions I could find, I have not yet struck upon a fix for this maddening problem. I have even tried replacing the NVIDIA nForce Serial ATA Controller drivers with MS, to at least so far no good effect.

I did not myself ever see a storport.sys error so am glad you spotted it. I will continue to dig...

What troubles me about this board, an MSI P7N Platinum, is that in all the surfing I've done on this issue I can never find any specific posts about Standby problems with it, as if my own setup was somehow unique. I realize it is old enough that maybe there aren't all that many W7 x64 systems installed to it though. I do not want to just toss it, as in every other way this Q6600 machine works perfectly and I have a myriad of specialized programs on it that I don't want to rebuild (ie replace) it without good reason.
My System SpecsSystem Spec
.

23 Feb 2015   #4
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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
My System SpecsSystem Spec
23 Feb 2015   #5
maxseven

Windows 7 Home Premium 64bit 6.1 Build 7601 (SP1)
 
 

Quote   Quote: Originally Posted by Arc View Post
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
Well I had done a recent Repair Install to assure all system files and have pared-back all non-MS and non-hardware related items so am going to continue down this track for now.

In any case that you found a pointer to the storage system is something I needed to regain my focus on this difficult problem.

My System SpecsSystem Spec
24 Feb 2015   #6
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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.
My System SpecsSystem Spec
24 Feb 2015   #7
maxseven

Windows 7 Home Premium 64bit 6.1 Build 7601 (SP1)
 
 

Quote   Quote: Originally Posted by Arc View Post
...just install the drivers via windows update only.
I have to try this route because nothing else is working. Thanks for reading--I really needed another pair of eyes on this thing.

If it weren't for the fact that MSI sold a lot of these boards I'd give up on S3, but in fact it seems that since I installed an SSD as the C:\Windows drive that S3 has become way less reliable than before. Maybe that's a clue again re: the storage drivers.

When surfing on this problem weeks back I found a site where the P7N Platinum and the P7N Diamond were reviewed together and it was stated that MSI was doing something special (i.e. tricky) with the Platinum re: the chipsets but I've not been able to find that site again. Maybe I will try again as that may help further. Funny, last year I thought "Never Again" re: Nvidia, thinking my next mobo would be manufactured by Intel, and just as I did that Intel went out of the motherboard-making business!!!!

:bangshead:
My System SpecsSystem Spec
24 Feb 2015   #8
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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.
My System SpecsSystem Spec
24 Feb 2015   #9
maxseven

Windows 7 Home Premium 64bit 6.1 Build 7601 (SP1)
 
 

Quote   Quote: Originally Posted by Arc View Post
Some SSDs are not for standby or hibernation.
Ha, ha! Do I ever know it! I had an OCZ that bricked a few years ago, going into Standby. I got it replaced and put it into a different PC where it's been fine (with a new firmware too). This Kingston has Sandforce also and (knocking on wood) has done well with all my shenanigans. But yes I know about Sleep Never!

Well I don't know if my Standby problem is solved yet, but after using DevMgr to do an "Update Driver" with the NVIDIA, and selecting MS' "Standard Dual Channel PCI IDE Controller" instead (it worked), I found there were two instances of the nvstor driver still in the system. nvstor.sys and nvstor64.sys were hidden in the Non-Plug and Play Drivers area and man it was tricky to get rid of them. I had to select the driver and change from Boot to Disabled and then Reboot and then go-back and Uninstall them and Reboot again and finally Delete them from system32\drivers. Until I did it in this fashion, Windows considered them essential files and refused to boot until it "repaired" the problem i.e. replaced these files. What a trip...

What I learned along this journey was that NVIDIA CONTROLLER DRIVERS DON'T ALLOW TRIM! So a side benefit (a big one AFAI'm concerned) to switching to the MS drivers is TRIM.

I will report back if it solves my S3 woes or if I am forced to S1...
My System SpecsSystem Spec
25 Feb 2015   #10
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Quote   Quote: Originally Posted by maxseven View Post
....... 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.
My System SpecsSystem Spec
Reply

 Computer does not reliably enter Standby/S3 mode




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Windows XP Mode Crashes when waking up the computer from standby/sleep
I don't know why on earth it does that. This starts happening everytime now. Here are the details Problem signature: Problem Event Name: BEX64 Application Name: VMWindow.exe Application Version: 6.1.7601.17514 Application Timestamp: 4ce7b2e6 Fault Module Name: ...
Virtualization
Task Scheduler - Put Computer into Standby Mode
Scheduling Sleep Mode via the Task Scheduler This tutorial shows you how to schedule your computer to go into Sleep Mode via Task Scheduler. It uses a combination of the program PSShutdown and VBScirpt. The advantages of using this instead of the Power Policy is that it can place logged off...
Tutorials
Computer crashed and won't enter safe mode. How do I restore it?
I left my laptop running for a while when i left the room. When I came back it had frozen, I hadn't been doing anything untoward, I had been running a few programs at once, just like firefox and word. Anyway I had to turn it off with the power button. Then when I tried turning it back on I was able...
BSOD Help and Support
Failure to enter Standby or Hibernation, stops at black screen
Hi again, I have another very nasty issue... My system fails to enter Standby or Hibernation. When I start the process, the monitor fades out to black - as normal - and the system begins to disable devices. I can see i.e. that an attached USB-Stick gets turned off. Unluckily, Windows seems to...
BSOD Help and Support
Blue Screen - Cannot Enter Safe Mode or Any Other Mode
All -- any help you can provide would be appreciated. I do not have any desire to pay Lenovo $100 to walk me through the steps of recovering the system. I have a lenovo ideapad y560 0646 - windows 7 64 bit. Each time I start the laptop, I get the following error (after the introductory...
BSOD Help and Support
Computer will not enter standby automatically
Hi, I have a PC that I use as a media center attached to my TV running Windows 7 RC and it worked perfectly until about a week ago when I upgraded my laptop to Windows 7 and placed them both in the same Homegroup. Every since then the Media Center will not enter standby mode either...
General Discussion


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 19:59.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App