After a crash, we like to see DIAGNOSTICS, gotten by expanding the HELP dropdown menu and selecting SAVE DIAGNOSTICS.  But the crash diagnostics are not always helpful, as diagnostic’s metrics stop when the CPU card crashes and when the redundant CPU takes over, now it starts to report to the diagnostic’s logging.Say a frame is using P2 as its active CPU and that card crashes, now P1’s card boots and starts its logging.  When you pull the diagnostics, it is reporting P1’s status … starting with the taking over from P2.  Not helpful if you want to know why P2 crashed in the first place.But wait … not as bad as you think… When you can, pull P1 and let P2 boot up and take its diagnostics.  The card stores quite a large amount of data and when it crashes, it spits out info that’s helpful to see why that happened.  So let the diagnostics load from the card and if you feel insecure about P2’s ability to perform, pull it and let P1 do its thing.BTW, if the Event Log is running on the PC, then you CAN get a historic log and it might be helpful for our engineers to find some info to explain the crash, but they really like the Diagnostic package best.