It's practically impossible...
It's not. I have a couple of systems, too, which were rebootet last time several years ago. When the system is stable and auto updates are off, why should a system not run for years?  Different weather conditions - thunder, f.e. Power disconnections. In all countries there is a planned power disconnections to support power lines, etc. Updating drivers... |
|
|
|
I have been runing vegas on windoz for nearlly a year now
One year without a single restart on Windows??  It's practically impossible... |
|
|
|
Thanks for reminder.
Windows 10 1709
AMD Driver 18.3.4
GPU-Z v2.9.0
what settings did you run the test on? config for srb and jce. That can indicate performance diff too. With JCE, I use auto config for GPU, disabled CPU. And with SRB, I set intensity to 53 (default is 51 for 580 8gb). 56 dual threads works best for SRB. But yea I get higher hashrate on JCE on tube algo but cn-heavy is the same. 59 works better... On JCE 944 now better than 832 or 864. But speed on JCE jumps up and down to much... About 100 h/s up/down... |
|
|
|
hi all,
--no-cpu to disable cpu mining (manual or auto) and its reciprocal --no-gpu (but better use the cpu-only version in such case). thanks Unclwish for the reply.
ok i note the requests about gpu fan/temp, right, but i will add read-only features. it may be damaging to set voltage too high or fan too slow. that's a job for afterburner or overdriventool. but temp/fan read is useful and needed for watchdog.
jce is detected as trojan like every miner, but it contains no malicious code, really.
Nice! Yes, it's just read-only features. For me, I use overdriventool to do overclock and undervolt, it's ok. Thanks for your support. Also, just to inform if no one knows yet. Just like SRB, running GPU-Z after running JCE-Miner can trigger the hashrate higher. Here is the steps: 1. Run the miner until you see the miner receives first job from pool. 2. Wait until the console of GPU-Z appear, and then close it. 3. Now, press h to see your hashrate. Other thing, below the screen shot of the comparison between SRB and JCE Miner, using same pool, same Overdriventool setting. It is 8x HIS 580 8GB Hynix. Algo: bittube v2 JCE Miner is higher about 10-20 h/s /card. https://imgur.com/NfqsMj3You forgot to point Windows version, drivers version and GPU-Z version to work all of it... Thanks for reminder. Windows 10 1709 AMD Driver 18.3.4 GPU-Z v2.9.0 This method woudn't work on Windows 10 1803. So it's allready useless... |
|
|
|
hi all,
--no-cpu to disable cpu mining (manual or auto) and its reciprocal --no-gpu (but better use the cpu-only version in such case). thanks Unclwish for the reply.
ok i note the requests about gpu fan/temp, right, but i will add read-only features. it may be damaging to set voltage too high or fan too slow. that's a job for afterburner or overdriventool. but temp/fan read is useful and needed for watchdog.
jce is detected as trojan like every miner, but it contains no malicious code, really.
Nice! Yes, it's just read-only features. For me, I use overdriventool to do overclock and undervolt, it's ok. Thanks for your support. Also, just to inform if no one knows yet. Just like SRB, running GPU-Z after running JCE-Miner can trigger the hashrate higher. Here is the steps: 1. Run the miner until you see the miner receives first job from pool. 2. Wait until the console of GPU-Z appear, and then close it. 3. Now, press h to see your hashrate. Other thing, below the screen shot of the comparison between SRB and JCE Miner, using same pool, same Overdriventool setting. It is 8x HIS 580 8GB Hynix. Algo: bittube v2 JCE Miner is higher about 10-20 h/s /card. https://imgur.com/NfqsMj3You forgot to point Windows version, drivers version and GPU-Z version to work all of it... |
|
|
|
Very nice. I today tested the miner first time a bit more on my RX580 8GB and it gives good results. At least in the same ball park as cast xmr, which was for me better than srbminer.
Since autoconf is a thing, is there also a cli parameter to disable CPU mining?
Use command line option --no-cpu |
|
|
|
Hello guys! Could someone help with right .bat and .config? I'd like to test using rig with six RX480 8G, blockch. driver. Thanks in advance)
For proper work of GPU miner it's need Windows 8.1 and higher with 18.3.4 or later driver. |
|
|
|
|
And it's need hw controls to overclock, undervolt, fan control, etc...
|
|
|
|
|
JCE, i can't understand, why miner can't allocate all of 4Gb vmemory of my 270X. Max it can use is 3,5Gb. If I set multihash to use higher than 3Gb, miner gives CL_memory allocate error...
In info about devices at start miner shows that card have 4Gb vmemory...
|
|
|
|
Both memory model and openCL code of version 0.32+ are completely new. It's somehow like Claymore 9 and 10+ : maybe better, maybe worse, but completely different. I cannot go back to the long-compiling versions, now i must still improve the new code. Good news ! Detecting OpenCL-capable GPUs...
Calling clGetPlatformIDs
Returned CL_UNKNOWN_ERROR -1001
Found 0 OpenCL PlatformIDs
0█└☻
I can reproduce the no-gpu bug on my Win7+betablockchain rig i just installed, and on which i'm writing from right now. I didn't find the cause yet, but i can reproduce! edit: Bad news this time I found the reason it failed on Win7 is that my protection technique of injecting my opencl code directly into the drivers, bypassing the normal way of calling OpenCL compiler, to prevent hackers to dump my code on the fly, is just not compatible with Win7. I've the choice to give up security, or to giveup Win7 support. I couldn't find any way to keep both, so I drop Win7 support on the GPU part (cpu mining still works down to Vista 32). Sorry JuanHungLo for the bad ending, but at least i fully understood the problem. Other miners work because they use a clear openCL api, I use a hacky one, on purpose, for security. I'll update my documentation to state Win7 is not supported. I tested on Win8.1 and it works fine. Maybe it's even better. Windows 10 often gives more mining speed than Win7. Windows 10 with at least 4Gb vmemory works with the same speed as Win7, and often quicker. I not understand why use Windows 7 at all. For these, who affraid Win10 spying and many unuseful options and apps, exists LTSB version of Windows 10 wich have minimal size and don't have many apps... Just google Windows 10 LTSB. |
|
|
|
|
JCE, please, add in report speed statistics for periods of time. An half hour, hour, etc...
And it's need minrigspeed option to restart miner if speed lower than pointed in option for 5 min or time pointed in 2nd option minrigspeedperiod.
P.S. Looks like at start and during several minutes in heavy algo speed every time differs...
|
|
|
|
|
JCE, I think you must change string when kernels compiles. It still writes "...it will be long..." Now it quick )))
|
|
|
|
On what drivers normal-v7 with 1.6.4 works? I have no shares on 18.7.1. Heavy works normal...
P.S. Miner didn't show rejected duplicate shares. Nicehash pool report rejected duplicate, but miner this share count to accepted...
P.P.S. Hmmm, on AMD site 18.7.1 driver from 19.07.2018... But I have installed from 12.07.2018... Will try to download and reinstall...
18.7.1 is buggy... Maybe there is a re-uploaded version with silent fix ) Updated redownloaded driver, but nothing changes. normal cnv7 didn't finds shares... Who else tried normalv7 algo on 18.7.1 driver? |
|
|
|
|
Tested new 32 version. Works fine. Especcially fast compiling - it's amazing! Thanx for it!
But I noticed that settings for GPU's now optimal some other than before. Maybe it's due to 18.7.1 driver.
Now best m.hash for heavy algo is 944, not 832 or 864...
For normal V7 close to twice m.hash from heavy.
And i noticed that speed now not so stable on heavy algo. It jumps +50-100 h/s up and down even after 10 minutes of mining...
|
|
|
|
|
On what drivers normal-v7 with 1.6.4 works? I have no shares on 18.7.1. Heavy works normal...
P.S. Miner didn't show rejected duplicate shares. Nicehash pool report rejected duplicate, but miner this share count to accepted...
P.P.S. Hmmm, on AMD site 18.7.1 driver from 19.07.2018... But I have installed from 12.07.2018... Will try to download and reinstall...
|
|
|
|
What about no finding shares on cn-v7 with 1.6.4 on nicehash?
its not a miner issue , or stupid nicehash changed something in their imaginary stratum, or i don't know and have to check it out  No, it's your miner issue, because other miners like Claymore 11.3 or JCE miner founds shares normal. But your miner not. I tried on 1.6.3 and tried noSSL port 3363 and SSL 33363. Eu server... No one share for 10 minutes. Speed 2kH/s. You can clearly see on the image it found a share in less than a minute, so its working. You first said no share for 4 hours, now 10 minutes. Next will be 2 seconds. 1st time I checked not 4 hours, but close to 1 hour. After when I tried I allways wait 10 minutes. But not 1.6.3, not 1.6.4 on SSL and not didn't find not 1 share for 10 minutes. I tried to run Claymore and JCE miner. They found shares every 1-2 minute at least. Here screenshot:  |
|
|
|
What about no finding shares on cn-v7 with 1.6.4 on nicehash?
its not a miner issue , or stupid nicehash changed something in their imaginary stratum, or i don't know and have to check it out No, it's your miner issue, because other miners like Claymore 11.3 or JCE miner founds shares normal. But your miner not. I tried on 1.6.3 and tried noSSL port 3363 and SSL 33363. Eu server... No one share for 10 minutes. Speed 2kH/s. |
|
|
|
|
What about no finding shares on cn-v7 with 1.6.4 on nicehash?
|
|
|
|
Is anyone else having issues with V1.6.4, CryptoNight Normal v7 and Nicehash?
I've tried on 2 different systems and neither will submit any valid shares.
I confirm. Didn't find any share at all for hour. Difficulty 100000. On heavy with 200000 diff average share found time about 40-50 sec. |
|
|
|
any have a config? for mining only 1 / 2 /3 gpu
i am try -d command not run
Use config file in wich describe only your 3 gpu's. Like this: "gpu_threads_conf" : [ { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 0, "multi_hash":832 }, { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 0, "multi_hash":832 }, { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 1, "multi_hash":832 }, { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 1, "multi_hash":832 }, { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 2, "multi_hash":832 }, { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 2, "multi_hash":832 }, ] |
|
|
|
|
Show Posts
