Windows 7: BSOD x0000001E on resume from S3 Standby/Sleep

Lister Of Smeg · 18 Mar 2013

I'm getting BSOD x0000001E crashes whenever I resume from S3 standby. I have never successfully completed a sleep/standby cycle on this PC since I built it and I need my PC to sleep in order to get work done as time permits.

Dsprague · 18 Mar 2013

It looks like your BSOD is being cause by your Marvell sata controller driver:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

*** WARNING: Unable to verify timestamp for mvs91xx.sys
*** ERROR: Module load completed but symbols could not be loaded for mvs91xx.sys
Probably caused by : mvs91xx.sys ( mvs91xx+3b890 )

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

Driver Reference Table - mvs91xx.sys

Looking at the time stamp on the driver it may be out of date, it is best to check too see if there is an update:

Code:

kd> lmvm mvs91xx
start             end                 module name
fffff880`014e8000 fffff880`0157a000   mvs91xx  T (no symbols)           
    Loaded symbol image file: mvs91xx.sys
    Image path: \SystemRoot\system32\DRIVERS\mvs91xx.sys
    Image name: mvs91xx.sys
    Timestamp:        Tue Oct 09 04:50:58 2012 (5073E572)
    CheckSum:         00050AB0
    ImageSize:        00092000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

you can check here for updates: Marvell - Support

Lister Of Smeg · 18 Mar 2013

Thank you for your help.

I have just noticed after reading your post, that for some reason, the driver installed is for a 91xx controller, whereas I believe that what I have on my mobo is a 9230 controller. I got the drivers from stationdrivers and I have two sets which are both meant to be the same version(????) but one version is 42MB and the other only 1.2MB. There is a tray utility which keeps crashing so it looks like I might of installed the the larger driver and it might of been for the 91xx series instead of the one for the 92xx series.

The Marvell site doesn't have a driver for the 92xx controller which is meant to have a model number of 88SE92xx, 88SE9230 in the case of my mobo. The Marvell site only list network drivers. I will uninstall the one that is installed and try the other one from station drivers.

Thanks again for your help, it's much appreciated. I have been leaving my PC for very long periods which is not something that I want.

Lister Of Smeg · 18 Mar 2013

For the first time since I re-built this system 15 days back, my PC has gone into and successfully resumed from S3 standby/sleep.

There are however some issues with the Marvell controller. Only 91xx drivers seem to install successfully or at least it generates a folder name to install to in Program Files (x86) named mv91xx and the drivers filenames do look like 91xx drivers.

I have attempted to update the firmware and it did appear to update but only in DOS, after a reboot it shows an firmware update message and then very briefly, so fast it is difficult to read, which looks like it says update successful. It does show the correct controller, 9230 but after erasing and updating the firmware and rebooting where it says that it is updating the firmware and a further reboot and then it's back to how it was.

After entering the Marvell Bios on the post screen it still shows the old firmware version.

I have repeated this several times and nothing is changing. The problems with the drivers were there after removing the old driver and before I tried a firmware update. There are no Raid drives on my system, the drives are all AHCI SATA so maybe that is the reason. [Edit] In fact there are, the Intel SATA controller is in Raid mode for the caching function provided by the on board Liteon mSATA SSD drive.

Britton30 · 19 Mar 2013

Only get driver for your motherboard from ASUS support, or any other drivers, always go to the manufacturer's site. 3rd party driver sites, aside from offering drivers for non-existent hardware, may install crapware you're not aware of.

Marvell BIOS, what is that? What firmware are you working with? Your SATA controllers should all be in AHCI mode.

Anti virus should be a priority, right up there with having a power supply.

essenbe · 19 Mar 2013

Gary is right, only install drivers from Asus site. They will have the proper Marvell driver for your board. Also, by chance, in bios do you have Internal PLL Overvoltage enabled? If you do, disable it. It serves a purpose with very high overclocks, but also will not allow you to wake up from sleep mode.

Lister Of Smeg · 19 Mar 2013

Quote: Originally Posted by Britton30

