Open MrMrRubic opened 1 year ago
Hmm yeah, windows doesn't show the error...
If I had to guess, not enough free space on P ?
Make sure to delete left-over files in -t
and -2
after a crash
hm, it shouldn't. P: (-t) have 528gb available before a plot and k32 should only need about 220(?), but i'll run it again to double check.
P: (-t) have 405gb available after the crash, R: (-2) have 69.9gb available. I can't see anything in the event viewer.
Try latest version, it should display an error message.
No error message in the output log.
Hmm dang, then it seems like it's being killed by the OS... which probably means not enough RAM.
I'd assume RAM as well, but watching it live it have about 8gb available, so i can't see how it could run out.
I had a friend test with my keys and it works on his system, so there's got to be someting wrong with my setup. I'm gonna reinstall to Windows 2022 this weekend (would change to some kind of linux, but i have a 12tb storage space i can't easily migrate), so i'll update on whether there's still an issue then.
Better try Linux first
What happened?
When trying to use:
-C 2
and up, the plotter crashes without any error or output to the log.My server has 128gb ram, of which 110g is used for ramdisk. I was watching the memory during the crash, and it never went over 120gb used in total (8gb available)
Version
Gigahorse CPU-plotter v2.0.0-6ddb7b
What platform are you using?
Windows server 2019, with all the latest updates
What ui mode are you using?
CLI
Relevant log output