[SOLVED] Computer takes 30 mins to boot when D: drive is connected because of wrong GPU drivers

Mar 13, 2022
2
0
10
Some time ago i sold my 1060 and got a 3070ti, while i was waiting for the new GPU i tried putting my old Radeon HD7850 to see if it would work. To minimize problems I installed the amd drivers on the D drive, to have an easy time to uninstall them. After the Amd died i just pulled it out and waited for the 3070.

After it came i tried to fire up the computer, but it got stuck on the black screen windows logo with spinning circles. After some time and a lot of restarts i got it to boot, cleared all programs except for data off the D drive(manually & display driver uninstaller) but it didnt help. Windows just REFUSES to shutdown even after 30 mins, it takes 10 to even recognise i pressed shutdown and sometimes wont boot even after an hour in the before mentioned windows logo. The only thing that helped is disconnecting the D drive.

Is there a way to do something? I dont want to reset all on it cuz i have some school files and gameplay footage(well over 500gb).

Thanks for your time
 
Last edited by a moderator:
Solution
The GPU has nothing to do with the drive failing. Which IS failing.

Your data should ALWAYS be backed up on one or more other deices.

Is this drive still readable?
If so, copy ALL that off to some other device. Forget trying to "fix" this one.
WHatever did happen, it appears the drive now suffers a corruption that throws the file indexing routines for Windows into a fit...or, the drive could simply be failing...

I've seen some SATA drives almost lock up a NVME-booting system (boot-up lengthened from 20 sec to 5 minutes) when connected, even after quick formatting the failing drive (even quick formatting, normally a 1 second process, then took 1 minute)..

You can try reading the drive from another computer, and see if similar chaos is caused....; if so, it might cause less chaos to try recovering needed data from within a Linux based OS.
 
WHatever did happen, it appears the drive now suffers a corruption that throws the file indexing routines for Windows into a fit...or, the drive could simply be failing...

I've seen some SATA drives almost lock up a NVME-booting system (boot-up lengthened from 20 sec to 5 minutes) when connected, even after quick formatting the failing drive (even quick formatting, normally a 1 second process, then took 1 minute)..

You can try reading the drive from another computer, and see if similar chaos is caused....; if so, it might cause less chaos to try recovering needed data from within a Linux based OS.
Sadly trying from another computer really isnt an option unless i tear one up mid lecture, do you think a data recovery place would be able to reset my drive and save the video files without it costing more than a new 2 tera HDD and a few hours <Mod Edit> around tranfering data?
 
The GPU has nothing to do with the drive failing. Which IS failing.

Your data should ALWAYS be backed up on one or more other deices.

Is this drive still readable?
If so, copy ALL that off to some other device. Forget trying to "fix" this one.
 
Solution