Dual Xeon on Windows version doesn't work (kills process)

[Hedonay]

So I'm using dual Xeon (8 cores, 16 threads each) server with 64G of ram and running Windows 2019 server. I start it with the following command (alpha version 0.2):

.\chia_plot.exe -p "key" -f "key" -n 1 -r 24 -u 7 -t E:\directory\ -d D:\directory\

What I get as a result is:

Final Directory: D:\directory\
Number of Plots: 1
Process ID: 7128
Number of Threads: 24
Number of Buckets: 2^7 (128)

And after that process is killed and does not continue.

I tried with lower number of threads (went even down to 4).

Was looking for help and got same configuration from a friend with same end result. Process killed and he's also not able to find a way to make it work.

Any ideas?

[tylerpuig]

Having this same issue with dual Xeons (8 cores as well).

I have already installed C++ redistributable.

[dasfliege]

Same problem here. Tried it on natively installed windows server 2019 on dual xeon but also on a windows 10 VM running on an ESX with dual xeon. Both have exactly the same issue.

[tigermumu]

Same problem... Tried everything... Still not worked

[AmA-sud]

same issue here , dual xeon and having the same problem, process starts then get killed,

pulled this error from the event viewer:

Faulting application name: chia_plot.exe, version: 0.0.0.0, time stamp: 0x60c180f8 Faulting module name: ucrtbase.dll, version: 10.0.17763.1490, time stamp: 0x48ac8393 Exception code: 0xc0000409 Fault offset: 0x000000000006e77e Faulting process id: 0x518 Faulting application start time: 0x01d75de5899c5a7d Faulting application path: C:\users\xxx\desktop\madmax\chia_plot.exe Faulting module path: C:\Windows\System32\ucrtbase.dll Report Id: 912d984b-0dad-4aa3-9572-1fbb58cbd574 Faulting package full name: Faulting package-relative application ID:

[jielee770]

same issue here , dual xeon cpu

Faulting application name: chia_plot.exe, version: 0.0.0.0, time stamp: 0x60c180f8 Faulting module name: ucrtbase.dll, version: 10.0.19041.546, time stamp: 0x43cbc11d Exception code: 0xc0000409 Fault offset: 0x000000000007287e Faulting process id: 0x2d18 Faulting application start time: 0x01d75de8ebbb75b7 Faulting application path: D:\chia_plotter\madMAx43v3r_chia-plotter_win_build_v0.0.2-alpha\chia_plot.exe Faulting module path: C:\Windows\System32\ucrtbase.dll Report Id: b227c3c3-3bbd-4489-b9a9-f35462ed47f0 Faulting package full name: Faulting package-relative application ID:

[stotiks]

Check this https://github.com/stotiks/chia-plotter/releases/tag/v0.0.3-alpha

On Thu, Jun 10, 2021 at 2:17 PM jielee770 @.***> wrote:

same issue here , dual xeon cpu

Faulting application name: chia_plot.exe, version: 0.0.0.0, time stamp: 0x60c180f8 Faulting module name: ucrtbase.dll, version: 10.0.19041.546, time stamp: 0x43cbc11d Exception code: 0xc0000409 Fault offset: 0x000000000007287e Faulting process id: 0x2d18 Faulting application start time: 0x01d75de8ebbb75b7 Faulting application path: D:\chia_plotter\madMAx43v3r_chia-plotter_win_build_v0.0.2-alpha\chia_plot.exe Faulting module path: C:\Windows\System32\ucrtbase.dll Report Id: b227c3c3-3bbd-4489-b9a9-f35462ed47f0 Faulting package full name: Faulting package-relative application ID:

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/madMAx43v3r/chia-plotter/issues/126#issuecomment-858535118, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALGV2WBUJJWJQJUM4KNM4ADTSCNMHANCNFSM46OBI2VA .

[Hedonay]

Check this https://github.com/stotiks/chia-plotter/releases/tag/v0.0.3-alpha …

Will do right away! Reporting back asap!

[Hedonay]

still have the same problem...

Using: .\chia_plot.exe -p "key" -f "key" -n 1 -r 24 -u 7 -t E:\ -d D:\

Getting:

Final Directory: D:\
Number of Plots: 1
Process ID: 8364
Number of Threads: 24
Number of Buckets: 2^7 (128)

