What firmware version are you on? We did have some improvements in later versions (latest is 2.0.1 from memory) to reduce resets / lock-ups.
But it sounds like the ChipSHOUTER is locking up or resetting. We’ve found that does happen in various setting combinations, which is why we recommend recovering via the reset method when needed. More often we see the ChipSHOUTER itself reset.
When you get that exception is anything unusual happening, what are you sending it?
Generally we recommend keeping as much state “externally” as possible so you can recover as you suggest, so that might be the “best” way. The ChipSHOUTER was by design allowed to run in areas which can cause internal stability, as those “unstable” areas vary per unit. So rather than add artificial limitations we let you push the limits of it as far as possible (and beyond). The “safety limits” where damage occurs are nowhere near this, so basically there isn’t a risk of much beyond the annoyance of the lock-up/reset problem.
I’ll ping @Alex_Dewar if he’s seen this issue as well, maybe there is a better fix than I know of!