BSOD On Wake From Sleep : 0x07A / 0x04F / 0x03B

Hi All!

Around mid-May I put the following system together:
Processor: i5-3570K
Motherboard: GIGABYTE GA-Z77X-UD5H-WB
Bios Version: F8
Memory: CORSAIR Vengeance CMZ8GX3M2A1600C9 (8GB (2 x 4GB) DDR3)
Graphics Card: EVGA 02G-P3-1568-KR (GeForce GTX 560 Ti 2048 MB GDDR5)
Hard Drive: OCZ Agility 3 AGT3-25SAT3-240G 240GB SSD (Boot)
Firmware 2.22
Seagate Barracuda ST1000DM003 1TB (Windows 7 also installed here)
Optical Drive: Asus DRW-24B1ST/BLK
PSU: OCZ ZX Series 850W Fully-Modular 80PLUS
Case: Corsair Obsidian Series 650D (CC650DW-1) ATX Mid
Cooler: COOLER MASTER Hyper N 520 RR-920-N520-GP
Monitor: ASUS VH232H Glossy Black 23" 5ms Widescreen @ 1920x1080
OS: Windows 7 Home Premium 64 bit (OEM)
Sound Card: On-board chipset
Keyboard: Dell SK-8135 (leftover from previous computer)
Mouse: Logitech G5
Printer: HP Officejet Pro 8500
HP Photosmart 8450

All components are new, except as noted.
We’ve had problems with BSODs from the beginning with this build. And I've been trying to squash this thing ever since. Humbled, I now bring it to you. CPU-Z & BSOD screen shots, as well as the requested Window7Forums-com Info folder are all attached.

Following is a brief narrative of my experiences so far. Hopefully you can find some value in them that will help cut to the heart of the problem. Initially I attributed it to the SSD & its Sandforce controller. There were a number of early issues -- which I think are now resolved -- that supported that supposition. The OCZ support forum seemed to concur at the time. Although I haven't completely dismissed the idea that it might still be the SSD, the current drive is an RMA replacement; the probability of me receiving two bad drives is extremely low.

Memory: I’m fairly confident that the memory is okay. I’ve run several passes with Windows Memory Diagnostic, as well as two separate runs of Mem86+ -- a 4 cycle sequence followed by a second an 8 cycle sequence several days later. Finally, I swapped the RAM out with another pair of sticks from another older computer that we’ve had no problems with (another home brew). The newer computer experienced another of the STOP:0x07a with the memory from the other computer installed (see June 29 BSOD screen shot – the0x07A stop never seem to complete a dmp file).

VIDEO CARD: After swapping the memory back I did a little research and found an article that noted you should always uninstall the old NVIDIA drivers before installing the new. I wasn’t sure if I had originally installed the 301.42 drivers I was running or if they were an update. So I completely uninstalled using Windows add/remove programs, then followed up with passes from CCleaner and Auslogics Registry Cleaner. I reinstalled only the video and PhysX drivers (I had also read that the audio drivers caused problems for some). The next day I received a new BSOD STOP:0x03B (see June 30 BSOD screen shot & log). This was the first time I am aware of running across this one.

Following this depressing turn I then removed the video card completely, uninstalled all NVIDIA drivers (add/remove programs, CCleaner, Auslogics Registry Cleaner, followed by Driver Sweeper) and switched over to the integrated Intel HD Graphics 4000. On Wednesday, July 4 we received another new BSOD STOP:0x04F (See attached screen shot). Again, dmp file creation failed. Friday morning we experience another of the 0x04F’s (See July 6, 9 am screen shot). This was followed by a 0x07A later that evening (See July 6, 9 pm screen shot). At this point the GTX 560ti card is still uninstalled.

The common thread to the overwhelming majority of these BSODs is that they occur on a wake from sleep. The exceptions to this seem to be the two 0x04F instances, which occurred in with the system already awake and in the midst of an action (e.g. the 0x04 on Friday 7/6 occurred while starting Windows Live Mail). Typically, we clear the BSOD by cycling the power. On restart, the system bypasses the log-in screen and returns right back to the condition it was in just prior to the stop (i.e. all apps & windows open).

Following are the Power Options Settings:
High Performance
Turn off Display: 10 min
Put entire computer to sleep: 20 min
Advanced Options:
Hard Disk : Turn off hard disk after: Never
Sleep after: 20 min
Allow Hybrid sleep: ON
Hibernate after: NEVER

Your efforts and experience are appreciated.
(I will have to post teh balance of the BSOD screen shots under a separate post -- aggregate file sizes exceeded limits)

