OctopussWhat the hell, installing this driver completely killed my sound. I can't play anything.

if you use HDMI audio its just defaulted to something else. go set it as default again.

manofthemFwiw it picked up my Origin games along with my Steam games. I haven't messed with anything about them yet though ;)

Edit: correction... BF4 isn't showing up :confused:

Do you have a desktop short cut for BF4?

If not, make one or it's not going to pick it up ;)

:edit do a restart too

Musselsif you use HDMI audio its just defaulted to something else. go set it as default again.

Nope. It did something to my system and now after reinstalling both drivers (and going back to older beta) the sound blaster audio service keep crashing. Originally there was no sound, so I removed the sound card from device manager and let it recognize it again, but then I noticed audio on Twitch was all sorts of messed up, I reinstalled the drivers and it seemed ok, but the service crashing started afterwards :(
I guess I'll have to reinstall the entire system, because there doesn't seem to be anything I can do.

Hit4When your graphics card doesn't work for no reason (from AMD) and you've tried many useless drivers like Crimson, you will know my post its not USELESS!!!

You could have chosen more appropriate forum to register on, like 4chan.

Tried to install the "legacy" version that "allegedly" "supports" my E-450 (with HD6000 series GPU). Guess what, driver and control panel aren't even listed in the components list (with normal drivers they are listed but refuse to install). AMD, are you fucking kidding me? AMD APU powered laptop, NEVER EVER AGAIN. And I suggest everyone else to follow the same rule. Because this is the level of their commitment towards their customers. Pathetic.

I'll only be buying Intel and NVIDIA powered portable devices from now on. Excellent job, just don't cry next time why you're sinking in fucking red numbers...

RejZoRTried to install the "legacy" version that "allegedly" "supports" my E-450 (with HD6000 series GPU). Guess what, driver and control panel aren't even listed in the components list (with normal drivers they are listed but refuse to install). AMD, are you fucking kidding me? AMD APU powered laptop, NEVER EVER AGAIN. And I suggest everyone else to follow the same rule. Because this is the level of their commitment towards their customers. Pathetic.

I'll only be buying Intel and NVIDIA powered portable devices from now on. Excellent job, just don't cry next time why you're sinking in fucking red numbers...

The crimson legacy driver is still beta. Only silly people complain about bugs in beta.
But I have to agree with you about AMD policy about support for their legacy products. It's really really poor :-(

It's HD6000, they say HD6000 are supported and yet they treat it like it's Radeon X600 and they just drop it from ALL support basically over night. They didn't even move it into legacy support. They just plain dropped the support altogether. Absolutely pathetic. Like I said, AMD portable device, never again.

RejZoRIt's HD6000, they say HD6000 are supported and yet they treat it like it's Radeon X600 and they just drop it from ALL support basically over night. They didn't even move it into legacy support. They just plain dropped the support altogether. Absolutely pathetic. Like I said, AMD portable device, never again.

15.11 works OK with my 6970....not much to write home about though, seems like the GUI got an update and not much else....

Here is the link I used.......
www2.ati.com/drivers/beta/radeon-crimson-15.11-ni-eg-64bit-with-dotnet45-win10-win8.1-win7.exe

btw is anyone having performance issues?
Upgraded my Monitor again (VE248H) and installed this set at the same time, now Panzer Corps is laggy as hell, plus the sound is cutting out.

Also fonts appear slightly fuzzy and washed out on the desktop.

It's the fact this is APU and they give like zero fucks about it. Discrete graphic cards are fine. And even then it's a bit of a dick move to toss out architecture that is technically still used for "current" gen cards (lower end ones). Yes, even HD7000 and HD6000 series. HD7000 is GCN for crying out loud!

RejZoRIt's the fact this is APU and they give like zero fucks about it. Discrete graphic cards are fine. And even then it's a bit of a dick move to toss out architecture that is technically still used for "current" gen cards (lower end ones). Yes, even HD7000 and HD6000 series. HD7000 is GCN for crying out loud!

Both APU & discrete 6xxx have support, did you even look at the link I posted?

There is a Crimson driver for legacy products only it's a Beta( what AMD driver isn't?) Scroll down the page
support.amd.com/en-us/download/desktop/legacy?product=legacy3&os=Windows+10+-+64

