iRonNuke
Jr. Member
Offline
Activity: 98
Merit: 6
|
 |
March 23, 2019, 07:44:37 PM |
|
Why am I getting a lot of rejected shares? "Pool rejected result 0x000074E1 for job[2] [low difficulty share]" By a lot I mean some, most shares are ofcourse accepted but still, quite frequent.
Pool difficulty is set at 120000 by default. May I change it for better results?
The pool I'm using is nanopool.org btw.
You get low diff shares when your gpu returns a bad result. So loosen on your OC , or depending of your card, maybe you use 'bad' mem. straps. Is there any way to see what GPU that is getting this error, if it's just one or all GPUs? I can see how many errors and frequency in %. It just says what job number it is? 95,5% accepted shares. Maybe not much to care about in about one hour?
|
|
|
|
pbfarmer
Member

Offline
Activity: 340
Merit: 29
|
 |
March 23, 2019, 10:07:34 PM |
|
Testing now 19.3.2 and ONT 0.2.8, the timing level whatever i put isn't changing the hashrate for me on Vega56. Is it just me or .. ?  I've never seen any results from changing timing levels in wattman. I get the sense they put in the functionality, maybe to provide actual timings at a later date.
|
|
|
|
pbfarmer
Member

Offline
Activity: 340
Merit: 29
|
 |
March 23, 2019, 10:22:25 PM Last edit: March 23, 2019, 11:00:47 PM by pbfarmer |
|
DOKTOR83, there is a memory pill for AMD Could you implement it on windows ? Right now it's linux only.
Cryptonights are not so sensitive to memory straps, it's good for ETH This is absolutely not true. At least earlier versions of CN (haven't personally confirmed w/ cnv4) saw significant benefits from lower latencies. ETH on the other hand, being bandwidth sensitive, does best w/ higher clocks, which in some cases requires higher latencies. For example - the commonly available 'ubermix' straps for samsung were great for CN - they do not seem to be the best for ETH as the timings are so tight, clocks tend to be capped around 2K.
|
|
|
|
AVP
Newbie
Offline
Activity: 96
Merit: 0
|
 |
March 23, 2019, 11:05:38 PM |
|
Is anyone experiencing crashes & freezes on GRAFT algo ?
I'm seeing this on RX 470 rigs & RX 560 rigs. (RX 570 rigs seem fine)
|
|
|
|
MinermanNC
Legendary
Offline
Activity: 2212
Merit: 1000
|
 |
March 24, 2019, 02:57:45 AM |
|
I have SRB MINER CN 1.181 running perfectly on windows 7 pushing 2 AMD 7790's Can not get it to run correctly on Windows 10 pushing 1 R9 270x. It starts and receives work from pool, but does not find any shares. Nor does it display any GPU readings "temp, fan speed etc.. shows all zeros there. Thanks  When you try out different drivers every time clear the cache directory. R9 270x cards work fine on W10 and 18.6.1 drivers. Hey thanks will give that a try. I have not done that and will try 18.6.1 drivers 
|
*BTC: 1DiR25SPo84sThzTATr27EZEQZLt6hv6tG
|
|
|
3MEHDI
Newbie
Offline
Activity: 6
Merit: 0
|
 |
March 24, 2019, 08:52:12 AM |
|
V1.8.1 - Fixed a bug that could crash miner if using CNV4 (R) algo - Fixed a bug that crashed miner if doing fast algo switching from CNV4 to any algo - Stales are not displayed anymore by default, added parameter --showstales which turns back on the display of stale shares - Changed --maxnosharesent default value from 15 minutes to 30 - Logging is now disabled by default in the example start.bat - Added parameter --preparedata, which could pontentially make a small speed increase on weak GPU's, but also could make it worse. All algos except webchain
+ If you are having ocassional crashes out of nowhere while mining the new V4 (R) algo, please update to version 1.8.1 as this issue is now (hopefully) fixed
+ The info miner displays and is called 'stale shares' is not displayed by default anymore, so if you miss it, and know what is it (it only displays the number of shares sent after a new job was received, it's not the real number of stale shares - that's something only the pool knows), then you can turn it back on by adding --showstales in start.bat
+ A new experimental (beta) parameter --preparedata added, and when enabled CPU will prepare some stuff for the GPU before it begins to work, so this *could* potentially lead to a small increase in hashrate on weaker, older GPU's. I tested on Vega56 and Rx58x series, and there was no gain, but i would like someone to test on weak cards that i don't have, older gcn1,2 series.
Please all of you having crashes on 1.7.9 and 1.8.0 on V4 algo , try out 1.8.1 as this issue should be fixed now.
Hi dear i install version 1.8.1 After 8 to 9 hours, the temperature of my Gpu increases without reason. Up to 80 ° C I will have to re-run the Meining software Again 8 to 9 hours later this happens The problem is not the cooling system 3x sapphire orginal pack vega 56 upgrade bios to vega 64 samsung chip
|
|
|
|
Piradoxlanieve
Newbie
Offline
Activity: 70
Merit: 0
|
 |
