Operating since the beginning of 2021, but currently only starts in BIOS.
Operating since the beginning of 2021, but currently only starts in BIOS.
My graphics card kept running the game engine throughout the day. I forgot to power it down before moving it to another machine, which caused it to stay on for hours. When I returned at the end of the day, the screen was black, so I powered it off by pressing the power button, thinking it was just the display. Unfortunately, the monitor sometimes behaves oddly and can go dark temporarily. In retrospect, holding that button likely wasn’t wise. After a restart, the system would only boot into BIOS occasionally, and once the error boot light appeared, it wouldn’t load Windows. I attempted several fixes—disconnecting, waiting, and even trying to flash the BIOS—but nothing worked consistently. Eventually, I tried updating the BIOS by copying a new file onto a USB stick and flashing it manually, but the screen still wouldn’t display. I also replaced the CMOS battery and changed the BIOS file to a different format, yet the issue persisted. I’m unsure if the motherboard was damaged, but I suspect something went wrong during the process. I’m considering upgrading to a better GPU, like a 3090, since my current setup is outdated. I’m hoping this wasn’t an accident and that I didn’t cause further harm. My specs include a 2080 Super, RTX 2080, 128GB RAM, and a 4K monitor. I’m still trying to figure out what happened and how to get it working properly.
You're asking for a clear breakdown of what you mean by "it won't let you into Windows." Are you referring to specific error codes or messages? It seems like you're concerned about potential damage to the SSD, possibly from powering off the PC hard. You mentioned a possible issue with the SSD and wondered if it might be recoverable by leaving it unplugged. You also referenced a link from Crucial about SSD recovery and suggested resetting the CMOS as a possible solution.
It's a samsung ssd 980 pro, it is showing up in the bios under my M2_1 slot, my boot order has hardisk set 1st which I think it right. I just try to exit the bios but it will just go back into bios, and when booted up the pc goes straight to bios instead of loading windows. I don't know if there is a way to specifically launch windows from the bios, but I haven't noticed any errors anywhere that look related to that. hmm, maybe I should look more into that though, maybe unplugging it, I could see maybe something getting messed up with the ssd, everything seems to be showing up though. EDIT: reseating and, loading bios and waiting five minutes and rebooting it didn't seem to do anything
Ahhh, after rebooting it, the system says no operating system was found. I’m thinking about disconnecting any drives without an OS and restarting again. I have another drive, so I’ll try that to see if anything happens. EDIT: I disconnected all drives except the M.2 drive that has Windows installed, and it reported it couldn’t recognize a boot device. So even though the Samsung appears, it seems the device was damaged when I turned it off.
I would consider the recommendations from Crucial, such as keeping it plugged in and resting in the BIOS for 15-30 minutes. I've also restored it by connecting only the power cable and not the SATA cable, doing the same for 15-30 minutes. If you have any extra drives, you might try installing an OS on one and checking the status of the (possibly damaged) drive.
It seems the M.2 might have been the issue. I was planning to install another SSD for the OS, but it worked fine and I managed to boot into Windows. Examining the M.2 revealed everything inside, which is reassuring since it looks like nothing was lost. Now I'm trying to figure out if I can restore it, as something about it didn't let me boot Windows through it. It feels like something was definitely damaged.
Do you know some Samsung 980 Pro models ran into issues with NVMe firmware that caused problems unless updated? Have you used Samsung Magician to check your NVMe drives? If your 980 Pro is non-functional due to outdated firmware, reach out to the manufacturer for warranty support or contact Samsung directly.
It seems you're facing a boot issue possibly due to a corrupted system file. You might need more advanced repair tools beyond basic commands like sfc /scannow.