Closed DuquetteRoxx closed 6 years ago
I have also tried setting affinity to CPU and all sync modes.
please delete the file nvidia.txt start the miner and post the file. Please copy&past the text instead of posting screenshots
If I delete the file and start the miner, it disables back-end nvidia.
There is nothing in nvidia.txt now, just the template.
/*
* GPU configuration. You should play around with threads and blocks as the fastest settings will vary.
* index - GPU index number usually starts from 0.
* threads - Number of GPU threads (nothing to do with CPU threads).
* blocks - Number of GPU blocks (nothing to do with CPU threads).
* bfactor - Enables running the Cryptonight kernel in smaller pieces.
* Increase if you want to reduce GPU lag. Recommended setting on GUI systems - 8
* bsleep - Insert a delay of X microseconds between kernel launches.
* Increase if you want to reduce GPU lag. Recommended setting on GUI systems - 100
* affine_to_cpu - This will affine the thread to a CPU. This can make a GPU miner play along nicer with a CPU miner.
* sync_mode - method used to synchronize the device
* documentation: http://docs.nvidia.com/cuda/cuda-runtime-api/group__CUDART__DEVICE.html#group__CUDART__DEVICE_1g69e73c7dda3fc05306ae7c811a690fac
* 0 = cudaDeviceScheduleAuto
* 1 = cudaDeviceScheduleSpin - create a high load on one cpu thread per gpu
* 2 = cudaDeviceScheduleYield
* 3 = cudaDeviceScheduleBlockingSync (default)
*
* On the first run the miner will look at your system and suggest a basic configuration that will work,
* you can try to tweak it from there to get the best performance.
*
* A filled out configuration should look like this:
* "gpu_threads_conf" :
* [
* { "index" : 0, "threads" : 17, "blocks" : 60, "bfactor" : 0, "bsleep" : 0,
* "affine_to_cpu" : false, "sync_mode" : 3,
* },
* ],
*/
"gpu_threads_conf" :
[
],
It also looks like they will only hash for a second or two, and then stop, repeatedly.
In that case please remove the file nvidia.txt
gain start the miner and post all output from the terminal.
xmr-stak 2.1.0 30888a3
Brought to you by fireice_uk and psychocrypt under GPLv3. Based on CPU mining code by wolf9466 (heavily optimized by fireice_uk). Based on NVIDIA mining code by KlausT and psychocrypt. Based on OpenCL mining code by wolf9466.
Configurable dev donation level is set to 2.0%
Totals: 306.6 (na) (na) H/s Highest: 303.6 H/s CONNECTION REPORT Pool address : nyc01.supportxmr.com:7777 Connected since : 2017-12-12 15:49:28 Pool ping time : (n/a)
Totals: 300.4 (na) (na) H/s Highest: 304.6 H/s [2017-12-12 15:50:09] : Difficulty changed. Now: 25000. [2017-12-12 15:50:09] : New block detected. [2017-12-12 15:50:26] : Difficulty changed. Now: 16854. [2017-12-12 15:50:26] : New block detected.
Whats your CFG file content for nvidia after you have deleted empty CFG and restarted miner - did it create a new CFG file? if it did whats in it?
Yes when I run it after deleting the nvidia config, it creates a new nvidia.txt but it just has the “template” inside it, no actual values set.
It has 2 gpu's on board right? Perhaps in this case it will be necessary to manually play with CFG. Maybe someone has any other titans CFG to compare with... have you tried any other miners with it, were they successful? if yes, then its possible to look in to configs generated by those miners and try applying it p.s. what driver you are using for your titan?
I'll bet this is the problem..
The NVIDIA driver is the latest? 388.59 WHQL
Yup. Tried deleting all previous versions/clean install and all that.
Looks like XMR-stak is unable to determine your GPU, this is a bug
Are there any values I can enter to force it to acknowledge the cards?
Leave only one GPU in the system and repeat all over again.
My friend is having a similar issue with his Titan X. Gave him your advice sergneo, will let you know what happens.
I have the same problem ... Titan X the old one (maxwell) and it is not being detected automatically ...
Specs: i7 5930K 128GB DDR4 @ 4200MHZ (2) GTX Titan X (SLI off) Windows 10 No overclocks on CPU, or GPU. Standard XMP overclock on the RAM.
Have tried every combination of threads and blocks, all of which produce 104 to 107 rate.
Have tried many values of bfactor. (nothing lower than 7 works, and 12 makes my system usable) All bsleep values between 5-100 seem to work.