Beta just means it's not WHQL signed, nothing else. There is no such thing as excuse "it's only a beta" because all the betas NEVER really changed or gained any actual fixes when they stopped being "beta"...

RejZoRBeta just means it's not WHQL signed, nothing else. There is no such thing as excuse "it's only a beta" because all the betas NEVER really changed or gained any actual fixes when they stopped being "beta"...

In W10 Beta means the driver doesn't meet WDDM 2.0 requirements laid down by Microsoft. (supported features iirc). U can find the info on MSDN.

RejZoRBeta just means it's not WHQL signed, nothing else. There is no such thing as excuse "it's only a beta" because all the betas NEVER really changed or gained any actual fixes when they stopped being "beta"...

Pill MonsterIn W10 Beta means the driver doesn't meet WDDM 2.0 requirements laid down by Microsoft. (supported features iirc). U can find the info on MSDN.

Neither of you are actually correct. There are beta drivers that are WHQL signed. I had a discussion with a mod the other day about that because as it turns out there are several betas where some of them are WHQL signed and others aren't. Also, beta drivers have supported WDDM 2.0 since 15.7.

For what it's worth, I bought my first 6870 back in October of 2010, it's now November of 2015. From my perspective, 5 years is a good stretch of support. I understand why @RejZoR is pissed off. I would be pissed off too if my graphics card wasn't supported anymore after just a year or so but, the E-450 was released 11 months after my 6870 was, August of 2011, so AMD had supported it for what? 3 and 1/2 years since release? For a cheap APU, that's not too bad. It's like saying, "I bought a 6870 a year ago, I'm so fucking pissed off that support was dropped on my 5 year old GPU that I just bought." So while I understand why your pissed off, just try to understand the opposite end: The APU is old, it's cheap, and in comparison to all their other products already owned by consumers, is a drop in the bucket. No offense but, I'm getting tired of hearing you whine about your E-450 almost on a weekly basis because support was dropped from low-end hardware that was released 4 years ago. It's not like it was released in 2011 with support dropped a year later.

and while support may have been dropped, the older drivers still work. the new ones are not likely to have new features for you anyway.

AquinusNeither of you are actually correct. There are beta drivers that are WHQL signed. I had a discussion with a mod the other day about that because as it turns out there are several betas where some of them are WHQL signed and others aren't. Also, beta drivers have supported WDDM 2.0 since 15.7.

Beta drivers are not WHQL signed. They're signed with an SDK test sig provided by MS for developers, it's not the same as whql.
This is because starting with W10 MS no longer allows any unsigned drivers at all...even for testing...

Pill MonsterBeta drivers are not WHQL signed. They're signed with an SDK test sig provided by MS for developers, it's not the same as whql.
This is because starting with W10 MS no longer allows any unsigned drivers at all...even for testing...

Pardon my ignorance but, then maybe you can explain why several people have said that they've had Windows 10 update their GPU drivers on them to a beta version? If by your logic that WHQL signed drivers are different from drivers with a testing signature, people shouldn't get beta drivers from Windows update if they're not WHQL signed. I personally haven't experienced this as I have driver updates from Windows disabled and I keep up with my GPU drivers religiously but, other have said this.

I would personally test this but, the last time I installed Crimson drivers I had to wait 25 minutes. I don't feel like reverting to an older beta just to see what the device manager says just to wait another 25 minutes to install the stupid drivers again.

Edit: I'm not saying all beta drivers are WHQL signed, I'm saying that some of them might be judging from what others have said on the forums. Once again, it requires investigation and I don't know for a fact myself.

Edit 2: @RCoon said it auto updated him to latest drivers. Here is the quote from the 15.11.1 thread.

RCoonThat's odd. After wierd resolution bugs I took a look at Catalyst and noticed it had downloaded this new 15.11.1 driver and installed it.

EDIT: A quick check of the AMD forums confirms this. Windows 10 does occasionally sign and install AMD Catalyst Beta drivers.

Musselsand while support may have been dropped, the older drivers still work. the new ones are not likely to have new features for you anyway.

