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

I am using AnyDesk, since TeamV disconnects me after 1 minute

I've just noticed that in general it's getting difficult to connect with Teamviewer since the ominous 1803 Windows 10 update. For whatever reason my rigs regularly become unresponsive for 10-20 sec repeatedly. Miner seems to still be doing its stuff but it's just extremely annoying when you can't connect or it takes you several tries to do so.

Hello,

I have arduino setup that pings my computer, for example, when using xmr stak arduino is pingg port 450 and makes a hard reset if the rig is frozen. Does a srbminer have something like this, like a page that can be used for monitoring, that I can use to ping with arduino, to reset the rig if miner/rig is frozen?

Thanks!

maybe ask the pool and give them your ip address that has been banned

I have an issue, without any incorrect share my IP adress has been banned from pools of different coins (arto & graft); how can that be possible ?

I can confirm that this behavior does happen.  Hard reboot required at times when gpu driver resets, but not every time.

probably gpu driver resets itself, but that shouldn't get TV disabled

no my rig not freeze. it only hang and make teamview disable. i connect monitor and can use mouse to close and run again

There is a watchdog that restarts miner when some of the gpu's hangs, but in some occasions it can't do anything if your rig freezes for example.
Claymore can't save you from a windows freeze too

Anyway, you can try to disable the watchdog with the --disablegpuwatchdog added in .bat

When one of vga down or disable or hang.
If use claymore just teamview reduce OC and reset program.
If use SRBminer when one of vga hash rate = 0, i cant use teamview cause it often make teamview network disable.

fix what?

just run 5 minuties in 1.5.6, when one of gpu hash rate = 0 cause  maybe i OC too hight your tool make my rig hang remotely, cant use teamview and vnc. i am going back home to connect my rig to monitor and use mouse to close tool and run again . Can you fix pls ?

Its not set automatically to 90c anymore, so you shouldnt have a prpblem anymore. Report please 

Same for me. Set "shutdown_temperature" or not in config file the result same. My rig alway auto shutdown. My card very cool at 50c. I will test new ver 1.5.6 today

V1.5.6

- Added support for Cryptonight B2N
- Added parameter "min_rig_speed" in config file
- Added parameter "main_pool_reconnect" in config file
- Added optional parameter --resetfans in .bat
- "shutdown_temperature" parameter now must be set to a value > 0 to get activated
- Added 1 min avg hashrate display
- Fixed a bug in watchdog restarting process
- Added support for CPU builtin OpenCL GPU (just for fun)


+ Cryptonight B2N is for Bitcoin2Network coin
+ "min_rig_speed" parameter defines the average hashrate we want to maintain. If 5 min average hashrate is less than the value we defined, restart miner. This option expects you to enter a value in H/S
+  "main_pool_reconnect" minimum value is 180 seconds (3 min), defines how often should miner try to reconnect back to main pool if not mining on it currently. If not set default value is 10 minutes.
It is activated only when it can't connect to main pool from the reconnecting process, so if user changes pool by pressing P, it won't try to connect back to main pool, because user changed the pool himself.
+ Removed auto fan reset on miner exit and put new parameter in bat : --resetfans, which if used resets fans to default settings on miner exit
+ CPU builtin OpenCL GPU

Tested and works on Intel HD 3000 builtin GPU

If user wants to use it has to put --usecpuopencl in bat, and define cpu_conf in config:

"cpu_conf":
[
   { "intensity" : 1, "worksize" : 1, "threads" : 1}
]

you can use "platform" : number , if not used, autodetected

This option is here more mostly for fun, as it hashes slower than a CPU miner would.
The OpenCL kernel is totally unoptimised, so maybe in the future if i get very motivated, i will look into speeding it up, if it's achiveable.

But hey, it's available, you can use it if you want

Tested and works on Intel HD 3000 builtin GPU

i not set the "shutdown_temperature" and the rig make a reboot and his freeze, i have Windows Version 1709 :9

No, it doesnt reached 90c, my GPU is 45c

could you tell me which algo is this?

@doktor83, today I saw this:
I have no blocking rules, so you should possibly check your devfee credentials in source

In my personal experience, I had same cards with same mem type and same OC settings, yet some did 950 h/s, some did, 980, some did 1020. When I shut down the miner and I restarted, this time a card would randomly work at 950, although it could be 1030 the previous run. By chance, I read here that someone had their hash rate increase when GPU-Z was turned on and he looped through each card.

In my case, no such thing is necessary. I just fire it up, and it "fixes" hash rates in 1-2 minutes. It fixes the hash rate fall from switching pools in a few minutes in the same manner.

I have 13 cards running, win 10, adrenaline drivers. Maybe it works for setups with many cards, maybe not. Maybe it works with adrenaline drivers, maybe not I can't be sure, but if you are suffering from random hashrates from the same card, this may work for you.