0xc000000d Error Code When Restarting ProDesk 600 G1 SFF

[Kenobi-Wan]

I am updating a pair of ProDesk 600 G1 SFF PCs to Windows 10 Pro and find that I am having the same issue with both units.  I get the blue Recovery screen with a 0xc000000d Error Code whenever I restart the PCs.  This only seems to happen, however, when I "Restart" them.  If I do a "Shut Down" and then start them back up again, everything is fine.  Only when I "Restart" them do I have the problem.  If anyone out there could throw me a bone as to how to resolve this, I would be extremely grateful. I have rebuilt both systems several times and always end up with the same issue.  Thanks!

[WAWood]

@Kenobi-Wan 

My guess is that when you do a restart, FastStartup is kicking in, but when you do a Cold Start, it is not.

Win10 has enabled a new hibernation process known as Fast Startup -- which is enabled BY DEFAULT. This is different from Fast Boot, which is a BIOS/UEFI option.

Fast Startup is supposed to dramatically speed up the booting process, but in some PCs, it actually slows it down or causes it to hang. It's also a new form of hibernation known as hybrid sleep -- and this causes battery drain to maintain the state of the PC while turned off.

Disabling Fast Startup might fix the booting problem.

There are two ways to disable FastStartup in Win10: (1) through the Control Panel, and (2) through an elevated command prompt.

Control Panel - Open Control Panel --> Power Options.
Select "Choose what the power buttons do"
Select "Change settings that are currently unavailable"
At the bottom of the Window, under Shutdown settings, uncheck the box regarding fast startup

Elevated command prompt - run the following command:
REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Power" /V HiberbootEnabled /T REG_dWORD /D 0 /F

In both cases, reboot Windows.

NOW, FastStartup is disabled.

See if that helps.

[Kenobi-Wan]

Alas no, it made no difference.  Any other ideas?  I've already tried running the repair on the install USB drive and it says that it can't fix the problem.

[WAWood]

@Kenobi-Wan 

Sorry no -- it looks like hibernate/sleep does not work on your PCs.  This is often related to video drivers, but not always.