Hi Richard,
It does look indicative, however, we'd need to know:
1. Who is using all the RAM (i rebooted a Win10 box here and its base RAM usage was a bit over 3GB, so if your app chews up 3+GB the memory consumption is plausible)
2. What processes are using 80% of the CPU?
It is possible for a single NT Thread to use up a complete CPU (core not socket).
It is also possible for this to occur more than once.
If this happens less and less power is available for other requests, you process the requests more slowly. There are more concurrent requests being handled. Memory usage spirals out of control and the system will eventually crash - i've done it
So, I'd check, what processes are using the CPU (the CPU is definately a solid clue)
If it your APP, check via ProcExp what threads are running and if any threads have been running for a very long time (other than the base APP thread). This can be done in a production environment.
If security software is misbehaving, it will normally be the one wasting CPU or memory, not your app.
Regards
Bill