Plotting Error

[pieterhelsen]

Hi everyone,

Just started plotting today, but can't seem to move past Table 2 or 3. I keep running into this plotting error:

	Bucket 127 uniform sort. Ram: 4.440GiB, u_sort min: 2.250GiB, qs min: 0.563GiB.
	Total matches: 4294735984
Caught plotting error: Matches do not match with number of write entries 4294735984 4294735597
[6500] Failed to execute script chia
Traceback (most recent call last):
  File "src\cmds\chia.py", line 80, in <module>
  File "src\cmds\chia.py", line 76, 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 "src\cmds\plots.py", line 134, in create_cmd
  File "src\plotting\create_plots.py", line 176, in create_plots
RuntimeError: Unknown exception

First two times the error occurred was at the end of Table 2. Third time was at the end of Table 3.
I started a fresh plot every time, making sure to remove the abandoned plot files from previous attempts.

I'm plotting on Windows 10, from the GUI using a 1TB M.2 NVMe drive with the following settings:

Starting plotting progress into temporary dirs: F:\chia and F:\chia
ID: 9083f6a3a22225a13a307ac91dcafe0c3362d3adafb98693ef29d959153d5e42
Plot size is: 32
Buffer size is: 4608MiB
Using 128 buckets
Using 2 threads of stripe size 65536

Any tips would be greatly appreciated!

[pieterhelsen]

Did a full reinstall of Chia, throwing away all config files in c:\Users\MY-USER\.chia; no such luck.
Issue happened again at the end of Computing Table 4.

[pieterhelsen]

@onemoretime1996 on Keybase pointed me in the direction of a possible hardware issue. Specifically disk, RAM or cooling.

My CPU is liquid cooled and not overclocked, so I ruled that out. A quick check disk on Windows revealed no errors, so I did a check of my RAM memory (using the Windows Memory Diagnostic tool) and found some issues with one of my RAM sticks.

After having taken out the stick, I am now running the plotter again to see if that fixes things.

[pieterhelsen]

Issue has been resolved by taking out the faulty stick of RAM.