Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
Thanks for pointing this out. This is specifically with ReLive, right?I tested all the recent driver versions and the dark video recording bug is in 25.10.2 and 25.11.1, in 25.10.1 and previous versions it works normal. @AMD_Vik
Here's a screenshot comparison of a video recording in a shadowed area in Black Ops 7. I also tested it in another game (MW2) and it had the same issue so it's not a Black Ops 7 bug. This was using a 9070 XT and I clean installed the drivers using DDU.
![]()
![]()
It's with the record function in AMD Adrenalin record and stream. My monitor is 4K 144Hz SDR (Samsung S28AG70). I also tested it in MW2 which had the same problem, there's a reddit post from 10 days ago describing the same problem here: https://old.reddit.com/r/AMDHelp/comments/1guzzb3/video_recording_too_dark_on_main_monitor/nn0vabf/Thanks for pointing this out. This is specifically with ReLive, right?
Are you using a HDR display? It almost looks like HDR > SDR tone mapping isn't occurring? Is this only happening with BO7? Are you seeing this across other titles?
Thanks for the info. It seems we started tracking this just two days ago. I'll follow the tickets to chime in.It's with the record function in AMD Adrenalin record and stream. My monitor is 4K 144Hz SDR (Samsung S28AG70). I also tested it in MW2 which had the same problem, there's a reddit post from 10 days ago describing the same problem here: https://old.reddit.com/r/AMDHelp/comments/1guzzb3/video_recording_too_dark_on_main_monitor/nn0vabf/
@AMD_Vik some guidance here would be helpful if you can ?Tried about 20 different combos today, only fix that works is to unplug HDMI from iGPU. The software will then start, short term fix for me is to plug third monitor into 9070XT but then the VRAM bug will mean my memory is running higher. Think this is some kind of RDNA 2 / 4 driver divergence and it can't start the software as it sees both my RDNA2 chip and 9070XT RDNA 4.Once i installed some new drivers recently, DDU and all that i think, adrenaline didnt launch. So i went meh and just installed them again without doing anything else like uninstalling since its the same driver im just trying to fix the software for, then rebooted then adre.. then launched ok. Dunno if it same would work for you.
somtimes i just insall new drivers over the top of the old drivers works all the timeOnce i installed some new drivers recently, DDU and all that i think, adrenaline didnt launch. So i went meh and just installed them again without doing anything else like uninstalling since its the same driver im just trying to fix the software for, then rebooted then adre.. then launched ok. Dunno if it same would work for you.
You're running displays from both igfx and nv48? if you use the cleanup utility (or ddu), and then run the auto detect installer, does that get you into a working state?Tried about 20 different combos today, only fix that works is to unplug HDMI from iGPU. The software will then start, short term fix for me is to plug third monitor into 9070XT but then the VRAM bug will mean my memory is running higher. Think this is some kind of RDNA 2 / 4 driver divergence and it can't start the software as it sees both my RDNA2 chip and 9070XT RDNA 4.
Hopefully this gets resolved soon
Hi Vik, yes nv48 and igpu. Tried both ddu and the clean up utility, neither workedYou're running displays from both igfx and nv48? if you use the cleanup utility (or ddu), and then run the auto detect installer, does that get you into a working state?
Actually not tried with auto detect after full clean. I will try that shortlyHi Vik, yes nv48 and igpu. Tried both ddu and the clean up utility, neither worked
This Star Citizen issue.
![]()
AMD GPU Error code 3221225477 work around. - Star Citizen Spectrum
If you have an AMD GPU and you're experiencing the crash on game startup with Error code 3221225477 this fix may work for you. Download and run the AMD Clean-up Utility, find it here. AMD Cleanup...robertsspaceindustries.com
![]()
Issue Council - Sign in
Create an account or sign in to Issue Council. Track bugs on and vote on the issues to help the development team identify what to work on next.issue-council.robertsspaceindustries.com
A friend of mine whose running an RX 9070 XT had no issues running Star Citizen on Driver 25.10.2, until last night when he updated Windows 11, right after that he ended up with the same problem, after removing driver 25.10.2 and rolling back to 25.9.1 it was fine again.
I remember this was not a problem for me until i updated Windows.
This problem seems a combination of 3 parties.
1, Microsoft, its only a problem after installing the latest Windows updates.
2, AMD's latest Drivers, because older ones work, and it seems a uniquely AMD problem, Nvidia GPU's seem to work fine.
3, Cloud Imperium Games, Because so far as i know no other game with EAC has this issue.
Amd dont refer to it as a vram bug with it being max speed all the time its to do with refresh rates. Say if you had 60hz in windows for refresh it will go low for idle consumption for vram but if say i switched to 75hz which is my monitor then vram is always running full pelt. Im not sure why as i dont think i got that with nvidia cards but ah well.Tried about 20 different combos today, only fix that works is to unplug HDMI from iGPU. The software will then start, short term fix for me is to plug third monitor into 9070XT but then the VRAM bug will mean my memory is running higher. Think this is some kind of RDNA 2 / 4 driver divergence and it can't start the software as it sees both my RDNA2 chip and 9070XT RDNA 4.
Hopefully this gets resolved soon
Hey skeeteruk, yes I am aware hence the use of my igpu for my third monitor which then fixes the issue for me. 2 monitor are fine as long as the refresh rates are multiples, problem is with 3 it's not possible which is fine but not when the driver breaks my igpu compatibility. Trying again now with the auto detect toolAmd dont refer to it as a vram bug with it being max speed all the time its to do with refresh rates. Say if you had 60hz in windows for refresh it will go low for idle consumption for vram but if say i switched to 75hz which is my monitor then vram is always running full pelt. Im not sure why as i dont think i got that with nvidia cards but ah well.
yeah its a nightmareAmd dont refer to it as a vram bug with it being max speed all the time its to do with refresh rates. Say if you had 60hz in windows for refresh it will go low for idle consumption for vram but if say i switched to 75hz which is my monitor then vram is always running full pelt. Im not sure why as i dont think i got that with nvidia cards but ah well.
the two factors affecting this are vertical blanking intervals between connected panels, and peak display bandwidth of all connected monitors.Amd dont refer to it as a vram bug with it being max speed all the time its to do with refresh rates. Say if you had 60hz in windows for refresh it will go low for idle consumption for vram but if say i switched to 75hz which is my monitor then vram is always running full pelt. Im not sure why as i dont think i got that with nvidia cards but ah well.
My issues also possibly started after the latest windows update, possibly related ?@AMD_Vik
Any idea on this with Star Citizen in DX11 mode? 25.9.1 works, 25.9.2 and 25.10.2 and 25.11.1 don't. Instant crash on Splash screen start up.
It was even crashing in Vulkan mode, i installed the Vulkan SDK and that fixed it for Vulkan mode.
![]()
![]()
AMD GPU Error code 3221225477 work around. - Star Citizen Spectrum
If you have an AMD GPU and you're experiencing the crash on game startup with Error code 3221225477 this fix may work for you. Download and run the AMD Clean-up Utility, find it here. AMD Cleanup...robertsspaceindustries.com
A bit more detail on it here.
It seems like Windows or EAC is blocking some critical components after the Windows update.
My issues also possibly started after the latest windows update, possibly related ?