• Happy holidays, folks! Thanks to each and every one of you for being part of the Tom's Hardware community!

Question PC unplugged for + 2 years, extremly slow and stuck at loading windows 10. What is the problem, could it be a dying SSD?

Cristi_13

Distinguished
Sep 1, 2016
10
0
18,510
Hello,

I had my PC unplugged for a little more than 2 years and today I decided to plug the power cables in and power it on.
The problem now is that it only get's passed the BIOS until the windows 10 blue square logo and the circle made out of dots spinning below it. I think it keeps spinning for a long time, maybe 5+ minutes, and then goes black, nothing I can do so I shut it down again.
Now after reseting many times and the machine sets itself in 'preparing reparations' (or something like that, and expremely slow, i had to go to eat and only after coming back the thing stopped loading things) It failed and displayed a menu where I hit 'restore point' (it did ask me for password, i intruduced it and passed to the next screen) and selected one of the 2 options both from 2021. It has been running for more than 2 (''restoring files'') hours and I'm thinking i'll shut it down because I bet it's trying to do things but it cannot, just like it could not pass the windows loading screen, and it's sucking power.
It's like the pc get's to the door (w10 loading screen), but cant pass through it to the data. Maybe the SSD (SAMSUNG 840 EVO 500GB) has died?
¿What can I do in this situation?
I did remove the cmos battery, same thing. I changed the battery with an unused on (but expired) and same thing. Also I read that a PC doesnt need the battery to boot into windows so i assume this has nothing to do with it.
I can access the BIOS and the SSD drive is detected and set as a boot drive (I only have this drive)
¿Is there a solution that would make the PC run and log into windows?
If not, ¿Is there a way that I can copy all the data from the SSD to another place?

Thank you
 
First thing first, if you have info on that drive you want to try and recover, you may be able to remove it and utilize a drive caddy to try and get it. You will most likely run into access permissions from being on a different PC. For that you might be able to get around it by creating a user name/password combo that matches the old system as an additional in users for this machine. Not particularly a whole new user account sign in, but similar to where you can add name/pass to access other PC on your network type thing.

Whether you can or cannot, go and create an up to date installer USB key from MS, use it to wipe the drive and attempt to reinstall OS. If you have issues there it could be a bad drive.

You might want to check the CMOS battery. In my own dealing I haven't ever had that cause issue aside from not saving BIOS level settings. I did see a video the other day where a PC that would not start causation was that battery being dead. YMMV
 
First thing first, if you have info on that drive you want to try and recover, you may be able to remove it and utilize a drive caddy to try and get it. You will most likely run into access permissions from being on a different PC. For that you might be able to get around it by creating a user name/password combo that matches the old system as an additional in users for this machine. Not particularly a whole new user account sign in, but similar to where you can add name/pass to access other PC on your network type thing.

Whether you can or cannot, go and create an up to date installer USB key from MS, use it to wipe the drive and attempt to reinstall OS. If you have issues there it could be a bad drive.

You might want to check the CMOS battery. In my own dealing I haven't ever had that cause issue aside from not saving BIOS level settings. I did see a video the other day where a PC that would not start causation was that battery being dead. YMMV
I'd want the recovery to be the last resort in case the ssd turns out to be faulty.
I googled how to check faulty ssd through command center and ran the commands wmic diskdrive get status and it said 'OK' as well as the command wmic /namespace:\\root\wmi path MSStorageDriver_FailurePredictStatus and it returned 'FALSE' which seems to mean it's ok. ¿Does this necesarily mean the ssd is not at fault?
Also ran the command for de RAM ''mdsched.exe'', it ran it but, of course, after finishing it the PC restarted to show the results and same issue, stuck in windows loading screenm athough this time got BLUE SCREENED.
Also tried changing the sata port to another one, same issue. Dont know what else can I try to do to figure out what the problem causing this is.
 
Well, It looks like I have solved It.
I removed the gpu and cmos battery for nearly 1 hour. Placed In a new battery and turned the machine on without putting back the gpu. Same thing, super slow black screen and bla bla bla, but I waited patiently and minutes after the mouse showed up and, next to it, the classic spinning wheel. After a while the windows screen to introduce my credential showed up, super laggy and slow.
Took a long time to display icons and let alone load anything.
I intuitively guesses that it must be the SSD having difficulty reading data and i assumed freeing space would help (only 30GB were left free before doing anything). So I slowly uninstalled 200GB of games and restarted.
Everything was still slow. I managed to open Samsung Magician and ran a benchmark and the results were: (MB/s read 60, write 390; random: read 60k write 50k)
I ran the built in performance optimizer (Advance option), took a couple of hours but solved the issue New data 300+ 300+/ 50k+ 50k+. Restarts fast and all and it only has 20TBW.
Somehow, even though I dont have it connected to the internet it almost guessed the current date right.
Gotta also give props to corsair for it's pre-applied thermal paste on their aio, after pretty much 10y it's still there and works like the 1st day.
Glad i didnt have to spend any money.
Thanks for trying to help.