F5F Stay Refreshed Hardware Desktop MB shared and set up W11 on the exterior of the case, with only a boot to the BIOS in the case itself.

MB shared and set up W11 on the exterior of the case, with only a boot to the BIOS in the case itself.

MB shared and set up W11 on the exterior of the case, with only a boot to the BIOS in the case itself.

H
Hetchok
Member
172
08-10-2025, 01:06 AM
#1
Asus Rog Strix Z690 Gaming-E underwent testing on its original case with W11 installed on a Samsung 980 NVME. Other NVMEs compatible elsewhere failed to install W. After setup, the system only booted into BIOS displaying code 98, which appeared memory-related in searches. Memtest cleared successfully, but attempting one stick at a time showed no improvement. The NVME was repositioned and tested in another M.2 slot; all connections were verified, CMOS reset, and BIOS updated to version 4101. Tested with IGPU, unplugged three SATA drives, and USB setup attempted via Rufus and Windows Media created USB still only reached BIOS. Even after saving and exiting, no changes appeared during reboot, though the system displayed USB as first boot device. CPU checks were avoided unless essential due to a custom loop; temperatures remain stable. A custom loop was used, including three SSDs (Gigabyte 3060TI, Samsung 980, 3 x 16GB G Skill F5 6400), Seasonic GS-Prime 850 Gold Plus, and the Asus Z690 with contact frame). Thank you for your assistance – greatly appreciated. Edited May 5, 2025 by Bartmole
H
Hetchok
08-10-2025, 01:06 AM #1

Asus Rog Strix Z690 Gaming-E underwent testing on its original case with W11 installed on a Samsung 980 NVME. Other NVMEs compatible elsewhere failed to install W. After setup, the system only booted into BIOS displaying code 98, which appeared memory-related in searches. Memtest cleared successfully, but attempting one stick at a time showed no improvement. The NVME was repositioned and tested in another M.2 slot; all connections were verified, CMOS reset, and BIOS updated to version 4101. Tested with IGPU, unplugged three SATA drives, and USB setup attempted via Rufus and Windows Media created USB still only reached BIOS. Even after saving and exiting, no changes appeared during reboot, though the system displayed USB as first boot device. CPU checks were avoided unless essential due to a custom loop; temperatures remain stable. A custom loop was used, including three SSDs (Gigabyte 3060TI, Samsung 980, 3 x 16GB G Skill F5 6400), Seasonic GS-Prime 850 Gold Plus, and the Asus Z690 with contact frame). Thank you for your assistance – greatly appreciated. Edited May 5, 2025 by Bartmole

S
steffekk123
Member
59
08-10-2025, 01:06 AM
#2
GS Prime comes with a 12-year warranty. Verify your BIOS includes "Legacy USB support mode." Also, ensure all Windows 11 requirements are met in the BIOS settings. Keep your message concise for better clarity.
S
steffekk123
08-10-2025, 01:06 AM #2

GS Prime comes with a 12-year warranty. Verify your BIOS includes "Legacy USB support mode." Also, ensure all Windows 11 requirements are met in the BIOS settings. Keep your message concise for better clarity.

N
NameAcht70688
Junior Member
21
08-10-2025, 01:06 AM
#3
Legacy turning it off or on doesn't matter; everything works well in BIOS. I didn't like the motherboard much from the beginning and faced issues right away, despite the good price. A replacement board is coming soon, thank you.
N
NameAcht70688
08-10-2025, 01:06 AM #3

Legacy turning it off or on doesn't matter; everything works well in BIOS. I didn't like the motherboard much from the beginning and faced issues right away, despite the good price. A replacement board is coming soon, thank you.

S
Sh4rKai
Member
64
08-10-2025, 01:06 AM
#4
Worked during testing but not during installation? Looked for any loose screws or components that might cause a short. Recently assembled a box with old parts—MOBO passed tests on the bench, installed in the case, no issues. My fix was removing the MMO, thoroughly inspecting for shorts or burn marks, but found nothing. On instinct, I used a thin packing sheet from the box and placed it under the MMO; it functioned perfectly afterward. Tried dual booting DOS 6.22 and WinXP just to confirm. My theory was a short was bridging the back of the MMO to the case, with padding providing insulation. So I checked for loose screws or similar.
S
Sh4rKai
08-10-2025, 01:06 AM #4

Worked during testing but not during installation? Looked for any loose screws or components that might cause a short. Recently assembled a box with old parts—MOBO passed tests on the bench, installed in the case, no issues. My fix was removing the MMO, thoroughly inspecting for shorts or burn marks, but found nothing. On instinct, I used a thin packing sheet from the box and placed it under the MMO; it functioned perfectly afterward. Tried dual booting DOS 6.22 and WinXP just to confirm. My theory was a short was bridging the back of the MMO to the case, with padding providing insulation. So I checked for loose screws or similar.

Y
Yolo_Jake_GG
Member
75
08-10-2025, 01:06 AM
#5
Yes, you meant the MOBO was removed and placed inside the anti-static bag for evaluation. Those bags are designed to be non-conductive, making them suitable for testing electronic components without risk of static discharge.
Y
Yolo_Jake_GG
08-10-2025, 01:06 AM #5

Yes, you meant the MOBO was removed and placed inside the anti-static bag for evaluation. Those bags are designed to be non-conductive, making them suitable for testing electronic components without risk of static discharge.