Computer won't load Windows and can't enter BIOS

Hey all, tldr my computer never goes past the POST screen. Restarting it a few times and looking around (but not changing) the BIOS, then restarting it some more led to Windows 10 eventually loading, though I'm not sure what changed that enabled it to do so, but now after restarting again it won't boot Windows and I can't even get it to go into the BIOS.

Motherboard is a Gigabyte Z490 Aorus Elite AC. CPU is an Intel 10700K. Four 32gb sticks of RAM. GPU is a GTX 1070. My windows is installed on a M.2 NVMe drive and there are two raid 1 HDD arrays and a SSD drive connected.

To go into some more detail, I went to backup my computer and opened it up and attached a couple of drives to it to backup to. I then turned the computer on and it wouldn't go past the POST screen. Restarted it a couple times with the same results. Then when went to the BIOS and looked around but nothing looked off, and it seemed to detect that there was a boot drive. I exited the BIOS and I don't know if it was after that restart or trying to restart it a couple more times but the computer finally loaded Windows, but I don't know what I did to cause anything different to happen.

I figured maybe it had something to do with the backup drives causing some weird issue, but I was able to use them to backup my data. I turned the computer off, took the extra drives out, restarted the computer and then had a similarly difficult time getting the computer to start again, but again Windows eventually loaded. I restarted the computer several days later, and now it won't go past the POST screen no matter what I do. It also now won't let me load the BIOS no matter how I've tried to tap the delete key.

I've tried clearing the CMOS by shorting the jumpers and by taking out the battery for a time (and replaced it with a new one), neither of which seemed to cause any changes.

I tried taking all the RAM out and trying different combinations of sticks in different slots. None of the combinations I tried seemed to change anything except, strangely just having one in the first slot led to the computer not even entering POST. The motherboard has four little LEDs labeled VGA, CPU, DRAM and BOOT, which I'm guessing have something to do with testing or indicating an error. When the computer was stuck in POST, the BOOT LED was lit, but when the one stick of RAM was in the first slot, the DRAM LED was lit. I didn't see in the manual where it mentions those lights or almost anything to do with troubleshooting, though I certainly could have missed it.

I'm considering replacing the motherboard with the same model and hoping that things magically boot up and run fine. Before I do that, does anyone have any ideas as to what's going on or how to fix it? Thanks!!

Can you remove the raided drives and see if it boots?

Edited by cryptodan, 25 February 2024 - 04:23 PM.

Hi, Welcome to BC.

 

Please always supply BIOS information and Ram speed and make when providing information.

Make sure BIOS Version is @ F24   Released : Dec 20, 2023

https://www.gigabyte.com/Motherboard/Z490-AORUS-ELITE-AC-rev-10/support#support-dl-bios  Check your Manual here if do not have one.

If not @ Version F24 see manual if it will do a No Boot Bios Update.

 

It does sound like a M.2 issue.

 

Note re ram speed : Non-ECC Memory Maximum Speed : DDR4-2933     Ram must match Chip not the Max speed of the Motherboard.

https://ark.intel.com/content/www/us/en/ark/products/199335/intel-core-i7-10700k-processor-16m-cache-up-to-5-10-ghz.html

If ram is faster than above it maybe the issue or also the issue.

Will need to get into BIOS and change the speed.

 

If get in turn off anything the speeds up the Boot example ASUS Fast Boot for the same reasons as below :

Turn off MS Fast Start : https://www.windowscentral.com/how-disable-windows-10-fast-startup /11

Make sure Power Plan is set to Balanced.

 

If using XMP turn it off.

If using F10 and Exit Bios with Optimized Settings then you are turning on stuff like Fast Boot so if exit those have to be turned off.

Edited by Pkshadow, 25 February 2024 - 07:41 PM.

Thank you for the replies!

I disconnected the four HDD drives that were part of the two RAID 1 arrays and this time I was able to get into the BIOS.

BIOS is version F4. I'm going to try updating it to F24. The Memory frequency is 2666MHz. XMP is off (due to the CMOS reset; it was on before) and Fast Boot is (and was) off.

