Black Screen After Installing Nvidia Ubuntu Install

Fix Frozen After Login In Ubuntu 1. Recently, I met the frozen problem after I log into Ubuntu. I searched around the solutions and summery them here. Whats the problem After boot into Ubuntu 1. RfwVWU84cnQ/hqdefault.jpg' alt='Black Screen After Installing Nvidia Ubuntu Install' title='Black Screen After Installing Nvidia Ubuntu Install' />If you are lucky, you might see mouse cursor, background wallpaper but nothing else. Solutions may work. Sincere you are in the frozen system, you can use AltCtrlF2 to get into command line interface. Then type your username and password to login. Or you can reboot your system and enter the Ubuntu recovery model then choose root Drop to root shell prompt. Vertical Mega Menu Jquery. After you get into command line interface, you may like to try the following solutions. Unlike in my Ubuntu 16. LTS flavors comparison which only included two main Ubuntu flavors Ubuntu GNOME Kubuntu, this time, Ive also added Xubuntu 16. After installing and enabling the nvidia proprietory drivers you would notice that the grub screen and the Ubuntu splash screen called Plymouth at startup and. VeE9.png' alt='Black Screen After Installing Nvidia Ubuntu Install' title='Black Screen After Installing Nvidia Ubuntu Install' />Re install Unity in Ubuntu 1. Try the following commands one by one to re install Unity desktop. Re install Graphics Card Driver in Ubuntu 1. If the first try doesnt work It happened to me, you may need to re install NVIDIA Driver. Try the following commands one by one. Dragon Ball Shin Budokai 2 Psp Iso. If it doesnt work for you It happened to me To. T, you may try the following steps sudo apt get install nvidia current. Hope you can login your Ubuntu now. But if your system hang out after install nvidia current Black screen with a blinking cursor and you have installed CUDA on your machine, you may mass up the different versions of nvidia driver. What you need to do is un installing the Ubuntus nvidia driver and install the driver from NVIDIA website. So get into the command lines interface via Ubuntu Recover Model and  try these steps. First, remove the current Nvidia graphics card driver sudo apt get remove purge nvidia Second, download Install Nvidia Driver 3. For 3. 2 bit x. 86 cd wget us. XFree. 86Linux x. NVIDIA Linux x. For 6. XFree. 86Linux x. NVIDIA Linux x. And then, chmod x NVIDIA Linux 3. NVIDIA Linux 3. Finally, I got my problem fixed. Hope it will help. This isnt an authoritative answer Ive just had this problem, sifted through the initial bogus media coverage, found a solution, and started speculating on the real cause. Heres a workaround for the problem, though this company mis diagnosed the problem it wasnt an ACL problem. This fix is opaque and comes from a third party, but it fixed the problem for me http www. Black Screen woes could affect millions on Windows Vista and XP. Note their fix is an exe and they dont tell you what it does. I appreciate that they are helping, but they should fully disclose their fix so at least advanced users can have confidence in their good intentions. Heres a better possible reason for why the problem occurred a registry key telling Windows which shell to run on login was corrupted a REGSZ key was missing a 0. Sounds somewhat plausible, but the fishy part is what caused that http www. Windows Black Screen Root Cause. My symptoms observations I ran into this problem on a Win. Windows Vista Ultimate. I log in, get a black screen, and Windows never proceeds to setting up my desktop, etc ie, Windows never launches explorer. Running the fixing tool from Prevx did solve the problem, however their diagnosis for the cause of the problem was wrong their initial hypothesis was the ACLs were incorrect and implied Windows Update patches broke it, but that was wrong. They followed up with the non null terminated string hypothesis. Before running Prevxs tool, the registry key existed, Reg. Edit visually displayed the expected value explorer. ACLs were fine.   Yet, of course, I couldnt successfully log in. My pure speculation about the cause So if the missing 0 hypothesis is correct, and if the Prevx tool deletes recreates the value in the registry key, obviously that should fix the problem. FYI look at the MSDN docs for Reg. Set. Value. Ex for a note about the lp. Data parameter needing a 0. But that doesnt explain how the value got messed up in the first place  I dont go around removing terminating zeros from REGSZ values for fun nor profit. Sounds like either random corruption, or more likely, something wanted to run something when Windows boots then incorrectly undid their change to the registry. I saw that some MS security folks suggested this could be caused by malware http blogs. Operating under that hypothesis, I ran Forefront on Wednesday using the current signatures, but it didnt report anything. That may not spot a novel virus or rootkit, of course. Another wild guess perhaps the act of installing certain classes of patches could cause the problem, due to a hypothetical bug in Windows Update. Windows Update does something on boot up to configure patches, and it looks like this happens after login but before Explorer is running. Perhaps Windows Update itself could be editing this registry key to replace the shell with another program that configures patches or options to explorer. If thats how it works which is a big guess, then maybe when WU restores the registry key value to explorer. Win. 7.   Of course, I would have expect to see a bad value for this reg key in Reg. Edit if this were the case. I didnt perhaps there were some unprintable characters in the string, or Ive empirically shot down my own wild guess. Note my problem occurred on a Windows 7 Ultimate machine that was upgraded from Vista Ultimate. Perhaps something during upgrade may have introduced some registry corruption that didnt show up until another value in the registry was changed later  BTW, to confirm the fix narrow down this fix, perhaps someone w a broken machine can reboot into Safe Mode, run Reg. Edit, delete HKEYLOCALMACHINESoftwareMicrosoftWindows NTCurrent. VersionWinlogonShell then recreate the Shell key as a REGSZ key, with the value explorer. If that works, that could help confirm the cause and allow us to give standalone instructions for a fix that we can have more confidence in as opposed to telling people to run an exe from a third party.