Windows 10 stuck at kernel boot, spinning circle

ET_Explorer said:
Have you tried any of these on this site > Aomei
Click to expand...
Hi,

I tried a lot of these things like this SFC and DISM or System Restore ( which failed and the restore point is no longer there).

A lot of them require you to be able to log in into Safe Mode and it doesn't work on my broken OS
 
Did you try to remove all disks (except the WD blue SN570) and change the boot order in your BIOS/UEFI settings? (WD Blue as first)
Please, re-send the result of bcdedit and diskpart (list disk, select disk 0, detail disk, list partition, list volume, select disk 1, detail disk, list partition, list volume).
 
xilolee said:
Did you try to remove all disks (except the WD blue SN570) and change the boot order in your BIOS/UEFI settings? (WD Blue as first)
Please, re-send the result of bcdedit and diskpart (list disk, select disk 0, detail disk, list partition, list volume, select disk 1, detail disk, list partition, list volume).
Click to expand...
Hey,

Yes

It looks like I have 3 boot managers now, all look exact same and are named the same and I can choose from them in the bios... They are working, but...still the same BSOD, though, ever since I replaced that system hive with the one provided by you. It now supposedly made a dump, but it is nowhere to be found...

Here is diskpart and bcdedit

Microsoft DiskPart version 10.0.19041.1

Copyright (C) Microsoft Corporation.
On computer: MININT-FDBU8O6

DISKPART>
Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
Disk 0 Online 1863 GB 195 GB *

DISKPART>
Disk 0 is now the selected disk.

DISKPART>
Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 System 100 MB 1024 KB
Partition 2 Reserved 16 MB 101 MB
Partition 3 Primary 1667 GB 117 MB
Partition 4 Recovery 508 MB 1862 GB

DISKPART>
Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 C Windows 10 NTFS Partition 1667 GB Healthy
Volume 1 D NTFS Partition 508 MB Healthy
Volume 2 FAT32 Partition 100 MB Healthy Hidden

DISKPART>
Leaving DiskPart...


Firmware Boot Manager
---------------------
identifier {fwbootmgr}
displayorder {bootmgr}
{1ab4bcd9-d78e-11ef-96a2-806e6f6e6963}
{3917a8b3-d78c-11ef-93db-806e6f6e6963}
{1ab4bcda-d78e-11ef-96a2-806e6f6e6963}
{1ab4bcdb-d78e-11ef-96a2-806e6f6e6963}
{8e45746d-ddff-11ef-8c49-806e6f6e6963}
timeout 1

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume1
path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {default}
resumeobject {d9303ca9-d645-11ef-80fd-18c04d47d83c}
displayorder {default}
toolsdisplayorder {memdiag}
timeout 0

Firmware Application (101fffff)
-------------------------------
identifier {1ab4bcd9-d78e-11ef-96a2-806e6f6e6963}
device partition=D:
path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description Windows Boot Manager

Firmware Application (101fffff)
-------------------------------
identifier {1ab4bcda-d78e-11ef-96a2-806e6f6e6963}
description UEFI:CD/DVD Drive

Firmware Application (101fffff)
-------------------------------
identifier {1ab4bcdb-d78e-11ef-96a2-806e6f6e6963}
description UEFI:Removable Device

Firmware Application (101fffff)
-------------------------------
identifier {3917a8b3-d78c-11ef-93db-806e6f6e6963}
device partition=C:
path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description Windows Boot Manager

Firmware Application (101fffff)
-------------------------------
identifier {8e45746d-ddff-11ef-8c49-806e6f6e6963}
description UEFI:Network Device

Windows Boot Loader
-------------------
identifier {current}
device ramdisk=[D:]\Recovery\WindowsRE\Winre.wim,{24333dac-b7db-11ef-8097-18c04d47d83c}
path \windows\system32\winload.efi
description Windows Recovery Environment
locale en-US
inherit {bootloadersettings}
displaymessage Recovery
osdevice ramdisk=[D:]\Recovery\WindowsRE\Winre.wim,{24333dac-b7db-11ef-8097-18c04d47d83c}
systemroot \Windows
nx OptIn
bootmenupolicy Standard
winpe Yes

Windows Boot Loader
-------------------
identifier {default}
device partition=C:
path \Windows\system32\winload.efi
description Windows 10 NVME
locale en-us
inherit {bootloadersettings}
recoverysequence {current}
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
resumeobject {d9303ca9-d645-11ef-80fd-18c04d47d83c}
nx OptIn
bootmenupolicy Standard

Resume from Hibernate
---------------------
identifier {d9303ca9-d645-11ef-80fd-18c04d47d83c}
device partition=C:
path \Windows\system32\winresume.efi
description Windows Resume Application
locale en-us
inherit {resumeloadersettings}
isolatedcontext Yes
allowedinmemorysettings 0x15000075
filepath \hiberfil.sys
bootmenupolicy Standard

Windows Memory Tester
---------------------
identifier {memdiag}
device partition=\Device\HarddiskVolume1
path \EFI\Microsoft\Boot\memtest.efi
description Windows Memory Diagnostic
locale en-us
inherit {globalsettings}
badmemoryaccess Yes

EMS Settings
------------
identifier {emssettings}
bootems No

Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Local

RAM Defects
-----------
identifier {badmemory}

Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}

Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}

Hypervisor Settings
-------------------
identifier {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200

Resume Loader Settings
----------------------
identifier {resumeloadersettings}
inherit {globalsettings}

Device options
--------------
identifier {24333dac-b7db-11ef-8097-18c04d47d83c}
description Windows Recovery
ramdisksdidevice partition=D:
ramdisksdipath \Recovery\WindowsRE\boot.sdi
 
I tried your newest hive. Now the OS is getting stuck on the first loading right after selecting it. After like 30 seconds max, the loading freezes.
 
Thanks. I ran the command, but it said that DISM initialization failed or something like that. Since I ran that command from Recovery it was saving the log on that recovery partition.

I searched for help for that command. I ran new command which saved a log file on C drive.
 

Attachments

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top