Solutions:
- Manual set your GPU’s clock speed.
- Use Decky PowerTools to limit your CPU’s frequency between 400 to 2800mhz
- Revert your Deck back to the 3.4.1 update.
Most active Steam Deck Bug Report Community Threads on the issues
https://steamcommunity.com/app/1675200/discussions/0/7529517132617601916/?tscn=1700480355
https://steamcommunity.com/app/1675200/eventcomments/7529517132614912523?snr=1_2108_9__2107&ctp=10
Has been an issue since the 3.5 beta/preview builds on October 20th. 0 response from the Valve Team. Not even a “we’re working on it”.
https://github.com/ValveSoftware/SteamOS/issues/1176
Steam Deck OLED is also affected.
https://steamcommunity.com/app/1675200/discussions/0/7529517132622363506/
I’ve been closely following this ongoing issue with the Deck since the release of the 3.5 beta/preview builds and the release of SteamOS 3.5.5 Stable. It seems like this bug has been a persistent thorn for many LCD users, and surprisingly, it’s also affecting the new Steam Deck OLED models.
For those unaware, if you are on 3.5.5, your unit may be affected by a GPU clock cycle bug in which the clock speed of the GPU will cycle between 200 and 1040 mhz. This can reduce performance and battery life in some games. You can verify if you have it, and test the performance loss by using the performance overlay, running a heavy game, and manually setting the GPU above 1040.
Associated with this bug is an audio crackling glitch, where it sounds like the Deck was submersed in jelly, with popping and laggy audio. There are also a bug with the Official Dock, in which the DisplayPort does not work for customers.
What’s more concerning is the lack of response from Valve. We’re yet to hear even a basic acknowledgment like “we’re working on it”. Valve has always been receptive and open to their customers, and strange to see, especially for an issue that’s been active for a while now. It’s not just in one place – the Steam Community thread (most active bug report thread for the Steam Deck) and GitHub issue tracker both highlight the severity and spread of this problem. Many users on the community forum feel that the update was rushed out in preparation for the Steam Deck OLED, and are even on the fence of refunding their OLED due to the software issue.
I believe it’s time Valve addressed this. The community’s frustration grows, which is understandable. A little communication can go a long way in this situation.
I don’t know where you found “actively communicating” considering that Valve was completely absent from these threads (they answered only after several threads including your popped out on reddit), but his answers seems more like damage control. He stated things that are not true (that 200/1040 bug is just slow drawing from overlay) while you even have video in your post that proves otherwise.
The thing is: probably this bug affects much more people but some of them just don’t really bother with overlay and state that they don’t have it (sorry but people like that are the worst, because they lack any tech knowledge but still voice their opinion), similar to how people pretend they have “smooth” (no stutters) framerate on some games where even people with 7800x3d and 4090 (like Dead Space remake) have issues and when asked to enable RTSS overlay they disappear from thread.
I perfectly understand people’s desire to defend Valve and tbh I think Valve will figure these issues out and actively working to resolve it, still they picked this update for almost a year then suddenly released it with few major bugs only because they wanted to ship OLEDs before holidays in USA. People were also actively downvoting all threads listing these issues as I stated here, like they do with almost every thread listing issues if it’s not made into stupid meme.