Can someone explain to me, please, what's difference and how is this possible? High chance of buggy stuff happening there.
I have 4 differently behaving runs in same test (techincally there were more. but i did them until caught all 4 states on screenshots).
With... Basically almost exactly same software setup.
1) Minimized Black Desert Online on remastered in city with lots of people around me (fishing event) for long enough so after opening and foregrounding game frames won't render in 1 or 2 seconds as if assets are rebuilding. As i have clean driver install and hadn't messed up with anything yet again, asset rebuilding works... "Normally".
Won't say pleasing, but "not normal" in my understanding is when game after foregrounding runs normally for second, THEN rebuilds assets for 1-2 seconds and after that goes running again. When this stuff begins to happen, chances for both sound stutters and/or game freezing almost completely increases exponentially. Yes, technically you can unfreeze game via volume changing (overlaying system element?) or alt-tabbing back and forth (alt-tabing may not fix issue and make game freeze instantly again, though). But that's doesn't fix problem!
2) Browser (Chrome Dev) with opened Youtube and playing videos.
3) MSI Kombustor. Test PBR-Donut, windowed, artifact scanning mode.
--------------------------------------------------------------------------------------------
What to pay attention on: VRAM frequency on screenshots and commentaries to them.
--------------------------------------------------------------------------------------------
Method of repeating is simple. Wait and run Kombustor. Then you have few possibilities. [GPU core frequency varies a lot in this test, so don't mind big differences in this number]
Variant 1: Everything runs as intended. Memory frequency is 2294-2304 as intended. When you return to the game, it runs fine and no asset rebuild is required.
Variant 2: Happens at random. Seemingly normal on first glance. But memory frequency is only around 900-1300 and not supposed 2300*. If you wait some time, or take screenshot, or run into game. Frequency have really high chance (close to 100%) return to supposed 2300 mHz value. Some actions usually are more effective than others in doing that. Screenshot almost guaranteed to ramp up memory frequency, while maximizing game can return you to low frequency state despite having full on 2300 while in game itself. Also going true fullscreen for this test makes this variant basically impossible to get from what i know.
*For information to some less knowledgeable people - it is impossible to set memory frequency manually to value this low. Test isn't hard on load. (it is used just to test VRAM artifacting on high frequency).
Variant 3: Worst from common ones. Frequency stays at 0, meaning memory STILL is deep in sleep. It won't come back until you force it on. When you maximize game, as memory frequency is at 0, it will rebuild assets for 1-2 seconds (in normal case instantly as you maximize it, in corrupted case it will happen second after).
BTW, fun part, and definitely a bug. When i attempted to record how launching game asset rebuilding cause memory frequency to actually be able to restore from 0 to supposed 2300, well... Game runs fine with 0 mHz memory frequency... For 2 seconds at max. Then it freezes, screen goes black, aaand... Crash!
And this one is consistent. Minimize BDO, wait for VRAM go into power down mode [you can check if line GPU Memory Clock exists. When it disappears this is time when VRAM powers down to 0 mHz and you can continue], then start recording, run MSI Kombustor tests, see that RivaTuner reports 0 mHz frequency as well, then open BDO from minimized mode (without stopping recording). Wait few seconds, aaand... crash. [Basically ... Record --> BDO asset loading = crash (may not be 100% chance to trigger. Record --> MSI Kombustor with 0 mHz memory --> BDO asset loading = crash]
Variant 4: "**bleep** is happening there". Actually this one was really strange. Core frequency is capped (not supposed to be like that. Especially taking in account power consumption which is no difference from normal one for this test and MUCH lower frequencies) , while memory is at 0 mHz. Framepacing graph have "pulse-like" appearance with terrible 1% lows and really low avg FPS.
I have 1 second recording of it made in attempt to see if recording could cause things to normalize somehow (forcing synchronisation, MPO issues and stuff...), but nothing changed. I have no idea how it happens in the first place (it was my first test today) and how to repeat it, but this one exists. Basically FPS got broken to hell as well as frame pacing (especially taking in account this is really light test).
1 Solution
Additional information. Managed to capture improper VRAM recovery on heavy load application.
For details.
1) As soon as you foreground game in this state it will freeze. And either load REALLY long time, or eventually crash driver for no responsiveness. Sometimes it can even hang up whole system requiring hard reset.
2) You still can move away from game window if you overlay ANYTHING on top of it, no matter if it is Windows interface overlay, alt-tabbed other application window or Ctrl+Alt+Delete / Win+Tab / Any another way to cause overlaying images.
3) When you attempting to move away from frozen game, action will be HEAVILY delayed.
4) As long as you have anything overlayed on top of game in this state, game will run fine, and even with max framerate (max load). But as soon as you go back to the game - it will freeze again.
5) Seems that enabling desktop recording can "fix" this behaviour with some lag. But in some other cases (as i showed in video linked to a previous post), it can just crash driver as well (Black Desert Online).
More detailed, but recorded on phone.
AMD 6750 XT, 22.10.3, Improper VRAM power state recovery after switching tabs. [Warframe]. + enabled...
How VRAM state restoration looked being recorded via Adrenalin screen capture.
VRAM state restoration via screen capture enabling. Recorded via Adrenalin
@Matt_AMD, @Ray_AMD. Sorry for bothering you two again (i really don't know who else i can call out towards). Can confirm that vertical synchronisation and Enchanced sync are kinda in broken state right now. Especially if different applications set different preferences with other applications.
Tried to do vsync always on enchanced sync
And first thing i got when i launched game when my video memory was in power down state (0 mHz) is THIS
That 144 hz is not what supposed to happen with Enchanced sync. And especially not with 0 mHz VRAM IN GAME WITH ACTIVE MOVEMENT! What was more surprising, though, is there was no lag in-game, it run fine, when everything reported no memory frequency. And even with alt-tabbing back and forth memory frequency stayed at 0 mHz. Is it reporting issue? I don't know. But as soon as i made this screenshot FPS got unlocked (look number 2) below). I will look if i am able to repeat this behaviour.
More fun!
1) That is how it is supposed to be with Enchanced sync and with unlocked FPS (and it is unlocked). Or with vsync being off.
Then, we are trying to experiment a bit...
2) Alt-tab out and back to game. Vsync is forced again. Press printscr... FPS becomes unlocked, **bleep**!
3) Alt-tab out and back again. VSync is again forced. Open Adrenaline overlay. Close overlay. FPS is now unlocked
4) VSync is being constantly forced on when overlay is active. Even if game was in FPS unlocked state
P.S. If you disable Enchanced sync (but leave vsync forced on), then you won't get constant switching between locked and unlocked FPS. FPS will always be locked
Granted i hadn't yet seen application permafreeze again, but i barely tried using forced on vsync. And i am pretty sure now that there is heavy chance for some synchronisation conflicts that can happen in background
And as i need to have unlocked FPS in some places i would prefer to either have working as intended Enchanced sync (that should not refer to previously set and now locked down vertical synchronisation option below it), or just use vsync as forced off. . . So... i will try again "off until application specifies" and will report if i see permafreeze happening again.
UPD: Couldn't repeat loading Warframe with 0 mHz memory clock. as it ramps up to normal value. Vsync is still really inconsistent.
UPD 2: Managed to get Warframe running with 0 mHz memory clock reporting. This time in mission. But when i launched it memory frequency was ok, and broke at some point in playing after switching between game and background application and back. When i started screen capture, game froze for second, then continued with max memory frequency. Maybe it had like 10-20 more FPS after?
Small UPD:
Got game permafrozen again. It was BDO. Used vsync "off, until application specifies" and enchanced sync combo.
Will try several days with vsync forced off again.
Behaviour difference
Off, until application specifies + enchanced sync. In game FPS is unlocked and stable. When you try to overlay anything on top, broken vsync engages. That vsync not just limits FPS and synchronizes it, but it also gets affected by any action with overlay, making FPS go down the pit with downwards spikes at random
--------------------------------------
That's how looks Globally off with Enchanced sync AFTER GAME RESTART (because it wouldn't apply on the fly to BDO).
As you can see no background FPS limitation is happening.
I've been trawling the web the past few days because I've been having very small band-like glitches in specifically Warframe with my 5700 XT (driver ver. 23.2.1) and came across this thread which seemed to be the only pertinent thread I could find discussing this specific issue anywhere.
I have found that the same audio issue persists, notably if I had Youtube or Twitch on on my other monitor (only while the stream/video was playing, even if muted. If paused, the banding stopped). Potentially Discord as well but I haven't been able to solo that one out yet to test it. Spotify, however, seems to work perfectly fine. Additionally, attempting to capture the game window (specifically the application itself and not my screen) with OBS yields a video file that shows no sign of the banding glitches. A video I had to take with my phone as a result is here:
Forcing any sort of V-sync on/off in game seems to do nothing, and no combination of free/enhanced sync being on/off in the Adrenalin software does anything either. Locking FPS to my monitor's refresh rate was ineffective, and so was locking it to a simple 60. I've tried fully reinstalling the game, rebooting my pc, and testing it with other games but of all the games I currently play, Warframe was the only one with this issue.
It's been driving me absolutely bonkers and I have yet to be able to find a proper fix unfortunately, mostly just want to echo that I've also been having the issue.
EDIT: I have done a bit more testing. Discord does not seem to contribute to the issue, but having Youtube open at all does (even if just on the home page).