(I will have to post the balance of the BSOD screen shots under a separate post -- aggregate file sizes exceeded limits)

Attached are the additional BSOD screen shots mentioned in my original post.

Software Concerns:

Code:

Start Menu\Programs\Auslogics\Registry Cleaner
Start Menu\Programs\TuneUp Utilities 2012

Many of us on the forums actually do not recommend automated optimization tools for Windows 7. Windows 7 does a much better job of handling its own optimization than its predecessors did. We especially do not recommend registry cleaning as an "optimization" step because automated registry cleaning causes more harm to the registry than it actually repairs.

In the future, if you need help optimizing Windows 7, please post a thread in Performance & Maintenance - Windows 7 Forums or follow the tutorial enclosed in that forum to Optimize Windows 7.

Analysis:

I see only a 0x7E and 0x3B in your reports. The first implicates your processor as a possible culprit. The second points to your SSD. Let's start with SSD troubleshooting steps.

SSD Troubleshooting:

• Make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
  
  
  
• Try doing a power cycle of the SSD. The following steps should be carried out and take ~1 hour to complete.
  1. Power off the system.
  2. Remove all power supplies (ac adapter then battery for laptop, ac adapter for desktop)
  3. Hold down the power button for 30 seconds to close the circuit and drain all components of power.
  4. Reconnect all power supplies (battery then ac adapter for laptop, ac adapter for desktop)
  5. Turn on the system and enter the BIOS (see your manual for the steps to enter the BIOS)
  6. Let the computer remain in the BIOS for 20 minutes.
  7. Follow steps 1-3 and physically remove the SSD from the system by disconnecting the cables for a desktop or disconnecting the drive from the junction for a laptop.
  8. Leave the drive disconnected for 30 seconds to let all power drain from it.
  9. Replace the drive connection(s) and then do steps 4-8 again.
  10. Repeat steps 1-4.
  11. Start your computer normally and run Windows.
  
  
  The above steps were a result of: Why did my SSD "disappear" from my system? - Crucial Community
  
  While that may not be your drive, a power cycle should be the same on all SSD drives. See how the system responds after the SSD power cycle.

SSD Firmware: v. 2.22 = most current

BIOS: The OCZ Technology Toolbox includes a button to flash the bios located directly below the flash firmware button. The bios button is greyed out suggesting that it is not a viable option at this time. Also, this is the most current version of the OCZ Technology Toolbox. I do not even find any info on the current BIOS version.

MB BIOS: v. F8 = most current

Chipset drivers: 9.3.0.1011 vs. 9.3.0.1019 on both Intel & Gigabyte support website.
I DLed the updated file and ran the Setup application in the INFUpdate folder. Although it stated that it installed everything successfully, the version listed for the driver is still 9.3.0.1011.

I thought to try updating manually following the instructions in the readme file in the INFUpdate folder. Attached is a copy of that README file. Section 9F (INSTALLING THE Windows 7* INF FILES AFTER OS INSTALLATION) covers my case. I get to item #10 and am stymied. There is no “MPS Uniprocessor PC” or “MPS Multiprocessor PC” listed in the Device Manager when viewing by connection (even with the “show hidden option active). Further, none of the options that are present have listings resembling item 12 in the instructions. Am I missing something here? Can you direct me to some better instructions than Intel offers in their readme file?

Hard disk controller drivers/SATA drivers
Intel SATA Controllers: (found under IDE ATA/ATAPI controllers in Device Manager)Intel 7 Series/C216 Chipset Family SATA AHCI Controller v. 11.1.0.1006 = most current (on Gigabyte site). Note: The RST v10.8.0.1003 drivers appear to be the latest support on the Intel site.

Marvell SATA Controller: (Found under “Storage controllers” in Device Manager) Marvell 91xx SATA 6G Controller v. 1.2.0.1010 = most recent on Gigabyte support site. Note none of the ports supported by the Marvell controller currently have anything plugged into them.

Hard Disk Controllers: Here I’m assuming you mean Hard Disk drivers. If I’m misinterpreting, please let me know where to find “Hard Disk Controller” in Device Manager. Under “Disk Drives” in the Device Manager, bothe the OCZ SSD and the Seagate HDD are assigned the disk.sys 7 partmgr.sys drivers v. 6.1.7600.16385. Since these are MS drivers they should be up to date (use Windows update service).

