ATI Catalyst 13.1 Black Screen/ BSOD

[ezekiel2517]

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

 

[kickthedamcat]

AMD told me the same thing they told me months ago in one of the emails they replied to me about 13.1 "At this time this matter is being investigated. Could you please help us by creating a bug report with us? These reports are sent to the Catalyst engineers for review. Hopefully with these reports a new driver would resolve it" I received this today after complaining yesterday. they haven't fixed this from 13.1 to 13.5 beta like they said HAY HAY now there would have to be some very smart engineers there, they can fix this or recall the chip so asus recall my board and give me a nice juicy one with a 990 chip as a free replacement I wish

Lucky you, at least you got a reply.
As regards the recall - that would be nice, but to be honest I don't see it coming.

na neither do I, I seen the military version motherboard similar to the m5a97 evo but with a 990 chip looks good, just tell em to send me one of them just noticed there is more smileys not just : )

 

[Too old to worry]

AMD told me the same thing they told me months ago in one of the emails they replied to me about 13.1 "At this time this matter is being investigated. Could you please help us by creating a bug report with us? These reports are sent to the Catalyst engineers for review. Hopefully with these reports a new driver would resolve it" I received this today after complaining yesterday. they haven't fixed this from 13.1 to 13.5 beta like they said HAY HAY now there would have to be some very smart engineers there, they can fix this or recall the chip so asus recall my board and give me a nice juicy one with a 990 chip as a free replacement I wish

Lucky you, at least you got a reply.
As regards the recall - that would be nice, but to be honest I don't see it coming.

na neither do I, I seen the military version motherboard similar to the m5a97 evo but with a 990 chip looks good, just tell em to send me one of them just noticed there is more smileys not just : )

That must have been the Sabertooth 990FX. Indeed, it looks fantastic. It has a fantastic price, too (twice that of the M5A97 EVO).
Anyways, to return to the topic. I just registered on the AMD Game forums (under the same nick) and started a thread entitled 'CCC above 12.10 + AMD 970 + Crossfire = Black screen/BSOD', presenting our problem as concisely as I could. At least this should bring it to their attention, and maybe a solution will be worked out.
Honestly, I'm getting hyperactive 😉.

 

[kickthedamcat]

Good name for the thread, ill check it soon and post my problems and specks

 

[Justin Rahme]

I have a question for all of you with 970 chip! Why do you even have a crossfire setup with this chipset? It doesn't support proper crossfire setup since it doesn't support more than one x16 pcie at a time. Or am I missing something here?
You shouldn't actually benifit by crossfire on a 970 motherboard.

AMD told me the same thing they told me months ago in one of the emails they replied to me about 13.1 "At this time this matter is being investigated. Could you please help us by creating a bug report with us? These reports are sent to the Catalyst engineers for review. Hopefully with these reports a new driver would resolve it" I received this today after complaining yesterday. they haven't fixed this from 13.1 to 13.5 beta like they said HAY HAY now there would have to be some very smart engineers there, they can fix this or recall the chip so asus recall my board and give me a nice juicy one with a 990 chip as a free replacement I wish

Lucky you, at least you got a reply.
As regards the recall - that would be nice, but to be honest I don't see it coming.

na neither do I, I seen the military version motherboard similar to the m5a97 evo but with a 990 chip looks good, just tell em to send me one of them just noticed there is more smileys not just : )

That must have been the Sabertooth 990FX. Indeed, it looks fantastic. It has a fantastic price, too (twice that of the M5A97 EVO).
Anyways, to return to the topic. I just registered on the AMD Game forums (under the same nick) and started a thread entitled 'CCC above 12.10 + AMD 970 + Crossfire = Black screen/BSOD', presenting our problem as concisely as I could. At least this should bring it to their attention, and maybe a solution will be worked out.
Honestly, I'm getting hyperactive 😉.

Link?

 

[Too old to worry]

I have a question for all of you with 970 chip! Why do you even have a crossfire setup with this chipset? It doesn't support proper crossfire setup since it doesn't support more than one x16 pcie at a time. Or am I missing something here?
You shouldn't actually benifit by crossfire on a 970 motherboard.

