Daria Schmidt

both of u are kinda right tbh

ok so liveness probes can kill a healthy but slow app, if describe shows Liveness probe failed events before restarts, increase initialDelaySeconds, or better, add a startupProbe so livenses only starts checking after the app is up.

lol same thing happened to me get the logs of the previous (crashed) container, not teh current one: [code] In describe, look at Last State: the Reason and Exit Code tell u a lot. OOMKilled / 137 is memory, Error / 1 is the app exiting,…

oh ive been there lol check Windows privacy settings: Settings Privacy & security Microphone . make sure microphone access is on, Let desktop apps access ur microphone is enabled, and the game isnt blocked. good luck man!

Is this a clean install on a wiped drive?

been there man my approach: make a restore point, download the previous driver pakcage sooo its ready, then try teh new one. if anything misbehaves, DDU and reinstall the old one. that makes updating a low risk experiment.