Sunday, July 31, 2011

Solution to: BSOD - nvvsvc.exe C++ Runtime Error Can't Log in

The Problem is probably caused by:

1. Failed windows update (probably while updating either the C++ runtime library or the nvvsvc.exe or nvidia graphics driver).
2. Corrupted registry files which you can't access because of the Black Screen of Death preventing you to login.

Other indications are:
1. Can't boot-up in safe mode.
2. Can't bring up the log-in screen no matter how long you wait or how hard you click or how many times to doodle with the mouse hoping the problem just heal by itself.
3. You've tried CHKDSK hoping it's caused by Disk Error, and
4. You've tried regenerating your disk, but NOTHING WORKS.

The first method that must be employed is a "SYSTEM RESTORE" through a windows repair disk.
1. Press F8 after computer post.
2. You will see options like "Repair your computer", "Safe Mode", and etc.,. Select Repair your computer.
3. In case "Repair your computer" is not on the list, insert a Windows Repair Disk.
4. Select language and hit next.
5. Choose Recover computer through System Restore.
6. Select an earlier restore point (3 days ago or just a moment before the time you suspect the error has occurred.
7. Restart computer.
8. Problem solved.

In case you disabled (or is disabled without you knowing it though some malware or something) your "System Restore", hence no restore point is created in your/for your computer, then proceed to the next solution.
In case you have reach the point wherein you believe that there is nothing to lose by trying this solution, but only something to gain, then try this:

If you have another OS installed in the system (you have a multiboot system):
1. Log-in to your computer using another OS.
2. Locate the root directory of your computer (that disk or partition in which you installed the OS that you can't open).
3. Locate and open the "windows" folder.
4. Locate and open the "system32" folder under that "windows" folder.
5. Locate and open the "config" folder.
6. You will see a folder named "RegBack". Open it and copy (ctlr+c) its contents and paste it on the "config" folder (by now you probably are in ~windows/system32/config/RegBack, you can return to config folder by clicking back, that arrow pointing left at the upper left hand corner of the window) and overwrite anything that  requires to be overwritten.
7. Log-in to the erratic OS.
8. Voila! You are now free of that stupid error.

If you don't have any other OS, obtain a repair disk and follow this.
1. Insert a repair disk.
2. Choose a language.
3. Choose "Startup Repair".
4. Wait.
5. Select (click) Locate Driver.
6. Choose the hard disk/Partition in which your OS is installed.

Locate and open the "windows" folder.
7. Locate and open the "system32" folder under that "windows" folder.
8. Locate and open the "config" folder.
9. You will see a folder named "RegBack". Open it and copy (ctlr+c) its contents and paste it on the "config" folder (by now you probably are in ~windows/system32/config/RegBack, you can return to config folder by clicking back, that arrow pointing left at the upper left-hand corner of the window) and overwrite anything that  requires to be overwritten.
10. Log-in to the erratic OS.
11. Voila! You are now free of that stupid error.

Hope this helps.


14 comments:
Write comments
  1. Please post your comments here for me to know if the solution works for you or not.

    ReplyDelete
  2. Thank you so much! I fixed this problem following your steps.

    I used my Windows 7 DVD to run the repair mode, clicked the 'load driver' button and then went to the 'windows/system32/config/RegBack' and I copied one by one files in there but when I wanted to paste it in the config folder nothing happend, so the solution is rename every single file, like SYSTEM to SYSTEM.bak (added .bak), DEFAULT.bak, etc. After that I pasted all the files (one by one because I couldn't selec all, don't know why) from RegBack without problem, rebooted my PC and now I'm writing from it.

    Thanks a lot.

    ReplyDelete
    Replies
    1. Thanks a lot! I fixed this problem by following the last solution and rename it like you did.

      Delete
  3. i'm not getting anywhere with this. i tried a lot of solutions and i'm about to take it to a local repair PC place. any suggestions for me? I have repair disc but when it goes to read it and show you the repair options I still get a BSOD with just a cursor.

    ReplyDelete
  4. I've done on your instructions and everything turned out. But lost the design theme of win 7 and I can't get it back. Installed the patch personalization - not helped. I do not know what to do now =\
    Please help anybody! =)

    ReplyDelete
  5. Thanks a lot. I used Linux Live CD then copied files from regback folder.

    ReplyDelete
  6. This comment has been removed by a blog administrator.

    ReplyDelete
  7. This has worked ! AWESOME!!! The Regback thingie works like a charm

    ReplyDelete
  8. Yesterday I was facing nvvsvc.exe C++ Runtime Error and unable to fix this problem and i think how to fix runtime error nvvsvc.exe C++ Runtime Error, so I searched on internet for the solving of this runtime error and open this web site link. It is very informative so thanks to fix runtime error nvvsvc.exe C++ Runtime Error from my system.

    ReplyDelete
  9. Step#5 Choose Recover computer through System Restore is where I got lost.
    With my Windows 7 installation DVD, I got no errors detected and no option to click or select "Locate Drivers". Any ideas?

    ReplyDelete
  10. This file nvvsvc.exe should be in running process. And to overcome with this solution, one needs to use the computer cleaning software which used to clean the corrupt registry files from the PC efficiently. And If still the problem persists, then call on the toll-free number of AskPCTechies.

    ReplyDelete
  11. Mark Aquillo, I connected my affected HD up as an external drive on another computer and performed the copy paste of the regbak files. Worked perfectly.

    Thanks for the suggestion

    ReplyDelete
    Replies
    1. I'm glad it helped you in a way, bill. :) Cheers!

      Delete