New build PC - seems to run mostly very well - but not shutting down cleanly

Hi all,

This is a new build PC, consisting of the following:

ASUS ROG Strix B650E-E motherboard
ryzen AMD 7900x processor (with Thermalright Peerless Assassin 120 White CPU Air Cooler)
Gainward GeForce RTX 4070 Ti SUPER Panther OC 16GB
Patriot Viper Venom DDR5 64GB (2 x 32GB) 6000MT/s
Lexar NM790 2TB SSD (os drive)
Samsung SSD 870 EVO, 2 TB (2nd drive)
Corsair RM850e (2023) PSU

I've re-installed windows a 2nd time, and still have the problem below.

I've updated to the latest bios, chipset drivers, all drivers and so on.

It seems to run really well - I've been using it for some modelling and rendering with Autodesk Maya, some light video editing with Davinci Resolve, and have ran cinebench on it several times. It seems to be stable.

But often when I turn it on, it takes around 40 seconds to boot to windows. This is how I know something has went from during shut down - a clean boot normally takes around 17 seconds.

The event viewer contains several errors, including a critical one related to windows not shutting down cleanly.


Warning:
Windows failed fast startup with error status 0xC00000D4.
Event ID 29, keywords (8796093022208)

Warning:
The previous system shutdown at 17:22:44 on ‎28/‎10/‎2024 was unexpected.
Event ID 6008, Keywords Classic

Critical:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event ID: 41, task category 63, keywords (70368744177664),(2)

Error:
Audit events have been dropped by the transport 0
event ID 1101 Keywords Audit Success

Warning
Intel(R) Ethernet Controller (3) I225-V network link is disconnected
Event id 27, keykwords Classic, source e2fnexpress

Error:
Faulting application name: SearchHost.exe, version: 2124.22709.10.0, time stamp: 0x66e38c1d
Faulting module name: dcomp.dll, version: 10.0.26100.1882, time stamp: 0x49a8a2b5
Exception code: 0xc0000005
Fault offset: 0x000000000002cd3e
Faulting process id: 0x3688
Faulting application start time: 0x1DB29E1352B18E9
Faulting application path: C:\Windows\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\SearchHost.exe
Faulting module path: C:\Windows\System32\dcomp.dll
Report Id: 9b24b263-e74b-4a04-9a55-b8a2521a8a97
Faulting package full name: MicrosoftWindows.Client.CBS_1000.26100.23.0_x64__cw5n1h2txyewy
Event ID: 1000, category Application crashing events

There are various other errors related to Hello for Business not being able to be launched, 'error setting traits on provider', Faulting application name: SearchHost.exe, several related to secure boot, several related to permissions for COM server application/distributed COM,


I've tried to reseat cables, ram.

I've got 2 x monitors installed, a webcam, a mouse and keyboard. Nothing else connected just now.

Any help appreciated!

Thanks in advance,

G
 
I haven't used windows for over 22 years, [I'm a Linux Man] Unfortunately I still have to maintain MS systems for family members

The previous system shutdown at 17:22:44 on ‎28/‎10/‎2024 was unexpected.
this is a catch-all could be any number of problems, check the event viewer

Audit events have been dropped by the transport 0
event ID 1101 Keywords Audit Success
another catch all check in the event viewer under the Audit Success tab

The previous system shutdown at 17:22:44 on ‎28/‎10/‎2024 was unexpected.
Event ID 6008, Keywords Classic
this tells you of an unexpected shutdown, again not why [check the logs]
Warning
Intel(R) Ethernet Controller (3) I225-V network link is disconnected
Event id 27, keykwords Classic, source e2fnexpress
check if on a separate card it is connected correctly, check and make sure you have the correct drivers, then check your cable to router connections. [Does not apply if you're using WI_FI]

Windows failed fast startup with error status 0xC00000D4.
Event ID 29, keywords (8796093022208)
Back to this one,
I noticed you are using SSD's Windows quick start/fast boot [call it whatever you like] was designed to speed up machines with SATA plate spinners, [it's a form of hibernation in which your machine never really switches off] IT is not keen on SSD's or NVME's so if its on, try disabling

a couple of other common causes are USB peripherals, especially pen-drives and of course the most common fault on any Windows system Corrupt download of either the base system or more often Updates

sorry I cannot be more specific, I hope this points you in the right direction
 
Your boot delay and critical errors after shutdown on a new build are likely linked to multiple potential causes. Here’s a troubleshooting path based on common causes for similar issues:

  1. Fast Startup Issue: The error 0xC00000D4 in Event ID 29 often points to problems with Windows Fast Startup. Try disabling Fast Startup to see if it impacts the shutdown/boot issues:
    • Go to Control Panel > Power Options > Choose what the power buttons do.
    • Click on Change settings that are currently unavailable, then uncheck Turn on fast startup and save the changes.
  2. Driver Conflicts or Incompatibilities: Even if your drivers are up-to-date, sometimes there can be conflicts, particularly with network or display drivers. The Intel I225-V Ethernet controller is known to occasionally cause issues; try reinstalling the network driver from the motherboard manufacturer’s website, as it may be better tuned than the Windows-provided driver.
  3. SearchHost.exe Crash: This error points to the Windows Search Indexer, and it can be a common cause of slow boot times. You can try rebuilding the search index:
    • Go to Control Panel > Indexing Options and select Advanced > Rebuild Index.
    • Disabling Search indexing for non-critical drives may also help improve stability if rebuilding does not solve it.
  4. Power Supply or Sleep States Issue: Since your system has a high-power setup, check your BIOS for any power management settings related to sleep states (S3, S4, S5) and disable anything that’s not needed. Additionally, ensure ERP settings (found under advanced power management in BIOS) are set correctly, as improper ERP settings can lead to improper shutdowns.
  5. Windows Updates and Integrity Check: Make sure Windows is fully up-to-date, then run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth in Command Prompt as Administrator to ensure there are no system file issues contributing to these crashes.
  6. Memory Settings and Stability: Since you have high-speed DDR5 RAM, verify that it’s running at stable settings. If you’re using XMP, try disabling it temporarily to check if the instability or boot time changes. Some systems may require BIOS fine-tuning for memory overclocks, even with supported RAM.
  7. Check Event Viewer for Secure Boot/COM Errors: Since you have errors related to Secure Boot, ensure it is correctly enabled or disabled based on your OS installation type (UEFI or Legacy). Incorrect Secure Boot settings can sometimes interfere with clean boot/shutdown.
If none of these steps resolve the issue, you may want to consider updating the BIOS again or testing each drive and RAM stick individually, as one faulty component can sometimes lead to critical errors during boot and shutdown. Let us know if any of these steps help or if further assistance is needed!
 
Back