Nice work!
Do not forget Reliability History/Monitor.
I would start looking in Process Explorer (Microsoft, free) to learn more about what all is running on my PC.
https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer
Objective being to determine is there are any other particular processes involved. May or may not be EasyAntiCheat related.
No need to take any immediate actions at first. Simply get a sense of what all is running and what each process actually is.
Any process that is not immediately identifiable should be researched to learn its' source and function(s).
I would also look in Task Scheduler for any triggers related to Software Protection Service or anything EasyAntiCheat related.
Something started or stopped that leads to system instability and the resulting crashes during that 5 - 15 minuted time period.
I would not expect any rules/triggers that intentionally "crash" the system. However, I can envision some buggy, corrupted, or mis-configured trigger resulting in a crash be the crash immediate or delayed....
Plus there is always the option to use PowerShell to search the EventViewer logs for entries with some specific word, code, etc..
Do not forget Reliability History/Monitor.
I would start looking in Process Explorer (Microsoft, free) to learn more about what all is running on my PC.
https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer
Objective being to determine is there are any other particular processes involved. May or may not be EasyAntiCheat related.
No need to take any immediate actions at first. Simply get a sense of what all is running and what each process actually is.
Any process that is not immediately identifiable should be researched to learn its' source and function(s).
I would also look in Task Scheduler for any triggers related to Software Protection Service or anything EasyAntiCheat related.
Something started or stopped that leads to system instability and the resulting crashes during that 5 - 15 minuted time period.
I would not expect any rules/triggers that intentionally "crash" the system. However, I can envision some buggy, corrupted, or mis-configured trigger resulting in a crash be the crash immediate or delayed....
Plus there is always the option to use PowerShell to search the EventViewer logs for entries with some specific word, code, etc..