I would normally agree but i cannot with the case with the AMD's 450 APU as it seems very anti flash now meaning watching video's do not work very well at all.

AsRockI would normally agree but i cannot with the case with the AMD's 450 APU as it seems very anti flash now meaning watching video's do not work very well at all.

...yeah, it also has a whopping 80 shaders. My Radeon 3650 has twice as many and struggles with 1080p output now. Simply put, the E-450 is seriously under powered and UVD2 very well might not support some of the more advanced features that have been added to flash. All in all, remember that your complaining about one of AMDs slowest (and oldest,) APUs. Remember, less than 100 GFlops of single precision GPU compute is a very weak iGPU.

All it takes is video encoded with a high profile to make it twice as hard to decode. It's not just drivers, it's the format of video and the level of encoding that's used. UVD2 and an underpowered iGPU simply might not be enough and newer software probably just makes matters worse.

AquinusPardon my ignorance but, then maybe you can explain why several people have said that they've had Windows 10 update their GPU drivers on them to a beta version? If by your logic that WHQL signed drivers are different from drivers with a testing signature, people shouldn't get beta drivers from Windows update if they're not WHQL signed. I personally haven't experienced this as I have driver updates from Windows disabled and I keep up with my GPU drivers religiously but, other have said this.

I don't know why but tbh I can't really see how that matters, do WU drivers have to be WHQL in W10? I dunno....first I've heard.. But WHQL drivers are listed as WHQL on AMD's site...Beta are listed as Beta..

It's not my logic btw, MS published this info during the beta testing stage. I'll see if I can find a link but you could look kit up youself on MSDN. Might even be TN.... I forget. It's a full page article anyway.

Wagner over at G3D modded some W10 drivers to get VSR working for Tahiti, even with testsigning enabled they wouldn't install on some systems with W10.... Ran fine on W7 though.
I happened to run across the MSDN article about 2 days beforehand..... he had to get them signed.

AquinusI would personally test this but, the last time I installed Crimson drivers I had to wait 25 minutes. I don't feel like reverting to an older beta just to see what the device manager says just to wait another 25 minutes to install the stupid drivers again.

Edit: I'm not saying all beta drivers are WHQL signed, I'm saying that some of them might be judging from what others have said on the forums. Once again, it requires investigation and I don't know for a fact myself.

Edit 2: @RCoon said it auto updated him to latest drivers. Here is the quote from the 15.11.1 thread.

I don't know what the exact differences are between the beta and whql sets, but in the Direct3D library it says certain WDDM features must be supported to pass WHQL.
That's my understanding....I kinda lost interest after frying my 7950. 0_o

Hmmm pretty big coincedence AMD dropping support right when a new OS, and new DX version comes out.... didn't they do that with the 59xx when DX11 was released?


P.S. after reinstalling Visual C updates, my lag went away.

Pill MonsterI don't know why but tbh I can't really see how that matters, do WU drivers have to be WHQL in W10? I dunno....first I've heard.. But WHQL drivers are listed as WHQL on AMD's site...Beta are listed as Beta..

Beta doesn't mean it can't be signed by WHQL.
msdn.microsoft.com/en-us/library/windows/hardware/ff553976(v=vs.85).aspx

Driver packages that pass Windows Hardware Certification Kit (HCK) testing can be digitally-signed by WHQL. If your driver package is digitally-signed by WHQL, it can be distributed through the Windows Update program or other Microsoft-supported distribution mechanisms.

Mix that with @RCoon getting a beta driver from Windows Update and you have your answer. I think to clarify, non-beta drivers are always WHQL signed whereas betas aren't always but sometimes are. Beta doesn't imply that it's not signed by WHQL though. At least that is what it's looking like from the 10 minutes of Googling I've done.

Aquinus...yeah, it also has a whopping 80 shaders. My Radeon 3650 has twice as many and struggles with 1080p output now. Simply put, the E-450 is seriously under powered and UVD2 very well might not support some of the more advanced features that have been added to flash. All in all, remember that your complaining about one of AMDs slowest (and oldest,) APUs. Remember, less than 100 GFlops of single precision GPU compute is a very weak iGPU.