AMD told me the same thing they told me months ago in one of the emails they replied to me about 13.1 "At this time this matter is being investigated. Could you please help us by creating a bug report with us? These reports are sent to the Catalyst engineers for review. Hopefully with these reports a new driver would resolve it" I received this today after complaining yesterday. they haven't fixed this from 13.1 to 13.5 beta like they said HAY HAY now there would have to be some very smart engineers there, they can fix this or recall the chip so asus recall my board and give me a nice juicy one with a 990 chip as a free replacement I wish

Lucky you, at least you got a reply.
As regards the recall - that would be nice, but to be honest I don't see it coming.

na neither do I, I seen the military version motherboard similar to the m5a97 evo but with a 990 chip looks good, just tell em to send me one of them just noticed there is more smileys not just : )

That must have been the Sabertooth 990FX. Indeed, it looks fantastic. It has a fantastic price, too (twice that of the M5A97 EVO).
Anyways, to return to the topic. I just registered on the AMD Game forums (under the same nick) and started a thread entitled 'CCC above 12.10 + AMD 970 + Crossfire = Black screen/BSOD', presenting our problem as concisely as I could. At least this should bring it to their attention, and maybe a solution will be worked out.
Honestly, I'm getting hyperactive 😉.

Link?

Here goes: http://forums.amd.com/game/messageview.cfm?catid=454&threadid=165661&enterthread=y

 

[antony209494]

AMD told me the same thing they told me months ago in one of the emails they replied to me about 13.1 "At this time this matter is being investigated. Could you please help us by creating a bug report with us? These reports are sent to the Catalyst engineers for review. Hopefully with these reports a new driver would resolve it" I received this today after complaining yesterday. they haven't fixed this from 13.1 to 13.5 beta like they said HAY HAY now there would have to be some very smart engineers there, they can fix this or recall the chip so asus recall my board and give me a nice juicy one with a 990 chip as a free replacement I wish

Actually they haven't fixed this from 12.11 till 13.5 beta. I don't understand why it is so hard to see what they changed from 12.10 to 12.11 and caused this problem with 970 boards...

 

[kickthedamcat]

looks like were going around in circles.
I do believe this problem is with the display driver and not ccc or other drivers it installs, some how when the dual displays are installed the chip gives out in an unusual way, maybe even a fluke incompatibility with the pci to pci bridge driver and the dual displays driver, I checked event viewer and the time the pc froze on a black screen (not froze more like dead) the event was that the pc was powered of without cleanly shutting down first (kernel power). the operating system scans drivers code in a manner of speaking and when it sees problems with injecting or other things it will shut down to protect and empty a bucket so you can get some error code and other details (blue screen), don't quote me on this lol I am horrible at explaining things and usually wrong, I don't get this blue screen, it seems every thing stops responding (even powered off in a way) hard dive light stops, no response from anything witch would make scene if the chip suddenly stopped some how, well this is how it is in my case anyway. I have had lots of problems in the past, lots of blue screens, lots of faulty hardware on older setups but nothing like this especially not from installing drivers and its suite, I remember the good old win 95 days, man you had to reinstall that bitch every second day, we have come a long way since then

 

[antony209494]

looks like were going around in circles.
I do believe this problem is with the display driver and not ccc or other drivers it installs, some how when the dual displays are installed the chip gives out in an unusual way, maybe even a fluke incompatibility with the pci to pci bridge driver and the dual displays driver, I checked event viewer and the time the pc froze on a black screen (not froze more like dead) the event was that the pc was powered of without cleanly shutting down first (kernel power). the operating system scans drivers code in a manner of speaking and when it sees problems with injecting or other things it will shut down to protect and empty a bucket so you can get some error code and other details (blue screen), don't quote me on this lol I am horrible at explaining things and usually wrong, I don't get this blue screen, it seems every thing stops responding (even powered off in a way) hard dive light stops, no response from anything witch would make scene if the chip suddenly stopped some how, well this is how it is in my case anyway. I have had lots of problems in the past, lots of blue screens, lots of faulty hardware on older setups but nothing like this especially not from installing drivers and its suite, I remember the good old win 95 days, man you had to reinstall that bitch every second day, we have come a long way since then

