F5F Stay Refreshed Hardware Desktop System failure detected. Please restart your PC to resolve the issue.

System failure detected. Please restart your PC to resolve the issue.

System failure detected. Please restart your PC to resolve the issue.

Pages (2): Previous 1 2
C
CG_Snipey
Junior Member
42
12-21-2016, 03:33 AM
#11
It seems the system is entering a loop. Are you wondering if this started after a fresh Windows install, or if the USB isn't even recognized? You likely mean the latter. After making the standard installation USB, put it in a rear port and keep pressing F11 during boot. This should take you to the boot menu where you can select the USB drive and pick UEFI if available.
C
CG_Snipey
12-21-2016, 03:33 AM #11

It seems the system is entering a loop. Are you wondering if this started after a fresh Windows install, or if the USB isn't even recognized? You likely mean the latter. After making the standard installation USB, put it in a rear port and keep pressing F11 during boot. This should take you to the boot menu where you can select the USB drive and pick UEFI if available.

I
Infamousy
Member
207
12-21-2016, 11:13 PM
#12
I created a bootable Windows 10 USB stick using the standard tool. I connected it to a rear USB port and turned on the machine. After pressing F11, I selected the USB drive, which showed partition 1 UEFI as the only option. The Windows installation screen appeared but I realized my SATA SSD wasn’t plugged in. I powered off, reinserted the SSD, and repeated the F11 selection. The installer didn’t appear; only the motherboard display remained visible, allowing me to press del repeatedly. It kept looping through CPU, VGA + Boot, VGA, Boot commands without progress. This behavior was similar to what happened with the NVMe drive. Checking the BIOS, pressing del quickly triggered a detection if the drive was recognized. Could something have changed in the BIOS? Should I update it to the latest version? Are there other issues I might be missing? Any settings in the BIOS might be missing? Thank you very much for your help, Brian.
I
Infamousy
12-21-2016, 11:13 PM #12

I created a bootable Windows 10 USB stick using the standard tool. I connected it to a rear USB port and turned on the machine. After pressing F11, I selected the USB drive, which showed partition 1 UEFI as the only option. The Windows installation screen appeared but I realized my SATA SSD wasn’t plugged in. I powered off, reinserted the SSD, and repeated the F11 selection. The installer didn’t appear; only the motherboard display remained visible, allowing me to press del repeatedly. It kept looping through CPU, VGA + Boot, VGA, Boot commands without progress. This behavior was similar to what happened with the NVMe drive. Checking the BIOS, pressing del quickly triggered a detection if the drive was recognized. Could something have changed in the BIOS? Should I update it to the latest version? Are there other issues I might be missing? Any settings in the BIOS might be missing? Thank you very much for your help, Brian.

H
henrydog19
Junior Member
45
12-22-2016, 03:48 PM
#13
In the BIOS, navigate to settings, then Advanced, followed by Windows OS Configuration. Adjust the BIOS UEFI/CSM Mode setting to UEFI if it isn't already.
H
henrydog19
12-22-2016, 03:48 PM #13

In the BIOS, navigate to settings, then Advanced, followed by Windows OS Configuration. Adjust the BIOS UEFI/CSM Mode setting to UEFI if it isn't already.

C
Ciera7
Member
225
12-22-2016, 08:20 PM
#14
It recognizes the USB stick I acquired, getting really excited when the language selection screen appeared, but I didn’t have the SATA drive plugged in. Once connected, it doesn’t let the USB load, even when using the F11 menu.
C
Ciera7
12-22-2016, 08:20 PM #14

It recognizes the USB stick I acquired, getting really excited when the language selection screen appeared, but I didn’t have the SATA drive plugged in. Once connected, it doesn’t let the USB load, even when using the F11 menu.

A
afonsozt
Junior Member
6
12-22-2016, 08:32 PM
#15
I'm struggling right now. The only thing that comes to mind is whether the storage device is configured for IDE, AHCI, or RAID. Should be AHCI. If not, there might be a problem with the motherboard. Try connecting different drives and see if it works. It might help to update or simply re-flash the BIOS.
A
afonsozt
12-22-2016, 08:32 PM #15

I'm struggling right now. The only thing that comes to mind is whether the storage device is configured for IDE, AHCI, or RAID. Should be AHCI. If not, there might be a problem with the motherboard. Try connecting different drives and see if it works. It might help to update or simply re-flash the BIOS.

N
179
12-22-2016, 09:53 PM
#16
Drive configuration is AHCI, probably need to flash the BIOS as mentioned. I have another motherboard I can test by intentionally failing it. Thanks again. I’ll let you know if anything changes. I usually dislike flashing BIOS—it always feels like something’s about to go wrong.
N
NicknameNumber
12-22-2016, 09:53 PM #16

Drive configuration is AHCI, probably need to flash the BIOS as mentioned. I have another motherboard I can test by intentionally failing it. Thanks again. I’ll let you know if anything changes. I usually dislike flashing BIOS—it always feels like something’s about to go wrong.

S
SuperTigresss
Posting Freak
768
12-23-2016, 06:53 AM
#17
I experimented with the chip on another board and achieved the same outcome. Used a reliable working chip and it performed flawlessly. It seems the original chip may have failed. I’ll need to send this elsewhere. I’ll reach out to my supplier for assistance. I plan to verify the other board’s chip just to confirm functionality. It’s been a challenge because of health concerns, but your guidance made things clearer and very helpful. Thank you again.
Best regards, Brian.
S
SuperTigresss
12-23-2016, 06:53 AM #17

I experimented with the chip on another board and achieved the same outcome. Used a reliable working chip and it performed flawlessly. It seems the original chip may have failed. I’ll need to send this elsewhere. I’ll reach out to my supplier for assistance. I plan to verify the other board’s chip just to confirm functionality. It’s been a challenge because of health concerns, but your guidance made things clearer and very helpful. Thank you again.
Best regards, Brian.

J
JGBCRAFT
Member
65
12-23-2016, 09:08 AM
#18
I kept the original drive intact, including the NVMe storage, and backed up any files I had there. I also performed a fresh Windows installation just to be safe.
J
JGBCRAFT
12-23-2016, 09:08 AM #18

I kept the original drive intact, including the NVMe storage, and backed up any files I had there. I also performed a fresh Windows installation just to be safe.

Pages (2): Previous 1 2