I was not suggesting that you investigate the 10016 entries. Quite the opposite.
"Event 6009 just says: "Microsoft (R) Windows (R) 10.00. 19044 Multiprocessor Free.""
In its General tab?
"Wonder why the PC cannot enter a true sleep state."
Wonder what happens in Safe mode.
Denis
Hi
I have tried booting into Safemode using MSConfig. In Safe mode I do not have an option to enter sleep or hibernate. The only options in the start menu are shutdown and restart.
- - - Updated - - -
Screen shot for event 6009
Oh, sorry. I wasn't thinking straight, was I. Those are always the only options in Safe mode.
- Has it always been like this?
- If you've updated the display driver in the past yet the problem persisted then I think that clears that possibility out of the way.
- I saw you mention running SFC and assume you meant using the command SFC /ScanNow in the normal manner. I was confused by your 'on the boot disk' comment because SFC is normally run from within the Windows OS. There are command switches for other situations but SFC /ScanNow within the running Windows is the normal procedure.
- I cannot think of any logic for running a Repair install and, if I was gong to run one, I'd make a new system image first, just in case. Repair Install - TenForumsTutorials Despite its name, a Repair install is a repair procedure not an installation.
I think that Event 6009 message is vying for the award for the most unhelpful Event viewer entry. But the competition is intense.
Best of luck,
Denis
Many thanks for all your help Denis.
I found a UEFI setting : ErP ready which had options for Disable, S4-S5, and S5. Default is disable. I thought these S states may help, but trying these did not help with my wake from sleep issue and the stopped Wake On Lan from working.
I have not been brave enough to try a Repair Install. As hibernate works I have set sleep off and removed it from the start menu. I have set Hibernate to hibernate after 15 minutes. Wake on LAN still works so this is a usable state for me.
I know nothing about settings in Bios/Uefi beyond what explanatory comments the interface shows.
In any case, the thing we call sleep is S3 Sleep so is not included in any S4-S5 settings.
"I have not been brave enough to try a Repair Install"
You don't need bravery. You just need a system image. I've never had a Repair install go wrong but I still make a new image beforehand because it is an intense operation [for the computer].
A Repair install overwrites all non-configurable Windows system files with replacement copies from the ISO used.
There have been examples of a Repair install changing user settings but that should not happen and is becoming rarer. We went through these shenanigans during Windows 7 as well and, by the end, its Repair install had removed all such cases.
All the best,
Denis
Just to clear this, ErP is an European Union norm that says that any turned off device should not consume more than 0.5W. S4 is hibernation and S5 is shut down, any of which are "device turned off". As said it doesn't affect sleep which is S3. A computer in S3 state mostly appears off, but actually it isn't because some things like the RAM are being fed, and if it loses power it must boot up the same as if it was in S0 (full "on" state).
I'd disable ErP because the 0.5W level is way too low, except in cases like this: Im doing the whole erp thing because i don't want to have the rgb led's on my motherboard lighting up my room when shutdown ( Bios Erp S4 or S5? - Republic of Gamers Forum - 645925 ). Some PSUs from around 2010 and before used to consume like 40W when plugged in but off. This is very excessive and a norm ended it. No BIOS setting can act in the inners of a PSU, this had to be solved by the PSU makers doing changes in the design (I didn't know they could achieve sub-watt consumptions from 40W before). The BIOS setting refers to limitation of some consumptions done for doing Wake on LAN or programmed boot-up, and for trickle currents. I suppose it can be done under 0.5W but it sounds me very forced, and I'd be happy with 2 or 5W instead.
Ad Astra,
I agree with JLArranz's very interesting post.
S0 is indeed the 'full on' state, the operating state.
It is not the same thing as S0 Modern standby.
Denis
Quote