March 24, 2019, 09:14:28 AM |
|
Since the last versions, the SRBMiner-CN.exe stopped working, I have to close and re-run manually, the executable does not restart itself, I'm mining bittube, my rig is 6 rx480, 1 rx580 and 1 gtx1070, before it did not happen but now it happens 2 times or 3 a day. Sorry my bad english. Windows error report Nombre de la aplicación con errores: SRBMiner-CN.exe, versión: 1.8.1.0, marca de tiempo: 0x00000000 Nombre del módulo con errores: SRBMiner-CN.exe, versión: 1.8.1.0, marca de tiempo: 0x00000000 Código de excepción: 0xc0000005 Desplazamiento de errores: 0x0000000000085db8 Identificador del proceso con errores: 0x165c Hora de inicio de la aplicación con errores: 0x01d4e1f818cc07ae Ruta de acceso de la aplicación con errores: C:\Users\RX480\Desktop\SRBMiner-CN\SRBMiner-CN.exe Ruta de acceso del módulo con errores: C:\Users\RX480\Desktop\SRBMiner-CN\SRBMiner-CN.exe Identificador del informe: 473c3244-8f9e-40f4-8ea6-5ed4271bbe3f Nombre completo del paquete con errores: Identificador de aplicación relativa del paquete con errores:
|
|
|
|
ikicha
|
 |
March 24, 2019, 11:57:02 AM |
|
V1.8.1 - Fixed a bug that could crash miner if using CNV4 (R) algo - Fixed a bug that crashed miner if doing fast algo switching from CNV4 to any algo - Stales are not displayed anymore by default, added parameter --showstales which turns back on the display of stale shares - Changed --maxnosharesent default value from 15 minutes to 30 - Logging is now disabled by default in the example start.bat - Added parameter --preparedata, which could pontentially make a small speed increase on weak GPU's, but also could make it worse. All algos except webchain
+ If you are having ocassional crashes out of nowhere while mining the new V4 (R) algo, please update to version 1.8.1 as this issue is now (hopefully) fixed
+ The info miner displays and is called 'stale shares' is not displayed by default anymore, so if you miss it, and know what is it (it only displays the number of shares sent after a new job was received, it's not the real number of stale shares - that's something only the pool knows), then you can turn it back on by adding --showstales in start.bat
+ A new experimental (beta) parameter --preparedata added, and when enabled CPU will prepare some stuff for the GPU before it begins to work, so this *could* potentially lead to a small increase in hashrate on weaker, older GPU's. I tested on Vega56 and Rx58x series, and there was no gain, but i would like someone to test on weak cards that i don't have, older gcn1,2 series.
Please all of you having crashes on 1.7.9 and 1.8.0 on V4 algo , try out 1.8.1 as this issue should be fixed now.
Hi dear i install version 1.8.1 After 8 to 9 hours, the temperature of my Gpu increases without reason. Up to 80 ° C I will have to re-run the Meining software Again 8 to 9 hours later this happens The problem is not the cooling system 3x sapphire orginal pack vega 56 upgrade bios to vega 64 samsung chip Try to disable automatic temp configuration or try extra conf : "target_temperature" : 70, "shutdown_temperature" : 80, Goodluck
|
|
|
|
babkaVkedax
Newbie
Offline
Activity: 59
Merit: 0
|
 |
March 24, 2019, 05:37:44 PM |
|
SRBMiner Cryptonight AMD GPU Miner All - rx 570 4gb problem All drivers, except Win10-64Bit-Crimson-ReLive-Beta-Blockchain-Workloads-Aug23 hash rate is 2 times lower than it should be eg: haven 750/780 --- 340/350 How to solve a problem? Thank.
|
|
|
|
iRonNuke
Jr. Member
Offline
Activity: 98
Merit: 6
|
 |
March 24, 2019, 05:50:16 PM |
|
SRBMiner Cryptonight AMD GPU Miner All - rx 570 4gb problem All drivers, except Win10-64Bit-Crimson-ReLive-Beta-Blockchain-Workloads-Aug23 hash rate is 2 times lower than it should be eg: haven 750/780 --- 340/350 How to solve a problem? Thank.
Why are you using a soon 2 year old driver?  Maybe that's the issue, don't know. But try atleast 1.8.6.1 or any newer and enable compute mode.
|
|
|
|
doktor83 (OP)
|
 |
March 24, 2019, 06:06:48 PM |
|
SRBMiner Cryptonight AMD GPU Miner All - rx 570 4gb problem All drivers, except Win10-64Bit-Crimson-ReLive-Beta-Blockchain-Workloads-Aug23 hash rate is 2 times lower than it should be eg: haven 750/780 --- 340/350 How to solve a problem? Thank.
Compute mode. Enable compute mode. https://www.srbminer.com/start.html
|
|
|
|
babkaVkedax
Newbie
Offline
Activity: 59
Merit: 0
|
 |
