Problem with PC slowing down after Windows reinstall
Problem with PC slowing down after Windows reinstall
So I think I know the problem. When I did the initial reinstall back in March, I did not disconnect all the internal drives as I did not know about those problems described in the guide. I figured that since I was erasing and formatting them it would be fine. But now it seems the 240 GB Kingston SSD is assigned as the boot drive as a result of that. Before I started the reinstall I ran either Crystal Disk Info or HD Tune Pro and saw that drive at 66% (my worst drive, as the HDD internal was 95%, and both the main internal SSD and the external HDD were 100%). So if my PC is booting from that drive, that would explain why it is running so much slower. I'm guessing there is no way to fix this and assign the main internal SSD as the boot drive?
It's connected but doesn't appear as a bootable drive in the BIOS, though it shows up elsewhere as storage. After reinstalling, I managed to finish but only after reconnecting the internal drives, and it remains slow afterward. The system is still sending no signal to my monitor again, and I've been using it all night trying to fix things, so I need to rest now. I updated my previous comment noting I started typing before seeing your reply.
I believe you ought to connect all your drives, remove every partition particularly the 66% hdd, and then attempt installation on the remaining ones.
@BKramer
Concerning benchmarks.
I’m not a benchmark user by nature. I don’t engage in stress testing either. There’s little confidence in these kinds of tools...
Mostly, I rely on utilities like Task Manager, Resource Monitor, Performance Monitor, and Process Explorer to assess system performance when needed.
I don’t feel the need to push every last bit of performance if it’s possible from the start.
I’ll definitely follow those who use benchmarking tools effectively.
= = = =
Timetable: not strictly time-dependent. The goal is to modify or install just one item at a time.
Wait until it’s stable before proceeding.
Issues could show up right away, after the next reboot, update, or even randomly.
I always want the ability to revert any change that causes trouble.
That's what I ended up doing, and the same approach I took before. I chose my preferred internal, which installed Windows onto it, but it caused the 66% drive to become the boot drive both times. My error for not knowing the proper method initially, but it seems I'm now in a difficult situation.
Thank you for the guidance. However, because of how I handled the reinstall in March, I believe a slow or failing drive might be set as the boot device, making the computer unreliable. I’m likely replacing it soon this week. Learning from this experience is important.