just 1 hour earlier, i got DAG error when mining ETH with RX570 4GB (my rig have 6 cards). i already set virtual RAM to 40 GB but it still keep telling me that DAG ERROR
Cannot allocate big buffer for DAG.
Cannot write buffer for DAG.
Any idea please?
me too  (( |
|
|
|
Keep it up, hope it optimize with VEGA  |
|
|
|
Nice !!! |
|
|
|
|
do u know how much fee shipping (tax+ship) to VietNam?
|
|
|
|
Wowwwwwwwww  |
|
|
|
What about hashrate for Vega 56 on monero per card !!!
u can see many information about vega on previous pages |
|
|
|
Any hand-on real review |
|
|
|
Hi doktor, I was using version 1.6.3 in my vega 56, using the 1.6.6 i got less 30 hs Using same settings, On other rigs with rx 580 and vega 64 got the same hashes. Just reporting  Tell him which driver you using. |
|
|
|
- If using Blockchain drivers, hashing speed should be like it was before in ver 1.6.2
U save my vegas, again !
Just out of curiosity, why dont you use some of the preferred drivers? Because it BlueScreenOfDeath everytime i install new driver, no matter which version, idk why, and yes i try so fucking many drivers version, so tired. So i just stick with Aug23. |
|
|
|
|
- If using Blockchain drivers, hashing speed should be like it was before in ver 1.6.2
U save my vegas, again !
|
|
|
|
will test new ver |
|
|
|
Hello
I have a few rigs & have tried SRB miner for a few days now ,the hashrate is high compared to XMR-STAK & xmring .The only problem is that on the pool side its showing a reduced hashrate of 10-15% .What till be the reason for this ?.
I have used the same port as XMR stak
Thanks
You probably got a lot stale shares, download latest 1.6.4 v and use --sendallstales parameter in bat, it will probably increase your effective hashrate Doc, is there any quick way to know pool support your --sendallstales command. (U tell in previous post that some pool don't support and may lose hashrate/share, right?, correct me if i wrong). I will test new ver. |
|
|
|
Anyone can share the devcon file config reset for vega, please.
.reset.bat cd %~dp0 timeout /t 10 devcon.exe disable "PCI\VEN_1002&DEV_687F" timeout /t 10 devcon.exe enable "PCI\VEN_1002&DEV_687F" timeout /t 10 This works for my Vega FEs @echo off cd %~dp0 devcon.exe disable "PCI\VEN_1002&DEV_6863" timeout /t 3 devcon.exe enable "PCI\VEN_1002&DEV_6863" timeout /t 3 pause thank you so much So based on what I have read here: On SRB 1.6.3 with Vega 64s, people are getting about 2165 H/s a bit more or less. I have been getting ~2180 H/s on each Vega FE with blockchain driver since SRB 1.5.4 or so.... If I cool them even better, I'd get 2200 on them too. So this all means as a Vega FE owner I should stick with my 1.6.1 and still have 5 or 10 H/s more than Vega 64 with the latest driver, not that it matters. But I am sure if ever they make another proper blockchain driver these cards can do much more.
i know that feel. Make the fan run 3500rpm minimum. Doc, i love u, my vega56 ref even reach 2000h/s with powersaving profile [2018-07-10 18:03:24] GPU3 : 2001 H/s [T: 69c, RPM: 4303, CC: 1400 MHz, MC: 950 MHz][BUS:3] intensity 120/ dual_threads true |
|
|
|
|
Anyone can share the devcon file config reset for vega, please.
|
|
|
|
Doc, tks for 1.6.3
I still stick with Aug23. I will test and report the result. Hope it got buff hashrate too!!!
Vega56 REF AUG23 driver 1.6.2 5648h/s 1.6.3 52xxh/s Sad. IDK why my rigs can't stable on new driver. Anyone vega here? which driver u using? Ouch. Im testing Vega on 18.3.4 version, it's really stable for me. ya, i will try, thank doc btw, someone should buy for you a white lab coat, haha, can't wait |
|
|
|
|
Show Posts
