ATI Catalyst 13.1 Black Screen/ BSOD

Page 9 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Toggle sidebar Toggle sidebar
Status
Not open for further replies.
E

ezekiel2517

Honorable
Jan 24, 2013
10
0
10,510
Hello, and thanks for your help. I recently upgraded my computer to Windows 8 (a clean install), and was updating all of my drivers. Everything was going fine until I got to the drivers for my Crossfire 6870/6850 graphics cards. During the installation of the latest (13.1) catalyst drivers, my screen flashes as normal during a driver update, but then freezes on a black screen. On a hard restart I get a BSOD on atikmpag.sys. This issue also occurred on windows 7 with anything past the 12.11 drivers. I tried manually installing the drivers in safe mode, which works but still BSODs on a restart. The most progress I've made was getting to my desktop with the 13.1 drivers manually installed, but the BSOD occurred after a restart. I'm not overclocking anything. Thanks in advance.

Specs:
Windows 8
AMD Phenom II x6 1075T (stock)
Crossfire HD6870/6850
128gb Crucial M4 SSD
Asus M5A97

Current drivers:
Catalyst 12.10
All other drivers (chipset, SATA etc) all up to date
 
Sort by date Sort by votes
I don't, usually use firefox or comodo dragon but ei10 was automactically updated

 
Upvote 0 Downvote
Dear Valued Customer,

Thank you for contacting ASUS Technical Service.

We're pushing AMD. AMD is checking the case now.
Would you please use the former driver which don't have the problem? We would trace AMD about this case. Once AMD update the case, we would contact with you. Sorry for keeping you waiting.

Sorry for the trouble. Wish you a good day.

If you continue to experience issues in the future, please do not hesitate to contact us again.
Best Regards,
 
Upvote 0 Downvote
I gave up lol. Even just using crossfire on older games with 12.10, some games simply do not work with crossfire or others sort of worked.

Ordered a 7870 XT yesterday and I'm trying to get rid of my HIS 5770.
 
Upvote 0 Downvote

yea mate, so have I.
this may not get fixed people, all I can say is sorry guys I tried to help but I am out of options and all I can do is please I ask you to remember what we have been schooled

 
Upvote 0 Downvote
recently Iv bugged the AMD tech support a lot and they have given me this answer:

"Your service request : SR #{ticketno:[8200542820]} has been reviewed and updated.
Response and Service Request History:
Sadly the testers were really dragging their feet on this whole issue, arguing about who would be allocated to actually investigate and fix the issue. I personally went over with the error-reporting-contact to obtain the system, the 2 7970 cards, and walked it over to the tester's desk, so at least we have him dedicated to the project now. The down side is that there isn't a fix yet, that's what he'll be working on now, but at least now there is accountability. No excuses about no hardware, no passing the buck, we have the engineer who is working on it, and he has everything, now he just has to get it fixed. It looks like we should have this fix on the horizon, and at that point we should have a CAP for Metro Last Light for CrossFire performance, as well as patches for single-GPU systems in the 13.5 Beta. Just make sure that the Metro Last Light community is using the www.amd.com/betareport form, we need to investigate all issues, including game-specific ones, so that will definitely be a big help.
In order to update this service request, please respond, leaving the service request reference intact.
Best regards,
AMD Global Customer Care"

they may be fixing it now but keep on contacting the tech support about this issue. Only by doing that will we get their attention and have them fix this issue that has not been fixed for five months. By putting pressure on them, that will get their attention and get them to fix it. We need to give AMD the message that we are discontent and that they need to fix it. That is why I'm getting some real responses now through continuesly contacting their tech support and giving the message that we are discontent without support for us who own a motherboard with a 970 chipset.
 
Upvote 0 Downvote
I'm so happy I found this thread! Now I know I'm not the only one with the 970 chipset problem. I managed to fix it by myself a while back after building a new Computer, but I can't remember how. I had to System Restore at one point due to some unintended updates!

