Installing AMD drivers = BSOD

luizsilveira

Honorable
Oct 16, 2013
23
0
10,510
Hi,

So I got this 4850 from a friend. The rest of my system is: a Dell optiplex 755 (bought refurbished), which comes with a Intel Core 2 Duo E6850 @ 3.00 Ghz, 4Gb of RAM. The new GPU is replacing the original GT 520. Since the PSU wouldn't handle it I also got a brand new XFX 450W pro.

All set and good to go. Uninstalled all drivers. When I'm running catalyst... blue screen of death and reboot. No matter what I try. It happens every time when it's "detecting devices" or something similar.

I've been looking all over the internet like crazy, and have tried the following:

a) make sure all drivers and uninstalled. Check.

b) Uninstall Daemon tools. Check.

c) find Installmanager.cfg and change WorkaroundInstall=false to true, then run setup again. Check. Although it comes back to false every time I run the install.

d) run the installer as admin. Check.

e) open the case and make sure all connections are firm, everything is plugged from the PSU. Check.

I'm trying version 13-9.

What else can I do or try? This is desperately frustrating.

Thanks.
 

luizsilveira

Honorable
Oct 16, 2013
23
0
10,510


And how would I know? It does work fine until I try to install the drivers. Right now I'm running it, with two monitors and all. But if I try to install the drivers, it crashes.

Anyway, I found out how to open the dump files. I'm not sure if they are all the same so I'll sample two of them:

111313-16130-01.dmp 13/11/2013 16:14:11 PNP_DETECTED_FATAL_ERROR 0x000000ca 00000000`0000000b fffffa80`05506080 00000000`00000001 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\111313-16130-01.dmp 2 15 7601 276.560 13/11/2013 16:14:48

111313-15693-02.dmp 13/11/2013 17:09:34 PNP_DETECTED_FATAL_ERROR 0x000000ca 00000000`0000000b fffffa80`06381510 00000000`00000001 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\111313-15693-02.dmp 2 15 7601 276.560 13/11/2013 17:10:08

Thanks.
 
Have a slight suspicion the issue lies with the motherboard. dell motherboards made in the last decade are pretty poor, had them fail frequently at the computer lab i work at while in school. If that is the windows install that came with the PC, there maybe be conflicting bloatware here as well.

Barring either of those issues, one thing to try would be disabling your antivirus for the install.
 

luizsilveira

Honorable
Oct 16, 2013
23
0
10,510
Now I have also tried installing previous versions (12.x), no joy. I turned off auto system restart to see if I could get a more detailed log, but for some reason I got no dmp file now.
 

luizsilveira

Honorable
Oct 16, 2013
23
0
10,510
Found the problem. This is the correct answer:

c) find Installmanager.cfg and change WorkaroundInstall=false to true, then run setup again. Check. Although it comes back to false every time I run the install.

However, every time I was doing that I ran the installer again. Which is stupid, because it then replaced the cfg file. The correct way is to edit the cfg file and then run SETUP.EXE from within AMD folder. Done.

Thanks for the help. Now... why does one have to do those kind of things for such an advanced driver/hardware is beyond me.
 

luizsilveira

Honorable
Oct 16, 2013
23
0
10,510
Nope.

So, making that cfg change lets all the installation process go through. It seems like it works but... it doesn't. Catalyst Control Center is not installed, and my driver is still "Microsoft Corporation WDDM 1.1".

Thanks quilciri, but turning off anti virus didn't solve the crashing.

Back to the starting point I guess.
 

luizsilveira

Honorable
Oct 16, 2013
23
0
10,510


In what sense do you mean? Because, if I search BSOD Catalyst there seems to be a whole bunch of people with similar issues. That's were I got the ideas to try a to f above.

I ran the install again and really, it seems like it installed it all bust installs nothing (with the WorkaroundInstall=true). Here's the log I get in the end:

Catalyst™ Install Manager
Installation Report
11/13/13 18:54:34


Hardware information

Name
Manufacturer Advanced Micro Devices, Inc.
Device ID 0xaa30
Vendor ID 0x1002
Class Code 0x000000
Revision ID 0x00
Subsystem ID 0xaa30
Subsystem vendor ID 0x1028
Other hardware

Existing packages
Packages for install
AMD Catalyst Install Manager
Final Status: Success
Version of Item: 8.0.915.0
Size: 20 Mbytes


Other detected devices

Error messages

I'm starting to get a bit disheartened indeed.
 

luizsilveira

Honorable
Oct 16, 2013
23
0
10,510
I realized I was downloading the latest AMD drivers, not regarding specific model. So now I have downloaded the legacy drivers (specific for the 4850 and other HD series). That's a start.

Same problem bsod though. But now when I change for WorkaroundInstall=true, the install takes much longer doing stuff. In the end I get this log:

Catalyst™ Install Manager
Installation Report
11/13/13 19:38:36


Hardware information

Name
Manufacturer Advanced Micro Devices, Inc.
Device ID 0x9442
Vendor ID 0x1002
Class Code 0x000000
Revision ID 0x00
Subsystem ID 0x0502
Subsystem vendor ID 0x1028
Other hardware

Existing packages
AMD Catalyst Install Manager

Packages for install
AMD APP SDK Runtime
Final Status: Success
Version of Item: 10.0.937.2
Size: 90 Mbytes
AMD Display Driver
Final Status: Fail
Version of Item: 8.970.100.1100
Size: 90 Mbytes
Catalyst Control Center
Final Status: Success
Version of Item: 2013.0429.2313.39747
Size: 150 Mbytes


Other detected devices


Manufacturer Advanced Micro Devices, Inc.
Device ID 0xaa30
Vendor ID 0x1002
Class Code 0x000000
Revision ID 0x00
Subsystem ID 0xaa30
Subsystem vendor ID 0x1028


Error messages

Driver Install: the driver package does not specify a hardware identifier

Edit: I was also using a HDMI converter and have read this could be a problem. So I disconnected that monitor and used a VGA converter instead, into an old monitor. Same problems.
 

luizsilveira

Honorable
Oct 16, 2013
23
0
10,510
Latest update: older driver (13-1-legacy_vista_win7_win8_64_dd_ccc) worked. With the WorkaroundInstall=true, obviously.

If I understand correctly it's roughly one year old but I'm fed up and I'll leave it at that. At least everything is working, including HDMI and the Catalyst Control Center, so I'll pretend I'm happy.

Thanks again for the help.