Hibernate time value changes at random

Lenovo Carbon X1 7th gen, running Windows 10 Pro, 22H2 and totally up to date with Windows and Lenovo updates (12 April 2023).

This morning the hibernate on battery value was 240 and plugged in was 759 - these were not values that I had set. Hours later they are different: both read 269. I have sometimes seen the on battery value has a very long number that always starts with 3 and is possibly 8 digits long. I have not seen the sleep values change. This has been going on for weeks. What a mess.
I have tried using a Windows power plan such as "balanced" and the same problem arises. I don't know if that absolves Lenovo drivers of guilt.
Does anyone have an idea for me?

I am not aware of anything in Windows itself that would change these settings. However, I do know that a lot of OEMs provide their own management software that alters these settings. It might be worth taking a look at any Lenovo utilities that include power management features to see if they may be causing this (assuming you even have any such utilities!).

Hibernate value changes after Sleep on battery setting is changed - ThinkPad - Lenovo Support US

I guess it's likely that some Lenovo driver is to blame. I thank the last person for that link to Lenovo. I followed the advice and started with "Restore default settings for this plan", but I was using the Lenovo Intelligent Power plan.

I then changed the Sleep After values, but not the hibernate values. 12 hours later the hibernate values were 760 and 759.
Now I'll try to use the Microsoft Balanced plan

- - - Updated - - -

Here are the default settings for the Microsoft Balanced plan.

I'll leave these ridiculous values in place and see what happens 12 and 24 hours from now.

bro67 said:

No, the link I posted clearly states it was a update to Windows back in 19h2 that caused this. Follow the info they posted.

Yes, but the problem has now come back. And the note from Lenovo that you referred to doesn't actually explain where the root of the problem is. I think it's likely that the problem is an interaction between MS power settings and Lenovo drivers, since I don't find any reports of this from non-Lenovo owners.

docGlenn said:

Yes, but the problem has now come back. And the note from Lenovo that you referred to doesn't actually explain where the root of the problem is. I think it's likely that the problem is an interaction between MS power settings and Lenovo drivers, since I don't find any reports of this from non-Lenovo owners.

pepanee said:

Just for the heck of it, I asked Siri how much is 35791394 (35,791,394) minutes is, as days. The answer to that is: 24,855.13 days...

This is someone's bad programming.

35791394 minutes is 2147483640 seconds.
2³¹ is 2147483648.

Why is 2³¹ so important? It's known as a signed 32-bit number, meaning one bit is taken to denote positive or negative numbers (leaving 31 bits to hold the actual value). What's happening is an overflow bug, where Lenovo power management is feeding Windows the wrong type of 32-bit number.

garlin said:

This is someone's bad programming.

35791394 minutes is 2147483640 seconds.
2³¹ is 2147483648.

Why is 2³¹ so important? It's known as a signed 32-bit number, meaning one bit is taken to denote positive or negative numbers (leaving 31 bits to hold the actual value). What's happening is an overflow bug, where Lenovo power management is feeding Windows the wrong type of 32-bit number.

Oh that's brilliant. I suspected something like that, but didn't pursue it. I'll hazard a guess that the value of NEVER is either 2³¹+1 (which would be -1 if the number is a signed integer) or any negative value. How the number gets truncated to a value just short of 2³¹ I don't know. I also don't know if Microsoft intended the values to be signed or unsigned int. Microsoft (and many other companies) have been careless with the signed/unsigned issue.

What this does imply is that some Lenovo software is pushing a bad value to the power settings.

- - - Updated - - -

I found the problem. It was a Lenovo driver update, which I can view only in Lenovo Vantage System Update history.


Then I disabled it inside Lenovo Vantage under Device/Power settings.


Problem solved!