All it takes is video encoded with a high profile to make it twice as hard to decode. It's not just drivers, it's the format of video and the level of encoding that's used. UVD2 and an underpowered iGPU simply might not be enough and newer software probably just makes matters worse.

So the real question is why did it perfectly play video's before ?, like come on video's have not just become more detailed or any thing.

Some one broke it and no one wants to fix it, stupid bs throwing away good tech as they just want to you to buy some thing else no wounder were having land fill problems.

AsRockSo the real question is why did it perfectly play video's before ?, like come on video's have not just become more detailed or any thing.

No but encoding video at a higher h.264 profile requires more compute by the hardware to decode it, even if quality remains the same it could be because of how the video needs to be decoded between different profiles. The benefit of this is no loss in IQ but results (usually,) in a smaller file.

I hope I'm the only one to post this experience. AMD issued a major upgrade on Nov. 24 called Crimson. I don't pay any attention to these things, but when I turned on my computer this morning, an AMD window appeared, announcing an upgrade was ready to install. I installed it. When it finished, it had knocked out all four of my computer monitors. No buttons, or restarts did anything but return black monitor screens. If you have Radeon graphics cards (I have 2 XFX R9 280X), beware of what may be in store for you if you download the upgrade immediately. It seems too early to know if my experience was a quirk. This is my first post. If I don't receive any help, I hope I can help someone from losing all of their day today the way I've lost mine.

AquinusBeta doesn't mean it can't be signed by WHQL.
msdn.microsoft.com/en-us/library/windows/hardware/ff553976(v=vs.85).aspx

Mix that with @RCoon getting a beta driver from Windows Update and you have your answer. I think to clarify, non-beta drivers are always WHQL signed whereas betas aren't always but sometimes are. Beta doesn't imply that it's not signed by WHQL though. At least that is what it's looking like from the 10 minutes of Googling I've done.

On the 2nd point I'm not sure we're talking about the same thing, off the top of my head all the drivers are signed by MS WHQL, some as whql and some as beta...
WHQL is the part of MS which does the certification.... if u get me. I'd have to check so don't quote me....


Also earlier I said the beta's are signed by an SDK cert, but that may be incorrect, iirc unsigned drivers use the temp SDK cert...... Beta's are properly signed hence my comment above....




***Edit, after rereading everything I've updated my post....I get the feeling we're saying the same thing in different ways....

To clarify, yes Beta and WHQL are whql signed....but not "WHQL passed"

Afaik non beta means non signed, which means an SDK cert , Beta= signed by Windows Hardware Quality Laboratories but doesn't meet the "WHQL", sig.... (I think this is an OEM requirement).


Does that make sense? :p

PS. - what type of developer are you? I assumed software so figured you'd know this stuff, prob better than me.... Are u doing web development?

I appreciate very much your response and your willingness to help. I couldn't ask for more. But as I said, "I don't pay attention to these things," meaning beta material I never touch. I'd have to search for the meaning of WHQL. So no, while I'm sure your statement is loaded with useful content, I am only a user, who has lost the use of my computer because AMD dropped a download on it that was a bomb. I just went along, and so far I've lost a whole day in futility. Inasmuch as this download is new, I'm hoping that others will read of my experience before they do their downloads, as I suspect thousands will be doing over the weekend There is no need for anyone to be innocently subjected to such a disaster.

@Aquinus I don't know how AMD drivers ever get past Beta stage..this is what an average bug list looks like on release...

You have to admit it's pretty long....many are standard issue. Like the TDR error for example,, every release without fail has a TDR bug.


Resolved Issues:

