Hibernate being faulty after version 1803?

I would run a Windows Energy report to get started. You will need to determine pattern with issue so you can get something meaningful. It appears from your description that it needs at least 2/3 days to happen

Create Power Efficiency Diagnostics Report in Windows 10

I would think this is a driver that has been updated. I'm just guessing the hit and miss could be how the driver is interacting with your system (Apps, hardware states, BIOS)

This is an older MS document. I think you are looking for the Platform Power Management section errors.

https://download.microsoft.com/downl.../PowerCfg.docx

What could have happened is that MS has loaded a default driver instead of a specific vendor driver. Since you built device I would audit what is on manufacturer's site and compare in device manager, is it a vendor driver or just a generic MS driver.

Ken

Hibernate has never worked correctly from day one.

bro67 said:

Hibernate has never worked correctly from day one.

Our experiences differ, though I have seen that others have problems. It seems to be make-specific.

It's my preferred method of turning off my laptops, just shut the lid and hibernate. Hibernation has worked perfectly for me since Windows '95, then in XP, Win7 (I skipped 8) and now in Windows 10 (1803, 17134.112) on a Samsung, Toshiba and Dell.

Agree hibernate can be iffy but some machines, newer machines work well before they are altered.

Any driver could be at fault which makes this hard to say that one. Since your are experienced with DDU you could try an older display driver. One you were using successfully in V1709 or V1703.

I would then do as I suggested, find the devices which should have specific drivers from your MB site and then see if Windows has loaded a generic one. These I would update to the vendor specific drivers.

Sure you could run the power report now. Of course I don't know where you are in cycle. You mentioned it takes 2/3 to appear.

I think I would wait at least that long before running. You should be able to see in the Platform Power management section which error it is report.

Maybe a strategy would be to run report every day at 18:00 hrs hoping to catch the state that is causing the issue.

As you don't want to go through a reload and you are messing with drivers please create an image with a product like Macrium Reflect. If things head south, way south, then you have a reliable restoration method.

Backup and Restore with Macrium Reflect

Rain08 said:

Well my desktop didn't had issues with it since it has done 28 consecutive days of doing hibernation. That is until someone accidentally removed the power plug on the socket while I was working and then I decided to upgrade to 1803.

Rain08 said:

Just an update. I've had done multiple hibernations (I think around 30+) in the span of 24 days... I also updated my GPU driver (w/ use of DDU) at like halfway point of the span. Although that's the only update that I've done and no Windows related stuff as far as I'm aware...

I'm not sure to mark this as solved since I didn't do anything and still uncertain on if this would occur again. I'd probably monitor it for another month to be sure.

I'm glad to hear hibernation is working for you again. Are you sure you did nothing at all? Did you perhaps turn hibernation off and on again with the powercfg /hibernate command? The most likely cause of your problem would have been some corruption of the hibefil.sys when the plug was pulled. Turning it off then on would have created a new hiberfil.sys.

re. other windows updates, my Dell, Toshiba and Samsung have now had the 10 July update to 1803 build 17134.165 and are still hibernating successfully.