MCU 'eboard' shutdown: Rescheduled timer in the past

[RichJeffries]

Firstly, I love what you guys have done here!

Unfortunately, I haven't actually been able to print anything.
I've installed both the KlipperScreen and GuppyScreen variants - both installed without any problems, seemed perfectly functional and could even access the web interface.

However, whenever I try to print, after a few seconds it fails with the message:
MCU 'eboard' shutdown: Rescheduled timer in the past
Transition to shutdown state: MCU 'eboard' shutdown: Rescheduled timer in the past
This generally occurs when the micro-controller has been
requested to step at a rate higher than it is capable of
obtaining.

The first entry about this in the log shows:
MCU 'eboard' shutdown: Rescheduled timer in the past
clocksync state: mcu_freq=144000000 last_clock=71277897452 clock_est=(488.816 66260684261 144000763.373) min_half_rtt=0.000601 min_rtt_time=476.968 time_avg=488.815(902.473) clock_avg=66260684261.552(129956865499.910) pred_variance=398650861.428 clock_adj=(33.460 143999776.179)
Dumping serial stats: bytes_write=68826 bytes_read=60036 bytes_retransmit=0 bytes_invalid=0 send_seq=2627 receive_seq=2622 retransmit_seq=0 srtt=0.004 rttvar=0.001 rto=0.025 ready_bytes=49 stalled_bytes=21115

I've tried a couple of small files (1.5Mb - 8Mb) with the same problem.
I tried disabling the camera and streaming options.
Memory usage under GuppyScreen was 73%

I've attached the full log for review.
The printer.cfg has stepper settings at 16.

Does anyone know a way of fixing this?

Cheers
Rich
klipper.log