I got the idea to investigate this from @Mario_Limonciello 's bug here , then running the script he suggested here ) helped me reproduce the issue with logs and test the replacement firmware. Thanks for the guidance @Mario_Limonciello , I really appreciate it!
