AMD Releases Catalyst 15.10 Beta Driversby Daniel Williams on October 14, 2015 12:30 AM EST
In a manner that appears it may be building momentum, AMD has released another new driver update. As this is a point driver release the changes aren't immense, but AMD has pushed through some stability fixes along with some other improvements to prep their drivers for some forthcoming game releases. As always these are all welcome news items.
First off there are a few notes on Ashes of the Singularity. Along with providing performance and quality optimizations there is also a fixed issue with a 'Driver has stopped responding' error showing up while playing in DirectX 12 mode. AMD does note however that there still remains issues with the game crashing on some AMD 300 series GPUs and Ashes of the Singularity may fail to launch on some 2GB cards.
For Star Wars: Battlefront high performance graphics can now be used on devices running switchable graphics. AMD is also aware of a small number of users who are experiencing crashes with GTA V on some AMD Radeon R9 390X GPUs. Some changes have been made that should resolve the issue and they will continue to monitor user feedback on the problem.
On the stability front AMD has brought fixes for a couple of TDR errors which caused a crash when toggling between minimized and maximized mode while viewing 4K YouTube content or running the Unreal Engine 4 DirectX benchmark. Additionally playback issues with both MPEG2 and intermittent playback issues in Cyberlink PowerDVD when connected to a 3D display through HDMI have both been resolved. Lastly there was a problem with driver installation halting on some configurations that is now fixed.
Those interested in reading more or installing the drivers for AMD's desktop, mobile, and integrated GPUs can find them on AMD's Catalyst beta download page.
Post Your CommentPlease log in or sign up to comment.
View All Comments
nandnandnand - Wednesday, October 14, 2015 - linkThe show must go on.
B3an - Wednesday, October 14, 2015 - linkErrors:
"has push though"
"AMD does not however"
Ryan Smith - Wednesday, October 14, 2015 - linkWhoops. Thanks for pointing that out.
weagle05 - Wednesday, October 14, 2015 - linkCalling it a point release is a weak distinction too, they are all year.month
Ryan Smith - Wednesday, October 14, 2015 - link"Point Release" is a term that has a specific meaning in the software industry, though it is originally derived from product numbering.
Reikon - Wednesday, October 14, 2015 - linkAs defined in the Wikipedia article you linked to, "The term "point release" refers to a common method of software versioning in which a major version is followed by a decimal point and a minor version. When a new minor version is released, the number after the decimal point is incremented, e.g. from 7.0 to 7.1, or from 2.4.9 to 2.4.10."
This means nothing for AMD drivers. It's Year.Month. The update going to 16.x just means it's 2016, while 15.10 to 15.11 could be a massive overhaul. You shouldn't use "point release" to dismiss an AMD driver update as minor.
Beany2013 - Wednesday, October 14, 2015 - linkFor what it's worth, I didn't know that - every day is a school day.
tamalero - Monday, October 26, 2015 - linkDidnt they stopped doing monthly releases since a year and half ago?
AS118 - Wednesday, October 14, 2015 - linkThat's cool, I guess I'll check these out. Beta drivers haven't crashed my system yet this year. Knock on wood.
medi03 - Thursday, October 15, 2015 - linkThe only time I ever had to roll back GPU driver, was with nVidia.