• [57198] GTA V - game crashes with a TDR error
• [59298] Final Fantasy XIV: Heavensward - game crashes when run in DirectX® 11 mode on some AMD Radeon™ R9 390x series products
• [76921] The AMD Radeon Settings application will use the system default browser when launching web content
• [77703] A crackling noise is heard when running a 3D application in AMD Crossfire™ mode with Vsync enabled
• [78455] Autodesk Max 2016 - A crash may be experienced when launching the application on some AMD Radeon™ products
• [78465] Prepar3D® - A TDR error may be experienced when launching the application on some AMD Radeon™ R9 200 and AMD Radeon™ R9 300 series products
• [80838] A TDR error may be experienced when playing fullscreen video using the Windows® 10 Movies & TV app on some laptops with AMD processors and GPU's
• [80840] Assassin's Creed Syndicate - Poor scaling may be experienced when launching the game in AMD Crossfire™ mode
• [80939] Secondary adapter may display error code 43 when enabling/disabling AMD Crossfire™
• [81499] AMD Freesync™ does not function on some Intel + AMD laptop systems under Windows® 7 and Windows® 8.1
• [81531] Assassin's Creed Syndicate - Flickering may be observed on rain drops that fall on in game characters
• [81593] A BSOD error may be encountered when launching Bluray / Windows Media Player with a wireless display
• [81790] Skype - The system may hang when connecting to a 1080p video call
• [81827] Tom Clancy's Rainbow Six Siege - Random corruption may be experienced in-game
• [99999] AMD Freesync™ does not function if a Youtube video is playing alongside a 3D application

Issues Resolved since AMD Catalyst 15.7.1 and included in this driver

• [58233] Ashes of the Singularity™ may fail to launch on some GPUs with 2GB Video Memory.
• [58435] Driver installation may halt on some configurations
• [58450] Some BENQ 144hz Freesync™ monitors may lose the signal while uninstalling the driver
• [58485] Anti-Aliasing settings not being retained after changes are applied
• [58495] DiRT Rally™ crashes during gameplay and benchmarking when launched in DirectX® 11 mode on some BENQ 144HZ Freesync monitors
• [58646] Assassin's Creed® Unity may experience minor frame stutter when AMD CrossFire™ mode is enabled
• [58677] World of Warships may crash on some AMD Radeon HD5000 and HD6000 series products
• [58781] The DirectX® Diagnostic tool does not report DirectX® 12 available on supported products
• [58800] Dragon Age: Inquisition may crash if launched in Mantle mode
• [59081] The AMD Catalyst Control Center 'update' option fails to download the latest driver
• [59403] Ashes of the Singularity™ ‐ A 'Driver has stopped responding' error may be experienced in DirectX® 12 mode
• [59474] Diablo 3 crashes in the Act 2 Desolate Sands area of the game
• [76924] A TDR error may be experienced while toggling between minimized and maximized mode while viewing 4K YouTube content
• [76930] Intermittent playback issues with Cyberlink PowerDVD when connecting to a 3D display with an HDMI™ cable
• [77073] Star Wars™: Battlefront is able to use high performance graphics when launched on mobile devices with switchable graphics
• [77176] A TDR error is experienced when launching Star Wars™: Battlefront while a You Tube video plays in the background
• [77255] The secondary graphics adapter is missing in the Device Manager and the AMD Catalyst™ Control Center after installation of the driver
• [77754] A TDR error or crash is experienced when running the Unreal Engine 4 DirectX® benchmark
• [77786] Video playback of MPEG2 video fails with a playback error/error code message
• [77970] Ashes of the Singularity™ may crash on some AMD 300 series GPUs
• [78654] An error may be experienced when installing the latest graphics driver package on some AMD Radeon™ R9 380 series products
• [79577] The Intel graphics is flagged in an error state in the Device Manager in systems with switchable graphics
• [79796] The Oculus runtime may crash on launch
• [419871] BSOD observed when performing an express uninstall of the display driver in 4K resolution
• [421165] Battlefield™ Hardline becomes unresponsive after toggling the in-game Vsync option.
• [421444] Transcoded clips may fail to play on some Drag and Drop devices
• [421570] Audio driver is banged out for non-primary ASIC after enabling CF and rebooting system
• [422056] 3DMark Farandole may crash when AMD Mantle is selected from the test suite
• [422249] A ‘missing Dll’ error message may be experienced while doing an express uninstall of the current driver
• [422249] DLL missing popup message may be encountered when performing an express uninstall of the display driver.
• [422261] Mantle-based application may crash when system is woken from sleep mode
• [422273] A crash may be experienced on some AMD Radeon™ R9 300 series products while running the Unigene benchmark
• [422291] Battlefield™ 4 may crash if run in Mantle mode with AMD Crossfire™ enabled
• [422342] Cyberlink PowerDVD plays 3D content in 2D mode
• [422621] With quad AMD CrossFire™ mode enabled, TDR or blank display occurs when launching DirectX® 9 application in full screen
• [422671] Flickering corruption may occur in Dirt Rally™ with Advanced Blending enabled
• [422674] Corruption may occur in DiRT Rally™ with CMAA enabled with Portrait SLS and AMD CrossFire™ mode enabled
• [422675] Intermittent BSOD occurs when launching a race in Dirt Rally™
• [422797] Display profiles are not retained after driver upgrade from 14.502 to 15.20
• [422800] Some “Kaveri” APU-based systems may experience minor performance drop on PCMark8® video_group_chat & Casual Gaming tests
• [422806] Battlefield™ Hardline crashes on pressing Ctrl+Alt+Del while running in AMD Mantle mode
• [422853] Some systems experience a minor performance drop from 15.15 to 15.20 in The Witcher 3: Wild Hunt with HairWorks enabled
• [423759] Unable to apply Fill mode in Eyefinity if 2560x1600 and 2560x1440 resolutions are used together
• [423924] Unable to create an Eyefinity SLS if one of the displays is a MST display device
• [425417] Windows 10 driver installation may halt on some systems with an AMD 990FX chipset and AMD CrossFire™ enabled.
• [425432] Some BENQ 144hz Freesync monitors may lose the signal while uninstalling the driver
• [425484] DiRT Rally™ crashes during gameplay and benchmarking when launched in DirectX 11® mode on some BENQ 144HZ Freesync monitors
• [425496] Mad Max ‐ Color corruption is observed when Alt+Ctrl+Del is pressed followed by the Escape key
• [425659] Assassin's Creed® Unity may experience minor frame stutter when AMD CrossFire™ mode is enabled

