[17mrk]

Windows 7 x64, Asrock Z77 Extreme 4, every driver installed and updated, latest bios installed on the mobo.

Sometimes, when I hibernate my system, my system hangs on a black screen after the "resuming windows" screen. No HDD activity led, no signal on monitor, nothing works, not even the reset button, and I have to keep the power button pressed for 5 seconds and try again. Sometimes it works on the second try, but not always. There is nothing in Windows Even Log. Windows was recently reinstalled too.

Why is this happening, how do I troubleshoot it, and how can I fix it?

I followed the sticky and generated some trace files but so far hibernation has not failed yet, so I don't know if they are useful.

Also, the system hangs on resume when using sleep and even Intel Rapid Start.

I am getting desperate, I hope someone can help with this.

Other hardware: Gigabyte GTX560Ti, i5 3570K, 8Gb Corsair DDR3 1600Mhz, WD Blue hard disk as system drive. Nothing is overclocked. All drivers and motherboard bios are updated.

This post has been edited by 17mrk: 02 March 2013 - 03:49 PM

[17mrk]

By the way, the system doesn't write the trace when hibernation hangs. How am I supposed to tell what's causing it to hang?

[allen2]

The proper way to analyze freezes is to configure the computer to allow at least a kernel memory dump (but a full memory dump might be needed in some cases) and configure to create a crash dump on demand.
The next step will be to analyze it or upload it somewhere (some members here have good debugging skills).

[17mrk]

allen2, on 03 March 2013 - 12:56 PM, said:

The proper way to analyze freezes is to configure the computer to allow at least a kernel memory dump (but a full memory dump might be needed in some cases) and configure to create a crash dump on demand.
The next step will be to analyze it or upload it somewhere (some members here have good debugging skills).

Ok then, I enabled the keyboard functionality for manual crashing of the system, and set up to create the full memory dump.

Now, I assume that the next time I get the black screen (which is just a black screen, no blinking cursor, no "no signal", windows displays a black screen and there is no activity led), I press the button combination to crash the system, then collect the memory log, and try to analyze it myself or upload it here hoping that some kind person helps me finding what's wrong. Is this correct?

Also, thank you very much already, I did not know of this possibility, and I already feel like this problem which has been plaguing my computer for years will be resolved.

[17mrk]

Actually, I just used hibernation over and over until the hang happened, but then my keyboard wasn't responding (in fact, I don't think it was powered on at all, since it's backlit and the backlight was off) so I couldn't force the crash to happen.

What should I do in this case?

[allen2]

If you're using an usb keyboard you need those reg entries.

[17mrk]

allen2, on 03 March 2013 - 02:40 PM, said:

If you're using an usb keyboard you need those reg entries.

I edited the registry correctly and tested them before, the bluescreen happened correctly, but then during the black screen hang my keyboard was powered off and the combination didn't work.

[allen2]

Ok then if you have another computer you can try the remote debugging (I never tried it so you're on you own there) and initiate a crash. You'll need to install windbg on the other computer and of course the proper cable to connect both computers.

You could also try using procmon but as even the keyboard doesn't reply when hung, i don't know if it would work. Configure a backing file (in the file menu), then hibernate, then restart and, after the hang, reboot and rename the backing file and launch procmon and try to open the backing file. If there are event from the hang time (if you wan to be sure wait at two minutes between the hibernate and the restart and after the hang).
From what you explained, your keyboard seems to be an usb one; if you have a ps2 keyboard, it could be worth to also try with it (sometimes bios/uefi doesn't handle properly usb until os is loaded).

This post has been edited by allen2: 03 March 2013 - 03:38 PM

[Tripredacus]

17mrk, on 02 March 2013 - 03:48 PM, said:

Windows 7 x64, Asrock Z77 Extreme 4, every driver installed and updated, latest bios installed on the mobo.

Other hardware: Gigabyte GTX560Ti, i5 3570K, 8Gb Corsair DDR3 1600Mhz, WD Blue hard disk as system drive. Nothing is overclocked. All drivers and motherboard bios are updated.

What mode is your hard disk in? IDE/AHCI/RAID? Do have have the IRST installed?

[17mrk]

Tripredacus, on 04 March 2013 - 08:38 AM, said:

17mrk, on 02 March 2013 - 03:48 PM, said:

Windows 7 x64, Asrock Z77 Extreme 4, every driver installed and updated, latest bios installed on the mobo.

Other hardware: Gigabyte GTX560Ti, i5 3570K, 8Gb Corsair DDR3 1600Mhz, WD Blue hard disk as system drive. Nothing is overclocked. All drivers and motherboard bios are updated.

What mode is your hard disk in? IDE/AHCI/RAID? Do have have the IRST installed?

AHCI, and I don't have IRST installed, I don't even know what it is to be honest, seems related to raid arrays and SSD and stuff like that, I don't have any of those, just an old fashioned mechanical hard drive as system drive + another one as archive.

By the way, I tried in every possible way to force a crash&dump during the black screen freeze and nothing, the keyboard doesn't respond at all.

[MagicAndre1981]

if the keyboard doesn't respond, you have a hardware issue.

[17mrk]

MagicAndre1981, on 05 March 2013 - 10:54 PM, said:

if the keyboard doesn't respond, you have a hardware issue.

What kind? My computer is 100% stable, the only issue is random and only happens when resuming from hibernation. Could it be the PSU that's not able to switch power state or something like that? I had a very similar problem on my older build, but now I replaced all hardware inside the computer, except the PSU and an old PCI TV Tuner.

This post has been edited by 17mrk: 06 March 2013 - 07:26 AM

[allen2]

Try removing the old pci tv tuner and see if the issue persist.

[17mrk]

allen2, on 06 March 2013 - 03:40 PM, said:

Try removing the old pci tv tuner and see if the issue persist.

It does persist.

Is there ANY way to troubleshoot this problem?

This post has been edited by 17mrk: 07 March 2013 - 11:02 AM