Call Of Duty: WW2 Stuck on Black Screen, takes forever to reboot.

[Disavowed |W|]

I've noticed, but im unsure what causes it; that Often after loading into a Map. My Steam Deck OLed(512) will begin to experience Mild to Severe FrameRate hitches, that last anywhere from a fraction of a second to 3~ whole seconds.

After intentionally keeping an eye out for the "Symptoms" i was able to open up the Level 5 Statistics Overview while the hitching was happening (The Hitches are not Relegated to Just In-Game, they will also bog down the Steam Deck OS) When these hitches begin, two things Occur:

RAM and VRAM will experience a minor leak, i've seen my stats report having 18+ GBs of RAM somehow (This worrys me greatly) And then my GPU will begin to "Thermal Throttle" (The hottest my Chips get is 70 Degrees C. so this is not the case (I also use the old Fan Curve)) and it will begin using less and less Wattage, until the Screen goes Black, Audio cuts out, and i need to hold the Power Button down for a long time.

This is my only real issue.

and it doesnt just effect WW2, it Effects EVERY CoD Game in some way. For Instance: in Black Ops 1 on Call Of The Dead, if you look out towards Jugg, your frames tank to Below 30, same for looking out into the Courtyard in Vurruckt.

Other than these things giving me Mini Heart-Attacks thinking my Deck is Bricked.

So Far, my Needs have been Catered to so well, i passed my old LED Deck to my Cousin (I was sick over 2 christmases and Birthdays) and grabbed the OLED model because i knew it would be Phenomenal.

And so Far Both Me, and my Cousin are VERY IMPRESSED!

[Disavowed |W|]

Update: I just got the Hitching again. closing out on my own seems to fix the problem.

doesn't explain how a Device with 16Gbs of RAM somehow Reports using 8.1gbs of RAM and 13Gbs of VRAM. when im told supposedly they have to share the 16Gbs between themselves. and at most split it Half/Half.

Valve, you cheeky, lovable Shut-In Genius' (all of you) have you guys finally managed to make it possible to Download more RAM?

if anyone could do it, I'd believe you'd do it first!

[Disavowed |W|]

Another Update: Strangely, while the Screen is Black, Both Trackpads remain responsive.
i mean that they are still clicking, and delivering Haptic Responses as "Normal" but I Still cannot access menus, or do really anything once The Black Screen takes over.

once it goes black, it uh. doesn't go back... unless I keep the Power Button held down for like 10+ seconds. and no longer than the first "Flash" of a white (Maybe Salmon?) LED Indicator Light. too long and It shuts-down mid "Verifying Installation".

[Disavowed |W|]

I had initially believed this Bug was being brought-up whenever i was attempting to use only an 11W TDP.

TDP or GPU Speed Limits are not the root Cause.

it happened again while i was letting the Game pull whatever resources it wanted.

again, this began as slight frame hitchings that devolves into a Stuck Screen.

this time it was the "Exit Game" Pop-Up box

only Remedy is holding the Power Button. Once Again.

I am still uncertain what precicely is the Hang-Up.

doesnt appear to be Shaders, or Texture problems. map Geometry is unchanged, scripting works as intended. and Multiplayer still preforms well, even while undergoing the Framerate Hitching.

everything for lack of an Explaination; is working as intended.

until the RAM starts Self-Inflating and it kills itself by, what i assume is calling upon RAM addresses that simply do not exist.

[Disavowed |W|]

Every Time i open up my Performance Overlay.

I see my Deck using more RAM than it owns.

Every Time. Without Fail now.

Why?

it was running so well before!

[Disavowed |W|]

RAM looks Perfectly Fine in Menus.

Once loaded into a Game. RAM becomes Untethered.

Pre-Game Numbers look fine. Nothing out of the Ordinary. Unless you count the Steam Deck allowing more than 8 Gbs of RAM to be used By the CPU/GPU.

it Reports to have 10Gbs of VRAM and 6Gbs of RAM. ok. at least that's 16, the real number.

then by Round 3 on Grösten Haus, suddenly:

my RAM is at 7.2 GBS
and my VRAM at the same time Reports to be using 12.7! Gbs!

holy jumping Jehovah!

that got out of hand FAST!

[Disavowed |W|]

