Download AMD Radeon Software Crimson 16.8.2 driver

Published by

Click here to post a comment for Download AMD Radeon Software Crimson 16.8.2 driver on our message forum
https://forums.guru3d.com/data/avatars/m/260/260114.jpg
I'm at a complete loss here. Windows is up to date, the drivers are DDU cleaned and all other system drivers are up to date, the UEFI on the motherboard is up to date. All stress tests pass flawlessly. WTF is the issue!!!? :bang:
The ISSUE is New Windows 10 !!!! This issues continue to happening after the April/May update and its not FIXED till now !!!! It's great OS but still needs some Magic Touch. Now im Happy that everything is OK on my Side (Tweaked it Heavily and its Fast and stable) But after the Redstone i can't log in into my MS account anymore, and Forza Apex cant log in into xBox Account ! But xBox App working well :bang: Ahh Not every issue is Driver related ! Most of them now is Windows 10 related !
https://forums.guru3d.com/data/avatars/m/229/229367.jpg
Will rollback and test an earlier driver, but, anyone else testing api overhead? Went from ~1680000 on 16.7.2 to ~1480000 on 16.8.2, DX11 ST. http://www.3dmark.com/compare/aot/160588/aot/157802 Left 16.8.2, Right 16.7.2. On 16.7.3 it always crashed on this test. To note that I've also upgraded Win10. Nothing else changed overclock wise.
Went back to 16.7.3 (somehow API Overhead test isn't crashing anymore) and DX11 ST seems to be back to normal. http://www.3dmark.com/compare/aot/160668/aot/160589 Left 16.7.3 - Right 16.8.2
https://forums.guru3d.com/data/avatars/m/265/265776.jpg
Not for me! I'm still hving issues with anniversary edition. I've tried modding my 280X bios to include UEFI, tried it with secure boot disabled, tried it with other OS selected under the secure boot options. It still bluescreens/freezes or crashes randomly. The same system has a hard drive with 8.1 installed in legacy mode and has had no such issues for the past year and continues to function. I can run for sometimes 0 seconds, or 30 minutes idling, or opening chrome crashes it, or opening GPU-Z 1.10 freezes the entire machine, etc. :bang: I'm at a complete loss here. Windows is up to date, the drivers are DDU cleaned and all other system drivers are up to date, the UEFI on the motherboard is up to date. All stress tests pass flawlessly. WTF is the issue!!!? :bang: If I had the money I'd buy a 1080 and put my current 970 in that machine. So sick of this bullsh'it. (The install was from MSDN ISO and is fresh, not an upgrade. It's a week old now which is how long I've been delayed by this).
Every single driver is layered, with the core layer being motherboard (chipset) drivers. On my system, I have issues running any 14.x+ or later RSTe driver on my X58 RAID. (Probably related to the firmware installed on the mobo) I also had a memory leak due to Win10 installing an archaic SM Bus driver. This would crash/hang my system after about a half hour, even if just idling. My solution was to get the latest Intel Chipset package, and running it with "-overall" switch to force update all components. Same install suddenly became super stable. Since you have a fresh install, I bet you didn't do this, assuming Win10 installed the best chipset config for you.
data/avatar/default/avatar09.webp
thats only useful if Intel changes the name of the devices. Mostly, it just re-installs the same infs again.
https://forums.guru3d.com/data/avatars/m/254/254962.jpg
Every single driver is layered, with the core layer being motherboard (chipset) drivers. On my system, I have issues running any 14.x+ or later RSTe driver on my X58 RAID. (Probably related to the firmware installed on the mobo) I also had a memory leak due to Win10 installing an archaic SM Bus driver. This would crash/hang my system after about a half hour, even if just idling. My solution was to get the latest Intel Chipset package, and running it with "-overall" switch to force update all components. Same install suddenly became super stable. Since you have a fresh install, I bet you didn't do this, assuming Win10 installed the best chipset config for you.
Actually, I did. That's one of the first things I do. I'm well aware of the preference Windows has for outdated SMBus drivers. Glad I'm not the only one! I use Snappy Driver Installer to help me get all the drivers. I'm going to reinstall again with 14393.67 but this time just use CSM legacy mode and forget about ever having a pure UEFI or even CSM UEFI system.... :'( I'll reflash back to the stock 280X G1 bios that doesn't have UEFI enabled (but is present) and just suck it up until I can get a 970 G1 in there. The BSODs come from the AMD kernal though. The 8.1 install I have on the same hardware has all the same drivers. Is secure boot actually useful to anyone anyway? I've had nothing but trouble with it.
https://forums.guru3d.com/data/avatars/m/259/259654.jpg
Actually, I did. That's one of the first things I do. I'm well aware of the preference Windows has for outdated SMBus drivers. Glad I'm not the only one! I use Snappy Driver Installer to help me get all the drivers. I'm going to reinstall again with 14393.67 but this time just use CSM legacy mode and forget about ever having a pure UEFI or even CSM UEFI system.... :'( I'll reflash back to the stock 280X G1 bios that doesn't have UEFI enabled (but is present) and just suck it up until I can get a 970 G1 in there. The BSODs come from the AMD kernal though. The 8.1 install I have on the same hardware has all the same drivers. Is secure boot actually useful to anyone anyway? I've had nothing but trouble with it.
Secure boot is basically a bootloader securing mechanism.
https://forums.guru3d.com/data/avatars/m/243/243702.jpg
Secure boot is basically a bootloader securing mechanism.
It's there to prevent execution of undesirable code during boot sequence. Therefore if ti is enabled, it will not allow loading of another OS from flash disk. Apparently that's good for local access control, but unless one has password on BIOS too, then it has no meaning for that purpose anyway. People who buy some 2-in-1/tablet/netbook devices are often cut off access to linux due to secure boot being enabled and not accessible from BIOS at all.
https://forums.guru3d.com/data/avatars/m/259/259654.jpg
It's there to prevent execution of undesirable code during boot sequence. Therefore if ti is enabled, it will not allow loading of another OS from flash disk. Apparently that's good for local access control, but unless one has password on BIOS too, then it has no meaning for that purpose anyway. People who buy some 2-in-1/tablet/netbook devices are often cut off access to linux due to secure boot being enabled and not accessible from BIOS at all.
That's true. There are ways around it that don't disable it, but nothing automatic as of yet.
data/avatar/default/avatar23.webp
Looking for help installing this driver 😀. When I installed the driver package it went just fine but after finishing installing the driver my screen just went poop black but the pc, mouse and keyboard still responding as in working normally (i still even hear the music and stuff). It just stay pitch black like that until i reboot then i thought it would go away but after the windows boot into the login screen, it just went black as well. Anyone knowing the issue can help this poor soul out? Thank you!
https://forums.guru3d.com/data/avatars/m/229/229367.jpg
@jasoncowboy, try removing it completely with DDU and installing it after.
https://forums.guru3d.com/data/avatars/m/259/259067.jpg
Don't forget to disable AV and disconect network cable from your computer. You should try to delete all temp files from c:\users\your name\AppData\Local\Temp. Also you should try a clean up with Ccleaner (from filehippo or else).
data/avatar/default/avatar32.webp
none of that is really necessary. just DDU into safe mode.
data/avatar/default/avatar09.webp
Still getting this annoying flicker on desktop with Freesync, even though the released notes say the issues is fixed. It's clearly not as plenty of people still reporting it. As soon as you play a game, once you exit back to desktop or alt+tab that's when the flicker starts. Only way to then get rid of it is to disabled and re-enable Freesync or change the monitor refresh rate. This has gotta be fixed soon, its incredibly annoying.
data/avatar/default/avatar31.webp
Don't know why, but I have massive stuttering with this and all 16.8.x. drivers in Unreal Tournament, Assetto Corsa (UT stutters immediately, AC after a few laps laps driven, until that everything is normal). If I rollback back to 16.7.3. everything works perfect.
https://forums.guru3d.com/data/avatars/m/198/198862.jpg
Don't know why, but I have massive stuttering with this and all 16.8.x. drivers in Unreal Tournament, Assetto Corsa (UT stutters immediately, AC after a few laps laps driven, until that everything is normal). If I rollback back to 16.7.3. everything works perfect.
Idk, i'll be trying UT tommorow just to test this.
data/avatar/default/avatar38.webp
I'm having bad luck with this driver and others on Windows 10 rs2 builds. Getting kernel panics and hard freezes during driver installs. Can't boot to Windows afterwards. Have to DDU the drivers in safe mode before I can boot normally again. I just want to use my 7730M ffs.
https://forums.guru3d.com/data/avatars/m/254/254962.jpg
I'm having bad luck with this driver and others on Windows 10 rs2 builds. Getting kernel panics and hard freezes during driver installs. Can't boot to Windows afterwards. Have to DDU the drivers in safe mode before I can boot normally again. I just want to use my 7730M ffs.
Yup, it's still fuc'ked. Whatever the problem is with this new build of windows is really serious and needs to be patched asap. What if I were an idiot and didn't know how to reinstall windows or dual boot? I'd be completely screwed.
https://forums.guru3d.com/data/avatars/m/263/263072.jpg
I'm having bad luck with this driver and others on Windows 10 rs2 builds. Getting kernel panics and hard freezes during driver installs. Can't boot to Windows afterwards. Have to DDU the drivers in safe mode before I can boot normally again. I just want to use my 7730M ffs.
If you have noticed this on first rs2 build, then you should've have reverted back to the rs1, and waited for it to be fixed. It's called Insider Preview because those are test builds, and they've said that first builds of rs2 are going to be more buggy then usual. Anyway, I think I don't have this problem during driver install. Will check it out.
https://forums.guru3d.com/data/avatars/m/224/224399.jpg
I suggest running the Windows branch for business. Let other poor souls find the bugs.