AMD Releases Catalyst 15.9.1 Beta Drivers

[btarunr]

AMD released a quick follow-up to its recent Catalyst 15.9 Beta drivers, to address a major video memory leak bug that caused the company to pull 15.9 Beta from its download servers. The new Catalyst 15.9.1 Beta drivers address that issue, and carry over the feature-set from 15.9 Beta, including optimization for Star Wars Battlefront Beta, and Fable Legends. It also addresses a bug that caused DirectX Diagnostics (DXDIAG) to not display Direct3D feature-level 12_0 from correctly displaying for Radeon GPUs that support DirectX 12, on Windows 10. Grab the driver from the links below.



DOWNLOAD: AMD Catalyst 15.9.1 Beta for Windows 10/8.1/7 64-bit | Windows 10/8.1/7 32-bit

View at TechPowerUp Main Site

 

[john_]

It didn't took them much time for this fix.

 

[RejZoR]

I bet they haven't fixed the AMD E-450 APU support... They just dropped it even though the thing isn't that old at all. And Win10 Windows Update somehow manages to still force install them and makes HW acceleration non functional.

 

[Assimilator]

http://support.amd.com/en-us/kb-articles/Pages/AMD-Catalyst-15.9-Beta-Memory-Leak.aspx

We are aware that some users are experiencing an issue in AMD Catalyst 15.9 Beta that causes all available video memory to be used whilst resizing active browser windows.

I have a more concise and accurate summary:

We don't bother testing our s**tty drivers because that's what our users, who spend hundreds of dollars on our video cards, should be doing for us, because we don't give a f**k once we have your money.

 

[jigar2speed]

I have a more concise and accurate summary:

Thats a wrong summary when you see a company follows up within 2 days.

 

[Xzibit]

Thats a wrong summary when you see a company follows up within 2 days.

He is bound to have problems when installing AMD drivers on a 970. I'd chalk that up to user error.

 

[john_]

I already knew what Assimilator's post would look like, before even looking at it.

 

[Ciric]

http://support.amd.com/en-us/kb-articles/Pages/AMD-Catalyst-15.9-Beta-Memory-Leak.aspx



I have a more concise and accurate summary:

You do know what a BETA driver is for? ...right?

If you can't accept bugs, then don't use beta drivers.

 

[Ja.KooLit]

http://support.amd.com/en-us/kb-articles/Pages/AMD-Catalyst-15.9-Beta-Memory-Leak.aspx



I have a more concise and accurate summary:

I smell fanboyism here.

Whats with all the retaliation here?

anyway, I am very happy that AMD has manage to fix it right away.

 

[Assimilator]

Thats a wrong summary when you see a company follows up within 2 days.

Proper testing and release validation is an integral part of the software development lifecycle. If AMD was doing proper testing and validation, the issue would never have appeared in the wild in the first place, period. The fact that they aren't doing that testing and validation means they're skimping on quality, and companies that skimp on quality are companies that don't give a s**t about their customers. There's a reason Microsoft's WHQL program costs money, and there's a reason why AMD has so few WHQL driver releases.

He is bound to have problems when installing AMD drivers on a 970. I'd chalk that up to user error.

Would you like a cookie for your weak trolling, mister "GTX 970 has 3.5GB memory"?

I already knew what Assimilator's post would look like, before even looking at it.

I already knew that you'd be s**tposting in this thread because you do the same in any thread where anyone says anything negative about AMD, regardless of whether it's warranted or not. It's almost like you're a fanboy unable to understand that criticism is often designed to encourage companies to up their game.

You do know what a BETA driver is for? ...right?

If you can't accept bugs, then don't use beta drivers.

A friendly reminder of this article: http://www.techpowerup.com/212724/its-now-been-over-160-days-since-a-catalyst-whql-release.html
A friendly reminder that the most recent AMD WHQL driver was released 8 weeks ago, whereas the most recent nVIDIA WHQL driver was released 1 week ago.
A friendly reminder that many people install AMD beta drivers because they don't have any other option to get working profile for their games, since AMD doesn't release WHQL drivers fast enough.

 

[Ciric]

A friendly reminder of this article: http://www.techpowerup.com/212724/its-now-been-over-160-days-since-a-catalyst-whql-release.html
A friendly reminder that the most recent AMD WHQL driver was released 8 weeks ago, whereas the most recent nVIDIA WHQL driver was released 1 week ago.
A friendly reminder that many people install AMD beta drivers because they don't have any other option to get working profile for their games, since AMD doesn't release WHQL drivers fast enough.

That doesn't change the fact that you're using a BETA driver, with all the little hickups that comes with that. -anyone with half a brain, knows to wait a couple af days after a BETA release, to see which bugs it includes.

 

