search

nicehash / excavator

NiceHash's proprietary low-level CUDA miner
https://www.nicehash.com
53 stars 19 forks source link

GTX 1070 - Version 1.3.8 alpha neoscrypt not work #78

Closed Kayfolom closed 6 years ago

Kayfolom commented 7 years ago

[17:11:24][0x00001518][info] Log started [17:11:25][0x00001518][info] core | Found CUDA device: GeForce GTX 1070 [17:11:25][0x00001518][info] core | Found CUDA device: GeForce GTX 1070 [17:11:25][0x00001518][info] core | Found CUDA device: GeForce GTX 1070 [17:11:25][0x00001518][info] core | Found CUDA device: GeForce GTX 1070 [17:11:25][0x00001518][info] core | Found CUDA device: GeForce GTX 1070 [17:11:25][0x00001518][info] api | Listening on 0.0.0.0:33333 [17:11:25][0x00001518][info] http | Listening on 0.0.0.0:38080 [17:11:25][0x00001518][info] core | Initialized! [17:11:26][0x00002300][info] net | Connecting to 169.50.175.203:3341 (neoscrypt.eu.nicehash.com) [17:11:26][0x00002300][info] net | Connected! [17:11:26][0x00002300][info] net | Authorized as 19M9g3vvfyDfUhdekwokAVanKdiTtSCmF2.node07 [17:11:26][0x00002300][info] algo-neoscrypt | New job_0 '000000096d78dbc0', diff=0.0078125 [17:11:28][0x00000774][info] wrkr1-1 | Algorithm: CUDA-neoscrypt parameters: B=1410 [17:11:29][0x00002b8c][info] wrkr3-3 | Algorithm: CUDA-neoscrypt parameters: B=1410 [17:11:29][0x00000d58][info] wrkr2-2 | Algorithm: CUDA-neoscrypt parameters: B=1410 [17:11:29][0x00002008][info] wrkr0-0 | Algorithm: CUDA-neoscrypt parameters: B=1410 [17:11:29][0x00002814][fatal] wrkr4-4 | CUDA error 'out of memory' in func 'cuda_neoscrypt::init' line 1258 [17:11:29][0x00001518][info] Shutting down [17:11:30][0x00001518][info] api | Closing [17:11:30][0x00001518][info] http | Closing

Overclocking disabled : {"id":1,"method":"device.set.tdp","params": ["0","100"]}, {"id":1,"method":"device.set.core_delta","params": ["0","0"]}, {"id":1,"method":"device.set.memory_delta","params":["0","0"]},

t4nja commented 6 years ago

Increasing virtual memory size should solve the problem. #104

t4nja commented 6 years ago

So I can finally reproduce this issue. When running standalone excavator everything works fine, but if there is NHM running on the system (doesn't have to be mining, it's enough that it's opened), then 'out of memory' crash occurs on the primary GPU. To avoid such issues, I suggest you to disable NeoScrypt on your primary card (only primary GPU is problematic, at least in my case) until this bug is fixed by the NHM team. Of course, the crash can still happen when using a standalone Excavator, since third party applications that are GPU consuming can crash the primary card as well, in such case just do the same - don't run neoscrypt on your primary card.

If this issue persists in the future, we'll work on a different implementation of the NeoScrypt (that won't need as much memory as current one).

I'm closing this (will reopen if needed), thank you all for your feedback! Keep on mining :)

Btw, we released new version of excavator today - https://github.com/nicehash/excavator/releases/tag/v1.3.9a

MossP commented 6 years ago

@dropky I have started seeing this error on v2.0.1.11 even though my primary card is my separate onboard graphics card. Has something changed in the latest build?

Edit: I've not yet tried the VM increase. About to try it now but through I would mention the issue.

MossP commented 6 years ago

@dropky Apologies, it appears that my primary card has switched to one of my mining cards. I'll apply the fixes suggested and try again. Thanks for the info.