GPU firmware install gone horribly wrong

luthierwnc

Distinguished
Apr 19, 2013
150
0
18,680
Hi All,

This was just one of those days. I plugged a second monitor into my GPU DVI slot and both monitors went black. I unplugged it and the original monitor stayed black.

So I unplugged both and put in the VGA cord from the mother board and it worked but I got a message that the Catalyst software was not working. Here is a list of the various components:

Dell Inspiron 660
i5 3330 B75 motherboard
8 GB RAM
128 GB SSD
1 TB HDD
Windows 7
Radeon HD 7750 GPU

That's when the real trouble started. I uninstalled the AMD software and reinstalled it. After I rebooted I got the same error message followed by a BSOD with a registry error. I disabled the auto-restart so I could read it. Another site recommended going to the safe mode page and selecting the last known good restore. That completely killed the computer so I couldn't even get back to the safe mode. I had the choice of fixing the error or starting Windows normally but that just said it couldn't fix it and looped back to the same message.

Eventually I put in the boot disk and did an image restore from a couple days ago. There wasn't much on the new SSD so other than time, I'm not out anything irreplaceable. Being a glutton for punishment I reinstalled the current AMD driver and got the same Catalyst message so I quickly uninstalled it and am using the onboard Intel HD 2500 graphics (which Catalyst doesn't automatically uninstall).

So, I'm stuck. The current driver crashes my system. It used to work fine (same driver -- I only downloaded it two weeks ago). The fan is spinning and in the device manager it said it was working properly.

Any ideas on how to go about getting happy? Thoughts and comments appreciated. sh
 
Solution
Un-install absolutely everything AMD. Run http://www.piriform.com/ccleaner/download. Re-download the driver from the AMD site (corrupted) & install reboot & try.
I did that (have a registered copy of cc) and the same thing happened. I was able to open Windows long enough to uninstall the Catalyst software but it completely crashes the system and goes back to the MSFT attempt to repair errors. It can't.

Here is the cc registry error log. This is only stuff that appeared in the hour between when I cleaned it and reinstalled the AMD drivers.

Missing Shared DLL C:\Windows\Microsoft.NET\Framework\v1.0.3705\vsavb7rt.dll HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDlls All users
Missing Shared DLL C:\Windows\Microsoft.NET\Framework\v1.0.3705\system.enterpriseservices.dll HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDlls All users
Missing Shared DLL C:\Windows\Microsoft.NET\Framework\v1.0.3705\mscorrc.dll HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDlls All users
Missing Shared DLL C:\Windows\Microsoft.NET\Framework\v1.0.3705\mscordbi.dll HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDlls All users
Missing Shared DLL C:\Windows\Microsoft.NET\Framework\v1.0.3705\mscorsec.dll HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDlls All users
Missing Shared DLL C:\Windows\Microsoft.NET\Framework\v1.0.3705\system.configuration.install.dll HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDlls All users
Missing Shared DLL C:\Windows\Microsoft.NET\Framework\v1.0.3705\microsoft.vsa.vb.codedomprocessor.dll HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDlls All users
Missing Shared DLL C:\Windows\Microsoft.NET\Framework\v1.0.3705\wminet_utils.dll HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDlls All users
Missing Shared DLL C:\Windows\Microsoft.NET\Framework\v1.0.3705\microsoft.jscript.dll HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDlls All users
Missing Shared DLL C:\Windows\Microsoft.NET\Framework\v1.0.3705\diasymreader.dll HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDlls All users
Missing Shared DLL C:\Windows\Microsoft.NET\Framework\v1.0.3705\iehost.dll HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDlls All users
Missing Shared DLL C:\Windows\Microsoft.NET\Framework\v1.0.3705\system.data.dll HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDlls All users
ActiveX/COM Issue InProcServer32\C:\Program Files (x86)\Google\Update\1.3.21.149\psmachine.dll HKCR\CLSID\{C6FDCC73-1418-46F2-AC7E-3AF1C18E0D33} HJH
ActiveX/COM Issue LocalServer32\C:\Windows\system32\igfxcfg.exe HKCR\CLSID\{A354BD60-4C0A-11d3-B561-00A0C92E6848} HJH
ActiveX/COM Issue InProcServer32\C:\Program Files\ATI Technologies\ATI.ACE\Core-Implementation\64\wbocx.ocx HKCR\CLSID\{EB2D089B-51AD-4DEA-98D3-C37A0F3479D7} HJH
ActiveX/COM Issue LocalServer32\C:\Windows\system32\igfxcfg.exe HKCR\CLSID\{EE2D6561-D63C-11D2-B561-00A0C92E6848} HJH
Missing TypeLib Reference ISearch - {47A7A4B0-2723-41BA-865E-EBBB7081A602} HKCR\Interface\{2CE4D4CF-B278-4126-AD1E-B622DA2E8339} HJH
Missing TypeLib Reference IUserHelper - {19D52A9A-379C-4720-BA00-3D396ECD24D7} HKCR\Interface\{915DA835-02FE-4953-92FA-624BDF5D85AB} HJH
Missing TypeLib Reference IiPodManagerUI - {19D52A9A-379C-4720-BA00-3D396ECD24D7} HKCR\Interface\{D775A119-EAC2-4F28-B06E-8AC16F2695DA} HJH
Unused registry key migwiz.exe HKLM\Software\Microsoft\Windows\CurrentVersion\App Paths\migwiz.exe All users
Application Paths Issue D:\Printer\Printer.exe HKCU\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Compatibility Assistant\Persisted All users
Installer Reference Issue C:\ProgramData\Microsoft\Microsoft Antimalware\Telemetry HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\Folders All users
Obsolete software key InstallShield HKLM\Software\InstallShield All users
Obsolete software key ATI HKLM\Software\ATI All users
Invalid firewall rule NetPres-In-TCP-NoScope - %SystemRoot%\system32\netproj.exe HKLM\SYSTEM\ControlSet001\services\SharedAccess\Parameters\FirewallPolicy\FirewallRules All users
Invalid firewall rule NetPres-Out-TCP-NoScope - %SystemRoot%\system32\netproj.exe HKLM\SYSTEM\ControlSet001\services\SharedAccess\Parameters\FirewallPolicy\FirewallRules All users
Invalid firewall rule NetPres-WSD-In-UDP - %SystemRoot%\system32\netproj.exe HKLM\SYSTEM\ControlSet001\services\SharedAccess\Parameters\FirewallPolicy\FirewallRules All users
Invalid firewall rule NetPres-WSD-Out-UDP - %SystemRoot%\system32\netproj.exe HKLM\SYSTEM\ControlSet001\services\SharedAccess\Parameters\FirewallPolicy\FirewallRules All users
Invalid firewall rule NetPres-In-TCP - %SystemRoot%\system32\netproj.exe HKLM\SYSTEM\ControlSet001\services\SharedAccess\Parameters\FirewallPolicy\FirewallRules All users
Invalid firewall rule NetPres-Out-TCP - %SystemRoot%\system32\netproj.exe HKLM\SYSTEM\ControlSet001\services\SharedAccess\Parameters\FirewallPolicy\FirewallRules All users
Invalid firewall rule NetPres-In-TCP-NoScope - %SystemRoot%\system32\netproj.exe HKLM\SYSTEM\ControlSet002\services\SharedAccess\Parameters\FirewallPolicy\FirewallRules All users
Invalid firewall rule NetPres-Out-TCP-NoScope - %SystemRoot%\system32\netproj.exe HKLM\SYSTEM\ControlSet002\services\SharedAccess\Parameters\FirewallPolicy\FirewallRules All users
Invalid firewall rule NetPres-WSD-In-UDP - %SystemRoot%\system32\netproj.exe HKLM\SYSTEM\ControlSet002\services\SharedAccess\Parameters\FirewallPolicy\FirewallRules All users
Invalid firewall rule NetPres-WSD-Out-UDP - %SystemRoot%\system32\netproj.exe HKLM\SYSTEM\ControlSet002\services\SharedAccess\Parameters\FirewallPolicy\FirewallRules All users
Invalid firewall rule NetPres-In-TCP - %SystemRoot%\system32\netproj.exe HKLM\SYSTEM\ControlSet002\services\SharedAccess\Parameters\FirewallPolicy\FirewallRules All users
Invalid firewall rule NetPres-Out-TCP - %SystemRoot%\system32\netproj.exe HKLM\SYSTEM\ControlSet002\services\SharedAccess\Parameters\FirewallPolicy\FirewallRules All users

The file C:\Windows\Microsoft.NET\Framework\v1.0.3705\vsavb7rt.dll is referenced as a Shared DLL and doesn't exist. These are often left behind after uninstalling software.

Solution: Delete the registry value.

The last couple sentences were ones I copied and pasted when cc explained the fix. Even the uninstall didn't get the reference to the display adapter which I uninstalled from there. It brought up the need to update the driver with a yellow triangle and exclamation point. It didn't get rid of the AMD high definition audio support either (also manually deleted). This sucker did not want to be rejected! It never asked for firewall permissions either.


From having done this a lot lately I did notice one thing irregular; the AMD download process did not ask me if I wanted to install or save. IIRC, it did before and I saved it to the desktop and scanned it before installing. I doubt AMD 's site has been hacked but in their uninstall process it does say it will get rid of everything, including the drivers, and it clearly didn't. Viruses do things like that too. It wouldn't be the end of the world to format the SSD and do a clean install. All my files are on the HDD and also on an external drive so no memories are at risk. If whatever the problem is can wreck that many registry files just by plugging in a pair of monitors, I'd rather not keep wanking around trying to save a relatively small amount of desktop building if a clean start ends all doubt.

Thanks for your comments and it is time to go to work. See you when I get home. sh

 
Thank you, The uninstall can be a pain in the ass sometimes. The AMD uninstall tool gives me an error, so I uninstall manually. I like to be current, when I should have left well enough alone.
If your reformat gives problems there is this :http://www.dban.org/download To really start over...just sayin..cheers
 
I know you have been on the edge of your seats for more news!

One problem seems to be that I can't entirely get rid of the onboard Intel HD 2500 graphics. When I install the AMD software and uninstall the onboard graphics, reboot and plug the monitors into the GPU I get nothing. Reboot again with the VGA on the motherboard I get the basic graphics on one screen. In the device manager the Intel software is out of the display adapters but there is a yellow exclamation point in the sound video and game controller section. Click on that and it will ask for new drivers. Restore those and the onboard graphics are back in the display adapter section. Both the Intel and AMD devices say they are working properly.

It stays weird. When the monitors are plugged into the motherboard, the Catalyst manager can identify them by number. I've scrounged around in the BIOS and can't find where I choose default graphics.

So, more info. Keep those idea coming! Thanks, sh
 
Sorry to have kept you waiting!

Got it all fixed. I've got a Bull Terrier. Trying to uninstall the Intel graphics is like telling her she just had her last piece of cheese. She still won't leave. However, this came down to having to repair all my .net framework 4 files after deleting the AMD files, reinstalling the latter and having both graphics drivers in the Device Manager. I tried to uninstall the Intel. It wouldn't leave either but the head-fake was long enough to trick the system into using the Radeon card.

We will reach a point where Scotty says, "Computer, run diagnostic." and it does.

Cheers, sh
 
So it would seem. For an instant the machine got confused and went to the default adapter. The AMD software does not automatically disable the Intel drivers (or the BIOS standard VGA). I did uninstalls, Driver Sweeper, and file searches. The more of them I got, the longer the screen stayed black. The Intel HD 2500 suite usually replaces the standard VGA. Right now the 2500 and the Radeon software both show in the display adapters and both say they are working.

The last issue I had to get around (overcome would be too strong a word) was that the .net framework software kept corrupting the AMD install. 3/4 of the time it would come back with some deep error in the log report but not say what it was. Then I would get the AMD warning and black SOD. I think it was on the 7forums someone said that he had to do a complete uninstall and reinstall of the framework software to get his to load. I used the repair tool from MSFT's download page and that put it right. Then reinstalled the AMD drivers. From there I uninstalled the Intel drivers and the screen came back black. I said something I won't repeat here but about a minute later, one of the screens came up. I'm using a pair of Asus V239 monitors and the second was set to DVI but had the HDMI plugged in. I reset that and it worked. However, the Intel HD 2500 reinstalled itself. At least the Radeon software got a foot in the door.

I learned a lot more about this than I'd planned but my rudimentary understanding is that without the ability to designate the graphics driver or PCI-E as the default in the BIOS, the basic drivers are always in the mix somehow. Maybe someone who knows more will refute or add to that. There are lots of tales of woe on the net about similar problems but I didn't find a step-by-step primer on the fix.

Cheers, sh