Windows 10 PC Freezing During Boot for no apparent reason

[RazorKitten]

Pasting my entire post from Microsoft forum which has received no replies.

PC has started freezing on boot, on the screen which shows 'Republic of Gamers' (Asus motherboard) and a circle of spinning dots, which freeze at a random time during their spin and remains frozen. Sometimes it displayed 'Beginning Diagnostic' or 'Starting Automatic Repair' which also freezes.

I have done the power cycle into Windows Repair and executed the Boot Repair option which told me it had completed successfully. Subsequently doing this again says it failed to execute the repair. Sometimes it reboots itself while the options are displayed, one time it rebooted after reaching the login screen.

Sometimes the PC boots into windows after multiple resets and no other issues seem to be present in Windows, and everything will work fine until the next time I switch off the computer. I have also done a System files repair from the command line which reported it found some corrupt files and repaired them, and I have run a disk check on the boot drive which reports no errors. I also tried the System Restore option which began to work then rebooted without providing a report on whether it did anything.

I have not altered any system files or boot related options, and the error did not begin immediately after installing a Windows Update or any hardware changes.

Needless to say, it is extremely frustrating and I'm well out of my depth trying to diagnose it. The Computer is about two years old and has been running more or less flawlessly until now. Windows was installed by the company who made the computer for me.

PC Specs: (In case any of this helps)

Windows 10 Home 22H2 (All updates as of time of this post)
Ryzen 5900X
Nvidia RTX3080Ti
32GB RAM
Boot drive nvme m.2 SSD 2TB
Virus/Firewall Windows Defender and Malwarebytes
USB Devices: Mouse/Keyboard (Razer), Microphone (Yeti)/Headphones (Astro)/Camera (Logitech), External drives

Contents of logfiles from SRT folder:

DISMRepairLogFile: (Small selection from very very long file)

