Print stopped for no apparent reason

[Oct_opus]

Hello everyone,

Last night I tried a 12h print on my duet 2 Wifi and for not apparent reason it just stoped.
I’v reformatted the SD card and ran the SD card test provided and the wiki but no errors was found.
If someone has an idea and could help that would be greatly appreciated, I'v tried looking online but haven't found any meaningful help.

Printer info:
Board: Duet 2 WiFi (2WiFi)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.1.1 (2020-05-19b2)

Here's the M122 output after the crash (I was sleeping during it):

=== RTOS ===
Static ram: 27980
Dynamic ram: 93952 of which 24 recycled
Exception stack ram used: 304
Never used ram: 8812
Tasks: NETWORK(ready,384) HEAT(blocked,1224) MAIN(running,1824) IDLE(ready,80)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 06:44:46 ago, cause: software
Last software reset at 2021-09-05 03:22, reason: Stuck in spin loop, spinning module GCodes, available RAM 8452 bytes (slot 3)
Software reset code 0x4083 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x200051f4 Task MAIN
Stack: 00457b03 0045b488 61030200 3f000000 3e49ba00 3edb6db7 b7b4d800 49742400 44fa0000 447a0000 447a0000 
Error status: 0
MCU temperature: min 50.5, current 51.0, max 57.6
Supply voltage: min 23.9, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2021-09-05 10:07:31
Cache data hit count 4294967295
Slowest loop: 356.64ms; fastest: 0.12ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 52.5ms, write time 0.0ms, max retries 4
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 15.69ms; fastest: 0.00ms
Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- WiFi -
Network state is active
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address b4:e6:2d:60:31:f9
WiFi Vcc 3.38, reset reason Unknown
WiFi flash size 4194304, free heap 20224
WiFi IP address 192.168.1.65
WiFi signal strength -56dBm, reconnections 0, sleep mode modem
Socket states: 0 4 0 0 0 0 0 0"

console.csv

Thank you

[jay_s_uk]

@oct_opus please update to the latest version 3.3.0

[Oct_opus]

@jay_s_uk I'm going to do that thanks. Do you know if a specific problem before that version that would have caused such problem ?

[jay_s_uk]

@oct_opus there have been many bugs fixed so it would be difficult to pinpoint

[deckingman]

@oct_opus It's good that you had the insight to run M122. Whilst I am no expert, this ought to be significant to someone like @dc42.

Last software reset at 2021-09-05 03:22, reason: Stuck in spin loop, spinning module GCodes, available RAM 8452 bytes (slot 3)

Hopefully updating the firmware as suggested by @jay_s_uk should fix it, but if not raise the issue again and post the M122 report again (Run M122 as soon as you can after the fault happens and certainly without cycling power).

[Oct_opus]

@deckingman Yes, I wonder what would cause this error to appear. I will update the firmware and if it happens again ill post the G-code along with it

[Phaedrux]

Post your config.g as well as the M122 if it happens again on 3.3 please.