That is the issue with amd cards, when they crashed and reset the driver, very rarely it returns to normal state
If you check with gpu-z or probably any monitoring tools, either the core or memory clock stuck and not coming back to idle state, at this point all you can do is hard reset, I've tried reenabling the cards through device manager, doesn't help
Topic: [Cast XMR] high speed XMR/CryptoNight miner for RX Vega GPUs (2 KHash/s) - page 140. (Read 206406 times)
November 05, 2017, 09:12:57 PM
November 05, 2017, 05:57:14 PM
Has anybody been able to run more than 5 Vega gpus in one rig with the blockchain drivers?
Once I put in the 6th card windows crashes for me.
when it crashes is it a mission to get windows to see the gpus again, or use them again i mean?
ihave 3 gpus and fark me, i get blue screens and stuff,i cant use msi afterburner for some bloody reason
and once i get a crash i struggle to get windows to see the gpus in a healthy state again
like when i run a miner sgminer claymore whatever it crashes again,
just want to know your experience
November 05, 2017, 05:45:28 PM
This miner totally outshines the RX 4xx/5xx series as the best of them could make you up to 700 Hash/s with modded Bios. Now this GPU which costs in Ebay the RX VEGA 56 in US cheapest price of 450-490 USD brand new gives us the hashing power of 3xRX 580 with modified Bios. Well done to the creator of such thing but why am I not seeing a fall in price of the RX 4xx/5xx series yet, they continue to be 300 USD or more at ebay ?
Mmm... even an RX 470 could do 860+ Hash/s. Not sure why you list 700 H/s as the maximum.
I like Vega as well, but my god what a hassle between the buggy blockchain driver, crossfire always enabled by default, and pos Wattman.
November 05, 2017, 05:42:24 PM
I have an issue when comparing hash rates reported from cast-xmr and the hashrates I see at the pool (supportxmr).
My benchmark rig is made of 4xVega56 flashed to 64 cards.
The hashrates for the rig shown by cast-xmr are 7870h/s, constant (i.e. no drops or anything). It's very stable within 40h/s.
However, the real hash rate reported by the pool (supportxmr) are lower than expected. I get 7250h/s. This is about 7.8% lower than reported by cast.
If we take into account:
-) 1.5% dev fee: 118,05 h/s
-) Rejected errors from old jobs (2%): 155 h/s
The total is 273h/s or 3.4%
I'm missing a total of 620H/s (7.8%!). That is another 347h/s 4.4% and is a relevant number.
I have no errors or disconnects. I've been chatting with the maintainers of supportxmr and they sustain that the 24hr period shall fall within 0.1-0.2% of the expected hash rate but mostly never beyond 1%. We're talking 4.4% here.
I'd like to ask if anybody is experiencing something similar, or do your real hash rates (from pools) actually match the reported cast-xmr rates?
thanks.
My benchmark rig is made of 4xVega56 flashed to 64 cards.
The hashrates for the rig shown by cast-xmr are 7870h/s, constant (i.e. no drops or anything). It's very stable within 40h/s.
However, the real hash rate reported by the pool (supportxmr) are lower than expected. I get 7250h/s. This is about 7.8% lower than reported by cast.
If we take into account:
-) 1.5% dev fee: 118,05 h/s
-) Rejected errors from old jobs (2%): 155 h/s
The total is 273h/s or 3.4%
I'm missing a total of 620H/s (7.8%!). That is another 347h/s 4.4% and is a relevant number.
I have no errors or disconnects. I've been chatting with the maintainers of supportxmr and they sustain that the 24hr period shall fall within 0.1-0.2% of the expected hash rate but mostly never beyond 1%. We're talking 4.4% here.
I'd like to ask if anybody is experiencing something similar, or do your real hash rates (from pools) actually match the reported cast-xmr rates?
thanks.
Is your 24-hour average at the pool consistently lower every day? I get much higher variance than 1% - but it goes both ways, and my average over several days is my hashrate -4.5-5%. I think that's normal - there may be other issues (little things, like the time to switch to mine the devfee, time to switch jobs, add up to something I assume) that make your miners' hashrate appear higher than normal. I don't know if the hashrate reported by the miner is an estimate or not, or whether it counts valid and invalid hashes.
Also, don't forget downtime. Even 15 minutes shaves off over 1%.
November 05, 2017, 05:33:12 PM
that aug 23rd driver just crashed my 3 vega 56 build, only the robin hood drivers seem to work
I cant get over 1500 hash using your cast-xmr , and thats with 1400 core, 1090 mem and 20% power limit.
My garage is quite cool temps not over 70 degrees so its not throttling
help pls
I cant get over 1500 hash using your cast-xmr , and thats with 1400 core, 1090 mem and 20% power limit.
My garage is quite cool temps not over 70 degrees so its not throttling
help pls
Go back to the BlockChain drivers. Use DDU to clean everything out. Restart. Install AMD Blockchain driver - DO NOT RESTART.
Instead, go into Regedit - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\
Find folder 000 - turn EnableAutoCrossfire to "0"
Find folder 001 - turn EnableAutoCrossfire to "0"
Find folder 002 - turn EnableAutoCrossfire to "0"
Then restart. That should bring your system up without crashing.
I prefer to use OverDriveNTool and the SoftPowerPlay registry mod.
Find a registry mod that works (meaning you can install that registry mod and restart and your system does not crash)
Then save as many copies as you need with one edited for "000" another edited for "001" another for "002" and so on. Then you just need to double-click on them and restart.
Try 1405 core / 905; Memory 1070 / 840 - use SoftPowerPlay mod
Reset HBCC in Wattman for each of your three cards.
Then launch Cast.
November 05, 2017, 04:09:30 PM
Yes, I factor uptime when making calculations.
My hashrate is consistently lower than what it should be. It's never higher over a 24h period (it's higher over shorter periods like 1h, but also much lower sometimes).
24hr is long enough to even out luck. This has been my experience with other miners (stak).
Pool switching shall not be a major factor. It takes few ms each time unless there's a major issue on the switching code.
It would be interesting to know if it's the same on other pools or if it's only on supportxmr.
My hashrate is consistently lower than what it should be. It's never higher over a 24h period (it's higher over shorter periods like 1h, but also much lower sometimes).
24hr is long enough to even out luck. This has been my experience with other miners (stak).
Pool switching shall not be a major factor. It takes few ms each time unless there's a major issue on the switching code.
It would be interesting to know if it's the same on other pools or if it's only on supportxmr.
November 05, 2017, 03:45:00 PM
I have an issue when comparing hash rates reported from cast-xmr and the hashrates I see at the pool (supportxmr).
My benchmark rig is made of 4xVega56 flashed to 64 cards.
The hashrates for the rig shown by cast-xmr are 7870h/s, constant (i.e. no drops or anything). It's very stable within 40h/s.
However, the real hash rate reported by the pool (supportxmr) are lower than expected. I get 7250h/s. This is about 7.8% lower than reported by cast.
If we take into account:
-) 1.5% dev fee: 118,05 h/s
-) Rejected errors from old jobs (2%): 155 h/s
The total is 273h/s or 3.4%
I'm missing a total of 620H/s (7.8%!). That is another 347h/s 4.4% and is a relevant number.
I have no errors or disconnects. I've been chatting with the maintainers of supportxmr and they sustain that the 24hr period shall fall within 0.1-0.2% of the expected hash rate but mostly never beyond 1%. We're talking 4.4% here.
I'd like to ask if anybody is experiencing something similar, or do your real hash rates (from pools) actually match the reported cast-xmr rates?
thanks.
My benchmark rig is made of 4xVega56 flashed to 64 cards.
The hashrates for the rig shown by cast-xmr are 7870h/s, constant (i.e. no drops or anything). It's very stable within 40h/s.
However, the real hash rate reported by the pool (supportxmr) are lower than expected. I get 7250h/s. This is about 7.8% lower than reported by cast.
If we take into account:
-) 1.5% dev fee: 118,05 h/s
-) Rejected errors from old jobs (2%): 155 h/s
The total is 273h/s or 3.4%
I'm missing a total of 620H/s (7.8%!). That is another 347h/s 4.4% and is a relevant number.
I have no errors or disconnects. I've been chatting with the maintainers of supportxmr and they sustain that the 24hr period shall fall within 0.1-0.2% of the expected hash rate but mostly never beyond 1%. We're talking 4.4% here.
I'd like to ask if anybody is experiencing something similar, or do your real hash rates (from pools) actually match the reported cast-xmr rates?
thanks.
Hi, many thanks for your feeback. I see similar issues with a 5% unexplained loss of hashes on 3x4 vega 56 rigs. I am currently with supportxmr and will keep for the next week to see how it goes and then I will consider switching pool to understand better where this could come from.
November 05, 2017, 01:34:46 PM
I have an issue when comparing hash rates reported from cast-xmr and the hashrates I see at the pool (supportxmr).
My benchmark rig is made of 4xVega56 flashed to 64 cards.
The hashrates for the rig shown by cast-xmr are 7870h/s, constant (i.e. no drops or anything). It's very stable within 40h/s.
However, the real hash rate reported by the pool (supportxmr) are lower than expected. I get 7250h/s. This is about 7.8% lower than reported by cast.
If we take into account:
-) 1.5% dev fee: 118,05 h/s
-) Rejected errors from old jobs (2%): 155 h/s
The total is 273h/s or 3.4%
I'm missing a total of 620H/s (7.8%!). That is another 347h/s 4.4% and is a relevant number.
I have no errors or disconnects. I've been chatting with the maintainers of supportxmr and they sustain that the 24hr period shall fall within 0.1-0.2% of the expected hash rate but mostly never beyond 1%. We're talking 4.4% here.
I'd like to ask if anybody is experiencing something similar, or do your real hash rates (from pools) actually match the reported cast-xmr rates?
thanks.
My benchmark rig is made of 4xVega56 flashed to 64 cards.
The hashrates for the rig shown by cast-xmr are 7870h/s, constant (i.e. no drops or anything). It's very stable within 40h/s.
However, the real hash rate reported by the pool (supportxmr) are lower than expected. I get 7250h/s. This is about 7.8% lower than reported by cast.
If we take into account:
-) 1.5% dev fee: 118,05 h/s
-) Rejected errors from old jobs (2%): 155 h/s
The total is 273h/s or 3.4%
I'm missing a total of 620H/s (7.8%!). That is another 347h/s 4.4% and is a relevant number.
I have no errors or disconnects. I've been chatting with the maintainers of supportxmr and they sustain that the 24hr period shall fall within 0.1-0.2% of the expected hash rate but mostly never beyond 1%. We're talking 4.4% here.
I'd like to ask if anybody is experiencing something similar, or do your real hash rates (from pools) actually match the reported cast-xmr rates?
thanks.
Is your 24-hour average at the pool consistently lower every day? I get much higher variance than 1% - but it goes both ways, and my average over several days is my hashrate -4.5-5%. I think that's normal - there may be other issues (little things, like the time to switch to mine the devfee, time to switch jobs, add up to something I assume) that make your miners' hashrate appear higher than normal. I don't know if the hashrate reported by the miner is an estimate or not, or whether it counts valid and invalid hashes.
Also, don't forget downtime. Even 15 minutes shaves off over 1%.
November 05, 2017, 01:20:04 PM
Is nobody using the new higher maximum speed for HBM2 on vega which is 1200 mhz. I was wondering which protocol likes this most of all. Doesnt seem this requires much more voltage to achieve and Ive read the timings are not looser to enable it either so it should help somewhere.
Use 1999 mhz not 1200 if you test or even 1170
Dagger is most sensible to memory clock.Use 1999 mhz not 1200 if you test or even 1170
In my tests all that higher then 1180 hbm produce "red" error strings in Claymore. Moreover, it seems that all above 1160 produce "fake" hashrate.
1150 is max for me. Tested on 2 rx vega64 liquid and 1 rx vega 56. 23 aug blockchain drivers. Temps were OK during tests.
November 05, 2017, 01:06:59 PM
Is nobody using the new higher maximum speed for HBM2 on vega which is 1200 mhz. I was wondering which protocol likes this most of all. Doesnt seem this requires much more voltage to achieve and Ive read the timings are not looser to enable it either so it should help somewhere.
Use 1999 mhz not 1200 if you test or even 1170
Use 1999 mhz not 1200 if you test or even 1170
November 05, 2017, 01:00:29 PM
I have an issue when comparing hash rates reported from cast-xmr and the hashrates I see at the pool (supportxmr).
My benchmark rig is made of 4xVega56 flashed to 64 cards.
The hashrates for the rig shown by cast-xmr are 7870h/s, constant (i.e. no drops or anything). It's very stable within 40h/s.
However, the real hash rate reported by the pool (supportxmr) are lower than expected. I get 7250h/s. This is about 7.8% lower than reported by cast.
If we take into account:
-) 1.5% dev fee: 118,05 h/s
-) Rejected errors from old jobs (2%): 155 h/s
The total is 273h/s or 3.4%
I'm missing a total of 620H/s (7.8%!). That is another 347h/s 4.4% and is a relevant number.
I have no errors or disconnects. I've been chatting with the maintainers of supportxmr and they sustain that the 24hr period shall fall within 0.1-0.2% of the expected hash rate but mostly never beyond 1%. We're talking 4.4% here.
I'd like to ask if anybody is experiencing something similar, or do your real hash rates (from pools) actually match the reported cast-xmr rates?
thanks.
My benchmark rig is made of 4xVega56 flashed to 64 cards.
The hashrates for the rig shown by cast-xmr are 7870h/s, constant (i.e. no drops or anything). It's very stable within 40h/s.
However, the real hash rate reported by the pool (supportxmr) are lower than expected. I get 7250h/s. This is about 7.8% lower than reported by cast.
If we take into account:
-) 1.5% dev fee: 118,05 h/s
-) Rejected errors from old jobs (2%): 155 h/s
The total is 273h/s or 3.4%
I'm missing a total of 620H/s (7.8%!). That is another 347h/s 4.4% and is a relevant number.
I have no errors or disconnects. I've been chatting with the maintainers of supportxmr and they sustain that the 24hr period shall fall within 0.1-0.2% of the expected hash rate but mostly never beyond 1%. We're talking 4.4% here.
I'd like to ask if anybody is experiencing something similar, or do your real hash rates (from pools) actually match the reported cast-xmr rates?
thanks.
Try using something like xmr-stak-amd and test it on their pool and see if you get the same variance, if so it's because it's hard to calculate real hash rate since the server doesn't know your hash rate until you submit 1 share, you can be unlucky and not find like 2 in a row and only 1 etc all that will influence it.
November 05, 2017, 11:52:00 AM
I have an issue when comparing hash rates reported from cast-xmr and the hashrates I see at the pool (supportxmr).
My benchmark rig is made of 4xVega56 flashed to 64 cards.
The hashrates for the rig shown by cast-xmr are 7870h/s, constant (i.e. no drops or anything). It's very stable within 40h/s.
However, the real hash rate reported by the pool (supportxmr) are lower than expected. I get 7250h/s. This is about 7.8% lower than reported by cast.
If we take into account:
-) 1.5% dev fee: 118,05 h/s
-) Rejected errors from old jobs (2%): 155 h/s
The total is 273h/s or 3.4%
I'm missing a total of 620H/s (7.8%!). That is another 347h/s 4.4% and is a relevant number.
I have no errors or disconnects. I've been chatting with the maintainers of supportxmr and they sustain that the 24hr period shall fall within 0.1-0.2% of the expected hash rate but mostly never beyond 1%. We're talking 4.4% here.
I'd like to ask if anybody is experiencing something similar, or do your real hash rates (from pools) actually match the reported cast-xmr rates?
thanks.
My benchmark rig is made of 4xVega56 flashed to 64 cards.
The hashrates for the rig shown by cast-xmr are 7870h/s, constant (i.e. no drops or anything). It's very stable within 40h/s.
However, the real hash rate reported by the pool (supportxmr) are lower than expected. I get 7250h/s. This is about 7.8% lower than reported by cast.
If we take into account:
-) 1.5% dev fee: 118,05 h/s
-) Rejected errors from old jobs (2%): 155 h/s
The total is 273h/s or 3.4%
I'm missing a total of 620H/s (7.8%!). That is another 347h/s 4.4% and is a relevant number.
I have no errors or disconnects. I've been chatting with the maintainers of supportxmr and they sustain that the 24hr period shall fall within 0.1-0.2% of the expected hash rate but mostly never beyond 1%. We're talking 4.4% here.
I'd like to ask if anybody is experiencing something similar, or do your real hash rates (from pools) actually match the reported cast-xmr rates?
thanks.
November 05, 2017, 11:37:55 AM
I have 2 RX VEGA 56.
I have tried both the stock and and I have also flashed the 64 bios.
I have tried all versions of this miner and all possible settings.
Initially, the miner starts at the expected speed. However, after a time interval that varies from 10 to 60 min, the speed drops by about 10% and stays like that stable.
For example, on the stock bios at -10% power, -4% GPU and 945 ram, I start at 1950 H/s and it then drops to about 1800.
The same happens at other power/ram/gpu settings, it always drops by about 10% after a while.
The same also happens with xmr-stak-amd
I am also mining equihash on the same machine with two GTX 1070s. Could this be the cause for the drop?
Any help appreciated.
I have tried both the stock and and I have also flashed the 64 bios.
I have tried all versions of this miner and all possible settings.
Initially, the miner starts at the expected speed. However, after a time interval that varies from 10 to 60 min, the speed drops by about 10% and stays like that stable.
For example, on the stock bios at -10% power, -4% GPU and 945 ram, I start at 1950 H/s and it then drops to about 1800.
The same happens at other power/ram/gpu settings, it always drops by about 10% after a while.
The same also happens with xmr-stak-amd
I am also mining equihash on the same machine with two GTX 1070s. Could this be the cause for the drop?
Any help appreciated.
As others have mentioned, be mindful of your temps. HBM is pretty sensitive. If you're seeing it on both cast and xmr-stak, it could very well be hbm getting too hot
Thx for your reply. Yep, I had read about the HBM temps. Unfortunately, this is probably not the reason. According to GPU-z, my HBM is at 55 C at -30% power
November 05, 2017, 11:16:04 AM
I have 2 RX VEGA 56.
I have tried both the stock and and I have also flashed the 64 bios.
I have tried all versions of this miner and all possible settings.
Initially, the miner starts at the expected speed. However, after a time interval that varies from 10 to 60 min, the speed drops by about 10% and stays like that stable.
For example, on the stock bios at -10% power, -4% GPU and 945 ram, I start at 1950 H/s and it then drops to about 1800.
The same happens at other power/ram/gpu settings, it always drops by about 10% after a while.
The same also happens with xmr-stak-amd
I am also mining equihash on the same machine with two GTX 1070s. Could this be the cause for the drop?
Any help appreciated.
I have tried both the stock and and I have also flashed the 64 bios.
I have tried all versions of this miner and all possible settings.
Initially, the miner starts at the expected speed. However, after a time interval that varies from 10 to 60 min, the speed drops by about 10% and stays like that stable.
For example, on the stock bios at -10% power, -4% GPU and 945 ram, I start at 1950 H/s and it then drops to about 1800.
The same happens at other power/ram/gpu settings, it always drops by about 10% after a while.
The same also happens with xmr-stak-amd
I am also mining equihash on the same machine with two GTX 1070s. Could this be the cause for the drop?
Any help appreciated.
As others have mentioned, be mindful of your temps. HBM is pretty sensitive. If you're seeing it on both cast and xmr-stak, it could very well be hbm getting too hot
November 05, 2017, 11:07:19 AM
I have 2 RX VEGA 56.
I have tried both the stock and and I have also flashed the 64 bios.
I have tried all versions of this miner and all possible settings.
Initially, the miner starts at the expected speed. However, after a time interval that varies from 10 to 60 min, the speed drops by about 10% and stays like that stable.
For example, on the stock bios at -10% power, -4% GPU and 945 ram, I start at 1950 H/s and it then drops to about 1800.
The same happens at other power/ram/gpu settings, it always drops by about 10% after a while.
The same also happens with xmr-stak-amd
I am also mining equihash on the same machine with two GTX 1070s. Could this be the cause for the drop?
Any help appreciated.
I have tried both the stock and and I have also flashed the 64 bios.
I have tried all versions of this miner and all possible settings.
Initially, the miner starts at the expected speed. However, after a time interval that varies from 10 to 60 min, the speed drops by about 10% and stays like that stable.
For example, on the stock bios at -10% power, -4% GPU and 945 ram, I start at 1950 H/s and it then drops to about 1800.
The same happens at other power/ram/gpu settings, it always drops by about 10% after a while.
The same also happens with xmr-stak-amd
I am also mining equihash on the same machine with two GTX 1070s. Could this be the cause for the drop?
Any help appreciated.
November 05, 2017, 10:10:33 AM
4x vega 56
mine avging 165w with -30 power - combined hash rate 7099
180w power at 0 - 7600
I followed the guide on reddit, wondering if voltage control not working properly?
wattman showing 905 core // 900mem - i just flashed the video bios and used the 1000 reg file on each gpu.
mine avging 165w with -30 power - combined hash rate 7099
180w power at 0 - 7600
I followed the guide on reddit, wondering if voltage control not working properly?
wattman showing 905 core // 900mem - i just flashed the video bios and used the 1000 reg file on each gpu.
November 05, 2017, 08:30:59 AM
RE: Temperatures:
58 on GPU is too much.
The temperatures that cast gives are the GPU temps. These are irrelevant for vega as it's the HBM that gets too hot.
@OP: Please add HBM temperatures to the log on cast-xmr ! These are all we care for with vega!
Now, my GPU temps are always around 48-50C. The HBM is usually 10 degrees hotter (58-60C). At 65 the HBM will back-off to cool down and this will cause lower hash rate.
My ambient temp is about 25C and my fans are ~3200-3400 RPM. I do have fresh air intake blowing ambient air on the rigs.
Whatever you do, 65 is the limit on HBM.
58 on GPU is too much.
The temperatures that cast gives are the GPU temps. These are irrelevant for vega as it's the HBM that gets too hot.
@OP: Please add HBM temperatures to the log on cast-xmr ! These are all we care for with vega!
Now, my GPU temps are always around 48-50C. The HBM is usually 10 degrees hotter (58-60C). At 65 the HBM will back-off to cool down and this will cause lower hash rate.
My ambient temp is about 25C and my fans are ~3200-3400 RPM. I do have fresh air intake blowing ambient air on the rigs.
Whatever you do, 65 is the limit on HBM.
November 05, 2017, 05:37:18 AM
Hi,
I'm using 2 Vega 64 with blockchain driver, 1100mhz mem
When launching castxmr everything goes well :
[10:57:53] GPU0 | 55°C | Fan 4646 RPM | 2045.7 H/s
[10:57:53] GPU1 | 53°C | Fan 4743 RPM | 1997.0 H/s
[10:57:58] GPU0 | 54°C | Fan 4641 RPM | 2043.3 H/s
[10:57:58] GPU1 | 58°C | Fan 4741 RPM | 1998.3 H/s
[10:57:59] GPU1 Found Nonce, submitting...
[10:57:59] Share Accepted -> +1
[10:57:59] Shares: 16 Accepted, 0 Errors | Hash Rate Avg: 4014.7 H/s | Avg Search Time: 17.3 sec
And after few minutes it drops :
[11:06:15] GPU0 | 55°C | Fan 4654 RPM | 1863.8 H/s
[11:06:15] GPU1 | 58°C | Fan 4742 RPM | 1850.3 H/s
[11:06:19] GPU0 | 55°C | Fan 4655 RPM | 1860.9 H/s
[11:06:31] GPU1 | 58°C | Fan 4745 RPM | 1653.1 H/s
[11:06:31] GPU0 | 55°C | Fan 4649 RPM | 1867.0 H/s
[11:06:31] GPU1 | 58°C | Fan 4742 RPM | 1894.3 H/s
[11:06:31] GPU1 Found Nonce, submitting...
[11:06:31] Share Accepted -> +1
[11:06:31] Shares: 28 Accepted, 0 Errors | Hash Rate Avg: 3868.7 H/s | Avg Search Time: 28.1 sec
Temperature is ok, I tried to give +50% (higher hashrate but still at 1800) , -30% (1600~) to power limit,
Someone experiencing same problem ?
I'm using 2 Vega 64 with blockchain driver, 1100mhz mem
When launching castxmr everything goes well :
[10:57:53] GPU0 | 55°C | Fan 4646 RPM | 2045.7 H/s
[10:57:53] GPU1 | 53°C | Fan 4743 RPM | 1997.0 H/s
[10:57:58] GPU0 | 54°C | Fan 4641 RPM | 2043.3 H/s
[10:57:58] GPU1 | 58°C | Fan 4741 RPM | 1998.3 H/s
[10:57:59] GPU1 Found Nonce, submitting...
[10:57:59] Share Accepted -> +1
[10:57:59] Shares: 16 Accepted, 0 Errors | Hash Rate Avg: 4014.7 H/s | Avg Search Time: 17.3 sec
And after few minutes it drops :
[11:06:15] GPU0 | 55°C | Fan 4654 RPM | 1863.8 H/s
[11:06:15] GPU1 | 58°C | Fan 4742 RPM | 1850.3 H/s
[11:06:19] GPU0 | 55°C | Fan 4655 RPM | 1860.9 H/s
[11:06:31] GPU1 | 58°C | Fan 4745 RPM | 1653.1 H/s
[11:06:31] GPU0 | 55°C | Fan 4649 RPM | 1867.0 H/s
[11:06:31] GPU1 | 58°C | Fan 4742 RPM | 1894.3 H/s
[11:06:31] GPU1 Found Nonce, submitting...
[11:06:31] Share Accepted -> +1
[11:06:31] Shares: 28 Accepted, 0 Errors | Hash Rate Avg: 3868.7 H/s | Avg Search Time: 28.1 sec
Temperature is ok, I tried to give +50% (higher hashrate but still at 1800) , -30% (1600~) to power limit,
Someone experiencing same problem ?
November 05, 2017, 04:38:56 AM
im getting one card at 75 same settings as others, which run at 60ish. no idea how to see whats wrong with it.
It could be caused by the different quality of sillicon inside the chip.Anyway I am received one invalid result due to computation failed - what does it mean?
And I don´t still figure out why random gpus sometimes shows 0h/s, but only once and then it´s back in the normal...
November 05, 2017, 03:46:01 AM
im getting one card at 75 same settings as others, which run at 60ish. no idea how to see whats wrong with it.
Jump to: