F5F Stay Refreshed Hardware Desktop System stopped working and installation is no longer possible

System stopped working and installation is no longer possible

System stopped working and installation is no longer possible

R
redstoneur
Member
57
11-26-2016, 10:15 AM
#1
I assembled my own PC and usually handle troubleshooting well, but I'm facing some issues now. Two days ago it started normally and then froze at the login screen. When I tried to restart, it shut down and booted into BIOS with everything appearing correctly—proper RAM and drives—but nothing loaded. I went to my parents, installed Windows via USB, but the setup crashed during the first step. Both a SATA and an NVME drive failed around the same time before the restart. After uninstalling all drives except one, the NVME was left mounted near the GPU for easier reinstall later. This time the installation succeeded, but now it crashes during setup, checking for updates and failing. When I tried to log in with my MS account, the process crashed and displayed a severe BSOD (attached). Could this be related to the motherboard or CPU? I'm trying a different drive to verify and hope I don't need to replace parts. Any suggestions would be appreciated.
R
redstoneur
11-26-2016, 10:15 AM #1

I assembled my own PC and usually handle troubleshooting well, but I'm facing some issues now. Two days ago it started normally and then froze at the login screen. When I tried to restart, it shut down and booted into BIOS with everything appearing correctly—proper RAM and drives—but nothing loaded. I went to my parents, installed Windows via USB, but the setup crashed during the first step. Both a SATA and an NVME drive failed around the same time before the restart. After uninstalling all drives except one, the NVME was left mounted near the GPU for easier reinstall later. This time the installation succeeded, but now it crashes during setup, checking for updates and failing. When I tried to log in with my MS account, the process crashed and displayed a severe BSOD (attached). Could this be related to the motherboard or CPU? I'm trying a different drive to verify and hope I don't need to replace parts. Any suggestions would be appreciated.

T
Thymusglied21
Junior Member
3
11-27-2016, 01:12 AM
#2
Consider starting with RAM, attempt to use just one stick or another kit if available
T
Thymusglied21
11-27-2016, 01:12 AM #2

Consider starting with RAM, attempt to use just one stick or another kit if available

T
TehStratosHD
Senior Member
492
11-30-2016, 09:13 AM
#3
Yes, you can connect the drives to another working PC using a USB adapter and run a diagnostic tool like CrystalDiskInfo to inspect them. Wipe the drives and attempt the process again. Also, verify your installation media—check if the ISO file and USB key are intact. If there’s an issue with the copy, consider regenerating the install media. Review the BIOS settings to ensure they’re appropriate for your system.
T
TehStratosHD
11-30-2016, 09:13 AM #3

Yes, you can connect the drives to another working PC using a USB adapter and run a diagnostic tool like CrystalDiskInfo to inspect them. Wipe the drives and attempt the process again. Also, verify your installation media—check if the ISO file and USB key are intact. If there’s an issue with the copy, consider regenerating the install media. Review the BIOS settings to ensure they’re appropriate for your system.

S
Simpl3Gaming
Junior Member
11
11-30-2016, 05:14 PM
#4
Are you being watched right now? (I don’t like those suggestions)
S
Simpl3Gaming
11-30-2016, 05:14 PM #4

Are you being watched right now? (I don’t like those suggestions)

R
Reltzy
Member
111
12-01-2016, 02:08 AM
#5
Yes even my spell and grammar checker have deserted me............ Ill edit it lol
R
Reltzy
12-01-2016, 02:08 AM #5

Yes even my spell and grammar checker have deserted me............ Ill edit it lol

E
emmylee33
Senior Member
710
12-01-2016, 08:09 AM
#6
I received my previous 64GB SSD I purchased, which was a new storage device for Windows installation. Everything functioned properly initially. Afterward, I reconnected all drives except one, which still wasn’t recognized. I’ll investigate further to see if the connection or drive is faulty. I don’t know why it worked now, but I’ll keep monitoring and update again. That particular drive was also the one I attempted to install Windows on before this—so it appeared at some point. The only missing connection right now is my soundcard because I forgot it. Updated December 6, 2025 by PWR_Fritz Added some updates
E
emmylee33
12-01-2016, 08:09 AM #6

I received my previous 64GB SSD I purchased, which was a new storage device for Windows installation. Everything functioned properly initially. Afterward, I reconnected all drives except one, which still wasn’t recognized. I’ll investigate further to see if the connection or drive is faulty. I don’t know why it worked now, but I’ll keep monitoring and update again. That particular drive was also the one I attempted to install Windows on before this—so it appeared at some point. The only missing connection right now is my soundcard because I forgot it. Updated December 6, 2025 by PWR_Fritz Added some updates

M
MyNameIsNoOne
Member
109
12-08-2016, 01:25 AM
#7
Update every drive and all hardware are back in the PC and appear again. I will now attempt to delete the 64GB drive and set up Windows on a better storage option.
M
MyNameIsNoOne
12-08-2016, 01:25 AM #7

Update every drive and all hardware are back in the PC and appear again. I will now attempt to delete the 64GB drive and set up Windows on a better storage option.

K
Kaspolman
Senior Member
434
12-09-2016, 09:40 AM
#8
Windows often shows display errors when running at resolutions above 1080p. This particular issue in Windows 10, where BSODs appeared blue (now black on newer versions), is quite similar to the one you shared. The crash message seems to point to a Hypervisor_Error. It would be helpful to retrieve dump files from that crash, as it can occur for various reasons. Visit C:\Windows\Minidump (sometimes minidumps are stored separately) and verify if any files exist. If present, return to the Windows directory and move the Minidump folder to your Downloads folder. Compress the folder and attach it to a message.
K
Kaspolman
12-09-2016, 09:40 AM #8

Windows often shows display errors when running at resolutions above 1080p. This particular issue in Windows 10, where BSODs appeared blue (now black on newer versions), is quite similar to the one you shared. The crash message seems to point to a Hypervisor_Error. It would be helpful to retrieve dump files from that crash, as it can occur for various reasons. Visit C:\Windows\Minidump (sometimes minidumps are stored separately) and verify if any files exist. If present, return to the Windows directory and move the Minidump folder to your Downloads folder. Compress the folder and attach it to a message.

C
Cleuless
Junior Member
19
12-09-2016, 02:29 PM
#9
I recently got it working on what I think is the original C drive, and everything is functioning perfectly now. It took me five hours, but it’s fixed everything. It cost me a lot of time and mental energy, but it’s done.
C
Cleuless
12-09-2016, 02:29 PM #9

I recently got it working on what I think is the original C drive, and everything is functioning perfectly now. It took me five hours, but it’s fixed everything. It cost me a lot of time and mental energy, but it’s done.