[Assimilator]

That doesn't change the fact that you're using a BETA driver, with all the little hickups that comes with that. -anyone with half a brain, knows to wait a couple af days after a BETA release, to see which bugs it includes.

I guess all those guys who have been waiting months for a new driver to fix games that don't work should just keep waiting, huh. I mean it's not like anyone buys a graphics card to play games with, they just like multi-hundred-dollar paperweights.

 

[john_]

You do know what a BETA driver is for? ...right?

If you can't accept bugs, then don't use beta drivers.

He only accept bugs in Nvidia WHQL drivers. They are features.

I already knew that you'd be s**tposting in this thread because you do the same in any thread where anyone says anything negative about AMD, regardless of whether it's warranted or not. It's almost like you're a fanboy unable to understand that criticism is often designed to encourage companies to up their game.

You just described yourself here.

 

[Ciric]

I guess all those guys who have been waiting months for a new driver to fix games that don't work should just keep waiting, huh. I mean it's not like anyone buys a graphics card to play games with, they just like multi-hundred-dollar paperweights.

Not only are you're a trolling Nvidia fanboy, but you also have comprehension challenges.

 

[Legacy-ZA]

If only they showed this much enthusiasm when I owned my HD6950 when their drivers also had a memory leak... on top of that, drivers were only being released every 6-9 months... Maybe, I would still be using AMD if it wasn't for that.

Now that your ship has a few holes, now you suddenly care about your customers... miraculously. Never again red team, sorry.

 

[jigar2speed]

Proper testing and release validation is an integral part of the software development lifecycle. If AMD was doing proper testing and validation, the issue would never have appeared in the wild in the first place, period. The fact that they aren't doing that testing and validation means they're skimping on quality, and companies that skimp on quality are companies that don't give a s**t about their customers. There's a reason Microsoft's WHQL program costs money, and there's a reason why AMD has so few WHQL driver releases.

Why do you want to look like a complete ignorant Nvidia fanboy ? Where were you when Nvidia's WHQL drivers were killing Nvidia Graphic cards ? Infact Nvidia did that twice ...

 

[Mussels]

Wheres the nvidia people hating on AMD's slow drivers now?

Critical bug in a beta = fast fix.


edit: oh wait, assimilator is already here. gotta love those cherry picked arguments that serve absolutely zero purpose except to justify his personal stance on video card preferences.

 

[RCoon]

Wheres the nvidia people hating on AMD's slow drivers now?

Critical bug in a beta = fast fix.


edit: oh wait, assimilator is already here. gotta love those cherry picked arguments that serve absolutely zero purpose except to justify his personal stance on video card preferences.

AMD sucks.

Unfortunately, so does NVidia.

Matrox is the best! Outputs to 8 displays. Where is your God now?

 

[Mussels]

AMD sucks.

Unfortunately, so does NVidia.

Matrox is the best! Outputs to 8 displays. Where is your God now?

i've still got a voodoo 2 in the shed, i should play PCI fanboy.

 

[Ferrum Master]

i've still got a voodoo 2 in the shed, i should play PCI fanboy.

My Kyro II will leave that Voodoo in the dust

 

[v12dock]

Proper testing and release validation is an integral part of the software development lifecycle. If AMD was doing proper testing and validation, the issue would never have appeared in the wild in the first place, period. The fact that they aren't doing that testing and validation means they're skimping on quality, and companies that skimp on quality are companies that don't give a s**t about their customers. There's a reason Microsoft's WHQL program costs money, and there's a reason why AMD has so few WHQL driver releases.

196.75 WHQL

 

[Casecutter]

Don't have a reason to update WHQL for several months... you're not working hard enough, fix a Beta-bug in like a day and half and your not doing enough.

It sounds like the issue many of our members talked about, and AMD heard and investigate. And somehow that's not good?

 

[truth teller]

there's a reason why AMD has so few WHQL driver releases.

how does that that have anything to do with this _beta_ driver? are you expecting amd to test all product configurations for a beta release?

at least amd beta releases never break cards like nvidias whql sometimes do

https://www.youtube.com/watch?v=sRo-1VFMcbc

you got any retort on that mr knowitall?

 

[ironwolf]

Anyone here try these yet and can [hopefully] report the mem leak got plugged?

 

[Mussels]

how does that that have anything to do with this _beta_ driver? are you expecting amd to test all product configurations for a beta release?

at least amd beta releases never break cards like nvidias whql sometimes do

https://www.youtube.com/watch?v=sRo-1VFMcbc

you got any retort on that mr knowitall?

i officialy request links to the story of that burned up system, because daaaaaaayumn.