You may want to disable "Allow hybrid sleep" in Power Options
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.
Hello all,
I recently upgraded my friends laptop from Windows 7 to Windows 8.
The laptop is a CQ60-XXXX series Compaq. She is indicating that now after the machine enters sleep mode it won't come out. It acts like it is... but it never resumes. A hard reset is required. I used remote assistance pulled the logs and I am seeing this..
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 1/1/2013 1:02:30 PM
Event ID: 137
Task Category: None
Level: Error
Keywords: (4)
User: N/A
Computer: Bethlaptop
Description:
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.
Event Xml:
< Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>137</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000004</Keywords>
<TimeCreated SystemTime="2013-01-01T18:02:30.493069300Z" />
<EventRecordID>808</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="2556" />
<Channel>System</Channel>
<Computer>Bethlaptop</Computer>
<Security />
</System>
<EventData>
<Data Name="SleepState">4</Data>
</EventData>
< /Event>
I have tried HP's website... BIOS was flashed last time I worked on the Machine. I was thinking maybe video drivers... It has the Intel Express 4 Graphics. Windows 8 installed them an Intel's website doesn't seem to offer a separate Windows 8 Driver for this chipset...
UGH! Any advice?
Windows for home | Previous Windows versions | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
60 answers
Sort by: Oldest
-
Anonymous
2015-10-31T13:59:27+00:00 -
Anonymous
2015-11-01T13:21:19+00:00 Since this error occurs with hibernate disabled, disabling hybrid sleep will do nothing. When hibernate is disabled you don't even have an option to disable allow hybrid sleep.
As I stated in other posts on this thread, It doesn't matter what you do the error will come back ... it will change if you use hibernate or sleep(s3) ... if you use sleep it will be an error with hibernate(S4) error, if you hibernate it will be an error with shutdown(S5).
So it doesn't matter, the error will just show for the "next" power state. If there was a S6 then the error would probably show up every time you shutdown(s5)
-
Anonymous
2015-11-03T00:39:00+00:00 Yes, I found it helpful but not satisfied. You would think that in this day and age as advanced these computers are this would not be an issue. We should be able to remedy these issues with out having to go through all this, Very complicated. it seams the faster and so called convenient systems are supposed to be the more time consuming and at times labor intensive it all is. I just don't know,I want to thank everyone for there time and advice it was insightful and I learned some things along the way Thank you.
-
Anonymous
2016-10-04T19:19:48+00:00 I don't recall getting this Event 137 message before upgrading from Win 7 to Win 10. Maybe I just missed it. Also, I do get the error in both a desktop machine that is set not to allow hibernation, and a laptop that uses both hibernation and sleep frequently. Neither has UEFI BIOS. Nevertheless, despite OrionsToy's excellent comments and those of many others, I find that on the laptop, as well as on the desktop, I get only "The system firmware has changed the processor's memory type range registers (MTRRs) across a sleep state transition (S4)." I never get a mention of the (S5) state. It may be that in my case the message only occurs with sleep, but not with hibernation.
The real problem with this error message (and many others in the Windows Event Viewer) is not just trying to understand whether it is in itself truly significant or not, but that it is impossible for a user to determine, without extensive research (like finding then reading this entire thread) whether it is important to the problem that you have. In my case, I was forced to look at it (like a couple of other posters here) because of a real return from sleep problem which gives me a blue screen, but creates no other useful events in the event viewer. So I was forced to default to probably wasting my time researching this error message, which most likely has nothing to do with my problem,...or does it?