BlackSOD crashing Explorer.exe referring msvcr80.dll after Login

[dknia]

Hi.

After a lot of searching and experimenting, I'm desperate and hope You guys can help. System specs in profile.

Problem started wit a Stop command that just flickered quickly short after the colored dots start animating in the very start of the boot process. It was a STOP: 0x0000007B. I somehow (don't remember how) managed to get one of my repair attempts to have the PC starting to the login prompt. When I press the start button, after a while i end up with a completely black screen. After a further minute or so, a crash screen comes up, complaining explorer.exe had an APPCRASH, and in the window it also refers to msvcr80.dll. This is documented in the attached pictures.

I can press C-A-D, and get task manager started. I can also start Chrome (but there is no network) and DirectoryOpus (file explorer) allowing me to access the file system. I have renamed all instances of msvcr80.dll, except for the ones that are in the directories under c:\Windows\winsxs\... and c:\Windows\Installer\$PatchCache$\... hoping to bypass the problem, but it still crashes with the same reference.

I have successfully done a fresh install of windows on another disk and also run memcheck, so the hardware seems OK.

I have no restore points to revert to.

I can not start regedit at all or a command prompt at Administrator level (normal cmd.exe is fine).

I need help on how to proceed

 

[Dsprague]

The BSOD you described in your post 0x7B is related to an inaccessible boot device the ususal causes:

Usual causes:  Hard drive, File system, Boot sequence errors, Device driver, Virus infection (in particular check the MBR)

first things first run through the hard drive diagnostics tutorial:

Hard Drive Diagnostic Procedure

next try running windows defender offline to check for a possible virus infection:

http://www.sevenforums.com/tutorials/166445-windows-defender-offline.html

 

[Jacee]

There are some ideas for trouble shooting or fixing Msvc80.dll here: How To Fix Msvcr80.dll is Missing or Not Found Errors

 

[dknia]

Thanks for the quick responses - however, I'm still stuck

Dsprague: The disk is available, as I am actually able to boot and get past the login screen and even start certain programs as described by running them from the task manager. Its the explorer.exe shell that does not come up, but crashes with the attached error messages, leaving me on the black screen. I have also already performed a virus scan, as I can actually bring the AvastUI up.

Jacee: The Msvcr80.dll is actually not missing, but is (maybe) failing. Actually, I have tried to rename all the occurrences of that file just to get past this breaking point, but to no avail. I have looked through the options in your link (I actually fund and tried that before posting here). But most are irrelevant or impossible when you have no shell (can't install stuff) and have no way of running cmd.exe in elevated /Administrator mode. If I try to run cmd.exe as administrator (from DirectoryOpus), it fails saying (translated from the Danish version, so wording may not be exact): System could not find the ?requested? environment setting".

Other good tips or advice?

 

[Jacee]

Have you read this? http://www.sevenforums.com/crash-lo...bleshooting-explorer-exe-crashing-issues.html

 

[dknia]

Jacee, thanks for the link. I had not seen it.

1, 2 and 5 all fail due to the system complaining "System could not find the ?requested? environment setting" like with other attempts mentioned above. 3 is not possible, as I have no access to the control panel and user settings, but I will try 4 once more with the download linked.

While I download and try this, other tips are welcome

 

[dknia]

Unfortunately - I can not run the setup.exe from my rudimentary BlackSOD boot . It complains like above "System could not find the ?requested? environment setting" (in Danish: "Systemet kunne ikke finde den angivne miljøindstilling").

Am I out of luck or does any of you have some other (desparate) measures I can take? If it helps, I have another disk in the same machine where I have installed a fresh W7, so I can boot that and access the disk with the sick installation.

 

[dknia]

I managed to rename the remaining msvcr80.dll files in the WinSXS-folder after doing some ownership and access right changes. After this, the system managed to boot into the apparently normal shell, albeit with a lot of error popups from applications that were missing the renamed files.

I have renamed them back, but problems are still there. First and foremost it appears that my user have lost administrator rights. I can not run eg. cmd.exe in elevated mode, and I can still not run windows installer.

I'll keep working, and hoping for input from here as well...