Farm error Farm crashed: Background task plotting-0 panicked Farm errored and stopped farm_index=0 error=Background task plotting-0 panicked

farm error,Windows gui show:

F\ [3.8t:

Farm crashed: Background task plotting-0 panicked

and log show:

2024-04-01T03:20:20.104701Z INFO Node: substrate: :sparkles: Imported #e[1;37m883456e[0m (0x66c7…0dd4)
2024-04-01T03:20:29.584487Z INFO Node: substrate: :zzz: Idle (27 peers), best: #883456 (0x66c7…0dd4), finalized #798553 (0x330f…3d9d), :arrow_down: 35.3kiB/s :arrow_up: 37.0kiB/s
2024-04-01T03:20:34.585859Z INFO Node: substrate: :zzz: Idle (27 peers), best: #883456 (0x66c7…0dd4), finalized #798553 (0x330f…3d9d), :arrow_down: 18.8kiB/s :arrow_up: 22.0kiB/s
2024-04-01T03:20:35.876958Z INFO Node: substrate: :sparkles: Imported #e[1;37m883457e[0m (0x1e31…7c30)
2024-04-01T03:20:38.278128Z INFO Node: substrate: :sparkles: Imported #e[1;37m883458e[0m (0x729a…a881)
2024-04-01T03:20:38.596244Z ERROR space_acres::backend::farmer: Farm errored and stopped farm_index=0 error=Background task plotting-0 panicked
2024-04-01T03:20:39.586884Z INFO Node: substrate: :zzz: Idle (27 peers), best: #883458 (0x729a…a881), finalized #798553 (0x330f…3d9d), :arrow_down: 27.4kiB/s :arrow_up: 62.8kiB/s
2024-04-01T03:20:39.986616Z INFO Node: substrate: :sparkles: Imported #e[1;37m883459e[0m (0x9018…0f66)
2024-04-01T03:20:40.959982Z ERROR jsonrpsee_core::client::async_client: [backend]: Networking or low-level protocol error: WebSocket connection error: connection closed
2024-04-01T03:20:40.971093Z WARN Node: sc_proof_of_time::source::gossip: Failed to send incoming message error=send failed because receiver is gone
2024-04-01T03:20:40.971119Z ERROR Node: sc_proof_of_time::source::gossip: Gossip engine has terminated
2024-04-01T03:20:40.971159Z ERROR Node: sc_service::task_manager: Essential task pot-gossip failed. Shutting down service.
2024-04-01T03:20:40.975696Z ERROR space_acres::backend: Failed to send run error notification error=send failed because receiver is gone
2024-04-01T03:20:41.024602Z INFO space_acres: Exiting space-acres 0.1.12 exit_status_code=Exit

Config: unchanged
CPU model and quantity: 5950x1
Number and size of memory modules: 8g2
Number of hard drives: 3.8t * 1
Problem description: Farming may crash after some time, while other machines with the same configuration and network can farm normally

Something bad must have happened before those log items, please upload the whole things somewhere like pastebin.com or gist.github.com

Here is the complete log

Looks like on Windows it doesn’t capture the full log with panic itself. Might be memory instability, you can check system log and check whether XMP is enabled in BIOS, it might be necessary to disable or to increase RAM voltage to stabilize it.

Same problem on my PC.

Environment:
Windows 11 23H2, Threadripper 16/32, RAM 128GB

Task:
.\subspace-farmer-windows-x86_64-skylake-gemini-3h-2024-mar-29.exe farm --farm-during-initial-plotting true --record-encoding-concurrency 5 path=E:\Subspace\farms_9,size=1000GB

Log:

Error: Background task plotting-0 panicked

2024-04-01T17:56:56.438432Z INFO {farm_index=0}: subspace_farmer::single_disk_farm::plotting: Plotting sector (89.10% complete) sector_index=834
2024-04-01T18:01:43.547938Z INFO {farm_index=0}: subspace_farmer::single_disk_farm::plotting: Plotting sector (89.21% complete) sector_index=835
2024-04-01T18:06:32.601558Z INFO {farm_index=0}: subspace_farmer::single_disk_farm::plotting: Plotting sector (89.32% complete) sector_index=836
2024-04-01T18:11:24.368846Z INFO {farm_index=0}: subspace_farmer::single_disk_farm::plotting: Plotting sector (89.42% complete) sector_index=837
2024-04-01T18:16:11.964063Z INFO {farm_index=0}: subspace_farmer::single_disk_farm::plotting: Plotting sector (89.53% complete) sector_index=838
2024-04-01T18:21:01.468039Z INFO {farm_index=0}: subspace_farmer::single_disk_farm::plotting: Plotting sector (89.64% complete) sector_index=839
2024-04-01T18:25:50.962761Z INFO {farm_index=0}: subspace_farmer::single_disk_farm::plotting: Plotting sector (89.74% complete) sector_index=840
thread 'thread ‘plotting-0.31plotting-0.24’ panicked at ’ panicked at crates\subspace-proof-of-space\src\chiapos\table.rscrates\subspace-proof-of-space\src\chiapos\table.rs::309309::4949:
:
index out of bounds: the len is 15113 but the index is 272043index out of bounds: the len is 15113 but the index is 18446744073709314967

stack backtrace:
note: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.
stack backtrace:
note: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.
2024-04-01T18:30:48.412295Z WARN {farm_index=0}: subspace_farmer::single_disk_farm::plotting: Failed to send sector index for initial plotting error=send failed because receiver is gone
2024-04-01T18:30:48.417932Z ERROR subspace_farmer::commands::farm: Farm exited with error farm_index=0 error=Background task plotting-0 panicked
Error: Background task plotting-0 panicked

Stack backtrace:
0:
1:
2:
3:
4:
5:
6: BaseThreadInitThunk
7: RtlUserThreadStart
PS C:\Subspace>

@micar your error may or may not be the same, but it was discussed on the forum multiple times: Thread 'plotting-1.1' panicked
Which is why I suggested checking memory/XMP above.