And this is what Event Viewer is giving me:

Faulting application name: chia_plot.exe, version: 0.0.0.0, time stamp: 0x60c1f35c
Faulting module name: ucrtbase.dll, version: 10.0.17763.1490, time stamp: 0x48ac8393
Exception code: 0xc0000409
Fault offset: 0x000000000006e77e
Faulting process id: 0x1b90
Faulting application start time: 0x01d75deb424c3e63
Faulting application path: C:\Users\Administrator\Desktop\MadMaxPlotter\chia_plot.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report Id: 081e3fbd-a84d-4023-8408-f77b8d384685
Faulting package full name: 
Faulting package-relative application ID: 

Did others try it too?

[jielee770]

still have the same problem...

Using: .\chia_plot.exe -p "key" -f "key" -n 1 -r 24 -u 7 -t E:\ -d D:\

Getting:

Final Directory: D:\
Number of Plots: 1
Process ID: 8364
Number of Threads: 24
Number of Buckets: 2^7 (128)

And this is what Event Viewer is giving me:

Faulting application name: chia_plot.exe, version: 0.0.0.0, time stamp: 0x60c1f35c
Faulting module name: ucrtbase.dll, version: 10.0.17763.1490, time stamp: 0x48ac8393
Exception code: 0xc0000409
Fault offset: 0x000000000006e77e
Faulting process id: 0x1b90
Faulting application start time: 0x01d75deb424c3e63
Faulting application path: C:\Users\Administrator\Desktop\MadMaxPlotter\chia_plot.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report Id: 081e3fbd-a84d-4023-8408-f77b8d384685
Faulting package full name: 
Faulting package-relative application ID: 

Did others try it too?

Faulting application name: chia_plot.exe, version: 0.0.0.0, time stamp: 0x60c1f35c Faulting module name: ucrtbase.dll, version: 10.0.19041.546, time stamp: 0x43cbc11d Exception code: 0xc0000409 Fault offset: 0x000000000007287e Faulting process id: 0x2f8c Faulting application start time: 0x01d75deaebafd9c9 Faulting application path: D:\chia_plotter\madMAx43v3r_chia-plotter_win_build_v0.0.3-alpha\chia_plot.exe Faulting module path: C:\Windows\System32\ucrtbase.dll Report Id: 9dbee78a-90c0-4b92-b849-d0ba7e0ec567 Faulting package full name:

same here

[soundy83]

No change for me. Same result as @Hedonay

[NikXO6]

Version=1 EventType=BEX64 EventTime=132677991621205982 ReportType=2 Consent=1 UploadTime=132677991623087843 ReportStatus=268435456 ReportIdentifier=7205e58a-40cb-4da0-9759-add5d6f89282 IntegratorReportIdentifier=59b0d043-9116-4c75-8c3e-8d999fb07168 Wow64Host=34404 NsAppName=chia_plot.exe AppSessionGuid=00002f1c-0002-0011-26f0-f12fee5dd701 TargetAppId=W:000688868ca76bff6b7d930701438b3622d10000ffff!0000809e738310f41ddb422bbb87b6b9e3a06bea137d!chia_plot.exe TargetAppVer=2021//06//10:11:11:24!0!chia_plot.exe BootId=4294967295 TargetAsId=1923 IsFatal=1 EtwNonCollectReason=1 Response.BucketId=962327d1addf2f8960664a04b8f4d365 Response.BucketTable=5 Response.LegacyBucketId=1181713336374711141 Response.type=4 Sig[0].Name=Application Name Sig[0].Value=chia_plot.exe Sig[1].Name=Application Version Sig[1].Value=0.0.0.0 Sig[2].Name=Application Timestamp Sig[2].Value=60c1f35c Sig[3].Name=Fault Module Name Sig[3].Value=ucrtbase.dll Sig[4].Name=Fault Module Version Sig[4].Value=10.0.19041.789 Sig[5].Name=Fault Module Timestamp Sig[5].Value=2bd748bf Sig[6].Name=Exception Offset Sig[6].Value=000000000007286e Sig[7].Name=Exception Code Sig[7].Value=c0000409 Sig[8].Name=Exception Data Sig[8].Value=0000000000000007 DynamicSig[1].Name=OS Version DynamicSig[1].Value=10.0.19042.2.0.0.256.48 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=3081 DynamicSig[22].Name=Additional Information 1 DynamicSig[22].Value=7a8d DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=7a8dfe8534def07d95ee540a409a5e32 DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=2478 DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=247869ccda3d28b60941806f74d7bc64 UI[2]=C:\Users\Chia_Miner\Downloads\madMAx43v3r_chia-plotter_win_build_v0.0.3-alpha\chia_plot.exe LoadedModule[0]=C:\Users\Chia_Miner\Downloads\madMAx43v3r_chia-plotter_win_build_v0.0.3-alpha\chia_plot.exe LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll LoadedModule[2]=C:\Windows\System32\KERNEL32.DLL LoadedModule[3]=C:\Windows\System32\KERNELBASE.dll LoadedModule[4]=C:\Windows\System32\ADVAPI32.dll LoadedModule[5]=C:\Windows\System32\msvcrt.dll LoadedModule[6]=C:\Windows\System32\sechost.dll LoadedModule[7]=C:\Windows\System32\RPCRT4.dll LoadedModule[8]=C:\Windows\System32\ucrtbase.dll LoadedModule[9]=C:\Users\Chia_Miner\Downloads\madMAx43v3r_chia-plotter_win_build_v0.0.3-alpha\libsodium.dll LoadedModule[10]=C:\Users\Chia_Miner\AppData\Local\Programs\Python\Python39\VCRUNTIME140.dll LoadedModule[11]=C:\Users\Chia_Miner\AppData\Local\Programs\Python\Python39\VCRUNTIME140_1.dll LoadedModule[12]=C:\Users\Chia_Miner\AppData\Local\chia-blockchain\app-1.1.6\resources\app.asar.unpacked\daemon\MSVCP140.dll LoadedModule[13]=C:\Windows\SYSTEM32\CRYPTBASE.DLL LoadedModule[14]=C:\Windows\System32\bcryptPrimitives.dll LoadedModule[15]=C:\Windows\SYSTEM32\CRYPTSP.dll LoadedModule[16]=C:\Windows\system32\rsaenh.dll LoadedModule[17]=C:\Windows\System32\bcrypt.dll LoadedModule[18]=C:\Windows\SYSTEM32\kernel.appcore.dll State[0].Key=Transport.DoneStage1 State[0].Value=1 OsInfo[0].Key=vermaj OsInfo[0].Value=10 OsInfo[1].Key=vermin OsInfo[1].Value=0 OsInfo[2].Key=verbld OsInfo[2].Value=19042 OsInfo[3].Key=ubr OsInfo[3].Value=985 OsInfo[4].Key=versp OsInfo[4].Value=0 OsInfo[5].Key=arch OsInfo[5].Value=9 OsInfo[6].Key=lcid OsInfo[6].Value=1033 OsInfo[7].Key=geoid OsInfo[7].Value=12 OsInfo[8].Key=sku OsInfo[8].Value=48 OsInfo[9].Key=domain OsInfo[9].Value=0 OsInfo[10].Key=prodsuite OsInfo[10].Value=256 OsInfo[11].Key=ntprodtype OsInfo[11].Value=1 OsInfo[12].Key=platid OsInfo[12].Value=10 OsInfo[13].Key=sr OsInfo[13].Value=0 OsInfo[14].Key=tmsi OsInfo[14].Value=34835 OsInfo[15].Key=osinsty OsInfo[15].Value=2 OsInfo[16].Key=iever OsInfo[16].Value=11.789.19041.0-11.0.1000 OsInfo[17].Key=portos OsInfo[17].Value=0 OsInfo[18].Key=ram OsInfo[18].Value=131008 OsInfo[19].Key=svolsz OsInfo[19].Value=111 OsInfo[20].Key=wimbt OsInfo[20].Value=0 OsInfo[21].Key=blddt OsInfo[21].Value=191206 OsInfo[22].Key=bldtm OsInfo[22].Value=1406 OsInfo[23].Key=bldbrch OsInfo[23].Value=vb_release OsInfo[24].Key=bldchk OsInfo[24].Value=0 OsInfo[25].Key=wpvermaj OsInfo[25].Value=0 OsInfo[26].Key=wpvermin OsInfo[26].Value=0 OsInfo[27].Key=wpbuildmaj OsInfo[27].Value=0 OsInfo[28].Key=wpbuildmin OsInfo[28].Value=0 OsInfo[29].Key=osver OsInfo[29].Value=10.0.19041.985.amd64fre.vb_release.191206-1406 OsInfo[30].Key=buildflightid OsInfo[31].Key=edition OsInfo[31].Value=Professional OsInfo[32].Key=ring OsInfo[32].Value=Retail OsInfo[33].Key=expid OsInfo[34].Key=fconid OsInfo[35].Key=containerid OsInfo[36].Key=containertype OsInfo[37].Key=edu OsInfo[37].Value=0 FriendlyEventName=Stopped working ConsentKey=BEX64 AppName=chia_plot.exe AppPath=C:\Users\Chia_Miner\Downloads\madMAx43v3r_chia-plotter_win_build_v0.0.3-alpha\chia_plot.exe NsPartner=windows NsGroup=windows8 ApplicationIdentity=05D35365BA157E0E5C07122DDE31F110 MetadataHash=-1473500955

