w7, nvidia gpus
algo aeon, get error duplicate shares
any ideea?
Topic: CryptoGen NVidia GPU Miner (Read 8534 times)
This can be a scam like many other new miners. Check your computers for RATs or Backdoors.
gonna try this miner
HiDid you try ?
Note that CryptoGen is valid for a lot of algorithms : phi2, phi, Lyra2z, and more
You can check and compare its benchmark rates on the pools, for example :
- https://bsod.pw/bench?algo=phi2&chip=0
- http://yiimp.eu/bench?algo=phi2&chip=0
gonna try this miner
HiDid you try ?
Note that CryptoGen is valid for a lot of algorithms : phi2, phi, Lyra2z, and more
You can check and compare its benchmark rates on the pools, for example :
- https://bsod.pw/bench?algo=phi2&chip=0
- http://yiimp.eu/bench?algo=phi2&chip=0
gonna try this miner
Hi guys
A new version v3.0.6 is available here :
https://github.com/genminer/cryptogen/releases/tag/v3.0.6
- Added ability to use pool's benchmarks with "stats" in pass
- Compiled with CUDA 9.1
- Tested with last nVidia driver 398.36
- Versions w32 + x64
Happy mining !
A new version v3.0.6 is available here :
https://github.com/genminer/cryptogen/releases/tag/v3.0.6
- Added ability to use pool's benchmarks with "stats" in pass
- Compiled with CUDA 9.1
- Tested with last nVidia driver 398.36
- Versions w32 + x64
Happy mining !
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.
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.
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.
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.
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.
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...
SureI 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...
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 :-)
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...
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...
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.and then instantly crashes...
I have 1080Ti's in various rigs..
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.
It simply just report no cards found.
and then instantly crashes...
I have 1080Ti's in various rigs..
and then instantly crashes...
I have 1080Ti's in various rigs..
Doesn't work with the latest nvidia driver for me 398.58 while alexis miner with Cuda 7.5 32bit does..
Any ideas?
HiAny ideas?
I didn't test last driver, it seems quite unstable.
What is your configuration ? Cards, OC settings and intensity, virtual memory sizing, algo, pool ?
Doesn't work with the latest nvidia driver for me 398.58 while alexis miner with Cuda 7.5 32bit does..
Any ideas?
Any ideas?
Hey.
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
HiAfter 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
What is your configuration ? Cards, OC settings and intensity, virtual memory sizing ?
And obv, do you use last 3.0.5 version ?
Hey.
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
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
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)
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)
Agreed, still having stratum connection interruptions occasionally it is noticable on the hashrate.
I think pickaxe is better with auto diff (and not only with auto diff, imo)
You should try and compare.
You should try and compare.
Jump to: