[CUDA] Error gpu 0: <cryptonight_extra_cpu_final>:391 "unspecified launch failure"

[JimmyBenne]

trafficstars

Hi I've already seen this issue but I'm posting it again (keep reading). I've compiled xmrignvidia for 32 bit successfully, after I did slavab73 change here : https://github.com/xmrig/xmrig-nvidia/issues/206

But when I start the program if I use the config.json from the binary release of xmrignvidiax64 (visual studio) on the console this error appears [CUDA] Error gpu 0: <cryptonight_extra_cpu_final>:391 "unspecified launch failure"... , also I've tried to use the config.json generated from the xmrig config site and the error changes in "NO CUDA device found" .

I've already tried as suggested from "xmrig"in another topic, to change the bfactor... I've tried with bfactor = 4, bfactor 8, bfactor 12... but it doesn't work P.s.:The nvidiax64 release doesn't have any problem and it works correctly

[RainbowMiner]

I had the same issue when testing CryptoNightV8, algo "-a cryptonight/2" (Compiled xmrig 64bit/CUDA10/Windows Visual Studio 2017/Running on GeForce GTX1070). For me, command line option "--bfactor=12" solved the problem. I did not experience the unspecified launch failure for other algorithm, only for cryptonight/2.

[etsam]

Error gpu 0: <cryptonight_extra_cpu_final>:391 "unspecified launch failure"

My GTX750Ti is also the same problem, modified bfactor = 4, bfactor 8, no effect. (xmrig-nvidia-2.8.3-cuda-8_0-win64.zip) there is no force or close the window directly.

The test also found that GTX650Ti had no problem.

[Xingez]

Had the same issue with my 1080TI. Changing --cuda-bfactor did no difference, but --bfactor to 12 solved it.

[demokom-gmail-com]

Hi guys, you simply have to decrease threads/blocks parameters in your config.json even if they were autogenerated.

[def670]

I am running a gigabyte gtx-1060 on 64bit ubuntu. This error came up after running stable overnight. I have set bfactor to 12 and will report back in after a while. I am in the midst of running the card thru varied test settings in pursuit of higher hashrates.

##from the looks of it changing bfactor from 6 to 12 has dropped the hashrate from approx 519.1h/s to ##427.9h/s that was my error - had to reboot the system and only had changed the bfactor. had not redone the clocking. now that its been clocked again (50,1600) thru powermizer the hash rate is up around 513h/s def