Win 7 Login screen to black screen w/ white cursor

dannyboy2233

Honorable
May 24, 2013
1,599
0
12,160
Hello all,
For the past four months, my desktop has been malfunctioning on login. I boot from my SSD by default, and it goes to a functioning login screen just fine. When I type in the correct password and log in, however, it goes straight to a nonresponsive black screen with a white cursor that I can control. I went into my BIOS to ensure that nothing was going wrong boot-wise, and I found out that my boot order was set to my HDD first, and my SSD was nowhere on that list- it was simply listed as "error". However, I find this hard to believe, as Windows itself loaded, and was on said SSD. I've looked around, but no one else seems to have had this specific problem. If nothing else works, I'll be trying a fresh install of Windows, and if that doesn't help then I may be forced to replace the SSD. Thanks in advance for any and all help!
Danny
 
Solution
Seems like windows explorer is having an issue running. Try hitting ctrl+alt+del then opening the task manager. Go to file then run task. This will bring up a run command. Type in "explorer.exe" without the quotes. Desktop should appear and you can run a chkdsk or sfc check to see if that create a more permanent solution.

BadAsAl

Distinguished
Did you clone another drive to the SSD before installing? If you did, try accessing the SSD from another PC using an enclosure or dock and give full access permissions to everyone (let me know if you need help with this). I have a machine with this issue and it started after I replaced the hard drive and cloned the old one. I haven't had a chance to try this fix yet as the machine is at a customer but I would love to know if it works.
 

Deeds4life

Reputable
Jan 28, 2015
85
0
4,660
Seems like windows explorer is having an issue running. Try hitting ctrl+alt+del then opening the task manager. Go to file then run task. This will bring up a run command. Type in "explorer.exe" without the quotes. Desktop should appear and you can run a chkdsk or sfc check to see if that create a more permanent solution.
 
Solution