In the BIOS, there is only one Boot Option and it says Windows Boot Manager (SHGP31-1000GM

The computer had been running almost constantly and without significant issues for over 3 years prior to this issue that seemed to happen after opening up the case and connecting the spare backup drives.

Edited by Xfjit3k7r, 25 February 2024 - 11:22 PM.

This may sound dumb but was it off when you connected?

Being run constantly is possibly the problem.  Not enough rebooting or updating of the system.  Being on version F4 with the Security issues F24 and before fixes is worth it. 

The Bios does a massive jump in numbers, not seen that before.

 

Ya it should only find the UEFI Partition for boot.   

 

It would seem it has been trying to get to the Boot Menu or Repair Menu.   Fix the Boot : https://www.easeus.com/partition-manager-software/fix-uefi-boot-in-windows-10-8-7.html Note for info only.

If you're talking about the extra backup drives, the computer was off when I connected them. I only connect/disconnect internal hardware when the computer is off. I almost always also have the switch on the back of the power supply flipped to off, but I'm not sure if I did before I connected the drives.

If it was a Boot or Repair menu issue, would that have been stopping me from going into the BIOS? And why could I then go into the BIOS after disconnecting the HDD's?

As mentioned M.2 issue.  M.2's can cause all sorts of issues.

 

They can appear as something else rather than a problem can point to for the M,2. (if follow)

 

Once install a M.2 in the proper slot then anything that happens maybe related to it.

 

If install into the slower slot then again anything can happen or it can be pinpointed to the M.2..

 

Totally crazy stuff that can only do by testing and changing.  Yes it can change how it is booting and not find the recovery which can be booted into using a Windows PE and then commands and instructions change.

 

Or the issue is the Bootloader for UEFI :

Have you run chkdsk /r on the drive/s ?     Did you do the EASEUS  UEFI Boot repair   ?

 

Dism should be run once get to the OS : From a DOS Command Prompt from START | type cmd.exe into the start search box | RIGHT-click on cmd.exe | select "Run as Administrator" then Copy/Paste --> :   DISM /Online /Cleanup-Image /RestoreHealth command then Enter
if it finds problems then reboot. (Completed Successfully : means reboot)
then
After : please Open another Admin Command Prompt and please run Copy/Paste --> SFC /SCANNOW into the Dos window or Powershell and Enter.  Reboot after.

 

Have you updated the BIOS yet. ?? As we are not there we do not know.  As well a Bios Update can change what happens.

 

You have not named the M.2 drive make/model.  Some have drivers you can get from Manufacturers site, others do not though they all may have monitoring software which can update the Firmware of the Drive in question.

 

As well the drives that were pulled may have drivers/firmware and /or monitoring software.

 

Unless tell us what you are doing we do not know.  Without telling us it is shot gun repair.

Thank you Pkshadow for the suggestions. I will look into how to do those things. I haven't used Windows PE or DISM or chkdsk or EASEUS UEFI Boot repair.

I haven't updated the BIOS, which is still version F4. I read some users had performance impacts when they updated. I have tried a few different things:

I reconnected the four HDD drives and checked out the BIOS some more.

In BIOS > System Info > "Plug in Devices Info" it then recognized the cards in two PCIe slots, but said N/A for all three M.2 slots, even though one seems like it should have listed the M.2 NVMe drive that contains the OS.
In BIOS > Settings > "NVMe Configuration" it said "no NVMe device found"

It seems odd that it didn't detect the NVMe drive but still detected the Windows Boot Manager that is on it.

Could the NVMe drive malfunctioning cause the computer not to be able to enter the BIOS?

I then took the NVMe drive out and put it back in the same slot and turned the computer on and the NVMe drive was detected in the BIOS. I then tried booting the computer normally and got a blue screen: "Stop Code: INACCESSIBLE BOOT DEVICE"

I then put the NVMe drive in the other m.2 slot and booted and got the same blue screen error. I then put the NVMe drive in an Insignia brand NVMe enclosure from Best Buy and connected it to a laptop, but the drive was not immediately recognized. I went to Windows Disk Management and it detects an additional disk but it says Unknown, Not Initialized and says I must initialize it before the Logical Disk Manager can access it. I am afraid to do that since I don't want to lose the data on the drive. That's where I'm at now. If it helps, the NVMe is a 1TB SK Hynix GOLD P31.

I'm trying to figure out whether it's more likely that the motherboard is malfunctioning or that it's just the NVMe drive (or both, I suppose).

Well I have a personal policy of withdrawing support when the BIOS is being refused to be updated.  

Everyone has performance hits when the BIOS is the Security issue, it's live with it and update.

It is not even noticeable and should not be on your system. Head shake.

 

So Support is withdrawn on this Topic and future topics till Bios is updated.  Good luck.

Pkshadow

Most of the bios vulnerabilities have yet to be exploited and nearly 99% require some sort of physical access to exploit it.

It was more than just the performance that made me hesitate. I read about people having functionality and stability issues as well. I didn't want to add another variable to the equation of what might be causing things not to work. It seems unlikely that bios version would be the cause of the issue, given that the hardware I'm trying to run the computer with is the same hardware that has successfully run for over 3 years up to this point, and I didn't update any drivers or anything recently.

Edited by Xfjit3k7r, 29 February 2024 - 03:46 PM.

Between F4 and F24 https://www.gigabyte.com/Motherboard/Z490-AORUS-ELITE-AC-rev-10/support#support-dl-bios There is a number that do not need direct Access as well it updates numerous Security, Checksom, Addresses Download Assistant Vulnerabilities Reported by Eclypsium Research which Gigabyte highly recommends, Updates Intel Management Engine.

 

As well when issue is Boot and Repair would it not be obvious choose to make sure the Boot is getting the Best BIOS info to actually start.

 

There is absolutely no reason not to. Sorry, is again my personal preference as well the only BSOD Kernel Expert usually recommends the same especially for AMD and for Intel Management Engine.

 

There are too many reasons why should update from the 2nd Bios release than against updating it.    All boards in the last 3yrs are meant to be updated.

 

(2of my  boards 2008, 2012 has no power on from rear i/o panel with dedicated USB Port and press the button, even then was do it as it can and should be done)