 Show Posts
|
|
Pages: [1] 2 »
|
I'm getting alot of "pool rejected share (Share Above Target)" errors at nicehash on CryptoNightR
Anyone else getting this too?
Yes, I am as well. Asked about it earlier in the thread but didn't get a response from anyone so figured if might just be my machine. Those errors are nicehash specific, because nicehash is so 'special'. You will get those on every miner, or if not, it means the miner is not showing those messages to the user  Is it Algo specific? I was using CastXMR on CryptonightV8 and on the pool side it was very rare to see rejected share percentage, whereas on Cryptonight-R and this miner I see 10-15% rejected more frequently pool side. |
|
|
|
I'm getting alot of "pool rejected share (Share Above Target)" errors at nicehash on CryptoNightR
Anyone else getting this too?
Yes, I am as well. Asked about it earlier in the thread but didn't get a response from anyone so figured if might just be my machine. |
|
|
|
|
Are "share above target" errors common when mining at Nicehash on Vegas?
My Vega64s are underclocked to 1200/950 core/mem.
|
|
|
|
|
I'm getting quite a few "share above target" errors mining CryptonightR at Nicehash on Vega 64. Miner is saying only 80-85% are accepted.
intensity=0
gpuworksize=16
threads=2
Card is underclocked/undervolted, running 1200MHz/950MHz
Is this normal?
|
|
|
|
How do you use only one GPU out of several in the same PC?
Use something like this, where index is the gpu you want to use: Thanks |
|
|
|
How do you use only one GPU out of several in the same PC? |
|
|
|
|
I'd definitely switch to this if I could use the Adrenalin drivers and get speeds similar to the blockchain drivers.
|
|
|
|
Hash is great -1970H/s+- with these OverdriveNTool settings:
[Profile_0]
Name=Vega56
GPU_P0=852;900
GPU_P1=991;900
GPU_P2=1084;900
GPU_P3=1138;900
GPU_P4=1150;900
GPU_P5=1202;900
GPU_P6=1212;905
GPU_P7=1407;950
Mem_P0=167;900
Mem_P1=500;900
Mem_P2=800;900
Mem_P3=950;900
Fan_Min=3000
Fan_Max=4900
Fan_Target=75
Fan_Acoustic=2400
Power_Temp=85
Power_Target=0
Have you ever tried doing a softpowerplaymod with those settings? Did it work? Whenever I try settings like that, card refuses to boot, or P states "disappear". |
|
|
|
If your hash rate is dropping every few minutes, then your problem is with bad values for P7 and P3 (OverDriveNTool), or too aggressive settings in XMR-STAK config file.
What do you mean by "bad values"? I get hash speed drops within a couple of minutes on my Vegas. Also, I cannot for the life of me get the powerplaysoftmod working for some reason. I noticed that the reg file spit out by OverdriveNTool was slightly different (different number of rows/columns) compared to the reg files posted in the Overclock.net thread. The files posted in the overclock thread allow me to boot into Windows but as soon as I try XMR, it crashes, but it works fine with Eth mining. The files spit out by OverdriveNTool more often than not causes Windows to not boot, so I have to boot into safe mode, load the stock reg file, then reboot, back to square one. Anyone can provide me with some advice on what to try? I'm only doing this because OverdriveNTool is not allowing me to change voltages, only clocks. Running blockchain driver on a Vega 56 and 64, and currently using MSI Afterburner to change voltages since it actually works. |
|
|
|
17.30.1029 BlockChain Drivers from Aug 23
The miner was a version of sgminer
Did you try a DDU and reinstall of the blockchain driver? |
|
|
|
I've scanned this topic but couldn't find an answer for this.
I have 4 Vega 64s that were running NiceHash Cryptonight at the 1900 H/s rate, but since trying to switch the Cast XMR, I keep getting the error about not finding the Compute Drivers.
Yes they are installed.
Win10
16 GB Ram
120 GB SSD (40 GB Virtual Mem)
Any ideas or pointers would be very appreciated. Thanks!
Which driver are you actually running? Which miner were you using before? |
|
|
|
xmr-stak is open-source software, can you point me the place in source code where it is (fast/slow mode depending on drivers version)?
See above post. Stak is slower (~1100h/s) with the 17.11.4 driver vs the blockchain driver. I don't believe that's what they are talking about... Of course the blockchain drivers hash more than 17.11.4 All Red was saying is if you want to play around with the 17.11.4 drivers - XMR-Stak doesn't do a driver check vs Cast which may I don't know if Stak does or doesn't do a "check" but the end result is the same, which is that it is slower, and that's what started the conversation in the first place (whether these programs can work with newer drivers and have good hash rates). |
|
|
|
xmr-stak is open-source software, can you point me the place in source code where it is (fast/slow mode depending on drivers version)?
See above post. Stak is slower (~1100h/s) with the 17.11.4 driver vs the blockchain driver. |
|
|
|
I've used the latest 17.11.4 Optional vega drivers on a machine and its main advantage is allowing the higher then 1107 memory speed and the 1200 SOC clock but its also less stable then the old August compute based drivers. Its mostly designed to further game performance, fix some game bugs nothing much has changed otherwise. Its worth a try if you havent got the results you wanted and/or are going to reinstall drivers anyway but nothing dramatic enough to alter a good working hash rate setup.
So does Cast XMR work at full speed with those drivers? I was of the impression that it still only worked with the blockchain drivers. No, tried with lastest AMD driver. The latest AMD drivers allow for a 'compute mode' swicth, which is equivalent to the blockchain driver. Sadly this miner seems to be a bit silly and refuses to work in optimized mode unless the driver is the blockchain beta. In non -optimized mode, i'm getting 1200 - 1300 h/s with my Vega with Claymore. ~1000 h/s with Cast try xmr-stak, it doesn't check driver version )) Unless it changed recently, it DOES in fact check driver version - and mines in a "slower" mode if you don't have the blockchain drivers. Yep, I tried XMR-Stak with the 17.11.4 driver and it was hashing slower on my 2 Vegas. Also, I did not see a compute/gaming toggle with those drivers. Went back to blockchain driver. Only problem for me is that voltage control is not working with the Blockchain driver and OverdriveNTool. MSI Afterburner works however. I tried the softpowerplay mod but it does something weird where power states keep disappearing when I set clocks/voltages to what I want (ie. on reboot the highest power state disappears, then if I change the next highest one, that disappears on reboot as well). Anyone have OverdriveNTool or softpowerplay working properly with the blockchain drivers? |
|
|
|
|
V1.5 and V1.6 have been crashing the 16.11 driver on my 290. This happens at stock and overclocked. Actually it's weird, I ran 1.5 from release right up until last Tuesday, so about 7 days, when it hung. Since then I cannot get V1.5 or 1.6 to run stable at stock or overclocked settings. This happens with stock or modded BIOSs. V1.3.2 runs without any problem, but speed is lower.
Could something have changed server side on Nicehash that is causing the crashing? Temps are fine as it is watercooled and VRMs are staying at under 70C. Not sure what could suddenly cause the instability.
|
|
|
|
I'm getting an "argument index out of range" error with v1.4 on a 290. Works fine on 1.3.2. Tried changing intensity values, taking out "experimental-kernel" but no luck. Anyone else?
This is a problem with nicehash and v1.4. Use a different pool or run 1.3.2 on nicehash. Will try to provide a fix. The root of the problem is that nicehash sometimes uses extremely long extranonces . This violates some of the optimizations I made for v1.4.0 which causes this error (it should have printed a nice log message but there was a bug there which ended up in this cryptic message). Thanks for the heads up. I went back to 1.3.2. |
|
|
|
I'm getting an "argument index out of range" error with v1.4 on a 290. Works fine on 1.3.2. Tried changing intensity values, taking out "experimental-kernel" but no luck. Anyone else?
This is my bat file:
optiminer.exe -s equihash.usa.nicehash.com:3357 -u someuser -p z -d 2 -i 6 --experimental-kernel
Try -i 5 -i 5 ; -i 4 ; w/o -i the same error and 0 S/s v 1.3 ... work great and I back to 1.3.2 - its still better than last Claymore 11.1 Yeah I also get 0S/s at any intensity. The GPU is doing something though since the GPU usage shoots to 100%, so I'm not sure what is wrong. v1.3.2 works fine for me. |
|
|
|
|
I'm getting an "argument index out of range" error with v1.4 on a 290. Works fine on 1.3.2. Tried changing intensity values, taking out "experimental-kernel" but no luck. Anyone else?
This is my bat file:
optiminer.exe -s equihash.usa.nicehash.com:3357 -u someuser -p z -d 2 -i 6 --experimental-kernel
|
|
|
|
Has anyone found a reliable bios mod for the Sapphire rx 480 8g cards that reduces power but keeps the h/s rate respectable? Most of what I have found on forums have been unstable. I have 4 rigs with 6x Sapphire 8g 480's that each run at around 1200w (and I have a 1300w psu) and 11.5A and deliver 260 H/s on each card with the stock bios and I am having to reduce their intensity each time the mining software speeds the mining up or the whole platform shuts down due to exceeding power limits. I have played with different power tools such as Watttool (Wattman is useless for multiple cards and settings in Claymore just freeze my systems) but I am a bit of an inexperienced computer user so I am not sure what to try and I don't want to damage my systems. I have read every page of this forum as I have worked through all the same issues with Open CL and cards not being recognized, and I appreciate the degree this forum supplies ideas and methods to help others work through their issues. So I am asking my first question around suggested settings in Watt tool or perhaps even a stable and capable bios mod that keeps power down while not giving up on the current performance, if possible. Any help is appreciated.
Wow, 1200w for 6x480?! That's way too power much I think. Is that at the wall? I have a reference 480 (stock BIOS) that runs at 1100/2000 0.85v, hashing at 230S/s and using about 100w. You should be able to get your 480s down to MAX ~150w each while keeping stock clocks at least. I am using Watttool to underclock/undervolt it. |
|
|
|
|
