Hello.
Any ideia what this error can be:
Cuda error in func 'neoscrypt_cpu_hash_1070' at line 1460 : the launch timed out and was terminated.
Cuda error in func 'neoscrypt_cpu_hash_1070' at line 1464 : the launch timed out and was terminated.
Cuda error in func 'neoscrypt_cpu_hash_1070' at line 1464 : the launch timed out and was terminated.
Cuda error in func 'neoscrypt_cpu_hash_1070' at line 1464 : the launch timed out and was terminated.
Cuda error in func 'neoscrypt_cpu_hash_1070' at line 1460 : the launch timed out and was terminated.
Closed program.
Thanks !
Any ideia what this error can be:
Cuda error in func 'neoscrypt_cpu_hash_1070' at line 1460 : the launch timed out and was terminated.
Cuda error in func 'neoscrypt_cpu_hash_1070' at line 1464 : the launch timed out and was terminated.
Cuda error in func 'neoscrypt_cpu_hash_1070' at line 1464 : the launch timed out and was terminated.
Cuda error in func 'neoscrypt_cpu_hash_1070' at line 1464 : the launch timed out and was terminated.
Cuda error in func 'neoscrypt_cpu_hash_1070' at line 1460 : the launch timed out and was terminated.
Closed program.
Thanks !
I have been hitting this issue several times. It shows up with 4 or more 1070's in my rig. If I only mine in 1 HSR Miner process with 3 devices (1070 gpus), then it doesnt seem to happen. So, I have been trying two HSR Miner instances with 3 cards each instance, so far thats been working. But I am lazy so I run one CC miner with 4 cards and one HSR miner with 3 1070's and its working ok. I have my Virtual Memory up to 68 GB for 7 1070's ... so I dont think thats the issue, but could be wrong. My rig only has 4 GB, so may a memory issue, but not sure.
When I account for the increased rejected shares and the ramp up time every time the HSR miner switches to the Dev pool, then I think its not too much better than CC Miner. But, HSR miner does some magic with GPU 0 that CCminer cant do (for some reason GPU0 is about 50-75% slower on CC Miner). So, I will keep it mining away!