In this case it easy thing since it is Windows 10 x64 1709 and it just siomply detect any card .. just not gpu device found which leads to the point it can't find any with the cuda device query.
Well the is no OC or algo involved in this error - just can't simply find a device - wanted to keep it simple.
That's strange.
All my tests on Win 10 x64 are corrects so far, with Cuda 7.5, 9.0, 9.1, and for platforms win32 and x64.
I'm also preparing a x64 release, maybe it'll be ok for you.
Post
Topic
BoardMining (Altcoins)
Re: CryptoGen NVidia GPU Miner
by
the_gen_miner
on 15/07/2018, 18:57:14 UTC
Hi
First test campaign with last nVidia driver 398.36 :
All is good. No problem encountered.
Keep testing for a while on different configurations & pools.
Well the 397.xx are okay but i find the new one very stable. I have no problem with alexis or any other ccminer, EWBF or such..they all run stable and reliable and a bit faster..
Sure people have problems because they oc the way they don't know what they did or do.. you should test and see what is wrong with the newest driver and your build given the fact that the years old alexis still work like a charm even with the newest There is no excuse to not do it...
Sure
Anyway, to test this new driver, I would like to know in which configuration you encounter problems : algo, oc settings, intensity, etc. Otherwise, it's like looking for a needle in a haystack :-)
It simply just report no cards found. and then instantly crashes...
I have 1080Ti's in various rigs..
Well, it's obviously a problem with the last driver. As I said before, I didn't start testing with this driver, but I've heard of problems with it.
I can just recommend to keep driver up to 397.x
In all cases, when a rig is full operational and in production, I recommend to keep its configuration as is, unless you're sure you get a big advantage in upgrading.
After a couple of hours mining Phi2, when switching back from devfee mining I receive an error all CUDA-capable devices are busy or unavailable. Randomly, but occasionally on several machines. Any suggestions? thanks
Hi
What is your configuration ? Cards, OC settings and intensity, virtual memory sizing ? And obv, do you use last 3.0.5 version ?
Post
Topic
BoardMining (Altcoins)
Re: CryptoGen NVidia GPU Miner
by
the_gen_miner
on 10/07/2018, 16:44:41 UTC
Generally, a stratum connection interruption comes from the pool, or from your Internet connection.
But the miner reconnects (except if the pool is down, in this case after 5 attempts it switches to the next pool in the list)
Post
Topic
BoardMining (Altcoins)
Re: CryptoGen NVidia GPU Miner
by
the_gen_miner
on 08/07/2018, 17:20:24 UTC
I think pickaxe is better with auto diff (and not only with auto diff, imo)
I think this miner performs well and on par with Cryptodredge if you setup the stratum difficulty manually.
Two things to focus on :
Fine tuning of intensity : for example, an intensity of 19 or 19.5 if fine for 1080 Ti
Difficulty : best way is to run with automatic diff from pool, then after stabilization, examine choosen diff from pool and force it in pool parameters
To force manually difficulty, change the "pass" parameter by adding a "d=" item : - in config file : "pass": "c=COIN,d=XX" - in command line : -p c=COIN,d=XX
replace COIN by coin code (ex: LUX) and XX by the wanted difficulty (ex: 48)
By the way, don't forget to define several pools in the coin config file : if a pool fails or can't be reached, CryptoGen automatically switches to the next pool in the list. This way, you never lose money !
I'm testing this miner, but I have a problem. When it starts mining the dev fee and connects to the dev pool it cannot restore to mine pool after that is the connection always goes to timeout.
I'm testing this miner, but I have a problem. When it starts mining the dev fee and connects to the dev pool it cannot restore to mine pool after that is the connection always goes to timeout.
I tried on 3 different yiimp based pools. I have 2 small rigs and it's also possible that the dev fee starts to mine not in sync at different times and makes it look like a lower average hashrate on the pool side.
That's probable : dev fee starts randomly during first hour of mining.
I tested this miner for 24 hours and I actually got better results with coolminer and ccminer 2.3 . The cryptogen displayed hashrate is higher but the real pool rate is lower. On the other side coolminer and tpruvot ccminer show a little lower on comp but the real on the hash on pool is higher.