netmebtc
Newbie
Offline
Activity: 72
Merit: 0
|
|
November 22, 2018, 03:37:44 AM |
|
Same issue for my 6Xvega Win10 SRBminer1.7.0 cryptonight V8 ,just stuck ,not hang, restart SRBminer again, then it work. Miner stops working without any errors. It just stops, but does not hang. With what it can be connected.
|
|
|
|
goran89
Newbie
Offline
Activity: 13
Merit: 0
|
|
November 22, 2018, 09:09:37 AM |
|
edited 580/8 srbminer 1.7.0 1230/2100 (880mv) - 1135-1140h/s haven "gpu_conf" : [ { "id" : 0, "intensity" : 54, "worksize" : 8, "fragments" : 1, "threads" : 2}, { "id" : 1, "intensity" : 54, "worksize" : 8, "fragments" : 1, "threads" : 2}, { "id" : 2, "intensity" : 54, "worksize" : 8, "fragments" : 1, "threads" : 2}, { "id" : 3, "intensity" : 54, "worksize" : 8, "fragments" : 1, "threads" : 2}, { "id" : 4, "intensity" : 54, "worksize" : 8, "fragments" : 1, "threads" : 2}, { "id" : 5, "intensity" : 54, "worksize" : 8, "fragments" : 1, "threads" : 2}, ] } HYNIX H5GQ8H24MJR 999000000000000022339D00CEDD6B4470551414B80D960B0040C400750314204A8900A00200000 018123745B92B3A16
I need better strap for my hynix card but just want to confirm that this is correct strap because it is much longer the original and also it has space between last group of 0. Can someone tell me correct version because I don't want to brick my card.
|
|
|
|
gerixusyu
Newbie
Offline
Activity: 24
Merit: 0
|
|
November 22, 2018, 09:25:08 AM |
|
|
|
|
|
doktor83 (OP)
|
|
November 22, 2018, 09:48:06 AM |
|
Hello Doktor,
So I usually enjoy using your miner. But since the v8 fork, I cannot use "gpu_conf" : command anymore. When I add some values to the integrity, worksize etc, the miner will not start but just shuts down for no reason. But if I delete the "gpu_conf" : line with its values, miner works fine. Its giving me headache like for real. Can you help me on this one?
have error in config, post and we help you fix that My config for normalv8 is: { "cryptonight_type" : "normalv8", "intensity" : 0, "double_threads" : true "gpu_conf" : [ { "id" : 0, "intensity" : 54, "worksize" : 8, "fragments" : 1, "threads" : 2}, { "id" : 1, "intensity" : 54, "worksize" : 8, "fragments" : 1, "threads" : 2}, { "id" : 2, "intensity" : 54, "worksize" : 8, "fragments" : 1, "threads" : 2}, { "id" : 3, "intensity" : 54, "worksize" : 8, "fragments" : 1, "threads" : 2}, { "id" : 4, "intensity" : 54, "worksize" : 8, "fragments" : 1, "threads" : 2}, { "id" : 5, "intensity" : 54, "worksize" : 8, "fragments" : 1, "threads" : 2}, ] } When I add "gpu_conf" : line, miner just won't start well actually it starts but then it just turns off by it self without saying anything. You are missing a , after "double_threads" : true
|
|
|
|
myka280
Newbie
Offline
Activity: 3
Merit: 0
|
|
November 22, 2018, 07:23:34 PM |
|
I believe at least a comma is missing after
"double_threads" : true,
|
|
|
|
XSlowHand
Newbie
Offline
Activity: 5
Merit: 0
|
|
November 22, 2018, 08:07:16 PM Last edit: November 23, 2018, 12:28:24 AM by XSlowHand |
|
Miner stops working without any errors. It just stops, but does not hang. With what it can be connected.
I have several rigs that run normal with 1.7. Just one stopped working yesterday and it cannot start anymore. No version of SRB-Miner starts anymore. I do get a callout saying SRB-Miner stopped working and I have the following in the eventviewer: Faulting application name: SRBMiner-CN.exe, version: 1.7.0.0, time stamp: 0x00000000 Faulting module name: igdrclneo64.dll, version: 0.0.0.0, time stamp: 0x5a96b19b Exception code: 0xc0000005 Fault offset: 0x0000000000030819 Faulting process id: 0x1d08 Faulting application start time: 0x01d4829d005c984a Faulting application path: C:\MinerStuff\SRBMiner-CN-V1-7-0nEW\SRBMiner-CN-V1-7-0\SRBMiner-CN.exe Faulting module path: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_250db833a1cd577e\igdrclneo64.dll Report Id: 42e2af91-4114-4f3f-b2a8-599c67ab5af2 Faulting package full name: Faulting package-relative application ID: Any suggestions anyone? The only thing that would be different here is, I ran out of HDMI-Dmmys. So on restart without a connected screen I have no onboard graphics. Could that be it? Forgot to try that while in the farm earlier... /Edit: igdrclneo32.dll intel integrated graphics, I guess the software is trying to launch using openGL or something and it is failing From https://www.reddit.com/r/PlayStationNow/comments/8hc7ig/possible_fix_for_windows_10_users_psnow_not/DDU-ing it now...and it works. Could it be an OpenCL or Miner bug?
|
|
|
|
badral07
Newbie
Offline
Activity: 8
Merit: 0
|
|
November 23, 2018, 02:16:51 AM |
|
Hello Doktor,
So I usually enjoy using your miner. But since the v8 fork, I cannot use "gpu_conf" : command anymore. When I add some values to the integrity, worksize etc, the miner will not start but just shuts down for no reason. But if I delete the "gpu_conf" : line with its values, miner works fine. Its giving me headache like for real. Can you help me on this one?
have error in config, post and we help you fix that My config for normalv8 is: { "cryptonight_type" : "normalv8", "intensity" : 0, "double_threads" : true "gpu_conf" : [ { "id" : 0, "intensity" : 54, "worksize" : 8, "fragments" : 1, "threads" : 2}, { "id" : 1, "intensity" : 54, "worksize" : 8, "fragments" : 1, "threads" : 2}, { "id" : 2, "intensity" : 54, "worksize" : 8, "fragments" : 1, "threads" : 2}, { "id" : 3, "intensity" : 54, "worksize" : 8, "fragments" : 1, "threads" : 2}, { "id" : 4, "intensity" : 54, "worksize" : 8, "fragments" : 1, "threads" : 2}, { "id" : 5, "intensity" : 54, "worksize" : 8, "fragments" : 1, "threads" : 2}, ] } When I add "gpu_conf" : line, miner just won't start well actually it starts but then it just turns off by it self without saying anything. You are missing a , after "double_threads" : true Holy shit, it worked. Thank you so much Doktor.
|
|
|
|
doktor83 (OP)
|
|
November 23, 2018, 08:36:43 AM |
|
V1.7.1- Added new algo FreeHaven - Small OpenCL optimisations - Added 3 different modes for heavy algos (Heavy, Haven, BitTube, Italo, FreeHaven) - Added value '9999' for fragments, that sets internally to the value it was in previous 1.6.8 version - Fixed benchmarking mode + startup monitor bug - Fragments, aes, bralock and heavy_mode can be set now outside gpu_conf, so it applies to every GPU - Freehaven algo is here, a lot of you were waiting for this - Added new parameter "heavy_mode", it can be used in gpu_conf, or just in the config, it is applied if not in auto mode (intensity = 0). It can be 1,2,3. 1: This is the default method for doing heavy calculations now, it's more stable and should produce less compute errors than in the previous 1.7.0 version. Note that worksize 9 isn't the optimal worksize anymore for Vegas if using this mode. Worksize 8 now gives better results, you just need to find a good value for intensity. 2: This is the calculation method from the previous 1.7.0 version, use it if you can get better results with it than with mode 1. Note for Vegas : worksize 9 is optimal here. 3: Experimental mode, it is the fastest but tends to produce the most compute errors, if your GPU's are tuned maximally to the edge. I put it here because maybe someone can get the best results with it. - Ellesmere 8gb cards just love to throttle hashrate on heavy algos, lot of you said you had better results on previous versions, so if you set fragments to 9999 it uses the same internal settings for it used in 1.6.8. I am sure with the new mode for heavy calculations higher hashrates can be achieved, but a lot of users just copy over the old settings and guess what, does are not optimal anymore. With the new method you should lower the intensity a little bit than before, and find the right fragments setting for your GPU's. Some users reported they have higher hashrates after playing a little bit with these settings. - I had to add parameters 'fragments', 'aes', 'bralock, and now 'heavy_mode' to the config file outside the 'gpu_conf' because.. well, nobody reads the first page or readme.txt anymore
|
|
|
|
doktor83 (OP)
|
|
November 23, 2018, 02:53:24 PM |
|
Auto setup for freehaven is sh*t, i forgot to tune it, so it uses settings like for heaven, which is obviously bad. For Vega try intensity 110, for other i dunno
|
|
|
|
sky2018miner
Newbie
Offline
Activity: 33
Merit: 0
|
|
November 23, 2018, 04:31:05 PM |
|
Having tested version 1.7.1 I will say with confidence for old pitcairn cards benchmark shows a huge drop on heavy, normalv7, normalv8, stellitev4 test interrupted by message Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram [ctx-> Program] for DeviceID 0 (Thread 0) [2018-11-23 17:25:04] GPU's Error initing. Stopping miner process [2018-11-23 17:25:04] Stopping miner process transition to kernel 2 did not give results I am completely disappointed with the miner great job
|
|
|
|
|
dingdongtobias
Newbie
Offline
Activity: 156
Merit: 0
|
|
November 23, 2018, 04:40:10 PM |
|
Having tested version 1.7.1 I will say with confidence for old pitcairn cards benchmark shows a huge drop on heavy, normalv7, normalv8, stellitev4 test interrupted by message Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram [ctx-> Program] for DeviceID 0 (Thread 0) [2018-11-23 17:25:04] GPU's Error initing. Stopping miner process [2018-11-23 17:25:04] Stopping miner process transition to kernel 2 did not give results I am completely disappointed with the miner great job
time sell old garbage and buy normal video cards
|
|
|
|
doktor83 (OP)
|
|
November 23, 2018, 04:56:19 PM |
|
Having tested version 1.7.1 I will say with confidence for old pitcairn cards benchmark shows a huge drop on heavy, normalv7, normalv8, stellitev4 test interrupted by message Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram [ctx-> Program] for DeviceID 0 (Thread 0) [2018-11-23 17:25:04] GPU's Error initing. Stopping miner process [2018-11-23 17:25:04] Stopping miner process transition to kernel 2 did not give results I am completely disappointed with the miner great job
you got 370 2gb right?
|
|
|
|
sky2018miner
Newbie
Offline
Activity: 33
Merit: 0
|
|
November 23, 2018, 04:59:24 PM |
|
I USE ALL THE OPPORTUNITIES FOR ME TO AVAILABLE
OLD MAPS, NEW MAPS EVERYTHING FLOWS AND CHANGES DECLINING POLARIS, VEGA do not show your temporary superiority
|
|
|
|
issie81
|
|
November 23, 2018, 05:16:46 PM |
|
have fast is freehaven algo doing people talking about 4/4.5Kh/s any info on this?
|
|
|
|
hmgp
Newbie
Offline
Activity: 11
Merit: 0
|
|
November 23, 2018, 05:46:37 PM |
|
Hey Dok.
Thanks for the constant updates on the miner.
Tried the last one and it seems I've lost 150 hs on each vega 56 on haven compared to the last one.
My config is as simple as possible. I did try to play with the values but it doesn't affect it. The miner starts above 6700 for 4 vega, then drops slowly to 6300 / 6200. Does seem watts are down a bit...
Any tips?
Thanks
|
|
|
|
doktor83 (OP)
|
|
November 23, 2018, 06:25:04 PM |
|
Hey Dok.
Thanks for the constant updates on the miner.
Tried the last one and it seems I've lost 150 hs on each vega 56 on haven compared to the last one.
My config is as simple as possible. I did try to play with the values but it doesn't affect it. The miner starts above 6700 for 4 vega, then drops slowly to 6300 / 6200. Does seem watts are down a bit...
Any tips?
Thanks
If you don't really want to play try : "intensity" : 61, "double_threads" : true, "worksize" : 9, "fragments" : 1, "aes" : 0, "bralock" : 32, "heavy_mode" : 2
|
|
|
|
livada
Newbie
Offline
Activity: 417
Merit: 0
|
|
November 23, 2018, 06:27:00 PM Last edit: November 23, 2018, 06:44:33 PM by livada |
|
V1.7.1 - Added new algo FreeHaven - Small OpenCL optimisations - Added 3 different modes for heavy algos (Heavy, Haven, BitTube, Italo, FreeHaven) - Added value '9999' for fragments, that sets internally to the value it was in previous 1.6.8 version - Fixed benchmarking mode + startup monitor bug - Fragments, aes, bralock and heavy_mode can be set now outside gpu_conf, so it applies to every GPU
Nice job DOC HAVEN algo: Vega 64LE have 1900+HR Vega 56 ref have 1800HRhttps://prnt.sc/lm5i9yhttps://image.prntscr.com/image/3rrcIubCSMK6Gr5a5aj_4g.jpgNot use any futures option. this is config for 1.6.4 wothout braloc-heavymode-fragment-aes and worksize is 8 int 56 for vega 56 and 60 for vega 64 3*vega56+1vega64 =710W from the wall { "id" : 0, "intensity" : 56, "worksize" : 8, "threads" : 2}, { "id" : 1, "intensity" : 56, "worksize" : 8, "threads" : 2}, { "id" : 2, "intensity" : 60, "worksize" : 8, "threads" : 2}, { "id" : 3, "intensity" : 56, "worksize" : 8, "threads" : 2}, --sendallstales --config config-haven.txt --pools pools-haven.txt --enableduplicategpuid --gpureorder EDIT: itry this : "intensity" : 61, "double_threads" : true, "worksize" : 9, "fragments" : 1, "aes" : 0, "bralock" : 32, "heavy_mode" : 2 but vega 64 have only 1750HR - vega 56 1650HR
|
|
|
|
doktor83 (OP)
|
|
November 23, 2018, 06:51:10 PM |
|
|
|
|
|
livada
Newbie
Offline
Activity: 417
Merit: 0
|
|
November 23, 2018, 07:01:37 PM Last edit: November 23, 2018, 08:31:06 PM by livada |
|
|
|
|
|
|