[SOLVED] New PC build keeps rebooting after bios - not booting from hdd nor USB

adam23_dav23

Commendable
Sep 2, 2017
4
0
1,520
Finally got my new pc going (after 2 years of building it) and installed windows 10 pro on it via Win 10 bootable USB.
Everything went fine.
Installed drivers, nvidia drivers, motherboard drivers and software, corsair and thermaltake software, rebooted several times after updates. All working fine.
Turned off PC to change Displayport cables to run Gfx cards as SLI, booted up fine.
Did a benchmark test, then a Final Fantasy XV benchmark test - all fine.
Shutdown windows, then turned off pc via PSU switch as some leds were still on
This morning, turned on pc. Now, not booting into anything. Loads up bios screen and can get into bios but after that just reboots over and over.

Steps taken to attempt resolve:
  • Tried smashing F8 to get see if I load safe mode - still failed
  • Changed Boot from UEFI to legacy - still failed
  • Changed SATA AHCI to Intel RST - still failed
  • Used Bootable USB devices such as Windows 10 boot usb and Hirens boot usb - still failed
  • Unplugged all HDD's, just left bootable usb - still failed (therefore not a Win10/hdd issue)
  • unplugged non-essential power devices such as LEDS, internal USB 2.0 io (9pin) Thermaltake fan controllers (which were have issues yesterday as all fans were working but not all controllers were showing up in the Thermaltake RGB app) , - still failed
  • replaced custom CPU cable with original cables. - still failed
  • updated BIOS - didn't resolve it.

- Last step which haven't done and DON'T WANT to do it unless there is definately no more options left, is to remove the CMOS battery but to get to it would mean might having to remove half of the water cool loop, gfx cards and bracket (which is a pain) just to get to it. Might be able to do it without removing if I had long chopsticks with a hook at the end...or one of them rubber suction cup arrows you get with a kids bow and arrow to get to it.

Can anyone advise what else can be done?
I was so close. Only worked for one day. maybe I should've left it on when I went to sleep and never shutdown.

Specs:
Motherboard: Gigabyte Aorus gaming 9
CPU: Core i9-7940x
PSU: Thermaltake 1250W iRGB
Video Cards: 2x Gigabyte Aorus 1080ti
Ram: 128GB G.Skill Trident
HDD: 2TB WD Black (plus 7 others but only running 1 to get windows working first)
Fans: 18x Thermal take riing plus - connected to 4 controllers
Keyboard: Corsair K95 platinum
Mouse: Logitech G905

Here are some photos of it and WHY don't want to get to the CMOS battery yet and shows it running in that one day.

20191218-132815.jpg
20191212-213031.jpg


20191218-171620.jpg
20191220-012032.jpg

20191220-012039.jpg
20191220-020933.jpg
 
Solution
Yea, tried other bootdrives but anyway, scratch that. Got it working.
All I did was unplugged PCIE cables as one was pulling hard on a LED cable, and saw one Addressable rgb pin connector came apart. Maybe that was touching something, don't know but once I reconnected those, gave a few motherboard connectors a little push in (with a chopstick), turned it back on...it started working.
And also the Thermaltake controllers I was having an issue where 1 or 2 not coming up..are all working and a aqua led ring is working now.

I've turned it off and turned it back on. Still working. Let's hope it stays

Maybe will not turn it off. Haha.
Well, can close this question now, even though I still don't know what I had done.

adam23_dav23

Commendable
Sep 2, 2017
4
0
1,520
Yea, tried other bootdrives but anyway, scratch that. Got it working.
All I did was unplugged PCIE cables as one was pulling hard on a LED cable, and saw one Addressable rgb pin connector came apart. Maybe that was touching something, don't know but once I reconnected those, gave a few motherboard connectors a little push in (with a chopstick), turned it back on...it started working.
And also the Thermaltake controllers I was having an issue where 1 or 2 not coming up..are all working and a aqua led ring is working now.

I've turned it off and turned it back on. Still working. Let's hope it stays

Maybe will not turn it off. Haha.
Well, can close this question now, even though I still don't know what I had done.
 
Last edited:
Solution