The system firmware has changed the processor's memory type range registers (MTRRs) across a sleep state transition (S4). This can result in reduced resume performance.

Supposedly there is a diagnostic tool in the Windows Performance Toolkit.  

C.f.

http://social.technet.microsoft.com/Forums/windows/en-US/d56d2cea-d9d5-46d2-acb7-c7b23eb56ead/what-is-the-best-way-to-find-why-windows-8-cannot-boot?forum=w8itprogeneral

(Microsoft search for

    xbootmgr xperf

)

Bump, bump. Did complete reinstall of Windows 8.1 x64 and still issue occurs. Both the event log error and Windows freezing to black screen not responding to anything, not even Reset button. Now it happens daily, I walk past the computer and notice it being turned on --> still both monitors are blank and refuse to receive any signal. Only way to resolve this is to hold Power button to shut down machine. I need to have WOL enabled as this is HTPC and Media Center Extenders connect to it - so PC waking every now and then is normal.

Interesting thing is that when this happens, and Media Center was recording live TV, the actual recording was finished just fine, so PC is not completely dead. Cannot ping nor remote desktop it to it, however. CTRL-ALT-DEL has no effect either. Issue never appears when playing games or doing something else hardware-demanding, it only occurs sneakily when system is idle. I cannot reproduce the issue by putting machine into sleep and waking it via Media Center Remote or WOL.

System has been running nicely for quite some time, before, so I perhaps need to revert back to Windows 7 to see if the issue occurs there. It did occur sometimes on Windows 8, and now constantly (daily) with Windows 8.1.

Things I've tried:

• Updated all drivers (Intel chipset, AMD GPU, Network, Sound card)
• Now been updating to latest AMD Radeon Catalyst drivers whenever they are released
• Reinstalled Windows
• Toggled Fast Boot
• Toggled USB Selective Suspend
• Disconnected monitors while issue is ongoing and plugging them back
• Toggled whether hard drives should sleep or not
• Toggled CPUID Limit in BIOS
• DIsconnected secondary HDMI monitor (TV), and only left monitor connected via VGA
• Toggled Intel Virtualization in BIOS
• Toggled PCI Express Link State Power Management
• Tried HIPM+DIPM in Hard Disk AHCI Link Power Management (default was HIPM)
• Enabled Driver verificator --> nothing strange
• Run chkdsk
• Nothing overclocked
• Temperatures very low
• Disabled nightly backups to Windows Server Essentials 2012 R2
• Uninstalled Windows Server Essentials 2012 R2 Connector
• Downgraded Motherboard BIOS to original that was when motherboard was bought

MOBO: ASUS P8Z77V_LX2 (latest BIOS)

CPU: Intel i5 3570

SSD (system): SanDisk SDSSDX120GG25 (latest firmware)

HDD: Samsung HD103UJ

Sound card: Terratec 7.1 PCI

Graphics: Gigabyte Radeon 7950

TV Card: Hauppauge HVR-2200

Network: Realtek PCIe GBE

JI find that after A sleep or being on for a day or two this error keeps popping up. The only thing is it doesn't allow my computer too go to sleep. I require to force it to sleep with keyboard button. I don't remember windows 7 acting like this. I will be upgrading my computer over the weekend and passing my motherboard and cpu on, Which I will be installing windows 7 back onto it. I will post if it keeps acting up on the windows 7 install.

Here is list of hardware.

MOBO Asus P8Z77V - Deluxe.

CPU Intel 2500k

Video card 780gtx sli

Hard drives OS corsair Force GT 90 0raid, Force 60 for pagefile

WD WD1000FALS 1Raid

>he only thing is it doesn't allow my computer too go to sleep. I require to force it to sleep with keyboard button.<

That is true here also. I turned off the Network adapter power on, and disabled the  selective USB, and Hybrid sleep, setting Sleep to 12 min., and turned off Multimedia from preventing sleep, but it still requires the sleep button, and still wakes up on its own by the morning. 

Not a big deal, but this is 2013.

ASRock 970 EXTREME3 mobo; AMD 6350 3.9ghz 6 core cpu; 8gb ram

I think by disabling the PC not to go to sleep nor Hibernate (ever) solves the issue.

I am trying this because I started to see this issue too.

Hope this helps for everybody.