[wahaobi]

No change for me. Same result as @Hedonay

[stotiks]

Thanks for testing. Need to dig deeper

On Thu, 10 Jun 2021, 14:59 wahaobi, @.***> wrote:

No change for me. Same result as @Hedonay https://github.com/Hedonay

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/madMAx43v3r/chia-plotter/issues/126#issuecomment-858559242, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALGV2WH53JROPC5LL2UDPJ3TSCSKZANCNFSM46OBI2VA .

[jielee770]

Thanks for testing. Need to dig deeper … On Thu, 10 Jun 2021, 14:59 wahaobi, @.***> wrote: No change for me. Same result as @Hedonay https://github.com/Hedonay — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#126 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALGV2WH53JROPC5LL2UDPJ3TSCSKZANCNFSM46OBI2VA .

thanks alot

[Hedonay]

Thanks for testing. Need to dig deeper …

What ever help you need, I'll gladly help out.

[NikXO6]

happy to test

[liuxx007]

No change for me.

[delucca]

Could you try running it inside Docker? https://github.com/madMAx43v3r/chia-plotter/pull/102

It should work. But you would need to setup proper RAM and CPU constraints to Docker

[liuxx007]

Could you try running it inside Docker? #102

It should work. But you would need to setup proper RAM and CPU constraints to Docker

I really appreciate your dedication. I don't know how it works Docker.

[delucca]

Could you try running it inside Docker? #102 It should work. But you would need to setup proper RAM and CPU constraints to Docker

I really appreciate your dedication. I don't know how it works Docker.

You can install it on Windows following this: https://docs.docker.com/docker-for-windows/install/

Them, you can run the following command in a terminal:

docker run \
  -v <path-to-your-tmp-dir>:/mnt/harvester \
  -v <path-to-your-final-dir>:/mnt/farm \
  odelucca/chia-plotter \
    -t /mnt/harvester/ \
    -d /mnt/farm/ \
    -p <pool-key> \
    -f <farm-key>

[delucca]

The only thing we need to do is compare the Docker container performance versus a native Windows compiled binary. In Linux Docker is 5% slower, but it seems Windows has some pre-defined memory limits to Docker

If that is true, you could change those memory limits in your Docker config in Windows (probably with the -m flag while running the container)

[liuxx007]

The only thing we need to do is compare the Docker container performance versus a native Windows compiled binary. In Linux Docker is 5% slower, but it seems Windows has some pre-defined memory limits to Docker

If that is true, you could change those memory limits in your Docker config in Windows (probably with the -m flag while running the container)

OK, I'll give it a try

[delucca]

The only thing we need to do is compare the Docker container performance versus a native Windows compiled binary. In Linux Docker is 5% slower, but it seems Windows has some pre-defined memory limits to Docker If that is true, you could change those memory limits in your Docker config in Windows (probably with the -m flag while running the container)

OK, I'll give it a try

Cool!

Please, after testing, tell me the results! Also, if you were able to run it in WSL please also compare Docker with WSL results. I don't have a Windows machine with me right now, and I'm curious regarding Docker impact on performance.

