search

madMAx43v3r / chia-plotter

Apache License 2.0
2.27k stars 664 forks source link

MadMax stops working #517

Open Elerong opened 3 years ago

Elerong commented 3 years ago

I had MadMax fully working.

Yesterday my windows has corrupted and I had to reinstall everything.

Installed all C++ packages 2015 and many others. It is fresh windows installation from USB with latest ISO. Installed python.

No other software has been installed. Previously I had version 03 working. Now none of the versions work.

Problem is: The MadMax software stops in Phase 1 and does not get past Table 4. It stops randomly between table 1-4. Many users have reported the same issue.

I believe it could be something to do with missing software that needs to be installed?

Any suggestions?

All I did is reinstall Windows.

nflows commented 3 years ago

I have exactly the same problem. Only on Windows 10 machine.

MrMorcego commented 3 years ago

Same problem Ubuntu 20.04. It stops oh P1 Table 3 sometimes is able to complete P1 T3 but it stops on P1T4 any solution?

liquidone commented 3 years ago

I am experiencing P1 crashes with Madmax on Ubuntu 20.04 as well using defaults. Official plotter works fine.

Elerong commented 3 years ago

I have an UPDATE FOR YOU GUYS. It is all working now!

What I have done:

it could be that virtualisation is required for the plotter or I had poor memory optimisation and caused the plotter to crashed. Could be that WSL package has helped it. I cannot tell which one it was.

You guys can start it by setting the RAM to 2666 or 2133 default and see if it works. If not then try enabling Virtualisation. Install docker and WSL2?

not sure which one caused it to work but I am past table 5 and it is working now!

moracabanas commented 3 years ago

In my case I have docker but I'm not using it. I run it from the next batch script:

.\chia_plot.exe -n 30 -r 6 -p <examplekey1> -f <examplekey2> -t <DISKA> -d <DISKB>

I just run it and minimize window. Sometimes runs ok indefinitely, sometimes gets stuck and you have to actually click the window and press any key so the shell shows a overtime amount of seconds for the last phase and continue plotting. Weird

moracabanas commented 3 years ago

This is an example image As you can see I started the last script then I check my computer and it stoped at Table 4 for some reason. I press (Enter or whatever) then it prints the Table 5 line and continues plotting

moracabanas commented 3 years ago

In my case I have docker but I'm not using it. I run it from the next batch script:

.\chia_plot.exe -n 30 -r 6 -p <examplekey1> -f <examplekey2> -t <DISKA> -d <DISKB>

I just run it and minimize window. Sometimes runs ok indefinitely, sometimes gets stuck and you have to actually click the window and press any key so the shell shows a overtime amount of seconds for the last phase and continue plotting. Weird

After some research it seems to be caused by a windows thing called QuickEdit Mode described on the next issues: https://superuser.com/questions/312132/command-prompt-hangs-until-keypress https://stackoverflow.com/questions/591047/command-line-windows-hanging-in-rdp-windows https://serverfault.com/questions/314194/why-does-windows-command-prompt-stalls-until-a-key-is-pressed-when-executing-lon

Hope it works for your case

madMAx43v3r commented 3 years ago

I think on table 5 and 6 it needs the most RAM disk space, so you could be running out of RAM causing swap usage which will slow things down a lot...

nflows commented 3 years ago

If your "CMD Window" get stuck - try to right click your cmd window on the topmost left (where the icon is) then click settings, In the 2nd area you see a checkbox "Quick-Edit-Mode". Uncheck it - it wont get stuck anymore...

moracabanas commented 3 years ago

If your "CMD Window" get stuck - try to right click your cmd window on the topmost left (where the icon is) then click settings, In the 2nd area you see a checkbox "Quick-Edit-Mode". Uncheck it - it wont get stuck anymore...

That is what was happening on my case, thanks for making clear to get a solution for everyone using windows

sved-SI commented 3 years ago

I have a problem too. Sometimes he makes one plot (but is INVALID in Hpool), then gets stuck. On sreeen show "press any key ...." Pressing the key, closes the window, and all is end. I tested RAM, NVME, nowhere to see problems, free place in all disk ... what could be wrong. For info, I also have Intelnuc i7, on which slowly but successfully make plots that are valid on hpool. The key is the same. thanks for the help

my hardware: Processor AMD Ryzen 9 5900X 12-Core Processor, 3701 Mhz, 12 Core(s), 24 Logical Processor(s) Installed Physical Memory (RAM) 32,0 GB Temp1: Samsung EVO Plus 2Tb Temp2: Samsung Evo 1Tb HDD: 4Tb

image

Xyber99 commented 3 years ago

I have a problem too. Sometimes he makes one plot (but is INVALID in Hpool), then gets stuck. On sreeen show "press any key ...." Pressing the key, closes the window, and all is end. I tested RAM, NVME, nowhere to see problems, free place in all disk ... what could be wrong. For info, I also have Intelnuc i7, on which slowly but successfully make plots that are valid on hpool. The key is the same. thanks for the help

my hardware: Processor AMD Ryzen 9 5900X 12-Core Processor, 3701 Mhz, 12 Core(s), 24 Logical Processor(s) Installed Physical Memory (RAM) 32,0 GB Temp1: Samsung EVO Plus 2Tb Temp2: Samsung Evo 1Tb HDD: 4Tb

image

I had the same problem and solved it. First I removed quick edit, no change. Then I restarted the computer, reduced the number of threads from 16 (my max), to 14. Now is plotting for 24 hours without any error. You should try that.

sved-SI commented 3 years ago

SOLVED! Ryzen 7 5900 and DDR4 3600 : they are not best friends obviously I change ram speed to 3200 and all work without any problem....

Thank you all for help and hopefully a better price for XCH ! Regards from Ljubljana!

ericmagee commented 3 years ago

I have an UPDATE FOR YOU GUYS. It is all working now!

What I have done:

  • Enabled Virtualisation on my PC
  • Overclocked my RAM to 4400MhZ
  • Installed Docker on my PC
  • Installed WSL update for Docker.

it could be that virtualisation is required for the plotter or I had poor memory optimisation and caused the plotter to crashed. Could be that WSL package has helped it. I cannot tell which one it was.

You guys can start it by setting the RAM to 2666 or 2133 default and see if it works. If not then try enabling Virtualisation. Install docker and WSL2?

not sure which one caused it to work but I am past table 5 and it is working now! THANK YOU ... THANK YOU!!! bumping my member down from 3600 to 3333 did the trick!!!! I'm back in business!!!
-- Ryzan 7 2700x 32GB DDR4 3600