keksik
Jr. Member
 Offline
Activity: 169
Merit: 1
|
 |
October 16, 2018, 10:47:55 PM |
|
hello im mining with:
6x rx 570 4gb
windows 10 x64
srbminer 1.6.8
1150/850 + 2000/850 (memory vary as range for all 6 is 1950-2050) elpida/hynix. my point is, it was stable for ethereum, i switched for lite v7 earlier today and later today wanted try V7 also, but now the gpus/miner throw warning like gpu xxx is mining 0H/s. and it happen for one or for all. any idea why it is happening? how to fix it?
what is ste optimal frequency for rx 570 and voltage?
|
|
|
|
|
|
|
|
|
|
|
|
Whoever mines the block which ends up containing your transaction will get its fee.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
P00P135
|
|
October 16, 2018, 11:09:26 PM |
|
hello im mining with:
6x rx 570 4gb
windows 10 x64
srbminer 1.6.8
1150/850 + 2000/850 (memory vary as range for all 6 is 1950-2050) elpida/hynix. my point is, it was stable for ethereum, i switched for lite v7 earlier today and later today wanted try V7 also, but now the gpus/miner throw warning like gpu xxx is mining 0H/s. and it happen for one or for all. any idea why it is happening? how to fix it?
what is ste optimal frequency for rx 570 and voltage?
Eth bios mods and memory straps arent the best for cryponote algos. so you'll need to re-tune to find what works best. |
|
|
|
|
|
tg88
|
|
October 17, 2018, 12:58:44 AM
Last edit: October 17, 2018, 03:05:21 PM by tg88 |
|
what is ste optimal frequency for rx 570 and voltage?
I would start testing with these clocks: Core: 1250/950 Mem: 1950/950 |
|
|
|
|
|
P00P135
|
|
October 17, 2018, 01:07:11 AM |
|
what is ste optimal frequency for rx 570 and voltage?
I would start testing with these clocks: Core: 2250/950 Mem: 1950/950 2250 core? Good way to blow up your 570  Probably meant 1250. |
|
|
|
|
dfish987
Newbie
Offline
Activity: 27
Merit: 0
|
|
October 17, 2018, 04:16:46 AM |
|
is anyonme else having issues keeping 1.6.8 running for some reason 2 of my 3 rigs running a mix of rx 480s and a 470 on one and rx 470s and a rx 570 on the other Rig i can't for the life of me get these too to run 24 hrs straight miner is always saying gpu crash and restarts some times 40 mins goes by some times they run for 4 to 5 hrs im just not a fan of this update 1.6.7 was much better but i have tried auto intensity which sets them around 55 and i tried lowering the intensity nothing works but heres the kicker my 8 gpu rx rig runs just fine but it is on the older verson of windows 1709 so is windows the problem with 1803 or what can i try ......  ? |
|
|
|
|
|
doktor83 (OP)
|
|
October 17, 2018, 05:23:42 AM |
|
So there is no way to get it to work with older AMD drivers like 15.12 ? This is on Windows 7.
Basically starting the start.bat or the SRBMiner-CN.exe results in an instant exit and doesn't even provide an error. Checked the log file and nothing was created.
put a pause at the end of the start.bat so it won't close the window and you probably have a parse error in the config file. |
|
|
|
hesido
Jr. Member
Offline
Activity: 157
Merit: 5
|
|
October 17, 2018, 05:26:07 AM |
|
is anyonme else having issues keeping 1.6.8 running for some reason 2 of my 3 rigs running a mix of rx 480s and a 470 on one and rx 470s and a rx 570 on the other Rig i can't for the life of me get these too to run 24 hrs straight miner is always saying gpu crash and restarts some times 40 mins goes by some times they run for 4 to 5 hrs im just not a fan of this update 1.6.7 was much better but i have tried auto intensity which sets them around 55 and i tried lowering the intensity nothing works but heres the kicker my 8 gpu rx rig runs just fine but it is on the older verson of windows 1709 so is windows the problem with 1803 or what can i try ...... ? 1803 is hot garbage, I just did a clean install, it doesn't work with the 18.3.1 drivers, and now with 18.6.1 + 1803 fell down to (on heavy) from 8500 to 7600. Insane loss of hashrate. People probably don't know what they are missing. I installed because 1.6.8 had lowered hashrates on my setup and maybe thought it was because it was tested on 18.6.1 but in my case this did not help. |
|
|
|
|
|
doktor83 (OP)
|
|
October 17, 2018, 05:30:20 AM |
|
I just checked on my test machines i have win10 v1703 and v1709, also win7 x64. @hesido I will (re) introduce a parameter in 1.6.9, which will probably help you re-gain the hashrate you had. Just have to make the algo switching crash-free first  |
|
|
|
hesido
Jr. Member
Offline
Activity: 157
Merit: 5
|
|
October 17, 2018, 07:23:32 AM |
|
I just checked on my test machines i have win10 v1703 and v1709, also win7 x64. @hesido I will (re) introduce a parameter in 1.6.9, which will probably help you re-gain the hashrate you had. Just have to make the algo switching crash-free first That's great to hear. I'll have to go back to 1703 or 1709 first though, there's probably nothing you can do about 1803 (and probably 1809) windows build. I'll just wait with this low hashrate on 1803 to test it first before going back, luckily I had made an image backup, but I have no idea what miners with new Windows installations can do, new windows installations will all be 1803 or higher. I suggest anyone with 1703 or 1709 to do a backup right this very moment. An update can make your mining a nightmare. The thing with 1809 + 1.6.1 is, one or two GPU may, by chance, hash at their previous performances. Maybe it's some I/O problem, maybe something else, but most definitely it's a bad combination. |
|
|
|
|
tanatana
Newbie
Offline
Activity: 51
Merit: 0
|
|
October 17, 2018, 08:44:49 AM |
|
what are the appropriate video card settings R9 270X 2GB?
{ "id" : 0, "intensity" : 56, "worksize" : 8, "threads" : 1} - thus gives an error
{ "id" : 0, "intensity" : 2, "worksize" : 8, "threads" : 1} - error
{ "id" : 0, "intensity" : 24, "worksize" : 4, "threads" : 1} - low speed 270 hs
{ "id" : 0, "intensity" : 48, "worksize" : 4, "threads" : 1} - low speed 360 hs
{ "id" : 0, "intensity" : 60, "worksize" : 4, "threads" : 1} - error
I'm looking for about 450
|
|
|
|
|
|
dragonmike
|
|
October 17, 2018, 09:14:56 AM |
|
I just checked on my test machines i have win10 v1703 and v1709, also win7 x64. @hesido I will (re) introduce a parameter in 1.6.9, which will probably help you re-gain the hashrate you had. Just have to make the algo switching crash-free first Well, hurry up, doc, you've got 24 hours! (well actually less 'cause we can't really test at night)... Can someone tell me how I can test CNv8 please? I need some kind of test-pool I can point my hash towards. |
|
|
|
|
Lio78
Newbie
Offline
Activity: 35
Merit: 0
|
|
October 17, 2018, 09:15:43 AM |
|
Hi, I have this message from my pool.
"low difficulty share" if I use v8 instead v7
I use SRBMiner 1.6.8 with Vega64 and RX580.
Anyone can help me please?
|
|
|
|
|
BS0D
Newbie
Offline
Activity: 20
Merit: 0
|
|
October 17, 2018, 09:27:58 AM |
|
I just checked on my test machines i have win10 v1703 and v1709, also win7 x64. @hesido I will (re) introduce a parameter in 1.6.9, which will probably help you re-gain the hashrate you had. Just have to make the algo switching crash-free first Well, hurry up, doc, you've got 24 hours! (well actually less 'cause we can't really test at night)... Can someone tell me how I can test CNv8 please? I need some kind of test-pool I can point my hash towards. Try to mine Wownero. It is already at v8. |
|
|
|
|
|
doktor83 (OP)
|
|
October 17, 2018, 09:30:49 AM |
|
I just checked on my test machines i have win10 v1703 and v1709, also win7 x64. @hesido I will (re) introduce a parameter in 1.6.9, which will probably help you re-gain the hashrate you had. Just have to make the algo switching crash-free first Well, hurry up, doc, you've got 24 hours! (well actually less 'cause we can't really test at night)... Can someone tell me how I can test CNv8 please? I need some kind of test-pool I can point my hash towards. Test on http://killallasics.moneroworld.com |
|
|
|
|
doktor83 (OP)
|
|
October 17, 2018, 09:31:31 AM |
|
Hi, I have this message from my pool.
"low difficulty share" if I use v8 instead v7
I use SRBMiner 1.6.8 with Vega64 and RX580.
Anyone can help me please?
Dont use V8 yet, Monero still haven't switch |
|
|
|
Lio78
Newbie
Offline
Activity: 35
Merit: 0
|
|
October 17, 2018, 09:35:46 AM |
|
Hi, I have this message from my pool.
"low difficulty share" if I use v8 instead v7
I use SRBMiner 1.6.8 with Vega64 and RX580.
Anyone can help me please?
Dont use V8 yet, Monero still haven't switch Thank you Doctor  |
|
|
|
|
|
dragonmike
|
|
October 17, 2018, 09:49:26 AM |
|
Dok, is there a way to incorporate MoneroV8 into the pools-algoswitch file, i.e. moneroocean would switch to MoneroV8 automatically if it's included there? I'd like to keep using the normal algoswitching until the fork - and then, arguably, moneroocean would switch everyone to Monerov8 after the fork.
...or do I need to restrict mining to XMR and populate the pools-fork.txt file with the v7 and v8 pools for it to switch?
|
|
|
|
|
|
doktor83 (OP)
|
|
October 17, 2018, 10:02:23 AM |
|
Dok, is there a way to incorporate MoneroV8 into the pools-algoswitch file, i.e. moneroocean would switch to MoneroV8 automatically if it's included there? I'd like to keep using the normal algoswitching until the fork - and then, arguably, moneroocean would switch everyone to Monerov8 after the fork.
...or do I need to restrict mining to XMR and populate the pools-fork.txt file with the v7 and v8 pools for it to switch?
if you are using MO, and the pool sends you a new job that is V8, miner will restart automatically with the v8 settings, so you don't need the pools-fork.txt trick. |
|
|
|
|
dragonmike
|
|
October 17, 2018, 10:03:46 AM |
|
Dok, is there a way to incorporate MoneroV8 into the pools-algoswitch file, i.e. moneroocean would switch to MoneroV8 automatically if it's included there? I'd like to keep using the normal algoswitching until the fork - and then, arguably, moneroocean would switch everyone to Monerov8 after the fork.
...or do I need to restrict mining to XMR and populate the pools-fork.txt file with the v7 and v8 pools for it to switch?
if you are using MO, and the pool sends you a new job that is V8, miner will restart automatically with the v8 settings, so you don't need the pools-fork.txt trick. Fantastic! I'll just add the v8 settings and pool under the algoswitch and bob's my uncle. If profitability lives up to expectations MO should switch to V8 pretty much straight after the fork goes live. |
|
|
|
|
|
doktor83 (OP)
|
|
October 17, 2018, 10:15:30 AM |
|
Dok, is there a way to incorporate MoneroV8 into the pools-algoswitch file, i.e. moneroocean would switch to MoneroV8 automatically if it's included there? I'd like to keep using the normal algoswitching until the fork - and then, arguably, moneroocean would switch everyone to Monerov8 after the fork.
...or do I need to restrict mining to XMR and populate the pools-fork.txt file with the v7 and v8 pools for it to switch?
if you are using MO, and the pool sends you a new job that is V8, miner will restart automatically with the v8 settings, so you don't need the pools-fork.txt trick. Fantastic! I'll just add the v8 settings and pool under the algoswitch and bob's my uncle. If profitability lives up to expectations MO should switch to V8 pretty much straight after the fork goes live. We will see  I am working on algo switching without miner restart, and everything works when NOT using MO (manual pool switch, that has different algo), but i still have to find why app crashes badly with MO algo switching |
|
|
|
|
