Closed Hedonay closed 3 years ago
Same issue with dual X5675 here, will try as soon as next version is released. Thanks in advance!
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...
Hi! I think BLAKE3 is ok Function bls::G1Element::FromByteVector raise exception "G1 element is invalid" on old cpus. Something wrong happens in relic library :-/
Hi! I think BLAKE3 is ok
Function bls::G1Element::FromByteVector raise exception "G1 element is invalid" on old cpus. Something wrong happens in relic library :-/
Tag me anytime if you need me to test new version, when you'll be able to make it.
There's quite a few of us who can't wait to test "MadMax plotter" on our Xeons... 😂
Does this issue exists in Ubuntu also?
Does this issue exists in Ubuntu also?
No. It's just a windows build issue.
Function bls::G1Element::FromByteVector raise exception "G1 element is invalid" on old cpus. Something wrong happens in relic library :-/
I'll look into it
@madMAx43v3r can the K size be defined in the command line on the windows version?
@madMAx43v3r can the K size be defined in the command line on the windows version?
Please try to stick to original problem related to Xeon processors. As far as I checked "readme", there is no K in it, but worth trying. If you need additional help on that, please check other issues or open a new one.
@madMAx43v3r can the K size be defined in the command line on the windows version?
Please try to stick to original problem related to Xeon processors. As far as I checked "readme", there is no K in it, but worth trying. If you need additional help on that, please check other issues or open a new one.
as many other, am still waiting for a fix on the windows dual xeon issue (as i have a DL380P Gen8 - Dual E5-2680 0), but just made me wonder on K33 and K34 just to allocated the space efficiently on the drives as I have 12TB drives if I stick to K32 there is always a 27GB empty space left , so I had to mix between K32 (102 plots) and K33 (4 plots) to get the drive to 99.9% full or do a K34 (24 plots ) to get the drive 100% full.
as many other, am still waiting for a fix on the windows dual xeon issue (as i have a DL380P Gen8 - Dual E5-2680 0), but just made me wonder on K33 and K34 just to allocated the space efficiently on the drives as I have 12TB drives if I stick to K32 there is always a 27GB empty space left , so I had to mix between K32 (102 plots) and K33 (4 plots) to get the drive to 99.9% full or do a K34 (24 plots ) to get the drive 100% full.
Imagine you're a developer, and you have to go through tons of unrelated messages, just to get relevant information, so you can fix issues people like you and I have. This is not forum, its issue report. Please stick to relevant information related to topic and help developers help us faster.
try again with latest master ./make_devel.sh
, I disabled usage of libgmp in relic, see a2ef17b9a1e13149bd7a89f24c34202a2c602a5b
all win builds with disabled
I see... maybe that's why? If gmp is disabled relic will do it's own magic, which might be the issue?
EDIT: to keep it ontopic.
Dual Xeon aborts after parameters are set.
@stotiks Got it working on Windows with a Ryzen using the exact same install method as on the Xeon server, but its extremely slow and sits more around 1% CPU usage than anything else.
R5 3600 using all cores.
how many threads, how fast is D:\MadMax\ ? EDIT: also offtopic
@madMAx43v3r I have a suggestion. There are a lot of users asking for help regarding Windows setups. Why don't we create a Discord community for those users? By doing so that kind of questions could be asked there without flooding the issues and PRs of this repository
My latest PR got more than 100 comments. Most of those were users asking for help to set up it on Windows. And because of that, I missed some real suggestions regarding the Docker image from other developers. I just saw that afterward because of all the flooding.
If you do so, we could simply mark the comments unrelated to the issue/PR as off-topic. Them Github would automatically hide it for us.
how many threads, how fast is D:\MadMax\ ? EDIT: also offtopic
12Gb/s SAS 15k in RAID0, My SSD's are even slower. Just read that its probably because of WSL2 though, so waiting for him to update and try again.
@madMAx43v3r I have a suggestion. There are a lot of users asking for help regarding Windows setups. Why don't we create a Discord community for those users? By doing so that kind of questions could be asked there without flooding the issues and PRs of this repository
My latest PR got more than 100 comments. Most of those were users asking for help to set up it on Windows. And because of that, I missed some real suggestions regarding the Docker image from other developers. I just saw that afterward because of all the flooding.
If you do so, we could simply mark the comments unrelated to the issue/PR as off-topic. Them Github would automatically hide it for us.
This would be great.
Will do later today
Will do later today
Let me know as soon you create please :D
Some users are calling me over Telegram (since my username is the same) and asking for aid. It would be good to help them all inside Discord instead :)
x58 x5675 Has the window problem been solved?
Still unearthing
------------------ 原始邮件 ------------------ 发件人: @.>; 发送时间: 2021年6月11日(星期五) 晚上10:18 收件人: @.>; 抄送: @.>; @.>; 主题: Re: [madMAx43v3r/chia-plotter] Dual Xeon on Windows version doesn't work (kills process) (#126)
x58x5675 的窗口问题解决了吗?
— 你收到这个是因为你评论了。 直接回复此邮件,在 GitHub 上查看或取消订阅.
It's strange. I did a plot in 68 min and now i cant run it again
I got the exact same problem on a Windows 10 @ Intel Xeon CPU X5680. Process is killed after parameters are listed. Windows event log says chia_plot.exe and it's module ucrtbase.dll is faulty. But newest Visual C++ 2015 redist is installed on that machine.
Oh what a day! What a lovely day! Crash on start fixed https://github.com/stotiks/chia-plotter/releases/tag/v0.0.4
Oh what a day! What a lovely day! Crash on start fixed https://github.com/stotiks/chia-plotter/releases/tag/v0.0.4
I'm helping a Windows user to test it! Let you know in a minute if it works
Oh what a day! What a lovely day! Crash on start fixed https://github.com/stotiks/chia-plotter/releases/tag/v0.0.4
I can confirm that this does now work on my Windows plotter. Thanks for the speedy fix @stotiks!
Oh what a day! What a lovely day! Crash on start fixed https://github.com/stotiks/chia-plotter/releases/tag/v0.0.4
Works like charm. Wonderful!
Oh what a day! What a lovely day! Crash on start fixed https://github.com/stotiks/chia-plotter/releases/tag/v0.0.4
I can confirm that this does now work on my Windows plotter. Thanks for the speedy fix @stotiks!
Awesome stuff folks, plotting away with Quad Xeon E7-4870's on Win 2016 - Thanks so much! Will post with any issues.
What about core limit? Whatever value you set, it uses all threads
Oh what a day! What a lovely day! Crash on start fixed https://github.com/stotiks/chia-plotter/releases/tag/v0.0.4
I'm helping a Windows user to test it! Let you know in a minute if it works
Confirm that it works :)
Awesome @stotiks
I will add a link to your releases in the readme
PS C:\madMAxv0.0.4> .\chia_plot -t "J:\MadMax_T1\" -2 "J:\MadMax_T2\" -d "D:\Disco_4T_Chia_0\" -p "xxxxxxxxxxxxxx" -f "xxxxxxxxxx" Final Directory: D:\Disco_4T_Chia_0\ Number of Plots: 1 Process ID: 3136 Number of Threads: 4 Number of Buckets: 2^7 (128) PS C:\madMAxv0.0.4>
Same error for me (0.0.3 and 0.0.4) Win 10-2004 - 19041-1052 @stotiks
Ryzen 9 5950X 128Gb Ram No Ram Drive
Dual X5675 here, seems like it's working, didn't crash yet :) Thanks!
Will do later today
Let me know as soon you create please :D
Some users are calling me over Telegram (since my username is the same) and asking for aid. It would be good to help them all inside Discord instead :)
Cheers for your efforts, but unfortunately mine still crashes :(
Faulting application name: chia_plot.exe, version: 0.0.0.0, time stamp: 0x60c38f6a Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf Exception code: 0xc0000409 Fault offset: 0x000000000007286e Faulting process id: 0xbe8 Faulting application start time: 0x01d75ef22958528a Faulting application path: C:\Plotter\chia_plot.exe Faulting module path: C:\Windows\System32\ucrtbase.dll
哦,多么美好的一天!真是美好的一天! 启动时崩溃修复 https://github.com/stotiks/chia-p
Oh what a day! What a lovely day! Crash on start fixed https://github.com/stotiks/chia-plotter/releases/tag/v0.0.4
I'm helping a Windows user to test it! Let you know in a minute if it works
Confirm that it works :)
cpu %100 cool
So... I wanna thank @madMAx43v3r and @stotiks for helping us all out. Much appreciated!!! You guys rock!
Also - thank you, @delucca, for helping out with Docker version!!!
For anyone looking for working Windows version, you can find it here: https://github.com/stotiks/chia-plotter/releases/tag/v0.0.4
I'm closing this issue report.
Seems like it's running well so far!
Thanks so much @madMAx43v3r and @stotiks , the community really appreciates your work.
No longer crashing on Dual Xeon (A big thank you), however looking at my Quad Xeon E7-4870, it will only utilise two out of the four CPU's. @stotiks @madMAx43v3r
Xeon 2678v3 still crash on v0.04, same issue with ucrtbase.dll...
Thank you @madMAx43v3r @stotiks and @Hedonay worked for me, thank you again.
Xeon 2678v3 still crash on v0.04, same issue with ucrtbase.dll...
try https://github.com/stotiks/chia-plotter/releases/download/v0.0.4/catchmeifyoucan.zip this prints more info
Thank you guys! Working perfect now, utilizing all CPUs!
What the ramdisk tool for windows.
I using primo ramdisk, but when i start plotting, my pc dump. Thanks
Still crashes for me after a while on 4x Xeon system using v.0.0.4 of Stotik. And thats the output of chia_plot.exe (Then it crashes):
Final Directory: F:\ Number of Plots: 1 Process ID: 8820 Number of Threads: 4 Number of Buckets: 2^7 (128) Pool Public Key: Mykey Farmer Public Key: Mykey Working Directory: B:\ Working Directory 2: G:\ Plot Name: plot-k32-2021-06-12-11-52-f3001f06cc15aedd4115fab6cf9a6113f52fe241af15f7050235d11b2a39f6ba [P1] Table 1 took 129.234 sec
With this Error in eventLog:
Faulting application name: chia_plot.exe, version: 0.0.0.0, time stamp: 0x60c38f6a Faulting module name: ucrtbase.dll, version: 10.0.14393.3659, time stamp: 0x5e9140a1 Exception code: 0xc0000409 Fault offset: 0x000000000006de4e Faulting process id: 0x564 Faulting application start time: 0x01d75eea14452e6e Faulting application path: C:\Users\Administrator\Desktop\madMAx43v3r_chia-plotter_win_build_v0.0.4\chia_plot.exe Faulting module path: C:\Windows\System32\ucrtbase.dll Report Id: af68249e-ef48-4804-89e0-9e91b9e7e9ee Faulting package full name: Faulting package-relative application ID:
https://github.com/stotiks/chia-plotter/releases/download/v0.0.4/catchmeifyoucan.zip
This brings me further: But Table 2 took aaaages :p Was using default params for -u and -t. Aborted it. Now testing with -u 256 and -t 64.
Final Directory: F:\ Number of Plots: 1 Process ID: 9108 Number of Threads: 4 Number of Buckets: 2^7 (128) Pool Public Key: MyKey Farmer Public Key: MyKey Working Directory: B:\ Working Directory 2: G:\ Plot Name: plot-k32-2021-06-12-12-10-9ff1dc957c79e1b79b754800d821e9e468514a05eda758c20810e375a1e194db [P1] Table 1 took 70.4861 sec [P1] Table 2 took 1104.99 sec, found 4294899996 matches
Using 4x Xeon E5-4650 with 512 GB RAM on Windows Server 2016
Xeon 2678v3 still crash on v0.04, same issue with ucrtbase.dll...
try https://github.com/stotiks/chia-plotter/releases/download/v0.0.4/catchmeifyoucan.zip this prints more info
Please take a look on this one.
Version=1 EventType=BEX64 EventTime=132679688727615968 ReportType=2 Consent=1 UploadTime=132679688730052439 ReportStatus=268435456 ReportIdentifier=fc540c3c-e563-46ac-9469-fe0b132542f4 IntegratorReportIdentifier=8747b4c6-7276-443f-83bd-97d35fedc0c1 Wow64Host=34404 NsAppName=chia_plot.exe AppSessionGuid=0000082c-0001-0006-c825-07f8785fd701 TargetAppId=W:000688868ca76bff6b7d930701438b3622d10000ffff!000069c92d263ef00696b52149b66c2d86b0f2ff0521!chia_plot.exe TargetAppVer=2021//06//12:06:01 8!0!chia_plot.exe BootId=4294967295 TargetAsId=1428 IsFatal=1 EtwNonCollectReason=1 Response.BucketId=3320417cd356f3e45cd7d0ced627a5a4 Response.BucketTable=5 Response.LegacyBucketId=2078359339829536164 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=60c44dc2 Sig[3].Name=Fault Module Name Sig[3].Value=chia_plot.exe Sig[4].Name=Fault Module Version Sig[4].Value=0.0.0.0 Sig[5].Name=Fault Module Timestamp Sig[5].Value=60c44dc2 Sig[6].Name=Exception Offset Sig[6].Value=00000000000fe371 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.19043.2.0.0.768.101 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=1033 DynamicSig[22].Name=Additional Information 1 DynamicSig[22].Value=76a3 DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=76a373cd86f1762b5955d337a726c094 DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=467c DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=467c5ada61002af9e128f048322a750d UI[2]=C:\Users\hahan\Downloads\madMAx43v3r_chia-plotter_win_build_v0.0.4\chia_plot.exe LoadedModule[0]=C:\Users\hahan\Downloads\madMAx43v3r_chia-plotter_win_build_v0.0.4\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\CRYPTBASE.DLL LoadedModule[9]=C:\Windows\SYSTEM32\CRYPTSP.dll LoadedModule[10]=C:\Windows\system32\rsaenh.dll LoadedModule[11]=C:\Windows\System32\bcrypt.dll LoadedModule[12]=C:\Windows\System32\bcryptPrimitives.dll LoadedModule[13]=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=19043 OsInfo[3].Key=ubr OsInfo[3].Value=1052 OsInfo[4].Key=versp OsInfo[4].Value=0 OsInfo[5].Key=arch OsInfo[5].Value=9 OsInfo[6].Key=lcid OsInfo[6].Value=2057 OsInfo[7].Key=geoid OsInfo[7].Value=251 OsInfo[8].Key=sku OsInfo[8].Value=101 OsInfo[9].Key=domain OsInfo[9].Value=0 OsInfo[10].Key=prodsuite OsInfo[10].Value=768 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=221130108 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=65428 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.1052.amd64fre.vb_release.191206-1406 OsInfo[30].Key=buildflightid OsInfo[31].Key=edition OsInfo[31].Value=Core 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\hahan\Downloads\madMAx43v3r_chia-plotter_win_build_v0.0.4\chia_plot.exe NsPartner=windows NsGroup=windows8 ApplicationIdentity=49D03459CEB7FBEA2EE24FD65C7EC500 MetadataHash=241368448
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:
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?