It’s interesting that you targeted that article on the Crucial Community site. A crash followed by the SSD not being recognized by BIOS was exactly the problem I experienced early on. And, although the procedures suggested by the OCZ support forum were not identical to the Crucial Community suggestions, they were similar. This SSD bios recognition symptom has since disappeared (i.e. I still get the BSODs, but SSD recognition by bios is no longer a problem). Still, there are enough differences in the Crucial procedure that it’s worth another go at it. Thank you for digging that one up!

I’ll perform these procedures and report back.

writhziden said:

While that may not be your drive, a power cycle should be the same on all SSD drives. See how the system responds after the SSD power cycle.

Well, it didn't take long to get some results.

I performed the SSD power cycle steps presented in your post. This morning we received another STOP:0x04F BSOD. And, like the other 0x04F's the system was unable to perform a memory dump to file. Attached is a screen shot of the BSOD on wake-up from sleep this morning. This was the first access of the computer today. Prior to the Blue Screen appearing, the monitor displayed a version of the desktop that was present when I walked away from the computer last night. The only anomoly was that the the control panel window was missing and, in its place was a small diaglog box stating something to the effect that the image file could not be read or was not in the right format... (something like that) It disappeared too quickly for me to get a photo of it, and was subsequently replaced by the BSOD.

PuZzLiNg1 said:

It’s interesting that you targeted that article on the Crucial Community site. A crash followed by the SSD not being recognized by BIOS was exactly the problem I experienced early on.

Strangely, I've experienced a step backwards. The bios did not recognize the SSD this morning. It's beeen about two & a half week since this happened. I had to perform my "standard procedure" for getting the SSD recognized again (this was standard until about two and a half weeks ago):

1. Power off the system.
2. Unplug ac adapter from power supply
3. Hold down the power button for 30 seconds to close the circuit and drain all components of power.
4. Reconnect all power supplies
5. Turn on the system and enter the BIOS
6. Adjust HDD boot priorities so that SSD boots first (As I might have mentioned, the Seagate HDD has a Windows install on it as a consequence of original SSD RMA)
7. Boot to Windows

Do you have the Marvell and Intel drivers installed in tandem? If so, please remove the Marvell drivers. Since nothing is using those ports, it is best that the drivers are uninstalled to prevent conflicts; they will be listed in IDE ATA/ATAPI controllers within Device Manager.

1. Click Start Menu
2. Right Click My Computer/Computer
3. Click Manage
4. Click Device Manager from the list on the left
5. Find the device you are trying to uninstall by expanding the appropriate set of devices
6. Right click the device
7. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
8. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK

To find the proper updated Intel drivers, there are some special steps to follow.

1. Go to the Intel driver update utility site...
2. Run the utility...
3. Click on the Chipset Driver link...
4. A page will come up with Intel storage technology listed...
5. Click the link for Intel® Rapid Storage Technology: Standard version...
6. Give it a minute to load and find out what storage driver is best for your chipset...
7. Click the Intel® Rapid Storage Technology link under Latest Downloads...
8. Download the drivers...
9. Install the drivers...

Also, have you tried installing on a platter drive to see if the problems persist? That would determine whether there is some SSD problem or incompatibility with your system.

writhziden said:

Do you have the Marvell and Intel drivers installed in tandem? If so, please remove the Marvell drivers. Since nothing is using those ports, it is best that the drivers are uninstalled to prevent conflicts; they will be listed in IDE ATA/ATAPI controllers within Device Manager.

It appears that Device manage lists the Intel RST controller and the Marvell controller as separate devices. (See attached screenshot)

Given this, do you still recommend the uninstall of the Marvell controllers? If so, is there a "more correct" method of uninstalling these drivers than simply selecting the "uninstall" button under the Drivers tab in the Marvel 91xx SATA 6G Controller properties window in Device Manager?

Thanks again!

You can probably remove them through Start Menu -> Control Panel -> Uninstall a program. If so, that would be a cleaner method. :)

And yes, I still recommend removing them if you are not using them. This is just to test.

Hi All,

I wanted to check back in and let you know how this finally got sorted.

After readingwrithziden's suggestions I finally broke down and performed a clean instal... several times. Although the more esoteric crash codes disappeared, the I'd still get the STOP:0x07a on wake from sleep. OCZ support has been outstanding in this case, and sent me a Vertex 3 as a replacement. Unfortunately, that didn't solve the problem.

I ended up purchasing an Intel 520 drive, installed windows on it, and haven't had a problem since. I cannot say for certain who is at fault here, but it seems like there was some sort of incompatibility between the Gigabyte Z77 motherboard, the OCZ SSD drives, and (perhaps) some other aspect of my system configuration. Regardless, all is well now.

Thank you again for all of the support.