1.1.6 Plotting hangs with "matches do not match with number of write entries" error

6 out of 8 new plotting processes started with 1.1.6 version hanged and showed no progress, but burn CPU. I used Process monitor verify that hanged plotters don’t issue and disk IO.

Here is how it looks in process explorer:

Here is stack dump of a hanging process:

Stack dump
0x0000000000000000
chiapos.cp37-win_amd64.pyd+0x2460a
chiapos.cp37-win_amd64.pyd+0x29ca2
chiapos.cp37-win_amd64.pyd!PyInit_chiapos+0x1203
chiapos.cp37-win_amd64.pyd!PyInit_chiapos+0x12f61
chiapos.cp37-win_amd64.pyd!PyInit_chiapos+0x12ff4
chiapos.cp37-win_amd64.pyd+0xb482
python37.dll!PyMethodDef_RawFastCallKeywords+0x34d
python37.dll!PyCFunction_FastCallKeywords+0x2a
python37.dll!PyArg_UnpackStack+0x4bb
python37.dll!PyEval_EvalFrameDefault+0xf98
python37.dll!PyEval_EvalCodeWithName+0x1ac
python37.dll!PyArg_UnpackStack+0x48c
python37.dll!PyEval_EvalFrameDefault+0x73e
python37.dll!PyEval_EvalCodeWithName+0x1ac
python37.dll!PyFunction_FastCallDict+0x1cf
python37.dll!PyEval_EvalFrameDefault+0x3e50
python37.dll!PyEval_EvalCodeWithName+0x1ac
python37.dll!PyFunction_FastCallDict+0x1cf
python37.dll!PyEval_EvalFrameDefault+0x3e50
python37.dll!PyEval_EvalCodeWithName+0x1ac
python37.dll!PyFunction_FastCallDict+0x1cf
python37.dll!PyUnicode_RPartition+0xc83
python37.dll!PyEval_EvalFrameDefault+0x2796
python37.dll!PyArg_UnpackStack+0x371
python37.dll!PyEval_EvalFrameDefault+0x154
python37.dll!PyEval_EvalCodeWithName+0x1ac
python37.dll!PyArg_UnpackStack+0x48c
python37.dll!PyEval_EvalFrameDefault+0x154
python37.dll!PyEval_EvalCodeWithName+0x1ac
python37.dll!PyArg_UnpackStack+0x48c
python37.dll!PyEval_EvalFrameDefault+0x154
python37.dll!PyEval_EvalCodeWithName+0x1ac
python37.dll!PyFunction_FastCallDict+0x1cf
python37.dll!PyUnicode_RPartition+0xc83
python37.dll!PyEval_EvalFrameDefault+0x2796
python37.dll!PyEval_EvalCodeWithName+0x1ac
python37.dll!PyFunction_FastCallDict+0x1cf
python37.dll!PyObject_Call_Prepend+0x69
python37.dll!PyThreadState_GetDict+0x3d9
python37.dll!PyObject_FastCallKeywords+0x176
python37.dll!PyArg_UnpackStack+0x4bb
python37.dll!PyEval_EvalFrameDefault+0x73e
python37.dll!PyArg_UnpackStack+0x371
python37.dll!PyEval_EvalFrameDefault+0x73e
python37.dll!PyEval_EvalCodeWithName+0x1ac
python37.dll!PyEval_EvalCodeEx+0x9b
python37.dll!PyEval_EvalCode+0x2d
chia.exe+0x2442
chia.exe+0x273e
chia.exe+0x88b9
KERNEL32.DLL!BaseThreadInitThunk+0x14
ntdll.dll!RtlUserThreadStart+0x21

There is nothing in the logs of failing plotters, just shows last operation and nothing else. But one of the plotter somehow managed to write an error to its log:

Total matches: 4295398282
Caught plotting error: Matches do not match with number of write entries 4295398282 4295398120
[17364] Failed to execute script chia
Traceback (most recent call last):
  File "chia\cmds\chia.py", line 81, in <module>
  File "chia\cmds\chia.py", line 77, in main
  File "click\core.py", line 829, in __call__
  File "click\core.py", line 782, in main
  File "click\core.py", line 1259, in invoke
  File "click\core.py", line 1259, in invoke
  File "click\core.py", line 1066, in invoke
  File "click\core.py", line 610, in invoke
  File "click\decorators.py", line 21, in new_func
  File "chia\cmds\plots.py", line 135, in create_cmd
  File "chia\plotting\create_plots.py", line 176, in create_plots
RuntimeError: Unknown exception
1 Like

I’ve never seen that error before. Are you sure the machine is stable? Passes memtest? passes prime95/mprime overnight?

You are right! Together with 1.1.6 update I swapped my RAM modules and one of them turned out to be defective.

I have the same problem. i will make memtest86 but it will take around 11 hours :frowning: