Computer intermittently fails to resume from S3, 0x00000116

[mikeymikec]

Spec:

Intel Core i5-4690k
ASUS Z97 PRO GAMER (latest BIOS)
Kingston 8GB DDR3-1600 (dual channel)
ASUS GeForce GTX 750Ti, display connected via DVI
Corsair CX430 PSU
Samsung 840 PRO 256GB SSD (OS)
WD Black 1TB (data)
Win7 SP1 64 (up-to-date)

Current problem:
Currently the computer fails to resume from S3 about once every ten days (and S3 is being used multiple times a day). Also the computer very occasionally comes out of S3 sometimes successfully, then during use it hangs within about 2 minutes of resuming (this has only happened twice). Also, again very occasionally (again twice IIRC), the computer resumes successfully, but there's a blank box on the screen and YouTube playback is graphically garbled. Rebooting fixes this particular issue.

One other point is that I intermittently get 'video hardware error' posted in the Windows reliability monitor (without any obvious symptoms of display issues, though I sometimes get a situation where the screen takes ten seconds longer to come on after resume, and the 'display' error gets posted in the event log).

Apart from the symptoms I've described, the computer runs completely stable regardless of the loads I throw at it.

Almost every time the main issue occurs (fail to resume from S3), BugCheck 0x00000116 is posted in the event log afterwards. The symptom when that issue occurs is that the fans come on, the power LED is in the 'on' state, but no keyboard response or anything on the display so I press the reset button. On one occasion this happened and Windows rebooted as if it was resuming from hibernate (making use of the hybrid sleep feature I guess), and nothing untoward was posted in the event log.

History:
I did a platform upgrade at the end of September this year (26/09/2015). The new components were the CPU and motherboard. I did a clean install of Win7 (ie. SSD partitions removed and let Windows recreate them) immediately after building the hardware.

I mentioned the intermittent S3 issue on another forum and an issue regarding Haswell and the C7 state was mentioned (at the time I was using a Corsair VX450W, more on that later), so I disabled C7 in the BIOS and the resume issue changed from every other day to once about every ten days.

Interestingly, the first problems took nearly ten days to appear after reinstalling Windows. I'm tempted to do a reinstall and maybe simply use motherboard drivers from the mobo CD, but in my experience, reinstalling without a clear and plausible set of reasoning tends to result in it not making any difference.

Other stuff I've tried since the C7 change:

Swapped Corsair VX450W for CX430 - as it hasn't helped I intend to reinstate the VX450.
BIOS reset ('load optimised defaults')
Disabled Windows power option: PCIE link state power management (from 'moderate' to 'off') - I've since reinstated this setting.
Updating drivers for everything I can think of including display (display driver done several times)
I've run memtest86 on the RAM more than once, no errors

Out of desperation I've disconnected all unnecessary USB devices (I had a PS/2 trackball connected via a USB adapter and a USB printer which is now network-only). I realise that 0x00000116 seems to be invariably a video issue, which would lead me to think that it's a graphics card fault, but it seems like a very odd fault for a graphics card to have considering it works under load perfectly well, and while it is still in warranty, it's out of the first year of warranty, which means I'll have to convince Asus that it is faulty.

Timeline:
Build date: 26/09
Resume probs: 06/10, 08/10, 12/10, 15/10, 07/11, 19/11
Video hardware errors: 04/10, 12/10, 18/10, 27/10, 03/11, 07/11, 09/11, 19/11
Hang: 19/10, 08/11
C7 change made on 15/10

 

[axe0]

BSOD Posting Instructions

 

[mikeymikec]

Attached.

 

[axe0]

Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Nvidia. Be sure the clean install box is checked and only install the Graphics driver and the PhysX driver.

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
2: kd> lmvm nvlddmkm
start             end                 module name
fffff880`05cc3000 fffff880`067a6000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        [COLOR="Red"]Sat Oct 03 03:54:49 2015[/COLOR] (560F3569)
    CheckSum:         00A9E36F
    ImageSize:        00AE3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[mikeymikec]

I've done as you suggested, bear in mind this involved skipping the 'HDMI audio driver' as well. I'll update the thread with my progress.

 

[mikeymikec]

Unfortunately the problem has happened again. This time the computer momentarily showed a mouse pointer with a small graphics corruption, then the monitor reported no signal. I left it for about 30 seconds before I pressed the reset button.

The system reported 0x00000116 had occurred after I rebooted (the 'your system has recovered from' window).

 

[axe0]

Just for clarification, we are talking about the system specs of the first post or from your 'My System Specs'?

 

[mikeymikec]

The specs are in the OP. I'll update the 'my system specs' shortly.