Bram M.

@loose probe 1kp yesss added a healthcheck and depends on so the app waits for the database, plus a restart policy. Deploys no longer cause 502s. Appreciate the checklist. owe u a beer 🍺

this... so much this hope that helps :)

hmmm for me it was the cable. swapped it and boom, fixed. any update on this? good luck man!

hmmmm ok spent my entire lunch break on limiter and im still not done what am i doing wrong??

ahh classic itnerrupt moderation tweaks can lower latency slightly but increase CPU usage... the difference is usually small.. ;) id only test it if uve ruled out bigger issues. good luck man!

hmm idk idk man that sounds like bad advice tbh idk maybe im wrong lol

+1 same here lmk how it goes

lol same thing happened to me also turn off any GPU overclock or undervolt profile, including factory "OC mode" in teh vendor app. A new driver can expose an undervolt that was only barely stable before.

wait do you see Event ID 4101 in the System log at teh same times as the black screens?

as a stopgap, netsh wlan show interfaces tells you teh state after waking, and restarting the WLAN service (net stop wlansvc then net start wlansvc in an admin terminal) is quicker than a reboot. worked for me anyway 🤷