Hey there! I'm here to help you. What's going on?
Hey there! I'm here to help you. What's going on?
I just assembled my first PC. Used an MSI DDR4 board, 64GB RAM, and a 1TB silicon SSD. It functioned well for a while, but last night everything went wrong. The game got blocked, Windows became unresponsive, and it ended up flashing to a blue screen about gathering crash info. After a restart, it still wouldn’t boot. Now I’m stuck in BIOS > Storage, showing M.2_2 but not detected. I removed the SSD and put it back in, then swapped it to M.2_1. Still nothing. Am I losing all my game progress?

I located and modified the jbat1 pins. It seems the reset happened because it asked about my cooler again, yet it still booted into BIOS. When I start up, it appears on a black screen with a single white dash for a few seconds—possibly around 30 seconds—before launching to BIOS. I removed the GPU and battery to confirm it wasn’t faulty. Also, I reinstalled the SSD in the M.2_2 slot where it was originally, so I’ll attempt another boot there shortly.
I tried, but it didn't work. The SSD (m.2_2) isn't showing up.
I experienced a failure with my 256GB Silicon Power NVMe drive too. I noticed warnings indicating it was malfunctioning. It seems there’s a chance you might still salvage useful data after replacing the drive, depending on your choices. Often, when these NVMe units fail, they lock into read-only mode, making them unsuitable for booting or regular storage, though data extraction remains possible. Also, confirm whether your boot configuration is set to UEFI or Legacy—ideally both options should be enabled.
It was a silent power issue. Also, an NVMe 1TB drive. UEFI enabled. I didn’t make any changes; it functioned until suddenly it stopped. A critical failure window appeared. It remained stuck in blue, showing progress bar at 0% for ten minutes before I restarted. The same message reappeared, then it restarted again, still stuck at 0%, and the BIOS is the only thing visible now.
I understand, I've told you all that before. It was a long day!
It likely stayed on the “Collecting Info” screen for a long time trying to access the event log, but failed since the storage device failed or was restricted to read-only mode.