Windows 10 Windows failed fast start up with error status 0xC00000D4

  • Thread starter Thread starter dpokrovsky
  • Start date Start date
D

dpokrovsky

Guest
Hello everybody,

This is exactly the error I can see in events almost every time after a seemingly correct shutdown. And yes, there were no unexpected shutdowns at all. First thing first — disabling fast start up in Windows power settings gets rid of this issue completely. But this is not what I am interested in — avoiding features.

My setup is i7-4770 + Z97 + 32GB DDR3 + 512GB SSD M.2 + 2x4TB HDD + GTX980 + PCIe sound card + Windows 10 Pro x64 10586.104. Everything had been tested extensively and seem to be very stable. There are no overclocks (beside Haswell default Turbo mode, but I managed to probe while it was turned off). Storage modes went full circle from AHCI to stand-alone drives in RAID to Intel Smart Response (RAID 0 for a part of SSD and HDD). BIOS mode is full UEFI (all disks are GPTed for granted), all non-existent devices are disabled, KB/mice via USB. All additional hardware and software could be taken out of the picture since I had the error without them.

And most of the time after shutting PC down I got the following records in an event viewer:

! Windows failed fast start up with error status 0xC00000D4. 29

! The previous system shutdown at H:MM:SS AM on DD/MM/YYYY was unexpected. 6008

X The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. 41 (63)





I've tried almost everything in BIOS, with drivers, power management configurations.

No memory dumps are generating upon shutdown. I was unable to trace a problematic shutdown process with xbootmgr because it crashes with "Couldn't find kernel logger in active logger list..." error when it fails, or returns no problem when it suddenly works.


I had a brief talk with a manufacturer support. They admitted they had a number of reports about the issue, but their engineers found no problems in BIOS code (therefore did not replicate).



I would accept that my hardware is broken, but I can see a lot of reports about the same issue on different platforms (but every time in connection with Haswell and 8 or 9-series chipsets) all over Internet since a fast start up was introduced in Windows 8. Unfortunately, all these threads have no happy ends. "Turn off the fast start up" at best.




So I am very curious — has anybody ever managed to solve this issue consciously? By chance? Got repair for a motherboard? Got working replacement for the same motherboard? Located the cause elsewhere? Maybe some fresh ideas? It would be great at least to find out — is it Windows or not Windows in charge!

Thanks in advance!

More...
 
Back
Top