Ivy Bridge BSOD when resuming from sleep

Greetings all.

I was very thankful to find this helpful community online and appreciate any help you may be able to offer.

I have a new Ivy Bridge system (3770k / Z77) and it's rock solid under load. I've literally virtual machines processing encrypted disk images at the same time it plays Civ V and it runs flawlessly. Never had a single issue under load.

However, when resuming from sleep, the system will sometimes BSOD. It doesn't happen every time, but has occured about 4 times in the last week or so. I've tried to ensure that drivers are up to date.

One other symptom that may help to diagnose: I've had to turn off the "blank screen" function because sometimes the screen won't come back after that. The system appears to be running but the display never returns.

System specs:
- Windows x64 Home Premium (OEM)
- i3770K @ stock clock
- Asrock Z77 Extreme6 MB
- 8MB Corsair RAM
- 850 W Raidmax PSU
- PowerColor Radeon 7950 (12.6)
- Intel 520 180GB SSD / Seagate Barracuda 1TB secondary SATA

I've attached the dump ZIP as requested in the sticky. The perfmon report is included in the ZIP folder.

Thanks again for any help you can offer

Best regards,
Philip

Hello and welcome to Seven Forums,

If you are overclocking your system, please return all overclocked components to their stock speeds. If the BSOD's are found not to be caused by the overclock, you can re-overclock the components once we have finished the diagnostics.

BSOD ANALYSIS

SSD Updates

You have an SSD installed. SSD's that are not updated are known to cause or contribute to BSOD's. Please make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• Marvell IDE ATA/ATAPI controllers (older drivers for these are especially problematic)

Other Hardware

The BSOD dumps you gave me do not give a definitive cause for your BSOD's.

As a result I recommend you check your hardware for issues. Please run Memtest86+ to check your RAM. Let it run for 6-8 passes overnight as described in the tutorial. Pay particular attention to parts 2 and 3.

Also check your HDD for errors using Seatools and chkdsk.. Download and create a bootable version of the Seatools for DOS program as described here. For check disk, follow this tutorial: Disk Check


Work through each of these steps and report back after you've completed each one. If you have any questions, feel free to ask
Stephen

Thank you for taking a look at the files I posted and for your response. I have so far checked the following per your notes:

• SSD firmware - I have the latest per the Intel SSD tool.
• BIOS Version - Updated to latest.
• Chipset Drivers - All updated to latest version.
• Hard disk controller drivers/SATA drivers - Latest Intel Rapid Storage dirver installed.
• Marvell IDE ATA/ATAPI controllers (older drivers for these are especially problematic) - I have checked on all storage controllers. Don't believe I have a Marevell IDE controller from what I can tell.
• All disks pass CHKDSK
• RAM passes Memtest86 (used v4.0a)

Today the system had another BSOD coming out of sleep (same error message) and I've since taken the following steps to further test this:

• Reset BIOS and Power Management defaults.
• Set power management scheme to "High Performance"
• Disabled "blank screen" again.
• Disabled integrated Intel HD4000 graphics unit in Device Manager
• Disabled "AMD Overdrive" on the Radeon 7950 card. Not sure this should impact since overdrive is only engaged under load, but we're clutching at straws here so worth a try.

I'll report back. Any other ideas gladly received.



The odd thing is that this system is absolutely 100% stable under any kind of load. It only has issues when coming out of sleep mode.

Ok, thanks for the update. Good self-troubleshooting by the way! Well done.

Let's try and see if we can find if a driver is causing the issue. It would make sense as the system is stable under load.

• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. In Windows 7:
  

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.
  
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
  
  When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
  verifier /reset
  -> Restart your computer.

Thanks to Writhziden for providing the Driver Verifier steps.


Make sense? I know these steps can be quite intimidating but work through them one at a time and you'll be fine! :)

Stephen

Thanks again. I'll look at this over the weekend.

I think I may have found the driver causing the error. I uninstalled the Intel Rapid Storage driver on Friday and haven't had a single BSOD since. I've tried to provoke one by regularly entering sleep mode. Not only that, but the odd behavior with screen blanking has also gone away. Very odd since this is an Intel chipset, Intel controller, and an Intel SSD.

I don't think the IRST driver is fundamentally flawed because many people report good results, but it's clearly capable of causing these issues as the releases notes for a prior version actually reference correcting BSOD issues when recovering from sleep.

In any event, the standard MS AHCI driver delivers perfectly respectable performance and, so far it appears, with complete stability.

Thanks again for the helpful diagnostic steps. I'll report back again in another week or so to confirm if the problem is truly gone. If the errors return, I'll activate driver verifier per your directions above.

Best regards,
Philip.

Thanks for the additional input. I am actually running Norton Internet Security 2012. From what I can tell it is installed and running correctly. Is there something I should check for beyond the indications in the UI?

Sorry, guess I needed a break from debugging. I do see NIS installed in your files, so I am not sure how I missed it other than possible burn out.

It is strange that the Intel controller would cause problems. When you updated it, did you use these steps:

1. Go to Intel® Driver Update Utility,
2. run the utility,
3. click on the link for Chipset Family,
4. Scroll down and select Standard Version or Intel Rapid Storage Technology (not the Enterprise version).
5. There is a page that loads with information on other Intel drivers for your system including Intel storage drivers. You may have to let it load for 10-15 seconds before it displays your particular drivers link.
6. Go to that link, download the drivers, and install them.

We've now been 100% BSOD and crash free all week despite my attempts at provocation. I'm therefore going to call this one solved. Given that stability and performance have both been excellent with the standard MS AHCI driver, I'm going to leave it in place for now. Who knows why the Intel driver had issues. writhziden, you're probably right that it just hadn't installed correctly but since there doesn't seem to be much upside to getting it working I'm going to leave well enough alone.

Thanks again to those who spent your time and effort helping on this. I really appreciate the help.

Best regards,
Philip.