Windows 10: Event ID Error Event 137, Kernel-Power

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.

Just browsing through my Event Viewer trying to knock out and solve any random errors when THAT pops up a few times a day. Could anyone give a clue as to what it means? Hardware or software issue?

:)

 

The system firmware has changed the processor's memory type range registers (MTRRs) across a sleep state transition (S4). [Continued]

Thanks, but turned it off through the GUI - well at least that is what the GUI displays, although looking at some threads the admin batch cmd seems to

work better for some.

Have noticed this issue on active Power Plans where hybrid sleep is not selected, but again, for some, that isn't

always the case.

 

Computer shuts down instead of going to sleep

I tried those as you've said but it there's no effect. The fixit link 'Run now' button is gray and can't be clicked with this message: We're sorry, but your operating system is not supported by Microsoft
Fix it at this time.

I am getting this error from event viewer if it helps:

Event ID: 137

Source: Kernel-Power

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.

 

Well (S4) is hibernation.

You could run a test by shortening your hibernation setting, make sleep after 15 and hibernate after 30, then stop using it and note wall clock time. Calculate when it will drop into hibernation. Wake it up fifteen minutes after it should have hibernated and see if the event coincides with the machine changing from S3 to S4.

To confirm your machine supports all the necessary sleep states at command prompt(admin) type

powercfg -a

 

I don't use hibernation nor sleep.

 

Interesting.

So do you power down at end of use of just let screen go black?

Can you identify an activity you are doing (or the system) that matches when the event error occurs.

Like they happen when you power on, power off, connect and external drive.

You could issue a power command to disable hibernation and see if this prevents error from happening.

powercfg -h off

 

I turn the computer off with the windows icon in the taskbar like everyone else. I do not unplug or plug in any usb devices nor extra drives. I turn it off at night while I sleep and boot it up when I wake up. If I have to go out, it would idle for a few hours. I do not use the sleep function. I've disabled those features. Not even a screen saver is used. This is bad for the TV's I use as displays, I know, better fix that. I don't turn off the TV's when I shutdown the computer, I let the inactivity feature take care of that.

As for the times listed in the event viewer, I do not notice when they occur. There are no hiccups, lags, freezes, or error boxes. I'll have to get back to you on what it is I may be doing at that specific time to trigger the error. I haven't kept track but I will now.

Wait, wait, just figured it out. That error seems to be aligned with the times I shut off the computer.

 

Great.

Just confirming, did you disable Hibernation or you just don't use. Now a days when windows shuts down it save some information for "Fast Start Up.

Next time you shut down hold the shift key down and click shutdown. This bypasses the process. See if you get an Event. It will take longer to start.

Here is one of the tutorials for reference.

Fast Startup - Turn On or Off in Windows 10

 

I disabled fast startup as one of the steps to avoid the DPC WATCHDOG BSOD. So I don't use that, or can I?

 

I don't know.

Lets just be double sure.

powercfg -h off

This kills hiberantion and Fast Start up. Test and see if event viewer is clear.

 

Unable to perform operation. An unexpected error (0x65b) has occurred: Function failed during execution.

 

You did from command prompt(admin). Sorry.

 

Yep. CMD dos box right? Rebooted and this time didn't get the function error I just mentioned. How odd.