Only get driver for your motherboard from ASUS support, or any other drivers, always go to the manufacturer's site. 3rd party driver sites, aside from offering drivers for non-existent hardware, may install crapware you're not aware of.

Marvell BIOS, what is that? What firmware are you working with? Your SATA controllers should all be in AHCI mode.

Anti virus should be a priority, right up there with having a power supply.

The problem with only using the manufacturer's site is that they are very quick to drop support for their motherboards and even when they are supporting them, they are very slow with providing drivers when the parts company driver writers are frequently producing updates. Updates which often fix problems. The only site I use for drivers are stationdrivers because they do tend to get stuff much sooner than the motherboard maker provides. Gigabyte, my previous board maker, never released Bioses which were available on stationdrivers, Bioses which provided some nice extra features such as saving Bios profiles to the hard drive.

My Intel SATA controller is in Raid mode for the Caching function provided by the mSATA SSD drive. The Marvell SATA controller can have firmware updates and one of which was meant to fix some slow downs. There was a firmware update provided by Asus for the Intel management engine. I've attempted to flash the firmware but been unable to get it to stay flashed. The Dos command has a readback function which just provides a verification of what Bios, firmware and autoload is on the chip and that indicated that it had been flashed. But when my PC is rebooted, it says it's updating the firmware and not to power off. Afterwards, when the Marvell Bios posts, it shows that the firmware version is back to what it was before I flashed it. Updating after the reboot should not be necessary because chip flashing doesn't work that way so it looks to me that something is interfering with the flashing. I'm certain that the update was done successfully before it was reverted back.

Quote: Originally Posted by essenbe

Gary is right, only install drivers from Asus site. They will have the proper Marvell driver for your board. Also, by chance, in bios do you have Internal PLL Overvoltage enabled? If you do, disable it. It serves a purpose with very high overclocks, but also will not allow you to wake up from sleep mode.

No, I don't have PLL Overvoltage enabled. I read that it can cause some problems with S3 standby when I was looking for the cause of the problems that I was experiencing, which included problems with S3 sleep and not being able to stay in it for more than a few seconds. Even Asus mentions that it can sometimes cause S3 standby problems in their overclocking pdf.

essenbe · 19 Mar 2013

Lister Of Smeg, I have never seen that count down with a driver update, but it does happen with a bios update every time. In case you don't know, many times the manufacturer will release a driver update and the motherboard maker will mod the driver to work with that particular board. And, yes I am fully aware that Asus does not release drivers quickly, but they will normally work OK. I know that Asus Modded an IME driver to go with a particular bios update. Several people have had problems with that bios. I flashed the bios back to an earlier one, but still have the modded IME driver. I am having no problems. So, the mod works but the problem is the bios. Others who downloaded the same IME driver from Intel still have problems. That's why I always use Asus drivers even though they may be a step behind. But it is not uncommon for manufacturers to mod drivers for a particular board.

Britton30 · 19 Mar 2013

OK, have it your way, there may be a good reason when board makers quit supporting it.

Lister Of Smeg · 21 Mar 2013

Quote: Originally Posted by essenbe

Lister Of Smeg, I have never seen that count down with a driver update, but it does happen with a bios update every time. In case you don't know, many times the manufacturer will release a driver update and the motherboard maker will mod the driver to work with that particular board. And, yes I am fully aware that Asus does not release drivers quickly, but they will normally work OK. I know that Asus Modded an IME driver to go with a particular bios update. Several people have had problems with that bios. I flashed the bios back to an earlier one, but still have the modded IME driver. I am having no problems. So, the mod works but the problem is the bios. Others who downloaded the same IME driver from Intel still have problems. That's why I always use Asus drivers even though they may be a step behind. But it is not uncommon for manufacturers to mod drivers for a particular board.

Thank you for your post, I will bear that in mind.

Some searches have revealed that I am not the only one with issues with the Marvell SATA controller. Other people have experienced the same problem problems with device manager and the drivers. At least that is nice to know. I think I will have to contact Asus about it and find out what they have to say.