It should be better than WSL, but 5% slower than native OS

[Hedonay]

Could you try running it inside Docker? #102

It should work. But you would need to setup proper RAM and CPU constraints to Docker

Wanted to give it a go a few hours back, but need to restart Windows when installing Docker, and I'm not able to do that at the moment. So the perfect solution would still be a working Windows plotter.

[delucca]

Could you try running it inside Docker? #102 It should work. But you would need to setup proper RAM and CPU constraints to Docker

Wanted to give it a go a few hours back, but need to restart Windows when installing Docker, and I'm not able to do that at the moment. So the perfect solution would still be a working Windows plotter.

Some users are reporting that Docker is limited by default to 1 CPU in Windows. I suggest using the --cpus flag while running it, like this:

docker run \
  -v <path-to-your-tmp-dir>:/mnt/harvester \
  -v <path-to-your-final-dir>:/mnt/farm \
  -m 8000 \
  --cpus 8 \
  odelucca/chia-plotter \
    -t /mnt/harvester/ \
    -d /mnt/farm/ \
    -p <pool-key> \
    -f <farm-key> \
    -r 8

[Hedonay]

Some users are reporting that Docker is limited by default to 1 CPU in Windows. I suggest using the --cpus flag while running it, like this:

docker run \
  -v <path-to-your-tmp-dir>:/mnt/harvester \
  -v <path-to-your-final-dir>:/mnt/farm \
  -m 8000 \
  --cpus 8 \
  odelucca/chia-plotter \
    -t /mnt/harvester/ \
    -d /mnt/farm/ \
    -p <pool-key> \
    -f <farm-key> \
    -r 8

Will just wait for next version of plotter. ;) But thank you anyway!

[delucca]

No change for me.

You were not able to run it on Docker?

[Hedonay]

No change for me.

You were not able to run it on Docker?

I believe he's replying to actual problem reported in this post.

[deannamnguyen]

I think we need to wait for the next version. Tried many time, all 3 release for Windows but no luck. Process killed after showing Number of Threads: 16 Number of Sort Buckets: 2^7 (128)

[zpzyyzp]

Maybe CPU without AVX2 will be failed.

[Hedonay]

Maybe CPU without AVX2 will be failed.

I really don't think AVX2 is used in this case. And since people are able to load plotter with single processor, there must be something else we are missing. I believe @stotiks will find a solution, we just need to wait a bit and maybe use plotter on some other machine till a new version is out.

[madMAx43v3r]

${BLAKE3_PATH}/blake3_avx2_x86-64_windows_gnu.S

AVX2 is used in BLAKE3

[madMAx43v3r]

and probably in bls/relic too

[Hedonay]

${BLAKE3_PATH}/blake3_avx2_x86-64_windows_gnu.S

AVX2 is used in BLAKE3

Thanx for info @madMAx43v3r! I was sure it can not be the reason for not working because we have a group of people on Discord installing it today on all sorts of single processors with no problem. On the other hand, those of us with dual Xeon servers are all out of luck.

[Coroconciu]

All three releases work on Windows Server 2016 with 2x E5-2698 v4 I have the latest supported Visual C++ Redistributable 14.29.30037

[Hedonay]

Visual C++ Redistributable 14.29.30037

Let me check and update if needed and try it again. Will report back.

[zpzyyzp]

161

Single processors E3 1230v2, i7-2600, E5 2670 and etc.... failed. All without AVX2.

[Hedonay]

All three releases work on Windows Server 2016 with 2x E5-2698 v4 I have the latest supported Visual C++ Redistributable 14.29.30037

Checked... Have the latest Visual C++ Redistributable... No luck there... and yes, Xeons in my server don't have AVX2...

[madMAx43v3r]

Mine don't have AVX2 either, but at least on Linux it auto-detects it and uses AXV1 or something else.

[madMAx43v3r]

If that's the issue, remove the following files from CMakeLists.txt:

    ${BLAKE3_PATH}/blake3_avx2_x86-64_windows_gnu.S
    ${BLAKE3_PATH}/blake3_sse41_x86-64_windows_gnu.S
    ${BLAKE3_PATH}/blake3_avx512_x86-64_windows_gnu.S
    ${BLAKE3_PATH}/blake3_sse2_x86-64_windows_gnu.S