The problem is definitely with the display driver and specifically with crossfire because if you install with the crossfire bridge on it freezes in a black screen on AMD display driver installation. If you install with both cards installed but not the bridge it installs properly and gives you a Video TDR failure BSOD (atikmpag.sys) when enabling crossfire from CCC (or VECC if you prefer). Whatever this bug is it's happening only with 970 chipsets and catalyst past 12.10.

 

[Too old to worry]

looks like were going around in circles.
I do believe this problem is with the display driver and not ccc or other drivers it installs, some how when the dual displays are installed the chip gives out in an unusual way, maybe even a fluke incompatibility with the pci to pci bridge driver and the dual displays driver, I checked event viewer and the time the pc froze on a black screen (not froze more like dead) the event was that the pc was powered of without cleanly shutting down first (kernel power). the operating system scans drivers code in a manner of speaking and when it sees problems with injecting or other things it will shut down to protect and empty a bucket so you can get some error code and other details (blue screen), don't quote me on this lol I am horrible at explaining things and usually wrong, I don't get this blue screen, it seems every thing stops responding (even powered off in a way) hard dive light stops, no response from anything witch would make scene if the chip suddenly stopped some how, well this is how it is in my case anyway. I have had lots of problems in the past, lots of blue screens, lots of faulty hardware on older setups but nothing like this especially not from installing drivers and its suite, I remember the good old win 95 days, man you had to reinstall that bitch every second day, we have come a long way since then

The problem is definitely with the display driver and specifically with crossfire because if you install with the crossfire bridge on it freezes in a black screen on AMD display driver installation. If you install with both cards installed but not the bridge it installs properly and gives you a Video TDR failure BSOD (atikmpag.sys) when enabling crossfire from CCC (or VECC if you prefer). Whatever this bug is it's happening only with 970 chipsets and catalyst past 12.10.

@antony209494
I fully agree with your line of thought. Obviously, as I have 5450s, I cannot say anything about how a Crossfire bridge impacts the situation, but I have experienced all the other symptoms. In my opinion - as in yours - this clearly points to an incompatibility between 970 chipsets and the newer CCC display driver versions.

@kickthedamcat
We will be going around in circles, more or less, until AMD deigns to look into our problem, which I hope will happen soon.

Meanwhile, if you've visited the AMD Game forums, I've only had one 'official' response, and this informing me that I should do a few things that I have already done. Please, if you guys have an idea how to escalate the matter, let me know.

 

[antony209494]

[/quotemsg]
@antony209494
I fully agree with your line of thought. Obviously, as I have 5450s, I cannot say anything about how a Crossfire bridge impacts the situation, but I have experienced all the other symptoms. In my opinion - as in yours - this clearly points to an incompatibility between 970 chipsets and the newer CCC display driver versions.

@kickthedamcat
We will be going around in circles, more or less, until AMD deigns to look into our problem, which I hope will happen soon.

Meanwhile, if you've visited the AMD Game forums, I've only had one 'official' response, and this informing me that I should do a few things that I have already done. Please, if you guys have an idea how to escalate the matter, let me know.[/quotemsg]

When I am talking about removing the bridge I mean it's the only way to install the driver correctly because if it is attached I think the installer attempts to enable crossfire when it's finished and the black screen occurs. Either that or you have to remove one of the two cards (obviously).

About their "official response" : There is nothing we can try that we haven't already! The problem is obviously with their drivers and they'd better get to work fixing instead of ignoring it. We have been waiting almost half a year and cannot wait any longer!

 

[antony209494]

looks like were going around in circles.
I do believe this problem is with the display driver and not ccc or other drivers it installs, some how when the dual displays are installed the chip gives out in an unusual way, maybe even a fluke incompatibility with the pci to pci bridge driver and the dual displays driver, I checked event viewer and the time the pc froze on a black screen (not froze more like dead) the event was that the pc was powered of without cleanly shutting down first (kernel power). the operating system scans drivers code in a manner of speaking and when it sees problems with injecting or other things it will shut down to protect and empty a bucket so you can get some error code and other details (blue screen), don't quote me on this lol I am horrible at explaining things and usually wrong, I don't get this blue screen, it seems every thing stops responding (even powered off in a way) hard dive light stops, no response from anything witch would make scene if the chip suddenly stopped some how, well this is how it is in my case anyway. I have had lots of problems in the past, lots of blue screens, lots of faulty hardware on older setups but nothing like this especially not from installing drivers and its suite, I remember the good old win 95 days, man you had to reinstall that bitch every second day, we have come a long way since then

