Thanks, next time it does it I'll check the hardware and other logs.
FWIW, I've got a slew of errors logged in the event viewer > Windows Logs > System folder that look like this....
Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 4/10/2018 10:44:44 AM
Event ID: 10016
Task Category: None
Level: Error
Keywords: Classic
User: DESKTOP-92VAG0G\Scott
Computer: DESKTOP-92VAG0G
Description:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160}
and APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
to the user DESKTOP-92VAG0G\Scott SID (S-1-5-21-3698288594-2598943044-754572877-1004) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
A question.... How would I go about finding out if the APP ID is for the app that keeps crashing. The APP ID NUMBER is always the same {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} But I have no idea how to find out what program uses that app id. It's also always the same error code in the log, ie. 10016
FWIW, these errors pre-date the installation of the new graphics card. I believe I may have found a way to stop these errors, I found it here....
https://social.technet.microsoft.com/Forums/en-US/7742f039-70af-49b5-b37e-9597da743971/event-id-10016-the-applicationspecific-permission-settings-do-not-grant-local-activation?forum=win10itprogeneral
It's the 3rd post down from the top... "How to assign permissions"
I think I may give this a try, what do you think...??