26-03-2022, 11:01 PM
I'd agree with that - it matches my understanding from some years back. But today, I'm less clear.
As mentioned, I used "Sleep" most of the time in the XP and W7 days, and if there was a power cut, it would have to start from cold. So this does imply that the RAM remained powered and refreshed.
But with W10, selecting "Sleep" appears to actually put it into hibernation, based on the fact that after a power cut it picks up exactly where it was left, implying that the RAM must be saved to HDD.
I'm talking about several desktop machines here, various ages, etc...
In the case of my laptop, it might well be genuinely sleeping (followed by Hibernate when the battery gets low). In the past I have had half-hearted attempts to figure this out by looking at the logs, but didn't really get anywhere. So I just shut down the laptop, and it's mostly OK. For PCs, I continue to use Sleep - in whatever form it actually is, but "Sleep" is what the menu says. I only reboot for updates
As mentioned, I used "Sleep" most of the time in the XP and W7 days, and if there was a power cut, it would have to start from cold. So this does imply that the RAM remained powered and refreshed.
But with W10, selecting "Sleep" appears to actually put it into hibernation, based on the fact that after a power cut it picks up exactly where it was left, implying that the RAM must be saved to HDD.
I'm talking about several desktop machines here, various ages, etc...
In the case of my laptop, it might well be genuinely sleeping (followed by Hibernate when the battery gets low). In the past I have had half-hearted attempts to figure this out by looking at the logs, but didn't really get anywhere. So I just shut down the laptop, and it's mostly OK. For PCs, I continue to use Sleep - in whatever form it actually is, but "Sleep" is what the menu says. I only reboot for updates
