Jump to content

Stuck in BIOS - Endless cycle - Can't get to home screen

The_LHIS
 Share
Posted

Hello, I am stuck in the BIOS and can't get out of it to fully boot up. To clarify, I can save and exit the BIOS, but the PC then restarts and goes right back to the BIOS, and it continues this cycle.  I don't know what happened, but I had just finished watching a youtube video, stepped away from my computer for a couple minutes, and then came back to find my computer in the BIOS. 

 

I can see my ssd boot drive and hard drive in the BIOS, as well as both sticks of RAM which show up. I have tried hard resetting the BIOS by pulling out the coin-sized battery. I have now updated to the latest version of the BIOS (2001). Neither of these things have changed anything. I've tried disabling fast boot and I have CSM enabled; this hasn't changed anything either. I haven't been able to disable secure boot though since it's greyed out (I don't know if that would make a difference). I don't have anything overclocked either.

 

I have no idea what else to do. My computer was working perfectly fine and then this happened out of nowhere. Any help would be greatly appreciated. Thanks!

 

 

Specs:

Intel Core i7-8700
ASUS Prime Z370-A
G.Skill Ripjaws DDR4-3000MHz 16GB (2 x 8GB)
ASUS GeForce GTX 1060 6GB ROG STRIX
Kingston A400 480GB SSD, Seagate BarraCuda 3TB HDD
Corsair TX550M 550W
Windows 10 64-bit
Link to comment
Share on other sites
Link to post
Share on other sites
Posted

Your ssd may have experienced some serious corruption which is preventing the boot loader from working. Try booting the windows installation drive to see if that works.

Don't ask to ask, just ask... please 🤨

sudo chmod -R 000 /*

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

... did you select your boot drive as boot device in the bios?

CPU: i7-2600K 4751MHz 1.44V (software) --> 1.47V at the back of the socket Motherboard: Asrock Z77 Extreme4 (BCLK: 103.3MHz) CPU Cooler: Noctua NH-D15 RAM: Adata XPG 2x8GB DDR3 (XMP: 2133MHz 10-11-11-30 CR2, custom: 2203MHz 10-11-10-26 CR1 tRFC:230 tREFI:14000) GPU: Asus GTX 1070 Dual (Super Jetstream vbios, +70(2025-2088MHz)/+400(8.8Gbps)) SSD: Samsung 840 Pro 256GB (main boot drive), Transcend SSD370 128GB PSU: Seasonic X-660 80+ Gold Case: Antec P110 Silent, 5 intakes 1 exhaust Monitor: AOC G2460PF 1080p 144Hz (150Hz max w/ DP, 121Hz max w/ HDMI) TN panel Keyboard: Logitech G610 Orion (Cherry MX Blue) with SteelSeries Apex M260 keycaps Mouse: BenQ Zowie FK1

 

Model: HP Omen 17 17-an110ca CPU: i7-8750H (0.125V core & cache, 50mV SA undervolt) GPU: GTX 1060 6GB Mobile (+80/+450, 1650MHz~1750MHz 0.78V~0.85V) RAM: 8+8GB DDR4-2400 18-17-17-39 2T Storage: HP EX920 1TB PCIe x4 M.2 SSD + Crucial MX500 1TB 2.5" SATA SSD, 128GB Toshiba PCIe x2 M.2 SSD (KBG30ZMV128G) gone cooking externally, 1TB Seagate 7200RPM 2.5" HDD (ST1000LM049-2GH172) left outside Monitor: 1080p 126Hz IPS G-sync

 

Desktop benching:

Cinebench R15 Single thread:168 Multi-thread: 833 

SuperPi (v1.5 from Techpowerup, PI value output) 16K: 0.100s 1M: 8.255s 32M: 7m 45.93s

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author
58 minutes ago, Sauron said:

Your ssd may have experienced some serious corruption which is preventing the boot loader from working. Try booting the windows installation drive to see if that works.

I’ve tried booting from my windows 10 installation USB but I get a compatibility error. Am I doing something wrong?

2763CAAB-9CEA-4466-A8C0-E38A01E2785A.jpeg

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author
40 minutes ago, Jurrunio said:

... did you select your boot drive as boot device in the bios?

Yes.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
9 hours ago, The_LHIS said:

I’ve tried booting from my windows 10 installation USB but I get a compatibility error. Am I doing something wrong?

 

No, that's all we needed to see. Clearly the problem isn't with your motherboard or anything that could prevent boot - the problem is your ssd. Before trying anything else it would be a good idea to clone your ssd to another drive in case it gets worse.

 

Then you could use chkdsk to attempt a repair of the drive. You should be able to do that from the installation medium, from the main screen select "advanced options" and "command prompt", then run chkdsk.

image.png.c2bd681da291cf806f77c60b2e811d2f.png

Don't ask to ask, just ask... please 🤨

sudo chmod -R 000 /*

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author
On 6/10/2019 at 4:59 AM, Sauron said:

No, that's all we needed to see. Clearly the problem isn't with your motherboard or anything that could prevent boot - the problem is your ssd. Before trying anything else it would be a good idea to clone your ssd to another drive in case it gets worse.

 

Then you could use chkdsk to attempt a repair of the drive. You should be able to do that from the installation medium, from the main screen select "advanced options" and "command prompt", then run chkdsk.

image.png.c2bd681da291cf806f77c60b2e811d2f.png

I just tried this now, and this is what I get. I’m not sure what this all means but nothing has changed.

B72CFE49-D367-4DFF-BB45-0EEE4043DBB8.jpeg

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
22 minutes ago, The_LHIS said:

I just tried this now, and this is what I get. I’m not sure what this all means but nothing has changed.

B72CFE49-D367-4DFF-BB45-0EEE4043DBB8.jpeg

It means your drive is almost certainly dead - or at least corrupted beyond repair. If you have really sensitive data on it you could try taking it to a specialized recovery company but, if you don't, just try reinstalling windows. If that doesn't work you'll need to buy a new ssd.

Don't ask to ask, just ask... please 🤨

sudo chmod -R 000 /*

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author
On 6/12/2019 at 12:12 PM, Sauron said:

It means your drive is almost certainly dead - or at least corrupted beyond repair. If you have really sensitive data on it you could try taking it to a specialized recovery company but, if you don't, just try reinstalling windows. If that doesn't work you'll need to buy a new ssd.

I ended up buying a new ssd. It sucks cause that drive was only 1 year old, but I guess that’s how it goes sometimes. 

 

Thanks for your help and quick responses!

Link to comment
Share on other sites
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing Troubleshooting

×