If the problem disappears after restarting, it is caused by memory allocation failure.
You can relatively easily set up a script in a way that Zorro needs vast amounts of memory, especially in TICKS mode and with small timeframes or long test periods. After a couple of runs, the memory on your PC becomes fragmented. This means although enough memory is available, it can not be allocated in the size needed for the simulation.
Zorro won't crash when memory allocation fails, but you'll see a Error 060 message. This is different in the charting library used by Zorro. It has no safeguard against memory fragmentation, but just crashes in such a case. In both cases you need to restart Zorro.