The problem is definitely with the display driver and specifically with crossfire because if you install with the crossfire bridge on it freezes in a black screen on AMD display driver installation. If you install with both cards installed but not the bridge it installs properly and gives you a Video TDR failure BSOD (atikmpag.sys) when enabling crossfire from CCC (or VECC if you prefer). Whatever this bug is it's happening only with 970 chipsets and catalyst past 12.10.

@antony209494
I fully agree with your line of thought. Obviously, as I have 5450s, I cannot say anything about how a Crossfire bridge impacts the situation, but I have experienced all the other symptoms. In my opinion - as in yours - this clearly points to an incompatibility between 970 chipsets and the newer CCC display driver versions.

@kickthedamcat
We will be going around in circles, more or less, until AMD deigns to look into our problem, which I hope will happen soon.

Meanwhile, if you've visited the AMD Game forums, I've only had one 'official' response, and this informing me that I should do a few things that I have already done. Please, if you guys have an idea how to escalate the matter, let me know.

When I am talking about removing the bridge I mean it's the only way to install the driver correctly because if it is attached I think the installer attempts to enable crossfire when it's finished and the black screen occurs. Either that or you have to remove one of the two cards (obviously).

 

[M3TAl]

The best way to escalate this? Simple, but hard at the same time, get media coverage. That will make AMD think twice. Get review sites like Tom's, Anand, PC Perspective, Tech Report, etc... to write an article showing how broken crossfire is on 970 chipsets.

Guarantee AMD would take notice then. They didn't do anything about frame latency and poor 7000's series crossfire performance until all the review sites beat them up over it.

So if we can somehow convince at least one of these sites to look at this issue then we have a chance.

 

[Mahisse]

Well I guess you could write to Tom's for starters. If not for getting noticed by AMD then to warn people about actually buying the motherboards with the 970 chipset if they're planning to crossfire.

 

[kickthedamcat]

I got a reply back from asus, long story short there not helping because windows 8 is not supported on the m5a97 boards and this is the first they have herd of the problem. I replied back stating that this problem happens on vista and windows 7 as well, so we will see what they say now, and I have sent them a link to this thread twice.

 

[kickthedamcat]

Well I guess you could write to Tom's for starters. If not for getting noticed by AMD then to warn people about actually buying the motherboards with the 970 chipset if they're planning to crossfire.

I think it is very important that consumers are aware of this problem, it is totally unfair that people will be buying this board not knowing that the chipset has a very serious issue. I wonder how many new customer's are purchasing this board with graphics for crossfire and are either RMA ing the cards or the board and having it sent back with a reply saying no problems were found and having to fork out a lot of money for postage, or are there people like me who purchase the board and only use one card, they purchase another down the track and only realise then that there is a serious flaw but buy that time warranty is up and RMA is out of the question. ill have to check my warranty I think it may still be in its time limit, guess you will have to get them to test with your crossfire setup if rma, new customers wont be using 12.10 they will either use the cd shipped with cards or get latest.

 

[M3TAl]

I read a Microcenter review 1-2 months ago on the m5a97 (or similar asus board) that gave it 1 star because of this particular issue. The user either returned it to Microcenter or Asus.

Ok I found the link, http://microcenter.com/product/398235/M5A97_R20_Socket_AM3_ATX_AMD_Motherboard

 

[kickthedamcat]

Dear Valued Customer,

Thank you for contacting ASUS Technical Service.

Please fill out attached feedback form.
Please do it as specific and accurate as possible.

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,
Cherry
ASUS Global Technical Support Center
Got this reply today, there is nothing I can find in this email to fill out nor is there any attachments. any one else received an email like this and filled out attached feedback form? I cant find shit.

 

[antony209494]

Got a (delayed) response from AMD telling me to try all the obvious stuff and that they are "aware" of the issues:

