Topic: SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching - page 271. (Read 237247 times)

How can I remove T: RPM: CC: MC: & bus after the H/s?
I use --adldisable & I see all sensors with 0 value.

I will try this next time.

However, unlike istr says, in my environment, keeping gpu-z open is actually good! Turns out it protects from hashrate drop, and unlike him, I do not go through each and every one of them to achieve the full speed, sorry to complicate things a bit, but that's the case with me!

Hi all,

I am the developer of the FREE rig-monitor - rig, pool, market data and power usage monitoring tool. I have just added support for SRBMiner to the app.

You can read about it here:https://bitcointalksearch.org/topic/new-free-rig-monitor-40-alpha-released-2128602

The binaries can be found here: https://github.com/rodneymo/rig-monitorv2/releases/tag/2.1.d.3

Anyone else got this problem with Vegas ?

Interesting, all that gpu-z does (or it should do ) is to run a few opencl queries, and some monitoring stuff. But who knows.
I tried that suggestion to fire up gpu-z and it should improve hash on 580 8g cards on heavy, but that is not the case here.

Here's an idea for you guys that gpu-z helps: try running --listdevices in a new console window while the miner is running in an other.
So , do a :

SRBMiner-CN.exe --listdevices
This does some opencl queries, maybe some of those that help pumping the hashrate ?

If started with Vegas miner does not create cached compiled kernels.
Each start it compiles kernels again. Only zero-sized file with name '687F' is created.
Start of the log looks like this.

in my case, i launch the miner with 60 intenisty, i kill the process and i relaunch it with 56 to have 1500 hs per vega56

I've seen also small changes in H/s with V7, it just increases a bit after running GPU-Z but the hash rate is more stable, only in 8GB cards, there is no change in 4GB ones.
When using Heavy with 8GB I get best results with almost maximum intensity: "intensity" : 62, "worksize" : 8, "threads" : 2
Setting it to 63 H/s go heavily down & with 64 don' work, when lowering to 61, 60... the H/s goes down.
But when I run V7 for 4GB is the same than Heavy "intensity" : 61, "worksize" : 8, "threads" : 2 is the max. & best.
For 8GB in V7 if I go with I higher than about 82 there is almost no increase in H/s & it becomes more unstable the higher the I, when 122 or so should give the best results, I think.
 

GPU-Z didn't use any GPU's resources. it just connects to GPUs and monitors them.

All this connected to low-level accessing to GPUs via AMD ADL or other low-level driver such as phymem or like this.
I noticed that effect about year ago. It happens on GGS miner too. And not only GPU-Z has the same effect ))). Some hardware monitoring tools can do that too. Like HWInfo, but not all versions. It's exists method even without any tools to do that, but only for GPU wich display connected to.

Must to notice that Claymore's miners never had that issue. His miners allways runs at max speeds. This another one proof that Claymore knows more than others on AMD GPU programming. Looks like he realy worked or works now for AMD.

Gentlemen,
things are very simple.

You have started SRBminer waiting a while, 2-3 minutes, to report the first hashrate total and give it some time to reach the top hashspeed as doktor83 says.
Then you realize the drop on some or all of your cards.
Now it's the time to fire up GPU-Z as miner runs and uses all the resources of GPUs.
I'm passing throu all GPUs one by one and then exiting from GPU-Z. If you stay running it you'll realize that there's a small drop in hashrate on all cards.
This is normal because of the memory resource usage of the 2 programs.
The great thing is that GPU-Z motivates SRBminer to reach the highest it can get.
As a programmer, I'm suspecting something with the interrupts or the memory management of GPUs.
For some cards it may need to run it a second time or and a third one.
Keep in mind that all this has to do with the RX 480-580 8gb cards which of course I run them with 2 threads and intensity 54, worksize 8.
I reach on them from 1070 to 1148 h/s.

There is no problem at all with RX 570-580 4gb cards. These cards, of course with 1 thread - worksize 8 - intensity 60-61, reach maximum hashing speed at once.
I'm getting on these cards from 755 to 780 h/s.
Sorry, I've forgotten to mention that all these are on heavy algorithm

I'm glad to help the community!
and waiting for a better miner from Doktor83.

Okay, well I am not gonna lower the intensity in that case, because I simply do not use the rig as a computer anyway Just for a couple of secs each and every other day.
Thanks for the answers!

i had this issue also some time ago ONLY if i´m on the desktop

after opening the Brwoser in fullscreen - the problem was solved

It has nothing to do with batteries. You have too high intensity set on your display card.

Have you guys noticed when the SRBminer is running that the cursor is moving like the pc is almost ready to hang? For example - if I am on my mining rig and want to open the browser just to check the stats from the pool, as I am trying to move the mouse it moves like I am playing a game with 5-6 FPS. It is moving really slowly...
I have checked the batteries, replaced them with new ones but the issue stays the same! Anyone with the same issue?

While SRB is running, I start GPU-Z. It takes a good while for it to initialize, but you can see the hashrate going up during the process. After some hours, rate fell a bit but it was still higher than it was before, I restarted GPU-Z and it went backup, just 5 minutes ago. It may be falling during pool switches, have to check the logs, but it's great something has a testable positive effect on the rate, which may be replicated inside SRB.

Anyone ever got this error?

[2018-05-13 00:26:37] What? A debugger or a hex editor? No way.

After this, SRBMiner just restarts.

Been pretty much fine though, 2 days running 10 vegas on CN heavy, 1450h/s 875 mem and 1430 core clock.

Know what it means?

Hi, could you please explain a bit detail about steps to achieve it? Did you run GPU-Z right before ran SRB? Or while you clicked start SRB Miner, you then ran GPU-Z? Thanks.

Hey, to clearify it. Do you let GPU-Z run while Mining or do you close it after the Miner starts and submitted the first shares?

this works fine, but the error does not output for those cards, the work does not interfere, so it's easy for information
^{[2018-05-13 08:51:08] hashrate: GPU0: 288.0 H/S
[2018-05-13 08:51:08] hashrate: GPU1: 285.0 H/S
[2018-05-13 08:51:08] hashrate: GPU2: 300.0 H/S
[2018-05-13 08:51:08] hashrate: GPU3: 0.0 H/S
[2018-05-13 08:51:08] hashrate: GPU4: 293.0 H/S
[2018-05-13 08:51:08] hashrate: GPU5: 306.0 H/S
[2018-05-13 08:51:08] hashrate: GPU6: 280.0 H/S
[2018-05-13 08:51:08] hashrate: GPU7: 273.0 H/S
[2018-05-13 08:51:08] hashrate: GPU8: 322.0 H/S
[2018-05-13 08:51:08] hashrate: GPU9: 309.0 H/S
[2018-05-13 08:51:08] hashrate: GPU10: 326.0 H/S
[2018-05-13 08:51:08] hashrate: GPU11: 336.0 H/S
[2018-05-13 08:51:08] hashrate: GPU12: 335.0 H/S
[2018-05-13 08:51:08] hashrate: Total: 3688.0 H/S
[2018-05-13 08:51:08] watchdog: GPU8 [thread16] hashing speed is 0}

recently I read your post and perform the test, it's true, gpu-z increases the hash, my old card 6870 of 140 h/s a 200 h/s