2024-10-09 14:39:36, Info DISM API: PID=1656 TID=1716 DismApi.dll: - DismInitializeInternal
2024-10-09 14:39:36, Info DISM API: PID=1656 TID=1716 DismApi.dll: <----- Starting DismApi.dll session -----> - DismInitializeInternal
2024-10-09 14:39:36, Info DISM API: PID=1656 TID=1716 DismApi.dll: - DismInitializeInternal
2024-10-09 14:39:36, Info DISM API: PID=1656 TID=1716 DismApi.dll: Host machine information: OS Version=10.0.19041, Running architecture=amd64, Number of processors=24 - DismInitializeInternal
2024-10-09 14:39:36, Info DISM API: PID=1656 TID=1716 DismApi.dll: API Version 10.0.19041.1 - DismInitializeInternal
2024-10-09 14:39:36, Info DISM API: PID=1656 TID=1716 DismApi.dll: Parent process command line: StartRep.exe - DismInitializeInternal
2024-10-09 14:39:36, Info DISM API: PID=1656 TID=1716 Enter DismInitializeInternal - DismInitializeInternal
2024-10-09 14:39:36, Info DISM API: PID=1656 TID=1716 Input parameters: LogLevel: 2, LogFilePath: C:\Windows\System32\Logfiles\Srt\DISMRepairLogFile.txt, ScratchDirectory: (null) - DismInitializeInternal
2024-10-09 14:39:36, Info DISM Initialized Panther logging at C:\Windows\System32\Logfiles\Srt\DISMRepairLogFile.txt
2024-10-09 14:39:36, Info DISM API: PID=1656 TID=1716 Initialized GlobalConfig - DismInitializeInternal
2024-10-09 14:39:36, Info DISM API: PID=1656 TID=1716 Initialized SessionTable - DismInitializeInternal
2024-10-09 14:39:36, Info DISM API: PID=1656 TID=1716 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath
2024-10-09 14:39:36, Info DISM API: PID=1656 TID=1716 Waiting for m_pInternalThread to start - CCommandThread::Start
2024-10-09 14:39:36, Info DISM API: PID=1656 TID=1796 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2024-10-09 14:39:36, Info DISM API: PID=1656 TID=1796 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2024-10-09 14:39:36, Info DISM API: PID=1656 TID=1716 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
2024-10-09 14:39:36, Info DISM API: PID=1656 TID=1716 m_pInternalThread started - CCommandThread::Start
2024-10-09 14:39:36, Info DISM API: PID=1656 TID=1716 Created g_internalDismSession - DismInitializeInternal
2024-10-09 14:39:36, Info DISM API: PID=1656 TID=1716 Leave DismInitializeInternal - DismInitializeInternal
2024-10-09 14:39:36, Info DISM API: PID=1656 TID=1716 Enter DismOpenSessionInternal - DismOpenSessionInternal
2024-10-09 14:39:36, Info DISM API: PID=1656 TID=1716 Input parameters: ImagePath: C:\, WindowsDirectory: (null), SystemDrive: (null) - DismOpenSessionInternal
2024-10-09 14:39:36, Info DISM API: PID=1656 TID=1716 Lookup in table by path failed for: DRIVE_C - CTransactionalImageTable::LookupImagePath
2024-10-09 14:39:36, Info DISM API: PID=1656 TID=1716 Waiting for m_pInternalThread to start - CCommandThread::Start
2024-10-09 14:39:36, Info DISM API: PID=1656 TID=1800 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2024-10-09 14:39:36, Info DISM API: PID=1656 TID=1800 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2024-10-09 14:39:36, Info DISM API: PID=1656 TID=1716 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
2024-10-09 14:39:36, Info DISM API: PID=1656 TID=1716 m_pInternalThread started - CCommandThread::Start
2024-10-09 14:39:36, Info DISM API: PID=1656 TID=1716 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2024-10-09 14:39:36, Info DISM API: PID=1656 TID=1800 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2024-10-09 14:39:36, Info DISM API: PID=1656 TID=1800 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2024-10-09 14:39:36, Info DISM PID=1656 TID=1800 Scratch directory set to 'X:\windows\TEMP\'. - CDISMManager::put_ScratchDir
2024-10-09 14:39:36, Info DISM PID=1656 TID=1800 DismCore.dll version: 10.0.19041.1 - CDISMManager::FinalConstruct
2024-10-09 14:39:36, Info DISM Initialized Panther logging at C:\Windows\System32\Logfiles\Srt\DISMRepairLogFile.txt
2024-10-09 14:39:36, Info DISM PID=1656 TID=1800 Successfully loaded the ImageSession at "X:\windows\SYSTEM32\Dism" - CDISMManager::LoadLocalImageSession
2024-10-09 14:39:36, Info DISM Initialized Panther logging at C:\Windows\System32\Logfiles\Srt\DISMRepairLogFile.txt
2024-10-09 14:39:36, Info DISM DISM Provider Store: PID=1656 TID=1800 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2024-10-09 14:39:36, Info DISM DISM Provider Store: PID=1656 TID=1800 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2024-10-09 14:39:36, Info DISM DISM Provider Store: PID=1656 TID=1800 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2024-10-09 14:39:36, Info DISM Initialized Panther logging at C:\Windows\System32\Logfiles\Srt\DISMRepairLogFile.txt
2024-10-09 14:39:36, Info DISM DISM Manager: PID=1656 TID=1800 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2024-10-09 14:39:36, Info DISM DISM Provider Store: PID=1656 TID=1800 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2024-10-09 14:39:36, Info DISM DISM Provider Store: PID=1656 TID=1800 Connecting to the provider located at X:\windows\SYSTEM32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2024-10-09 14:39:36, Warning DISM DISM Provider Store: PID=1656 TID=1800 Failed to load the provider: X:\windows\SYSTEM32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2024-10-09 14:39:36, Info DISM DISM Provider Store: PID=1656 TID=1800 Connecting to the provider located at X:\windows\SYSTEM32\Dism\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2024-10-09 14:39:36, Info DISM DISM Provider Store: PID=1656 TID=1800 Connecting to the provider located at X:\windows\SYSTEM32\Dism\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2024-10-09 14:39:36, Info DISM DISM Provider Store: PID=1656 TID=1800 Connecting to the provider located at X:\windows\SYSTEM32\Dism\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2024-10-09 14:39:36, Info DISM DISM Provider Store: PID=1656 TID=1800 Connecting to the provider located at X:\windows\SYSTEM32\Dism\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2024-10-09 14:39:36, Warning DISM DISM Provider Store: PID=1656 TID=1800 Failed to load the provider: X:\windows\SYSTEM32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2024-10-09 14:39:36, Info DISM DISM FFU Provider: PID=1656 TID=1800 [C:\] is not recognized by the DISM FFU provider. - CFfuImage::Initialize
[1656] [0x80070002] FIOReadFileIntoBuffer:(1452): The system cannot find the file specified.
[1656] [0xc142011c] UnmarshallImageHandleFromDirectory:(641)
[1656] [0xc142011c] WIMGetMountedImageHandle:(2906)
2024-10-09 14:39:36, Info DISM DISM WIM Provider: PID=1656 TID=1800 [C:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
2024-10-09 14:39:36, Info DISM DISM VHD Provider: PID=1656 TID=1800 [C:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2024-10-09 14:39:36, Info DISM DISM FFU Provider: PID=1656 TID=1800 [C:\] is not recognized by the DISM FFU provider. - CFfuImage::Initialize
2024-10-09 14:39:36, Info DISM DISM Imaging Provider: PID=1656 TID=1800 The provider FfuManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage
2024-10-09 14:39:36, Info DISM DISM VHD Provider: PID=1656 TID=1800 [C:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2024-10-09 14:39:36, Info DISM DISM Imaging Provider: PID=1656 TID=1800 The provider VHDManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage
[1656] [0x80070002] FIOReadFileIntoBuffer:(1452): The system cannot find the file specified.
[1656] [0xc142011c] UnmarshallImageHandleFromDirectory:(641)
[1656] [0xc142011c] WIMGetMountedImageHandle:(2906)
2024-10-09 14:39:36, Info DISM DISM WIM Provider: PID=1656 TID=1800 [C:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
2024-10-09 14:39:36, Info DISM DISM Imaging Provider: PID=1656 TID=1800 The provider WimManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage
2024-10-09 14:39:36, Info DISM DISM Imaging Provider: PID=1656 TID=1800 No imaging provider supported CreateDismImage for this path - CGenericImagingManager::CreateDismImage
2024-10-09 14:39:36, Info DISM DISM Manager: PID=1656 TID=1800 physical location path: C:\ - CDISMManager::CreateImageSession
2024-10-09 14:39:36, Info DISM DISM Manager: PID=1656 TID=1800 Event name for current DISM session is Global\__?_Volume{c246709a-4de0-4a17-af97-cba6655cbf80}__2455229469_393216_747993 - CDISMManager::CheckSessionAndLock
2024-10-09 14:39:36, Info DISM DISM Manager: PID=1656 TID=1800 Create session event 0x42c for current DISM session and event name is Global\__?_Volume{c246709a-4de0-4a17-af97-cba6655cbf80}__2455229469_393216_747993 - CDISMManager::CheckSessionAndLock
2024-10-09 14:39:36, Info DISM DISM Manager: PID=1656 TID=1800 Copying DISM from "C:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
2024-10-09 14:39:36, Info DISM DISM Manager: PID=1656 TID=1800 Successfully loaded the ImageSession at "X:\windows\TEMP\37855526-DB90-42A0-829D-DE3A892C9785" - CDISMManager::LoadRemoteImageSession
2024-10-09 14:39:36, Info DISM DISM Image Session: PID=1808 TID=1836 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2024-10-09 14:39:36, Info DISM DISM Provider Store: PID=1808 TID=1836 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
2024-10-09 14:39:36, Info DISM DISM Provider Store: PID=1808 TID=1836 Connecting to the provider located at X:\windows\TEMP\37855526-DB90-42A0-829D-DE3A892C9785\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider

[RazorKitten]

SrtTrail:

Startup Repair diagnosis and repair log
---------------------------
Last successful boot time: ‎10/‎9/‎2024 1:59:18 AM (GMT)
Number of repair attempts: 2

Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = C:\windows
AutoChk Run = 0
Number of root causes = 0

Test Performed:
---------------------------
Name: Check for updates
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System disk test
Result: Completed successfully. Error code = 0x0
Time taken = 16 ms

Test Performed:
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 1609 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Target OS test
Result: Completed successfully. Error code = 0x0
Time taken = 16 ms

Test Performed:
---------------------------
Name: Volume content check
Result: Completed successfully. Error code = 0x0
Time taken = 47 ms

Test Performed:
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 93 ms

Test Performed:
---------------------------
Name: Internal state check
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Check for installed LCU
Result: Completed successfully. Error code = 0x0
Time taken = 2313 ms

Test Performed:
---------------------------
Name: Check for installed driver updates
Result: Completed successfully. Error code = 0x0
Time taken = 625 ms

Test Performed:
---------------------------
Name: Check for pending package install
Result: Completed successfully. Error code = 0x0
Time taken = 1437 ms

Test Performed:
---------------------------
Name: Boot status test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Setup state check
Result: Completed successfully. Error code = 0x0
Time taken = 47 ms

Test Performed:
---------------------------
Name: Registry hives test
Result: Completed successfully. Error code = 0x0
Time taken = 407 ms

Test Performed:
---------------------------
Name: Windows boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Bugcheck analysis
Result: Completed successfully. Error code = 0x0
Time taken = 109 ms

---------------------------
---------------------------
Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = C:\windows
AutoChk Run = 0
Number of root causes = 0

Test Performed:
---------------------------
Name: Check for updates
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System disk test
Result: Completed successfully. Error code = 0x0
Time taken = 15 ms

Test Performed:
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 1688 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Target OS test
Result: Completed successfully. Error code = 0x0
Time taken = 15 ms

Test Performed:
---------------------------
Name: Volume content check
Result: Completed successfully. Error code = 0x0
Time taken = 47 ms

Test Performed:
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 125 ms

Test Performed:
---------------------------
Name: Internal state check
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Check for installed LCU
Result: Completed successfully. Error code = 0x0
Time taken = 2578 ms

Test Performed:
---------------------------
Name: Check for installed driver updates
Result: Completed successfully. Error code = 0x0
Time taken = 625 ms

Test Performed:
---------------------------
Name: Check for pending package install
Result: Completed successfully. Error code = 0x0
Time taken = 1407 ms

Test Performed:
---------------------------
Name: Boot status test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Setup state check
Result: Completed successfully. Error code = 0x0
Time taken = 46 ms

Test Performed:
---------------------------
Name: Registry hives test
Result: Completed successfully. Error code = 0x0
Time taken = 407 ms

Test Performed:
---------------------------
Name: Windows boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Bugcheck analysis
Result: Completed successfully. Error code = 0x0
Time taken = 93 ms

---------------------------
---------------------------

[Bad 💀 Motha]

It should enter repair mode if you get 3 failed boots in a row

[Set-115689]

No idea.

Unplug extra usb devices and see how that goes?

Run crystaldiskinfo to check drives. Windows test isn't good.

Can run windows short memory test. Press windows key and type memory and click on the memory diagnostic test. It's a light test.

Run a dism/sfc cycle?

Press windows key and type cmd. Right click on command prompt and select run as administrator. Then type sfc /scannow and hit enter. When it's done restart the pc. Then press windows key and type cmd. Right click on command prompt and select run as administrator. Then type DISM /Online /Cleanup-Image /RestoreHealth and press enter. Then reboot the pc when it's done. Run sfc /scannow again.

Repairing from recovery seems to never work. Can try from a windows install usb stick.

[Bad 💀 Motha]

I would just go on a working PC and make your own Win10 22H2 USB Flash Drive using Media Creation Tool -or- Rufus + Win10 ISO

Then boot to this USB drive on the problem system and do a clean install. The previous OS + Files will get pushed to "c:\windows.old"

To which you can get into to get your files after the OS install has completed and you reach the OS Desktop.

[RazorKitten]

Thanks for replying. :D

sfc scan - No violations detected

DISM - No corruption detected

CrystalMark - no errors detected

Guess I'll look into the flash drive thing... wish I knew what caused this, I guess I can just put it down to Windows being Windows?

[jeffpmaxs6]

Maybe you will be good after a clean install. I’m just not 100% convince it’s not the drive or MB setting at this point.

[RazorKitten]

I havent changed any system, bios, clock or voltage setting or any internal hardware since getting the PC in 2022 and everything works flawlessly once it actually boots, including everything running off the same drive Windows is on. Weird.

I got a reply from Microsoft and they asked for some logfiles to analyse, so we'll see if that results in something... or if I just doxed myself.

[jeffpmaxs6]

I can just think of resetting the BIOS and checking the boot order. If it isn’t hardware or a hardware settings or bad driver, then I guess that just leave reinstalling windows. If that doesn’t fix it, then back to square one.

[RazorKitten]

Yeah, for the time being I'm just not turning it off. Since its my work and play computer I need it to be always available, and the problem only occurs on boot. At least I have it working now and can investigate fixes.

I do have a vague memory of a computer in the past trying to boot from a device that wasn't attached, although I have no idea how the BIOS would get altered in this way because I did check it and the settings are exactly as they were when she was first activated. If there was a power, heat or memory issue I expect it would show up when running a demanding game or stress test, of which I have done both without issue.

This motherboard has a BIOS Reset button and BIOS Flashback USB port on the back, neither of which have ever been touched. Frankly I'm loathe to do anything to the BIOS unless I'm 100% certain its gone wrong, I'm a bit of a cack-handed idiot and I simply cannot afford to knock this PC completely out of action, or render any of my setup inoperable.

[RazorKitten]

And it just spontaneously rebooted mid stream. That can't be good.

[jeffpmaxs6]

Maybe there is a conflict. You can disable things in Startup in Task manager. And try under clocking you GPU, then your ram and then CPU, but you don’t want to touch the BIOS. Maybe it’s the Drive and if you have another Drive move windows. Or reinstall windows, but if that don’t fix it. Then um. Can you use Hibernate?

[HypersleepyNaputunia]

i would try taking out your ssd
booting up a live linux system usb stick see if you can recreate the problem, do a few reboot cycles play with it for a few hours

if no problem, then id bet windows is issue
if you have problem again, we can narrow it down to hardware, next step would be to try testing ssd for problem

[RazorKitten]

Wow this one took a WHILE to sort out, turns out it was Razer drivers (mouse n keyboard). I should have figured that out earlier honestly but I wasn't at liberty to take the PC offline and work on it. Also I got cancer. I've had better months.

Thanks for the suggestions and feedback folks. Happy computering!

[Phénomènes Mystiques]

This issue reminds me of the WIn11 boot-loop regarding the 2002 external MIDI controller.