Strangely, Infinite Warfare has the same sort of "RAM Anomaly" where my Overlay will display that it is using more RAM than physically possible.

However, it is somehow, MORE STABLE. in that it hasn't crashed EVER, and it doesn't have Anywhere near the same stuttering Problems.

Hypothesis:

This is a problem with how The Proton Layer translates certain Older Direct-X functions. what functions Precisely, is still yet to be determined.

more findings will follow, as I begin to understand this problem better.

[Disavowed |W|]

Nevermind.

Infinite Warfare just gave me it's first crash.
unsure why the Steam OS Crash Reporter didnt seem to do anything even after i enabled it.

Same RAM ANOMALY, more than the 14.47gbs stated in the Setting's tab.

crashed after loading back into Zombies In SpaceLand (Previously Bug-Free) within about 20 seconds, strangely. the crash had the Repeating-Audio bug usually associated in my mind with Team Fortress 2 and connecting to a Lobby.

(Sp-sp-sp-SPY-A SPY-A SPY AROUND-- -- -- HERE!)

Very, Very Strange.

using Proton 8. i suppose i should mention, which was working Flawlessly.

but now it seems everything is becoming rapidly unstable for some reason.
I really wish i knew more about what was going on. but i simply Don't.
and all the recent Black-Screenings have me quite worried.

i keep hearing talks of people's Decks getting ruined in one way or another, and I really just want to ere on the side of Caution. is it really only me experiencing these issues?!

[deaddoof]

Originally posted by Disavowed |W|:

Strangely, Infinite Warfare has the same sort of "RAM Anomaly" where my Overlay will display that it is using more RAM than physically possible.

However, it is somehow, MORE STABLE. in that it hasn't crashed EVER, and it doesn't have Anywhere near the same stuttering Problems.

Hypothesis:

This is a problem with how The Proton Layer translates certain Older Direct-X functions. what functions Precisely, is still yet to be determined.

more findings will follow, as I begin to understand this problem better.

Applications overcommit ram all the time. Operating system will always have optimization to make sure the all active pages are in RAM, but unused ram are accounted for.

You can increase the graphic/main memory split in the bios, but I cannot think of ways to debug right now.

dmesg -T | egrep -i 'killed process'

You can run it after the crash to see whether your system is killing processes.

[Disavowed |W|]

Originally posted by deaddoof:

Originally posted by Disavowed |W|:

Strangely, Infinite Warfare has the same sort of "RAM Anomaly" where my Overlay will display that it is using more RAM than physically possible.

However, it is somehow, MORE STABLE. in that it hasn't crashed EVER, and it doesn't have Anywhere near the same stuttering Problems.

Hypothesis:

This is a problem with how The Proton Layer translates certain Older Direct-X functions. what functions Precisely, is still yet to be determined.

more findings will follow, as I begin to understand this problem better.

Applications overcommit ram all the time. Operating system will always have optimization to make sure the all active pages are in RAM, but unused ram are accounted for.

You can increase the graphic/main memory split in the bios, but I cannot think of ways to debug right now.

dmesg -T | egrep -i 'killed process'

You can run it after the crash to see whether your system is killing processes.

Alright then, thanks for the Insight! I'll keep on it just trying to narrow down what may be instigating the Crashes, outside of these Normal RAM Behavior.

[deaddoof]

Originally posted by Disavowed |W|:

Alright then, thanks for the Insight! I'll keep on it just trying to narrow down what may be instigating the Crashes, outside of these Normal RAM Behavior.

https://lwn.net/Articles/785947/

https://lwn.net/Articles/627419/

https://www.kernel.org/doc/gorman/html/understand/understand016.html

https://lwn.net/Articles/253361/

https://dev.to/yugabyte/mirage-of-memory-part-3-overcommit-5g84

You should check whether the OOM is running. OOM killing your processes isn't normal behavior. It is a system desperate to conserve enough resources.

[Disavowed |W|]

I really appreciate the Future Reading material! even if i dont parse much of it im sure this'll at least show me some Under-the-hood goings-on!

[deaddoof]

Originally posted by Disavowed |W|:

I really appreciate the Future Reading material! even if i dont parse much of it im sure this'll at least show me some Under-the-hood goings-on!

Nope. mostly basic OS stuff. Windows does this stuff too. This stuff is not enough to diagnosis problems.