Issue with Gigabyte H310M M.2 2.0 boot loop

F5F Stay Refreshed Hardware Desktop Issue with Gigabyte H310M M.2 2.0 boot loop

Issue with Gigabyte H310M M.2 2.0 boot loop

Issue with Gigabyte H310M M.2 2.0 boot loop

L

Lazer18
Member

69

10-10-2016, 11:05 PM

#1

I was attempting to set up RAID on my Gigabyte H310 motherboard with an Intel i3 9100F processor and a 4 GB DDR4 RAM stick. After adjusting the UEFI BIOS settings to disable CSM support, I restarted the system but encountered a boot loop. The computer kept spinning without any display output or progress. I reset the CMOS, unplugged all components, and tried booting again, but the issue persisted. I also replaced the RAM and a new graphics card, yet nothing worked. I’m still unable to see anything on the screen and need assistance. Thank you in advance!

L

Lazer18

10-10-2016, 11:05 PM #1

I was attempting to set up RAID on my Gigabyte H310 motherboard with an Intel i3 9100F processor and a 4 GB DDR4 RAM stick. After adjusting the UEFI BIOS settings to disable CSM support, I restarted the system but encountered a boot loop. The computer kept spinning without any display output or progress. I reset the CMOS, unplugged all components, and tried booting again, but the issue persisted. I also replaced the RAM and a new graphics card, yet nothing worked. I’m still unable to see anything on the screen and need assistance. Thank you in advance!

B

blondi2000
Junior Member

11

10-19-2016, 01:01 PM

#2

Did you also test onboard video and dedicated? That's unusual.

B

blondi2000

10-19-2016, 01:01 PM #2

Did you also test onboard video and dedicated? That's unusual.

F

FML420
Junior Member

27

10-19-2016, 01:16 PM

#3

This model doesn't include built-in video capabilities.

F

FML420

10-19-2016, 01:16 PM #3

This model doesn't include built-in video capabilities.

K

khaledkb_
Senior Member

724

10-20-2016, 08:37 AM

#4

Sorry for the delay. I managed to resolve it. The process involved removing the C-MOS battery rather than using the reset button. Thanks!

K

khaledkb_

10-20-2016, 08:37 AM #4

Sorry for the delay. I managed to resolve it. The process involved removing the C-MOS battery rather than using the reset button. Thanks!