What kind of expertise one should have to do that kind of debug? Windows driver developer? Or even someone who wrote firmware?
I wrote some embedded firmware for simpler ARM CPUs, but I have very little understanding of this technical explanation.
I feel like these kind of issues are guarded from ordinary developers by being too complex to understand, although it might just be me. May be if technical stack was more approachable, we would have more quality reports and workarounds? If there're 100 people in the world who could understand the problem, it's bad situation.
IMO, the hardest is to initially find the faulty subsystem, and then to find a suitable instrument to trace/debug it.
It's great if you have a working software which shows the possible culprit (as in this case), but often you have only vague guess what could be the reason, and you need to test everything one by one, write you own code, or sometimes use hardware probe.