If you have an Asus P8Z77-V pro + intel 3570k+ Win8pro x64 please post here

[jojo2013]

I'm having 2 problem with this mobo. In administrative event viewer I get these 2 errors. Asus p8z77-v pro
Event id 13<---I get this every 1 or 2 days
: The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly.

Event id 137---->I get this every time I put the PC to sleep
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.

If you don't see these errors could you tell me:
1. What BIOS version you're using?
2. What is the EC and ME version in the BIOS? You can see it in the time & date settings.
3. Are you using secure boot?
4. What chipset driver are you using?

I have posted this issue in other forums. I only got responds from 2 p8z77v users. I need a respond from a p8z77v-pro users.
http://rog.asus.com/forum/showthread.php?31990-P8Z77-V-...

 

[Bubbaleone]

Fix event ID 13 by updating the BIOS to version 1908, then open an elevated command prompt and run this command to fix event ID 137:

fsutil resource setautoreset true c:\

Verify that the command completes successfully, then close the command prompt and reboot. Check Event Viewer > System to validate that the error is no longer getting logged.

You should also be running Intel Chipset Driver v9.3.0.1021, Intel Rapid Storage Technology Driver Software v11.5.0.1207, Intel Management Engine Interface v8.1.0.1263, Intel Management Engine Firmware upgrade program, and Asmedia SATA Controller Driver v1.3.4.0, all available (along with BIOS v1908) on the ASUS P8Z77-V PRO download page.

Note: After updating the BIOS install the chipset driver first, then install the Intel Management Engine Firmware upgrade program and run it before installing the IRST, IMEI, and Asmedia drivers.

Intel Management Engine Firmware upgrade program
For better Windows® 8 compatibility, this tool will update the Intel® Management Engine(ME) firmware to 8.1.
Before using the tool, make sure the Intel Management Engine Interface Driver is installed and follow the simple instruction.
1.Download and extract the file to a folder
2.Double click the MEtool execution file to run the updating tool
3.Follow the tool instruction to complete updating
*During updating, DO NOT shut down or restart system to prevent an incomplete update.

.

 

[jojo2013]

I'm already using 1908.
fsutil resource setautoreset true c:\
didn't fix it. I think something when wrong with it. After I restart I see event id 136(ntfs)
"The default transaction resource manager on volume C: encountered an error while starting and its metadata was reset. The data contains the error code."
I google this error. On eventid.net it said to delete .blf and .regtrans-ms. it'll regenerate the file after reboot. It didn't regenerate it. I didn't permanently delete it.

I think you mistake the event id 137 (ntfs) for the kernel power one. It's not the same thing.

 

[Bubbaleone]

When the command completed, the message that the command completed successfully would have been displayed; was it? Install the chipset driver, run the firmware upgrade program and either install or verify that the driver versions I listed are already installed, then run the commandline again.

 

[jojo2013]

When the command completed, the message that the command completed successfully would have been displayed; was it? Install the chipset driver, run the firmware upgrade program and either install or verify that the driver versions I listed are already installed, then run the commandline again.

The command did complete successfully when I inputted it. Where did you get that command? Have you seen the Kernel-power error yourself?

As for Event id 13. The bios did not fix it. If fact all the bios 1616 and up gave me that error. I think I found the cause. 2 User on amazon.uk reported seeing this error with their deluxe version. 1 user reported back not seeing the error with Asus AI suite uninstalled. I'll have to test that out.