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.

I have been looking for the answer to this issue since windows 7. It will happen no matter what version of windows you are using. Will happen if you have an older MB with BIOS or a newer MB with UEFI. It will happen with a clean install of windows 7, 8, 8.1 and 10.  It has nothing to do with intel storage... it has nothing to do with your video drivers, I don't have intel. My system is all AMD and has had 3 different video cards in it. This error happened with all the different video cards.  It has even happened with a clean install without installing the video driver yet. System power state S4 is the hibernate state. My hibernate is disabled. (powercfg.exe /hibernate off) so I should not be seeing anything about S4 at all.

I have had this issue for over 5 years and have been looking for an answer for it the whole time. I have still yet to find an answer. Microsoft doesn't have any idea what this error is... I just wish they would remove it so it didn't show up in my logs 2 to 5 times a day depending on how many times my computer sleeps.

Hey MS... if you can't figure out what the error is for over 5 years... how about you go in and remove the triggering of the error to the log files.... since you can't fix the error and it doesn't seem to effect the operation of the PC .. just remove the printing of the error to the logs ... it wont fix the issue but at least you wont look so incompetent. I mean really .... you keep releasing new OS's yet you can't fix a bug that has worked its way into the past 4 .. maybe even 5 operating systems. I don't know if I was having this issue in XP... I never checked back that long ago.

Just enabled hibernate to see if that got rid of the error ... nope .. same error but this time its S5 instead of S4

With hibernate enabled, went into sleep but woke before hibernate ... back to same error with S4

So it is changing the MTRRs to hibernate(S4) state when in sleep(S3) and shutdown(S5) state when in hibernate(S4)... Good thing there isn't a S6 because it would change it to S6 every time it shutdown(S5) and this error would happen... lol

You brought up another good point... IT DOES ONLY HAPPEN when it's been sleeping for an EXTENDED period of time. Not to the point where it would go into an AUTO-Hibernate but longer than just putting it to sleep then waking it back up.

This is due to a DEEP SLEEP state. check if the Hybrid Sleep state is enabled in power config control panel. If disabled, check to see if your sleep state in the bios is not set to S1. if on a laptop, you cant change that setting because all laptops use the S3 sleep state for power conservation.

I wish it was that easy.  I have an AMD system with a MSI motherboard so I don't have those bios settings nor do I see an AMD equivalent.  I also have hibernate disabled in WIN 8.1 so I am not sure why the system would be entering S4 to begin with. 

I was getting the error regularly until a couple of weeks ago.  I'm hoping I got lucky and a recent bios or software update may have resolved the issue.

The solution is to limit the functionality with Intel Rapid Start in BIOs. The hibernation partition is not created and the BIOS for Intel RST is enabled, as stated in the Intel RST User Guide. Intel RST PDF.

I have a Asus P8Z77-V Pro, and this settings are enabled by default, however nobody actually creates a hibernation iFFS partition in the OS drive and when win8 enters into S4 it is not able to save the memory registers, and thus created this event ID 137.

Change the settings of Entry of S3 wake and active page threshold support to disabled. Now save the settings and reboot the PC.

IF this does not solved the problem, then DISABLED Intel Rapid Start Technology. The PC is still ABLE to resume from sleep, only that during a power loss, the PC will boot as normal and not able to recover the previous sleep state.

Your BIOs setting for Intel RST may differ, but this should be able to solve the harmless eventID 137.

I got rid of this error completely. It's back now. I'm too lazy troubleshoot it again or switch thru back ups. I think this error is harmless. The difference with my OS setup now is Intel visualization is disable in the BIOS and the OS is installed from the cd not from update. The 2nd cause of this error might be from the ASUS 2 AI utility, on win8 anyway. I didn't see this error with my other users. This error might be from a specified hardware. I asked a hardware reviewer with the same MOBO(Asus p8z77v-pro) as mine and he has the error too. I also posted the error on Asus ROG forum. So far no one could relate to my error. Someone suggested it could a UEFI bios issue.