Known Issues:

• [58978] Dirt Rally - A crash may be experienced starting a new race with AMD Crossfire™ and AMD Freesync™ enabled
• [78139] PowerDVD - 3D playback may fail on some configurations using an HDMI 2.0 dongle
• [79428] Starcraft 2: Flickering may be observed in the 'Episode 3' campaign
• [80251] Fable Legends: The DirectX® 12 benchmark may fail to launch on some configurations
• [80836] Call of Duty: Black Ops 3 - Flickering or poor performance may be experienced when running in AMD Crossfire™ mode
• [81402] Assassin's Creed Syndicate - A crash may be experienced when setting game to Ultra-High graphics mode
• [81403] Flickering may be observed on some Freesync monitors while playing Wolfenstein - The New Order and Battlefield™: Hardline with Vsync disabled
• [81448] A system restart may be experience when waking the system from sleep mode on some systems with Intel processors
• [81489] Unable to create 4x1 or 2.1 portrait mode SLS with 4K displays
• [81651] Star Wars™: Battlefront - texture corruption may be experienced if the game "Field of View" setting is > 100
• [81736] Call of Duty Online - the game may crash if the Printscreen key is pressed on a 4K monitor
• [81777] Launching a game from the Game Manager may launch on a single display after enabling and disabling AMD Crossfire™ in a 3x1 AMD Eyefinity™ setup
• [81809] A crash may be experienced if an HDMI™ display is a cloned display device on an HP Envy 15 notebook
• [81844] Unable to change resolution if a wireless display is the only connected display
• [81856] Marginally increased power consumption may be observed during video playback
• [81859] Flickering may be experienced on some monitors when AMD Freesync™ is enabled
• [81915] Assassin's Creed Syndicate - Building textures may be missing on some AMD Freesync™ displays with Vsync enabled
• [82083] Ark Survival Evolved - Poor performance may be experienced when running in AMD Crossfire™ mode
• [82093] Star Wars™ : Battlefront - Some flickering may be experienced in shaded areas of the screen while game levels are loading
• [82213] Star Wars™ : Battlefront - Some users may experience minor flickering or corruption at different game location or while viewing the in-game cinematics
• [82387] Assassin's Creed Syndicate - The game may crash if the Gaming Evolved "In Game Overlay" is enabled. A temporary workaround is to disable the AMD Gaming Evolved "In Game Overlay"