March 24, 2019, 07:24:40 PM |
|
SRBMiner Cryptonight AMD GPU Miner All - rx 570 4gb problem All drivers, except Win10-64Bit-Crimson-ReLive-Beta-Blockchain-Workloads-Aug23 hash rate is 2 times lower than it should be eg: haven 750/780 --- 340/350 How to solve a problem? Thank.
Compute mode. Enable compute mode. https://www.srbminer.com/start.htmlThank you very much.
|
|
|
|
babkaVkedax
Newbie
Offline
Activity: 59
Merit: 0
|
 |
March 24, 2019, 07:33:10 PM |
|
SRBMiner Cryptonight AMD GPU Miner All - rx 570 4gb problem All drivers, except Win10-64Bit-Crimson-ReLive-Beta-Blockchain-Workloads-Aug23 hash rate is 2 times lower than it should be eg: haven 750/780 --- 340/350 How to solve a problem? Thank.
Why are you using a soon 2 year old driver?  Maybe that's the issue, don't know. But try atleast 1.8.6.1 or any newer and enable compute mode. Oddly enough, but all video cards with 4GB of Win10-64Bit-Crimson-ReLive-Beta-Blockchain-Workloads-Aug23 show a higher hash rate! Thanks for the answer.
|
|
|
|
doktor83 (OP)
|
 |
March 24, 2019, 07:34:47 PM |
|
SRBMiner Cryptonight AMD GPU Miner All - rx 570 4gb problem All drivers, except Win10-64Bit-Crimson-ReLive-Beta-Blockchain-Workloads-Aug23 hash rate is 2 times lower than it should be eg: haven 750/780 --- 340/350 How to solve a problem? Thank.
Why are you using a soon 2 year old driver?  Maybe that's the issue, don't know. But try atleast 1.8.6.1 or any newer and enable compute mode. Oddly enough, but all video cards with 4GB of Win10-64Bit-Crimson-ReLive-Beta-Blockchain-Workloads-Aug23 show a higher hash rate! Thanks for the answer. Well if you don't have problems with the blockchain driver + you have better hashrate, why don't you stay on it ? 
|
|
|
|
babkaVkedax
Newbie
Offline
Activity: 59
Merit: 0
|
 |
March 24, 2019, 07:59:37 PM |
|
SRBMiner Cryptonight AMD GPU Miner All - rx 570 4gb problem All drivers, except Win10-64Bit-Crimson-ReLive-Beta-Blockchain-Workloads-Aug23 hash rate is 2 times lower than it should be eg: haven 750/780 --- 340/350 How to solve a problem? Thank.
Why are you using a soon 2 year old driver?  Maybe that's the issue, don't know. But try atleast 1.8.6.1 or any newer and enable compute mode. Oddly enough, but all video cards with 4GB of Win10-64Bit-Crimson-ReLive-Beta-Blockchain-Workloads-Aug23 show a higher hash rate! Thanks for the answer. Well if you don't have problems with the blockchain driver + you have better hashrate, why don't you stay on it ?  On one computer I put video cards on 8GB and 4GB. There is a problem with 4GB. Now the problem is solved. Thank.
|
|
|
|
|
doktor83 (OP)
|
 |
March 24, 2019, 08:53:41 PM |
|
Hi....I have 8 rigs, this is the only one that will not run the newest version. Any suggestions? Here's the log:  for marketcash use an earlier version, this bug will be fixed in the next version
|
|
|
|
ledgerdary
Newbie
Offline
Activity: 7
Merit: 0
|
 |
March 25, 2019, 10:15:55 AM |
|
In the top post, it is suggested to use Driver 19.3.2 for Cryptonight V4. I'm running a Vega 56 on 1.8.1, but since I updated my drivers from 18.6.1 to 19.3.2, I get low difficulty shares that get rejected by the pool every now and then. Any suggestions on how to solve this? And is anyone else running 56s in a similar manner? Is CC 1400/950, MC 950/900 optimal? Thanks in advance!
|
|
|
|
smeads
Newbie
Offline
Activity: 17
Merit: 0
|
 |
March 25, 2019, 12:35:30 PM |
|
for marketcash use an earlier version, this bug will be fixed in the next version When will the new version w/ the fixes for MKT be released? You should have mentioned this in the current release, I would not have released an update of my software with your newest mining software. Please push out the fix soon.
|
|
|
|
doktor83 (OP)
|
 |
March 25, 2019, 12:56:15 PM |
|
When will the new version w/ the fixes for MKT be released? You should have mentioned this in the current release, I would not have released an update of my software with your newest mining software. Please push out the fix soon.
I plan on releasing the new version today, i couldn't mention that MKT isn't working because i did not know until i saw your screenshot 
|
|
|
|
|