This discussion is for community members to share their experience using AMD Software Adrenalin Edition 25.1.1. For the full driver release notes and download link refer to: AMD Software Adrenalin Edition 25.1.1 driver release notes.
If you would like to report an issue with AMD Software Adrenalin Edition 25.1.1, please use the AMD Bug Report Tool. If you require technical assistance with your AMD product, please contact AMD Customer Care.
IMPORTANT! When submitting a bug report against this driver, please make sure to include the following tag into the bug report description field using this format:
FORUM-DriverVersion-Username. For example, if your username was GAMER56 and the driver version was 25.1.1, use the tag FORUM-25-1-1-GAMER56
It is absolutely unacceptable that Marvel’s Spider-Man 2 is outright crashing on startup for RX 580 users while NVIDIA has ensured that even older GPUs like the GTX 970 can run the game. The RX 580 is objectively more powerful than the GTX 1650, which meets the game's minimum requirements, yet your drivers prevent it from running at all.
This is not a hardware limitation—it’s a driver issue, and it’s your responsibility to fix it. NVIDIA had no problem updating their drivers to allow older cards to work, yet AMD continues to ignore users who still rely on Polaris GPUs. If NVIDIA can do it, there is no excuse for AMD’s inaction.
Polaris cards are still widely used, and abandoning them like this is nothing short of negligence. I expect a proper response, not a generic “your card is too old” excuse. Will AMD address this issue, or should users just accept that Radeon GPUs don’t get long-term support and move to NVIDIA instead?
Can we get an actual NON-Optional Update now? Nvidia has gotten 3 update so far, you guys are slow as molasses.
KCD 2 just came out, and I actually LOSE FPS when FSR is on. This is unacceptable.
Get your Sht together.
I do appreciate the driver update, but there's still a major issue that I think needs to be looked at. Radeon 7000 and upcoming 9000 series has strong potential, but its performance in Blender Cycles still lags behind expectations. Despite significant hardware advancements, rendering efficiency remains suboptimal compared to competitors. Optimizing HIP support, improving kernel compilation times, and enhancing viewport responsiveness would make Radeon GPUs a more viable choice for 3D artists. Addressing these bottlenecks will not only improve adoption among creators but also strengthen AMD’s position in professional rendering workloads. I urge you to prioritize these enhancements to fully leverage the power of RDNA3 (and new RDNA4) in content creation. I know far too many content creators who would switch to Radeon in a heartbeat if it weren't for this trouble. This is also especially a major league problem considering 3D Animation is just one of those things that can't be easily replaced by AI, thus more and more people will be coming to this field.
Today the Automatic Windows Update "Advanced Micro Devices, Inc. - Display - 32.0.13018.6" disrupted the functionality of the AMD Adrenaline software.
To disable the Automatic Windows Update for Drivers you can follow this instructions:
https://community.amd.com/t5/general-discussions/how-do-i-stop-windows-10-from-updating-my-graphics-...
The version installed prior to the Windows Update disruption was the Adrenaline 25.1.1 (Jan 2025)
I noticed what happened because while I was browsing the screen went black two times during 3 seconds and I heard two times the "new device sound".
In Windows event viewer I have the following ERRORS:
Fault bucket LKD_0x1A8_10_OSGraphicsMonitorNoModeSetMultimonSdcFailed_dxgkrnl!DISPLAYSTATECHECKER::CreateBlackScreenLiveDump, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 6ab6dcf6-7b7d-4468-beb3-aa0b148a7e95
Problem signature:
P1: 1a8
P2: a
P3: 0
P4: 0
P5: 0
P6: 10_0_26100
P7: 0_0
P8: 256_1
P9:
P10:
Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20250209-1235.dmp
\\?\C:\WINDOWS\SystemTemp\WER-984031-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.bba2bb62-a6e5-4720-ba10-5459ee6e28ec.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1a8_3748bd66a7bb3ae96eac533a61a9ac86d47cc_00000000_cab_77b1bff8-ccfd-48e5-bd2e-afb11c403598\WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20240808_1_EC_0_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.892e9b76-d41f-4fff-9e8c-438f4fbbbfa8.tmp.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1a8_3748bd66a7bb3ae96eac533a61a9ac86d47cc_00000000_cab_77b1bff8-ccfd-48e5-bd2e-afb11c403598\WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.90bdd6bc-7524-4a49-87c4-937f8d41e7cb.tmp.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.54bc5b1e-9c03-4fb7-bc0d-57b08d042f22.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.14988e99-42b6-47ae-8869-3ee2741c128a.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f0d02efe-5792-48de-8093-f2d65814f979.tmp.xml
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a8_3748bd66a7bb3ae96eac533a61a9ac86d47cc_00000000_cab_77b1bff8-ccfd-48e5-bd2e-afb11c403598
Analysis symbol:
Rechecking for solution: 0
Report Id: 77b1bff8-ccfd-48e5-bd2e-afb11c403598
Report Status: 268435456
Hashed bucket:
Cab Guid: 0
and
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0
Problem signature:
P1: 1a8
P2: a
P3: 0
P4: 0
P5: 0
P6: 10_0_26100
P7: 0_0
P8: 256_1
P9:
P10:
Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20250209-1235.dmp
\\?\C:\WINDOWS\SystemTemp\WER-984031-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.bba2bb62-a6e5-4720-ba10-5459ee6e28ec.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1a8_3748bd66a7bb3ae96eac533a61a9ac86d47cc_00000000_cab_77b1bff8-ccfd-48e5-bd2e-afb11c403598\WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20240808_1_EC_0_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.892e9b76-d41f-4fff-9e8c-438f4fbbbfa8.tmp.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1a8_3748bd66a7bb3ae96eac533a61a9ac86d47cc_00000000_cab_77b1bff8-ccfd-48e5-bd2e-afb11c403598\WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.90bdd6bc-7524-4a49-87c4-937f8d41e7cb.tmp.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.54bc5b1e-9c03-4fb7-bc0d-57b08d042f22.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.14988e99-42b6-47ae-8869-3ee2741c128a.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f0d02efe-5792-48de-8093-f2d65814f979.tmp.xml
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1a8_3748bd66a7bb3ae96eac533a61a9ac86d47cc_00000000_cab_77b1bff8-ccfd-48e5-bd2e-afb11c403598
Analysis symbol:
Rechecking for solution: 0
Report Id: 77b1bff8-ccfd-48e5-bd2e-afb11c403598
Report Status: 4
Hashed bucket:
Cab Guid: 0
I see this post nearly weekly. The answer is the same. Turn off automatic updates of drivers through windows update.
If you're using windows home follow this:
If you're using windows pro follow this:
even with this driver version, still cannot run FF7 rebirth on 680m(6800U)
it's a bit weird cuz 680m supports required features - it's RDNA 2 family
also the game can be run on 6800U device with SteamOS clones
- I installed ChimeraOS on my One X player mini(6800U) and it worked
so I guess that the hardware fulfils requirement of the game.
then maybe the problem on Windows can be solved by driver update.
This discussion is now locked as AMD Software: Adrenalin Edition 25.2.1 Optional Update has just been released.