The system reinitializes the boot process each time it reaches the Windows Recovery Environment.
The system reinitializes the boot process each time it reaches the Windows Recovery Environment.
Details:
- GIGABYTE Aorus Z790 Prox X
- 14900K overclocked with "Optimisation" preset, CPU Upgrade set to Default
- COSAIR DOMINATOR TITANIUM RGB DDR5 RAM 32GB (2x16GB), DDR5 7000MHz CL34, CMP32GX5M2X7000C34W, XMP 1 7000 34-42-42-96-1.450V
- RTX 4080 SUPER FE stock configuration
- Samsung SATA SSD 850 1TB
- Kraken X72 with LGA1700 bracket
- VCCCIN AUX adjusted to 2.0V for stable boot, following a previous successful adjustment on an X299 7820X
I haven’t performed advanced overclocking and stick to the original settings for CPU and RAM XMP profiles. I’ve also experimented with lowering RAM speeds gradually, but the issue persists only during cold boots. It’s only when the system powers off that it becomes unstable. Any suggestions?
xAPPLExPIEx
10-09-2024, 12:15 PM #1Windows 11 has been fully updated and installed on a freshly formatted Samsung 970 M.2 NVMe drive. Upon cold startup, it consistently launches into the Windows Recovery Environment, and after rebooting via UEFI, it operates smoothly. The system remains stable regardless of the workload.
Details:
- GIGABYTE Aorus Z790 Prox X
- 14900K overclocked with "Optimisation" preset, CPU Upgrade set to Default
- COSAIR DOMINATOR TITANIUM RGB DDR5 RAM 32GB (2x16GB), DDR5 7000MHz CL34, CMP32GX5M2X7000C34W, XMP 1 7000 34-42-42-96-1.450V
- RTX 4080 SUPER FE stock configuration
- Samsung SATA SSD 850 1TB
- Kraken X72 with LGA1700 bracket
- VCCCIN AUX adjusted to 2.0V for stable boot, following a previous successful adjustment on an X299 7820X
I haven’t performed advanced overclocking and stick to the original settings for CPU and RAM XMP profiles. I’ve also experimented with lowering RAM speeds gradually, but the issue persists only during cold boots. It’s only when the system powers off that it becomes unstable. Any suggestions?
If BCD configuration issues arise, you can reset it using the command. (Run from elevated command prompt)
Also, show a screenshot from Disk Management. The bootloader partition might be too small, which is causing your issue.
masterpet09
10-13-2024, 10:25 PM #2Display screenshot of the command output from bcdedit. It must be executed in an elevated command prompt, or you'll encounter access denied errors. (Upload the image to imgur.com and share the link)
If BCD configuration issues arise, you can reset it using the command. (Run from elevated command prompt)
Also, show a screenshot from Disk Management. The bootloader partition might be too small, which is causing your issue.
The content appears to be an image located at the specified URL.
BobbyNeymar
10-14-2024, 01:10 AM #3Here is the information from the provided link.
The content appears to be an image located at the specified URL.
Ideal size should range from 350MB to 500MB.
First, you'll require a Windows installation disk.
If unavailable, prepare one using an 8GB USB flash drive.
https://www.microsoft.com/software-download/windows11
Next, boot the system from the installation media and open the command prompt.
Press Shift+F10 to launch it.
Run the following commands sequentially:
diskpart
list disk
select disk x
(choose 238GB disk, verify disk number, replace x with correct value, x=0 or x=1)
list partition
select partition x
(select 237GB windows partition,
replace x with appropriate number,
x=2 or x=3)
shrink desired=500
create partition efi size=500
format fs=fat32 quick
assign letter=H
select partition 1
(select 100MB EFI system partition)
delete partition override
list volume
(remember note the drive letter for the 237GB partition, it could be C: or D
exit
bcdboot C:\windows /s H: /f UEFI
(I'm assuming the Windows partition drive letter is C:. If it's D: adjust accordingly.)
Boot files created successfully.
If you encounter any problems, stop immediately and display the command output.
Screenshot of the process shown here.
Bootloader area is limited to 100MB, which may lead to issues.
Ideal size should range from 350MB to 500MB.
First, you'll require a Windows installation disk.
If unavailable, prepare one using an 8GB USB flash drive.
https://www.microsoft.com/software-download/windows11
Next, boot the system from the installation media and open the command prompt.
Press Shift+F10 to launch it.
Run the following commands sequentially:
diskpart
list disk
select disk x
(choose 238GB disk, verify disk number, replace x with correct value, x=0 or x=1)
list partition
select partition x
(select 237GB windows partition,
replace x with appropriate number,
x=2 or x=3)
shrink desired=500
create partition efi size=500
format fs=fat32 quick
assign letter=H
select partition 1
(select 100MB EFI system partition)
delete partition override
list volume
(remember note the drive letter for the 237GB partition, it could be C: or D
exit
bcdboot C:\windows /s H: /f UEFI
(I'm assuming the Windows partition drive letter is C:. If it's D: adjust accordingly.)
Boot files created successfully.
If you encounter any problems, stop immediately and display the command output.
Screenshot of the process shown here.
One observation I made before doing what you instructed was upon booting directly into BIOS I noticed that my M.2 Windows OS drive was now showing up in the "Peripherals" section; whereas, prior to this I would only see the SSD (see the final image I've uploaded to Imgur). Any idea what that is about? I'd noticed that it was absent in BIOS on my last build – I'm reusing the M.2 drive from that build.
Is there anything else I need to do from this point on? The 100MB partition is now unallocated. Is there any point messing with that or will it just remain unused?
https://imgur.com/a/l5bpKnD
View: https://imgur.com/a/l5bpKnD
😵💫👍
Right, I followed your instructions to the letter and everything went exactly as you described.
One observation I made before doing what you instructed was upon booting directly into BIOS I noticed that my M.2 Windows OS drive was now showing up in the "Peripherals" section; whereas, prior to this I would only see the SSD (see the final image I've uploaded to Imgur). Any idea what that is about? I'd noticed that it was absent in BIOS on my last build – I'm reusing the M.2 drive from that build.
Is there anything else I need to do from this point on? The 100MB partition is now unallocated. Is there any point messing with that or will it just remain unused?
https://imgur.com/a/l5bpKnD
View: https://imgur.com/a/l5bpKnD
😵💫👍
I'll keep an eye out for any strange behavior or failures moving forward, but right now I feel confident about this fix. Here, enjoy a chilled glass of milk and a cookie for your troubles 🥛+🍪.
Many, many thanks!!
Over and out . . . 🤪👍
meandmoreme
10-31-2024, 09:18 PM #8I attempted a cold boot after leaving the pc off for roughly half an hour and it started without problems. I suspect you might have succeeded! I wouldn't have bothered checking that during the Win installation since nothing in the process suggests paying attention to limited space for the boot manager.
I'll keep an eye out for any strange behavior or failures moving forward, but right now I feel confident about this fix. Here, enjoy a chilled glass of milk and a cookie for your troubles 🥛+🍪.
Many, many thanks!!
Over and out . . . 🤪👍