Thank you for contacting AMD!

I apologize for the inconvenience.

I understand you are having trouble getting your Crossfire set-up to work.

Can you kindly provide full detail system specifications so I can look into other areas that may contribute to the problem? Please provide specific details on the graphic cards with the part number and manufacturer.

What is the Power Supply Unit?

We are aware of issues with Catalyst 13.X. At this moment can you try the following guide below.

I suggest you use DriverSweeper to Analyze and clean all your AMD Display driver folder files to ensure you have a clean installation of Catalyst.



Steps:

1. Download DriverSweeper (Install it).

http://www.techspot.com/downloads/4266-driver-sweeper.html

(Make sure you filter out the bundle software, only install DriverSweeper by itself)

2. Uninstall your Current Catalyst driver. (Control Panel -> Uninstalling a program -> AMD Catalyst Install Manager -> Changes -> Express Uninstall

3. Boot into safe mode (Hold down F8 during post to get into Safe mode) and run Driver Sweeper.

4. Analyze and Delete AMD display driver folder. (Make sure to wait for DriverSweeper to complete. It will prompt you for a reboot once it completes.)

5. Reboot to normal Windows mode.

6. Install Catalyst (Display driver).

This should complete all the software troubleshooting steps. If problems persist, you are likely to have a hardware issue.

 

[arkj93]

Got a (delayed) response from AMD telling me to try all the obvious stuff and that they are "aware" of the issues:

Thank you for contacting AMD!

I apologize for the inconvenience.

I understand you are having trouble getting your Crossfire set-up to work.

Can you kindly provide full detail system specifications so I can look into other areas that may contribute to the problem? Please provide specific details on the graphic cards with the part number and manufacturer.

What is the Power Supply Unit?

We are aware of issues with Catalyst 13.X. At this moment can you try the following guide below.

I suggest you use DriverSweeper to Analyze and clean all your AMD Display driver folder files to ensure you have a clean installation of Catalyst.



Steps:

1. Download DriverSweeper (Install it).

http://www.techspot.com/downloads/4266-driver-sweeper.html

(Make sure you filter out the bundle software, only install DriverSweeper by itself)

2. Uninstall your Current Catalyst driver. (Control Panel -> Uninstalling a program -> AMD Catalyst Install Manager -> Changes -> Express Uninstall

3. Boot into safe mode (Hold down F8 during post to get into Safe mode) and run Driver Sweeper.

4. Analyze and Delete AMD display driver folder. (Make sure to wait for DriverSweeper to complete. It will prompt you for a reboot once it completes.)

5. Reboot to normal Windows mode.

6. Install Catalyst (Display driver).

This should complete all the software troubleshooting steps. If problems persist, you are likely to have a hardware issue.

Hello,

I have been following this thread since January when AMD released the Catalyst 13.1 drivers. I also have an Asus M5A97 EVO running two HD6850s in Crossfire. None of the drivers since 13.1 and including 13.1 have worked on my system. They all cause black screens or full system lockups. I have emailed AMD tech support as a few of you have and they gave me this exact same advice, which I tried to no avail. Obviously the AMD 970 chipset is the "hardware issue" that AMD is referring to in their email. I don't know why AMD has not been able to communicate effectively with the manufacturers of their motherboards but this issue infuriates me. To see that so many people on this forum and others have the exact same issue on many different operating systems/hardware setups baffles me. If anyone from AMD is monitoring this forum I think I can speak for all of us when I say that I will think twice about purchasing AMD hardware in the future. How they turned a blind-eye to people with "outdated" chipsets like the 970 SB makes me sick that even in this instant gratification internet era companies continue to fail to provide decent technical support.

Thank you all for your time and attempted solutions/troubleshooting but it appears that AMD has really dropped the ball on this one.

 

[kickthedamcat]

Got a (delayed) response from AMD telling me to try all the obvious stuff and that they are "aware" of the issues:

Thank you for contacting AMD!

I apologize for the inconvenience.

I understand you are having trouble getting your Crossfire set-up to work.

Can you kindly provide full detail system specifications so I can look into other areas that may contribute to the problem? Please provide specific details on the graphic cards with the part number and manufacturer.

What is the Power Supply Unit?

We are aware of issues with Catalyst 13.X. At this moment can you try the following guide below.

I suggest you use DriverSweeper to Analyze and clean all your AMD Display driver folder files to ensure you have a clean installation of Catalyst.



Steps:

1. Download DriverSweeper (Install it).

http://www.techspot.com/downloads/4266-driver-sweeper.html

(Make sure you filter out the bundle software, only install DriverSweeper by itself)

2. Uninstall your Current Catalyst driver. (Control Panel -> Uninstalling a program -> AMD Catalyst Install Manager -> Changes -> Express Uninstall

3. Boot into safe mode (Hold down F8 during post to get into Safe mode) and run Driver Sweeper.

4. Analyze and Delete AMD display driver folder. (Make sure to wait for DriverSweeper to complete. It will prompt you for a reboot once it completes.)

5. Reboot to normal Windows mode.

6. Install Catalyst (Display driver).

This should complete all the software troubleshooting steps. If problems persist, you are likely to have a hardware issue.

Hello,

I have been following this thread since January when AMD released the Catalyst 13.1 drivers. I also have an Asus M5A97 EVO running two HD6850s in Crossfire. None of the drivers since 13.1 and including 13.1 have worked on my system. They all cause black screens or full system lockups. I have emailed AMD tech support as a few of you have and they gave me this exact same advice, which I tried to no avail. Obviously the AMD 970 chipset is the "hardware issue" that AMD is referring to in their email. I don't know why AMD has not been able to communicate effectively with the manufacturers of their motherboards but this issue infuriates me. To see that so many people on this forum and others have the exact same issue on many different operating systems/hardware setups baffles me. If anyone from AMD is monitoring this forum I think I can speak for all of us when I say that I will think twice about purchasing AMD hardware in the future. How they turned a blind-eye to people with "outdated" chipsets like the 970 SB makes me sick that even in this instant gratification internet era companies continue to fail to provide decent technical support.

Thank you all for your time and attempted solutions/troubleshooting but it appears that AMD has really dropped the ball on this one.

If these boards are still getting sold stating that they are compatible with crossfirex then I don't think they can drop the ball not for long anyway, I don't know much about consumers rights and the law but I highly doubt a company can lawfully sell an item knowing it can not do what they specified, now us consumers have told them there is a problem and they can very easily reproduce this problem in there labs all they need is a board with a 970 chip and dual amd graphic cards.

 

[kickthedamcat]

Maybe what we should be asking is, who can actually run crossfire on these motherboards, will be interesting if there is any people who have the latest drivers running xfire on a 970 chip especially the m5a97 evo mainboard.

 

[M3TAl]

Unlikely for such people to post in here considering they have no reason to be looking into the problem.

 

[arkj93]

Yes it just seems very strange that AMD could produce every driver up to and including 12.1 with no issues for 970 chips and then suddenly the latest drivers no longer work. It seems to me like they deliberately wrote it into their code to only have support for the newest graphics processors and chipsets. If that's the case then every time they update their software then some older hardware will no longer be supported as they try to phase out obsolete chips. In the meantime though I realized through the AMD website that the 13.4 and 13.5 drivers both still use the 12.104 display driver. So for us folks who are still using the 12.1 or 12.2 drivers series we should be OK on benchmarks. Still I wish they would fix this problem, it's been almost four months for us who are suffering the wrath of the update! I have built intel/nvidia machines in the past so I would have no problem going back permanently if they cannot get it together. Still though I have spent almost 2000 usd on watercooling both of my cards as well as my cpu so getting a new mobo or even graphics cards would be an incredible waste. I was warned by people close to me that AMD has specific issues with driver support/compatibility I guess I should've listened!

 

[kickthedamcat]

GOD DAMN MOTHER ******* FIX MY **** AMD *****

 

[M3TAl]

Saying the 970 chipset is older is inaccurate. 990X/FX and 970 were released Q2 2011. It is highly unlikely there will be another chipset for the AM3+ platform or an AM based platform after AM3+.

AMD is moving to APU's only after Steamroller, meaning only the FM2 platform and whatever comes after FM2 will exist. The AM platform is near the end of the line.