I had a similar issue with an HP Omen gaming rig I have. Fix was the same as the article but I put up with it for years.

Sometimes I would investigate but the monotony of tracing things in the Event Viewer and analysis was too much for my ADHD-addled brain. Enter Claude CLI and working through it with prompts plus allowing Claude to execute PowerShell to diagnose was painless and resolved the problem.