Looks like I'll be bugging AMD tech support to help pile on the pressure! 😛

 
Upvote 0 Downvote
My possessor heatsink fan blows across the ram and the mosfets heatsink (think they are called mosfets) the 970 chip heatsink gets no airflow, seems to be in a dead spot and dam does this chipset get hot, especially when running crossfire. I had to mount a fan blowing directly at it and it makes a big difference. next time you are messing around very lightly touch the chipset heatsink, mine is a burner.
 
Upvote 0 Downvote

yea its probably running at normal operating temperature but i'm just a bit paranoid, good if it had a thermal sensor that would really be the only way to tell, so I guess if its burns my finger its probably around 60 to 80 degrees Celsius, dont think it would be over 80 because that would not just fell to hot I think at that temperature or over would cause injury to my fingers :)
 
Upvote 0 Downvote
ccc 12.10 is no go for me as I get explorer crashes with this older driver, a lot of people did when 12.10 was released. ends up being atiumd64.dll causing this so now I'm fucked cant use any driver at all now so the only thing I can do is remove a card. what a fucking waste of money, I will think very hard in the future about buying AMD hardware and will never again buy an AMD based graphic card. welcome back to nvidia and a better physx performance PS Fuck you amd.
 
Upvote 0 Downvote
This is so sad. I recently tried to go crossfire with an Asus M5A97 LE r2.0. Caused so many problems with BSOD's and black screens I ended up taking the card out thinking "never again, AMD...." - They need to fix this shit right now.

Edit: Have you seen how many "reads" this topic has? Jesus. 😵
 
Upvote 0 Downvote
don't lose hope yet guys, 13.6 is still a brand new beta and they haven't released a stable driver past 13.4 yet so I'm guessing they're still working on this. AMD knows this thread exists I have mentioned it in my emails to them as many of you have. After they find out that the new beta still doesn't correct the problem their engies will begin working on a solution.

EDIT:
also, on the page that elroy supplied in his link it says
"Resolved issues:

Resolves HDMI Audio drop-out issues on the AMD Radeon HD Series products.
Resolves issues with the AMD Catalyst Control Center showing Audio Display messages at incorrect times."

No where does it advertise a fix for us yet, so my guess is they're waiting til the next stable release that isn't a beta driver.
 
Upvote 0 Downvote
Ok so I have been reading the thread and I had the same problem.
Windows 7
M5A97 mobo
FX6100
6770 crossfire
600w power supply
Mine worked until the most recent windows update and then I started to get the bsod. I had to re install windows first. I then installed all the updates. I installed the catalyst control center but I did a custom install. I unchecked everything except for the control center. I install the ccc because that is really all you need so that you can enable crossfire. I then went into reg edit and located enableulps and changed the value to 0. I did it in both 0000 and 0001. I then enabled crossfire in ccc. After crossfire was up and running I installed Microsoft security essentials. So far so good everything is still working! Took a few hours but atleast it's working again. If you are like me and have to have everything working or you just want to throw it away then give this a shot. Hopefully it will work for others.
 
Upvote 0 Downvote
Here's a reply I just received from AMD. I know it's been said before, but I want to keep this thread alive as it seems A LOT of people have this issue. At least they can come here for updates and information on the problem.

"This is an known issue that has been reported a few times in the 13.1-13.5 suites regarding CrossFire configurations and the 970 chipset, and is being actively investigated by the driver team. If you have tried the 13.6Beta suite at http://support.amd.com/us/kbarticles/Pages/amdcatalyst13-6winbetadriver.aspx and still have these crashes, I would recommend reverting back to the 12.11Beta suite at www.amd.com/beta as this was the last suite that was not reported to have this issue. If the installation is successful, stick with this suite while the Catalyst team is investigating this issue. You can also bookmark the 13-6 page as any patches or fixes that are released will be available on that page directly."
Click to expand...

 
Upvote 0 Downvote
Today I updated to 13.1 and give me a black screen during the install and the monitor now gives no signal... Trying to get my video/graphics card out and putting in another one hopefully works or dunno what to doo...
 
Upvote 0 Downvote
Status
Not open for further replies.

TRENDING THREADS

Latest posts

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom