

I do agree that best solution is that we don’t need it.
Sadly bassed on what i hear, users are willing do Things on kernel level to cheat. Ie read/Write memory from a different program.
Youtube: Core dumped: can a gamer company really sabotage your PC? made a good video summarizing the issue.
I hope that a solution in some sense does not need to send more than som checksums that failed if there is a debug enabled, sign kernel modules that not trusted (ie. self sign), notify the program that hi there is a other program trying read your program’s memory or provided some restrictions memory space that even with debug enable you can’t read that space.



























I found that llms can be useful in troubleshooting.
Maybe start with comparing hardware sensor stats GPU/CPU temp/frequency/fan etc.
I think is useful to use a bleeding edge OS since what you are talking about, is a combination of kernel/drivers, user space tools and software.
Start with something low level maybe clpeak or as part of Phoronix Test Suite. A game is a complex software that touches many parts of a system, especially for laptops where some resources are shared.