Windows not booting

[Shreyas swamy]

My windows isn't booting up. The asus symbol appears and then goes into bios. I have an asus z390 e gaming motherboard. Rtx 2060. 16gb ram. I7 9700k. I reset bios and it didn't work. I plugged in the windows usb I have and it went into repair mode. There is no reset option. The motherboard has led's to show status and the led glows green/yellow. According to manual it's a Boot problem. Please help!!

 

[WaggishOhio383]

Just a few questions I thought of that might help clarify the situation. How long have you had this computer? Is this your first boot after installing Windows or have you had it for a while? Is it possible that your hard drive has somehow come disconnected from the motherboard or power supply? Have you tried manually going into the boot menu for your motherboard and selecting where to boot from? Were there any errors last time the computer shut down or did it turn off normally?

[Haro]

3 minutes ago, WaggishOhio383 said:

Just a few questions I thought of that might help clarify the situation. How long have you had this computer? Is this your first boot after installing Windows or have you had it for a while? Is it possible that your hard drive has somehow come disconnected from the motherboard or power supply? Have you tried manually going into the boot menu for your motherboard and selecting where to boot from? Were there any errors last time the computer shut down or did it turn off normally?

That is exactly what I would say 

I would add to that as well

Does it boot after multiple attempts and then doesn't?

[George134]

I think this is a hard drive/ssd problem make sure the hard drive/ssd is plug in to the motherboard and the power supply but if you have this plugged in it is most likely something internal with the hard drive/ssd.

[Shreyas swamy]

I built it a month back. It worked perfectly for a month but then it started to crash 2 days ago when I was playing fortnite. I force shut it down as none of the keys were working. The same thing repeated and today I reinstalled my GPU driver and updated windows. I checked the wires and they are tight.i didn't try manually choosing where to boot from.

Also it today I played other games on it and it didn't crash. I ran cpu and gpu stress tests and both didn't cross 70 c. I uninstalled and reinstalled fortnite and when I was in the lobby it crashed and hasn't booted into windows since then.

 

[WaggishOhio383]

14 hours ago, Shreyas swamy said:

I built it a month back. It worked perfectly for a month but then it started to crash 2 days ago when I was playing fortnite. I force shut it down as none of the keys were working. The same thing repeated and today I reinstalled my GPU driver and updated windows. I checked the wires and they are tight.i didn't try manually choosing where to boot from.

Also it today I played other games on it and it didn't crash. I ran cpu and gpu stress tests and both didn't cross 70 c. I uninstalled and reinstalled fortnite and when I was in the lobby it crashed and hasn't booted into windows since then.

It sounds to me like something is wrong with either your Windows installation or your hard drive itself. Here's what I would do, provided you haven't activated Windows yet and you aren't worried about losing your files.

 

Plug in your Windows USB, but instead of going into repair mode, act like you are doing a fresh install. Select the custom installation option and you will get taken to a screen that shows your connected drives. If your hard drive isn't shown here, then the hard drive is probably faulty. If you are able to see your hard drive, manually delete all partitions and format the drive to remove all the files on it. You can then continue to freshly install Windows from scratch. Hopefully this should fix any issues that you were having before. Note that doing this will probably cause you to lose your Windows activation if you have activated it (though you may be able to use your activation key again. I'm not sure) and you will lose all your files unless they were saved to OneDrive of course. Unfortunately, there's not much else you can do without being able to boot your computer so you don't have many other options.

 

One other thing you could do is try dual booting Linux on your computer. If you could get Linux working, grub may allow you to boot into Windows and back up all your files. If you're interested in that option, and want to know how to do it, just let me know.

 

I know neither of these options are ideal, so if anyone knows of a better way to try and fix this that is less risky as far as the potential to lose all your files and what not, I would definitely try that first. However, I'm not sure of any other way to do it myself so the advice would have to come from someone else.

[Shreyas swamy]

I have two different drives a c drive San disk SSD and a d drive Kingston hard drive. I erased the c drive using the command prompt but after it was successful the pc didn't detect the SSD anymore. Windows is on the SSD and all my personal files are on the d drive. Now when I turn it on even with the drive it doesn't do anything and I go directly into bios. Any ideas of what to do now? 

[WaggishOhio383]

38 minutes ago, Shreyas swamy said:

I have two different drives a c drive San disk SSD and a d drive Kingston hard drive. I erased the c drive using the command prompt but after it was successful the pc didn't detect the SSD anymore. Windows is on the SSD and all my personal files are on the d drive. Now when I turn it on even with the drive it doesn't do anything and I go directly into bios. Any ideas of what to do now? 

What do you mean by your PC not recognizing the C drive anymore? If you erased your C drive then Windows isn't on it anymore. Your computer isn't doing anything because there's nothing for it to boot to. Just reinstall Windows on your SSD using the custom install setting. All of the files on your D drive will be perfectly safe.

[Shreyas swamy]

That's the thing I plug in the drive and nothing happens for a while then it goes into bios.

Ive been trying the whole day for the usb to do something. I even tried disabling fast boot up to see if the usb would be detected. But nothing happened.