Freezing in every game, occasionally causing total system lockup

[DivideTheZero]

Hello, I've been having this problem ever since I got the Deck. Every game at some point, will lockup and I'll be forced to either quit the game, or occasionally force shut down the system. Possibly hardware issue?

The freezing occurs at seemingly random times, but *usually* within the first 15 minutes of launching a game. The game will freeze, the screen will go black for a sec, then when it comes back the game will be completely unresponsive. Audio still plays, and I can usually use the overlay and exit the game. Sometimes the overlay will also be unresponsive, and I have to force shut down the system. (Note: In these scenarios, I can still hear the overlay, I just can't see it)

This freeze occurs in *every single game I have tested*. H:ZD, Control, Hitman 3, No Man's Sky, Half Life 2, ME: Legendary, etc.

It appears like the GPU is crashing or resetting. Graphics settings and intensity appear to have zero impact on the issue. Happens just as often on low presets as on high presets.

So far I have tried re-imaging the deck, and opted into the beta branch. No change.

[wasabinator]

亚里士阙德 původně napsal:

Does anyone tried “BATTERY STORAGE MODE” from BIOS.
After the operation, the steam deck returned to normal and only crashed twice during several days.
However, when the battery level was low (below 40%), the screen freezed very frequently. After recharging, the crash problem is alleviated.
That is to say, when the battery level is low, it is easy to crash. When the battery level is high, the crash phenomenon occurs less (occasionally).
So I think it may have something to do with power management or battery voltage.

I honestly think any tweak and outcome is simply a placebo. The problem will still be there.

[deaddoof]

Lets celebrate.

An AMD developer managed to reproduce a sdma0 timeout

https://gitlab.freedesktop.org/drm/amd/-/issues/2220#note_2146527

Let hope this bug is relevant for us and fixable within the next few months.

[Kosmo零]

Somehow I doubt sdma0 timeout somehow related to Steam Deck freezes plague.

[deaddoof]

Kosmo零 původně napsal:

Somehow I doubt sdma0 timeout somehow related to Steam Deck freezes plague.

Hits all rembrandt chips. Hard to reproduce. Hardware decode can trigger it. The problem with the deck freezes is that it might be multiple issues in one. An AMD staff manage to reproduced one with logs. Its good news.

[Alecslee]

As someone that has got 4 different steam decks, the original one, 2 rma, and another bought in the sales time (wich i refunded), i can confirm that this is something that happens IN ALL steam decks, the only difference is that some people play less than others , or play less games etc so they think they don't have those freezings, but its only because they haven't played enought or enought games to reproduce it, its just as simple as that, because all my 4 Steam decks have reproduced the same behaivor again and again, so we have to assume this is something is going to happen sooner or later if you use your deck frequently with a ton of different games (mostly in triple A games).

And about the solutions, don't waste your time, nothing works, i've even test to undervolt (wich is something that have work for some people with amd gpu on regular pcs) but nah, i've got freezings in doom eternal and Sackboy the same way they happened without the undervolting. Only a reimagine stops the freezings for a while, but its a placebo, they are going to came back at some point, and the rma isn't the solution too because is something innherit to deck gpu of the deck.

I think in fact its not a decks problem, but a AMD one, because you can google about "freezing with sound" and you will find a lot of people with regular windows Pc with AMD cards that have this same , freezings, so its clear to me that is a amd bug that i really doubt they are going to fix at this point.

Trying to be positive, i've played hundreds of games in steam deck, and those freezings have only happened in maybe 9-10 of those 300+ games, so its not something gamebreaking, but its sad that you have to play allways with the "fear" of those freezings to apear again.

[deaddoof]

Alecslee původně napsal:

And about the solutions, don't waste your time, nothing works, i've even test to undervolt (wich is something that have work for some people with amd gpu on regular pcs) but nah, i've got freezings in doom eternal and Sackboy the same way they happened without the undervolting. Only a reimagine stops the freezings for a while, but its a placebo, they are going to came back at some point, and the rma isn't the solution too because is something innherit to deck gpu of the deck.

I think in fact its not a decks problem, but a AMD one, because you can google about "freezing with sound" and you will find a lot of people with regular windows Pc with AMD cards that have this same , freezings, so its clear to me that is a amd bug that i really doubt they are going to fix at this point.

Trying to be positive, i've played hundreds of games in steam deck, and those freezings have only happened in maybe 9-10 of those 300+ games, so its not something gamebreaking, but its sad that you have to play allways with the "fear" of those freezings to apear again.

Well yea. Why do you think Linux crowd tried to get AMD to open up their firmware? All the cool interesting power management stuff happens in firmware.

I want them to open it up because it will allow universities to poke around and they will suggest cool stuff for their dissertations.

[johangp19]

Dang, is this real? s***, been having this issue since yesterday (just realized while trying to play Octopath I and II and got the error) and found out this discussion looking for a fix, its really heartbreaking, I though it was a game compatibility issue or something. My Deck is only 2 months old, this sucks. Don't think I ll be able to RMA my device at all as I live in Latin America, bought the device through a friend of mine who was traveling from USA and he delivered to me.

What I dont understand is why Spiderman Remastered is working 100% on my Deck, been testing for like 3 or 4 straight hours now and no crashes. Had the issue with Octopath I and II, Crash Bandicoot 4, Bioshock Infinite and DQXI all between the first 15 - 30 minutes. I have more than 100hrs in the following games with no issues at all: Death s Door, Souldiers, Street Of Rage 4, Chained Echoes and yes, as u might have noticed, these are all non demanding titles (that s why I didnt realize earlier, I was mostly playing indie games and roms) but it makes no sense to me that Spiderman is working perfectly, I really dont get it, in fact, I dont remember Elden Ring crashing and I played for like 5-6hrs back when I bought the device, cant test right now as I m low on storage.

Another thing to notice is that I have a lot of third party apps, heroic, discord, spotify, chrome, lutris, quacked games, emulators, mugen games, clone hero, windows libraries, bottles, and IF I REMEMBER CORRECTLY all the games I mentioned that are currently crashing, were at least once quacked in my device previously before buying them, except for Bioshock which I imported it from Epic Store, so, MAYBEEE... it could be software related? I dunno if this is even important man but I mentioned it anyway.

I ll be praying someone comes up with a solution or maybe i just factory reset my device when I get a new SSD and it magically fixes, lol. RMA is not an option for me. if not, then I guess i ll be finishing a loooot of indies and oldie roms in the upcoming days, xD (trying not to cry)

[deaddoof]

johangp19 původně napsal:

What I dont understand is why Spiderman Remastered is working 100% on my Deck, been testing for like 3 or 4 straight hours now and no crashes. Had the issue with Octopath I and II, Crash Bandicoot 4, Bioshock Infinite and DQXI all between the first 15 - 30 minutes. I have more than 100hrs in the following games with no issues at all: Death s Door, Souldiers, Street Of Rage 4, Chained Echoes and yes, as u might have noticed, these are all non demanding titles (that s why I didnt realize earlier, I was mostly playing indie games and roms) but it makes no sense to me that Spiderman is working perfectly, I really dont get it, in fact, I dont remember Elden Ring crashing and I played for like 5-6hrs back when I bought the device, cant test right now as I m low on storage.

Another thing to notice is that I have a lot of third party apps, heroic, discord, spotify, chrome, lutris, quacked games, emulators, mugen games, clone hero, windows libraries, bottles, and IF I REMEMBER CORRECTLY all the games I mentioned that are currently crashing, were at least once quacked in my device previously before buying them, except for Bioshock which I imported it from Epic Store, so, MAYBEEE... it could be software related? I dunno if this is even important man but I mentioned it anyway.

I ll be praying someone comes up with a solution or maybe i just factory reset my device when I get a new SSD and it magically fixes, lol. RMA is not an option for me. if not, then I guess i ll be finishing a loooot of indies and oldie roms in the upcoming days, xD (trying not to cry)

Pretty hard to trigger. But we do not know whether your bug is related to this thread. Can you post the crash logs?

 sudo journalctl --list-boots

sudo journalctl -b -xe <bootnumber>

Copy and paste the last 50+ lines I guess.

[johangp19]

deaddoof původně napsal:

johangp19 původně napsal:

What I dont understand is why Spiderman Remastered is working 100% on my Deck, been testing for like 3 or 4 straight hours now and no crashes. Had the issue with Octopath I and II, Crash Bandicoot 4, Bioshock Infinite and DQXI all between the first 15 - 30 minutes. I have more than 100hrs in the following games with no issues at all: Death s Door, Souldiers, Street Of Rage 4, Chained Echoes and yes, as u might have noticed, these are all non demanding titles (that s why I didnt realize earlier, I was mostly playing indie games and roms) but it makes no sense to me that Spiderman is working perfectly, I really dont get it, in fact, I dont remember Elden Ring crashing and I played for like 5-6hrs back when I bought the device, cant test right now as I m low on storage.

Another thing to notice is that I have a lot of third party apps, heroic, discord, spotify, chrome, lutris, quacked games, emulators, mugen games, clone hero, windows libraries, bottles, and IF I REMEMBER CORRECTLY all the games I mentioned that are currently crashing, were at least once quacked in my device previously before buying them, except for Bioshock which I imported it from Epic Store, so, MAYBEEE... it could be software related? I dunno if this is even important man but I mentioned it anyway.

I ll be praying someone comes up with a solution or maybe i just factory reset my device when I get a new SSD and it magically fixes, lol. RMA is not an option for me. if not, then I guess i ll be finishing a loooot of indies and oldie roms in the upcoming days, xD (trying not to cry)

Pretty hard to trigger. But we do not know whether your bug is related to this thread. Can you post the crash logs?

 sudo journalctl --list-boots

sudo journalctl -b -xe <bootnumber>

Copy and paste the last 50+ lines I guess.

Okay, so I just type this on Konsole right? will do! Just closed Spiderman Remastered, so yeah...like I was saying, thats like 6 straight hours no crashes with that game in particular. I just launched Octopath I, as soon as it crashes, i ll upload the log. Ty

[johangp19]

Okay im back!!! So.. Octopath 1 just crashed, took around 2hrs this time, weird. Here s my log:

(deck@steamdeck ~)$ journalctl
Oct 31 13:03:23 steamdeck pipewire[1236]: spa.alsa: hw:acp5x,1: (0 missed) snd_pcm_avail after recover: Broken pipe
Oct 31 13:03:23 steamdeck systemd[1089]: Stopped target Bluetooth.
Oct 31 13:03:23 steamdeck systemd[1089]: Reached target Bluetooth.
Oct 31 13:10:09 steamdeck pipewire-pulse[1238]: mod.protocol-pulse: client 0x5572944ad4b0: send channel:4294967295 20, error -32: Broken pipe
Oct 31 13:11:17 steamdeck [131256]: Could not parse number of program headers from core file: invalid `Elf' handle
Oct 31 13:11:17 steamdeck systemd-coredump[131232]: [] Process 130828 (AppRun) of user 1000 dumped core.

Module /usr/bin/emulationstation without build-id.
Module /home/deck/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so with build-id 4ca6d734ad587cfa9>
Module linux-vdso.so.1 with build-id fc0b1d015333387da9503d91748546915bb5ffb1
Module libnss_resolve.so.2 with build-id 45c3990437688b991b44b47ad80e69cbc790a661
Module libnss_mdns_minimal.so.2 with build-id 8eb55de0d3252a36920a5d74c2da924a902cfff4
Module libnss_mymachines.so.2 with build-id 1c377cb1c9751798d291f2a1c9905ce199c46abd
Module libFLAC.so.12 with build-id 1ed77e941a46d5d0550af4c61c3965aaecdcb33d
Module libasyncns.so.0 with build-id 3ed7e52f247b08f1dff19aef6a253ee4c5c785c0
Module libsndfile.so.1 with build-id 923361ca7a51d29651ef1e282559cbff70e31cde
Module libpulsecommon-16.1.so with build-id 17e5c781f557e60fbc789cb631816a4a29230f4a
Module libpulse.so.0 with build-id 0c1618cb1e11cc14128914e45965433374cbd10e
Module libpulse-simple.so.0 with build-id 7879cf719df0389789b262cf61606de309ebf227
Module libncursesw.so.6 with build-id b9917757481e6fa6097e2a1f31f5bb5eaf138c4e
Module libedit.so.0 with build-id 4b0babfcad161c2ad0af6e59e2493258db23a331
Module libelf.so.1 with build-id 5ba0792747dce7480d031794ed90c620da72dbff
Module libdrm_amdgpu.so.1 with build-id 84c55b198afb267724c1d704a4a6384458446e28
Module libdrm_radeon.so.1 with build-id 121a4f7e02db7ecdf8badd7aa64c6860aff121aa
Module libsensors.so.5 with build-id dc8b2c1c0d8525411aca188ea3cc3fb86d381d30
Module libLLVM-14.so with build-id 16d23f3ab6fb7269b2f13a9932a2a7ec4b1d5104
Module radeonsi_dri.so with build-id b32451043607982d62c807313e843eba0d1cf2e7
Module libxcb-xfixes.so.0 with build-id e231a68d00ee4cfa12a2c31e755a9e2c1e7be450
Module libxcb-sync.so.1 with build-id 13025f6de23a271636ad321c77eda98801e62e8e
Module libxcb-present.so.0 with build-id 8ed389d9cd6ad7110fbb00c93b32e0efaa71a6b1
Module libxcb-dri3.so.0 with build-id 088c750254cc139e7d62b8a3fc7795a138447ccf
Module libxshmfence.so.1 with build-id 132b07a9077d5068fc07934d2a447b03c35a5f55
Module libXxf86vm.so.1 with build-id b0dccf26256706727cd89edf8a562618d754b6ee
Module libxcb-dri2.so.0 with build-id 7bde0abc84135ae6258a8d1d130864071c2cc327
Module libX11-xcb.so.1 with build-id f92352eae0a30aea89d11beb22367fa985288925
Module libxcb-glx.so.0 with build-id 71d5b6691f53a235696da49ffa2178d643ecc228

[matveysiniy]

Hello. Found a stress test on the internet for an internet browser that reboots the graphics processor in the process. Could not successfully complete it from chrome and firefox, the screen freezes and goes out in the process, the test ends differently but obviously fails. When I checked the log through journalctl > mylog.txt, found the error gfx_0.0.0.0.0 timeout. Could you please try running this test from under steam deck and share the results? https://testdrive-archive.azurewebsites.net/graphics/webglstresstest/
Why would I want that?
In order to diagnose the video controller in steam deck this way. Since I haven't had any gpu issues in games, I'm wondering if this test can be performed successfully on other serviceable devices. Either I still have a problem with the gpu chip that hasn't manifested itself yet

[Rodomar705]

matveysiniy původně napsal:

Hello. Found a stress test on the internet for an internet browser that reboots the graphics processor in the process. Could not successfully complete it from chrome and firefox, the screen freezes and goes out in the process, the test ends differently but obviously fails. When I checked the log through journalctl > mylog.txt, found the error gfx_0.0.0.0.0 timeout. Could you please try running this test from under steam deck and share the results? https://testdrive-archive.azurewebsites.net/graphics/webglstresstest/
Why would I want that?
In order to diagnose the video controller in steam deck this way. Since I haven't had any gpu issues in games, I'm wondering if this test can be performed successfully on other serviceable devices. Either I still have a problem with the gpu chip that hasn't manifested itself yet

It's just software, and yep, this causes an instant GPU crash since it rendering a corrupted OpenGL scene. Smart drivers just ignore the scene and proceed through, other are more sensitive and they can cause a driver crash. The real problem is that the driver sometimes do not recover from it, which is the problem. Nothing to do with hardware, don't worry.

[matveysiniy]

Rodomar705 původně napsal:

It's just software, and yep, this causes an instant GPU crash since it rendering a corrupted OpenGL scene. Smart drivers just ignore the scene and proceed through, other are more sensitive and they can cause a driver crash. The real problem is that the driver sometimes do not recover from it, which is the problem. Nothing to do with hardware, don't worry.

Thank you. You are the only one who replied to this post, I posted it on several forums and people ignored it for some reason. Perhaps they were confused because they couldn't successfully perform this stress test on their serviceable decks

[deaddoof]

johangp19 původně napsal:

Okay im back!!! So.. Octopath 1 just crashed, took around 2hrs this time, weird. Here s my log:

(deck@steamdeck ~)$ journalctl
Oct 31 13:03:23 steamdeck pipewire[1236]: spa.alsa: hw:acp5x,1: (0 missed) snd_pcm_avail after recover: Broken pipe
Oct 31 13:03:23 steamdeck systemd[1089]: Stopped target Bluetooth.
Oct 31 13:03:23 steamdeck systemd[1089]: Reached target Bluetooth.
Oct 31 13:10:09 steamdeck pipewire-pulse[1238]: mod.protocol-pulse: client 0x5572944ad4b0: send channel:4294967295 20, error -32: Broken pipe
Oct 31 13:11:17 steamdeck [131256]: Could not parse number of program headers from core file: invalid `Elf' handle
Oct 31 13:11:17 steamdeck systemd-coredump[131232]: [] Process 130828 (AppRun) of user 1000 dumped core.

Module /usr/bin/emulationstation without build-id.
Module /home/deck/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so with build-id 4ca6d734ad587cfa9>
Module linux-vdso.so.1 with build-id fc0b1d015333387da9503d91748546915bb5ffb1
Module libnss_resolve.so.2 with build-id 45c3990437688b991b44b47ad80e69cbc790a661
Module libnss_mdns_minimal.so.2 with build-id 8eb55de0d3252a36920a5d74c2da924a902cfff4
Module libnss_mymachines.so.2 with build-id 1c377cb1c9751798d291f2a1c9905ce199c46abd
Module libFLAC.so.12 with build-id 1ed77e941a46d5d0550af4c61c3965aaecdcb33d
Module libasyncns.so.0 with build-id 3ed7e52f247b08f1dff19aef6a253ee4c5c785c0
Module libsndfile.so.1 with build-id 923361ca7a51d29651ef1e282559cbff70e31cde
Module libpulsecommon-16.1.so with build-id 17e5c781f557e60fbc789cb631816a4a29230f4a
Module libpulse.so.0 with build-id 0c1618cb1e11cc14128914e45965433374cbd10e
Module libpulse-simple.so.0 with build-id 7879cf719df0389789b262cf61606de309ebf227
Module libncursesw.so.6 with build-id b9917757481e6fa6097e2a1f31f5bb5eaf138c4e
Module libedit.so.0 with build-id 4b0babfcad161c2ad0af6e59e2493258db23a331
Module libelf.so.1 with build-id 5ba0792747dce7480d031794ed90c620da72dbff
Module libdrm_amdgpu.so.1 with build-id 84c55b198afb267724c1d704a4a6384458446e28
Module libdrm_radeon.so.1 with build-id 121a4f7e02db7ecdf8badd7aa64c6860aff121aa
Module libsensors.so.5 with build-id dc8b2c1c0d8525411aca188ea3cc3fb86d381d30
Module libLLVM-14.so with build-id 16d23f3ab6fb7269b2f13a9932a2a7ec4b1d5104
Module radeonsi_dri.so with build-id b32451043607982d62c807313e843eba0d1cf2e7
Module libxcb-xfixes.so.0 with build-id e231a68d00ee4cfa12a2c31e755a9e2c1e7be450
Module libxcb-sync.so.1 with build-id 13025f6de23a271636ad321c77eda98801e62e8e
Module libxcb-present.so.0 with build-id 8ed389d9cd6ad7110fbb00c93b32e0efaa71a6b1
Module libxcb-dri3.so.0 with build-id 088c750254cc139e7d62b8a3fc7795a138447ccf
Module libxshmfence.so.1 with build-id 132b07a9077d5068fc07934d2a447b03c35a5f55
Module libXxf86vm.so.1 with build-id b0dccf26256706727cd89edf8a562618d754b6ee
Module libxcb-dri2.so.0 with build-id 7bde0abc84135ae6258a8d1d130864071c2cc327
Module libX11-xcb.so.1 with build-id f92352eae0a30aea89d11beb22367fa985288925
Module libxcb-glx.so.0 with build-id 71d5b6691f53a235696da49ffa2178d643ecc228

Ahhh. I see dump info

sudo coredumpctl info 130828

sudo coredumpctl debug 130828

Once you are in gdb, enter "bt"

I might recommend you make a new thread and report the bug to Valve support. Your crash is probably different and easier to fix than the bug here.

If you reboot, you might have grab the wrong bug. If so, you now have two bugs.

The way jounalctl -b flag works..

0 is the current boot
-1 is the previous boot log
-2 is two boots ago.

[deaddoof]

matveysiniy původně napsal:

Rodomar705 původně napsal:

It's just software, and yep, this causes an instant GPU crash since it rendering a corrupted OpenGL scene. Smart drivers just ignore the scene and proceed through, other are more sensitive and they can cause a driver crash. The real problem is that the driver sometimes do not recover from it, which is the problem. Nothing to do with hardware, don't worry.

Thank you. You are the only one who replied to this post, I posted it on several forums and people ignored it for some reason. Perhaps they were confused because they couldn't successfully perform this stress test on their serviceable decks

Yea. You should list your entire environment which also include the webbrowser. Listing your entire environment including version numbers matter because they need to copy your steps.

Sometimes, bugs reproduction can be a pain like the bug in this whole thread. You have to communicate every detail.