Look, on the plus side the the Kernel loaded so the CP3 isn't fully hosed. So it may be able to be recovered and then the program checked for what could be causing the issue.

So advanced commands you can try in toolbox

ThreadPoolInfo - events are being blocked
ThreadPoolSize - change the size, WHEN we need more than 7 threads. Like a single S+ with 100 inputs.
SPLUSTasks - what is going on in S+
ListActiveModules



Debug Commands

DBGPKTTX/RX
Between TLDM and Logic

DEBUG
Between ESA/Cresenet and TLDM

SIGDEBUG
Prints out what S#P state of a signal on a device is

SPLUSDBGTX/RX
Shows packets between logic and S+


That *SHOULD* help ya.