Acutally I added them with the change to new BLAKE3 code, thinking it was going to improve performance...

[madMAx43v3r]

sse41 and sse2 should be fine, my old Xeons have it, so I'll remove avx2 and avx512 then...

[madMAx43v3r]

see 77b4049c0e2654462630eaf930c63fed018756e2

[Hedonay]

sse41 and sse2 should be fine, my old Xeons have it, so I'll remove avx2 and avx512 then...

Great!!!! So with this @stotiks should be able to create new build, if I understand correctly?

[madMAx43v3r]

yes give it a shot

[Hedonay]

yes give it a shot

Thank you very much for looking in to it. Much appreciated!!! Will wait for next alpha version that'll include this correction and close this ticket as soon as we test it out.

[celalanak]

Dear @madMAx43v3r and @Hedonay Why am I still getting this error?

System Dell R720 Server 2016, E4-2670 x2 64ram 3x300 sas 1tb evo 512 evo

Thank you,,

Faulting application name: chia_plot.exe, version: 0.0.0.0, time stamp: 0x60c1f35c Faulting module name: ucrtbase.dll, version: 10.0.14393.3659, time stamp: 0x5e9140a1 Exception code: 0xc0000409 Fault offset: 0x000000000006de4e Faulting process id: 0x1fe4 Faulting application start time: 0x01d75e3047d2610f Faulting application path: C:\Users\xxxchia\Desktop\maddmax\chia_plot.exe Faulting module path: C:\Windows\System32\ucrtbase.dll Report Id: 8f41f2c6-4d7f-467e-abf5-22ce22b28276 Faulting package full name: Faulting package-relative application ID:

[Hedonay]

Dear @madMAx43v3r and @Hedonay Why am I still getting this error?

System Dell R720 Server 2016, E4-2670 x2 64ram 3x300 sas 1tb evo 512 evo

Thank you,,

Faulting application name: chia_plot.exe, version: 0.0.0.0, time stamp: 0x60c1f35c Faulting module name: ucrtbase.dll, version: 10.0.14393.3659, time stamp: 0x5e9140a1 Exception code: 0xc0000409 Fault offset: 0x000000000006de4e Faulting process id: 0x1fe4 Faulting application start time: 0x01d75e3047d2610f Faulting application path: C:\Users\xxxchia\Desktop\maddmax\chia_plot.exe Faulting module path: C:\Windows\System32\ucrtbase.dll Report Id: 8f41f2c6-4d7f-467e-abf5-22ce22b28276 Faulting package full name: Faulting package-relative application ID:

You'll need to wait for a new version. I think Stotiks will be able to build a new one with corrections MadMax did. When new version is out, try it and report back. New version will probably be 0.0.4, and you'll be able to find it here: https://github.com/stotiks/chia-plotter/tags

[celalanak]

Dear @madMAx43v3r and @Hedonay Why am I still getting this error? System Dell R720 Server 2016, E4-2670 x2 64ram 3x300 sas 1tb evo 512 evo Thank you,, Faulting application name: chia_plot.exe, version: 0.0.0.0, time stamp: 0x60c1f35c Faulting module name: ucrtbase.dll, version: 10.0.14393.3659, time stamp: 0x5e9140a1 Exception code: 0xc0000409 Fault offset: 0x000000000006de4e Faulting process id: 0x1fe4 Faulting application start time: 0x01d75e3047d2610f Faulting application path: C:\Users\xxxchia\Desktop\maddmax\chia_plot.exe Faulting module path: C:\Windows\System32\ucrtbase.dll Report Id: 8f41f2c6-4d7f-467e-abf5-22ce22b28276 Faulting package full name: Faulting package-relative application ID:

You'll need to wait for a new version. I think Stotiks will be able to build a new one with corrections MadMax did. When new version is out, try it and report back. New version will probably be 0.0.4, and you'll be able to find it here: https://github.com/stotiks/chia-plotter/tags

Thank you 🙏🙏 @Hedonay

[toto99303]

Same issue with dual X5675 here, will try as soon as next version is released. Thanks in advance!

[sjd2651]

Same issue with dual X5670 here, will try as soon as next version is released. Thanks in advance!