FordGT90Concept
"I go fast!1!11!1!"
- Joined
- Oct 13, 2008
- Messages
- 26,259 (4.63/day)
- Location
- IA, USA
System Name | BY-2021 |
---|---|
Processor | AMD Ryzen 7 5800X (65w eco profile) |
Motherboard | MSI B550 Gaming Plus |
Cooling | Scythe Mugen (rev 5) |
Memory | 2 x Kingston HyperX DDR4-3200 32 GiB |
Video Card(s) | AMD Radeon RX 7900 XT |
Storage | Samsung 980 Pro, Seagate Exos X20 TB 7200 RPM |
Display(s) | Nixeus NX-EDG274K (3840x2160@144 DP) + Samsung SyncMaster 906BW (1440x900@60 HDMI-DVI) |
Case | Coolermaster HAF 932 w/ USB 3.0 5.25" bay + USB 3.2 (A+C) 3.5" bay |
Audio Device(s) | Realtek ALC1150, Micca OriGen+ |
Power Supply | Enermax Platimax 850w |
Mouse | Nixeus REVEL-X |
Keyboard | Tesoro Excalibur |
Software | Windows 10 Home 64-bit |
Benchmark Scores | Faster than the tortoise; slower than the hare. |
I was reading about PAYDAY 2 via Steam and not much else was happening/going on then suddenly, I saw this screen flash for a second:
Unfortuantely, it restarted before I read the last line.
Upon restarting, it didn't boot into Windows. It booted straight into EFI Shell. I exited out of that and noticed:
a) the boot device wasn't set to "UEFI: Windows Boot Manager" like it should have been. It was instead set to "UEFI: Hard Disk."
b) the Crucial MX100 SSD was missing from the SATA list.
I hard restarted the computer which brought the Crucial back. I restarted again to get back into EFI Shell, discovered fs2: is the Crucial SSD and did a dir list on it:
-Program Files (x86)
-temp
-Users
-Windows
Where is Program Files, PerfLogs, and ProgramData? The logical conclusion is the SSD is toast but this is new territory for me. How do I verify the SSD is toast? It has SMART I assume but what SMART reader will work outside of Windows in either EFI Shell or booted in to?
Edit: And I almost forgot the "super weird" part. I was working my server with to access the internet and look up some stuff while my computer was down. Not long after, I lost internet. I power cycled the router and tried accessing the router config page getting 404. I power cycled my NetGear switch and the config page was still getting 404. I looked at the lights on the switch and they were all flashing fast (my computer, server, and cable to router). I unplugged the cable to the router and the server and my computer lights kept flashing. I plugged it back in and unplugged my computer...the activity stopped and the server could once again access the config page/internet. No idea why but my computer (in EFI BIOS or Shell) was spamming the network.
Unfortuantely, it restarted before I read the last line.
Upon restarting, it didn't boot into Windows. It booted straight into EFI Shell. I exited out of that and noticed:
a) the boot device wasn't set to "UEFI: Windows Boot Manager" like it should have been. It was instead set to "UEFI: Hard Disk."
b) the Crucial MX100 SSD was missing from the SATA list.
I hard restarted the computer which brought the Crucial back. I restarted again to get back into EFI Shell, discovered fs2: is the Crucial SSD and did a dir list on it:
-Program Files (x86)
-temp
-Users
-Windows
Where is Program Files, PerfLogs, and ProgramData? The logical conclusion is the SSD is toast but this is new territory for me. How do I verify the SSD is toast? It has SMART I assume but what SMART reader will work outside of Windows in either EFI Shell or booted in to?
Edit: And I almost forgot the "super weird" part. I was working my server with to access the internet and look up some stuff while my computer was down. Not long after, I lost internet. I power cycled the router and tried accessing the router config page getting 404. I power cycled my NetGear switch and the config page was still getting 404. I looked at the lights on the switch and they were all flashing fast (my computer, server, and cable to router). I unplugged the cable to the router and the server and my computer lights kept flashing. I plugged it back in and unplugged my computer...the activity stopped and the server could once again access the config page/internet. No idea why but my computer (in EFI BIOS or Shell) was spamming the network.
Last edited: