Miner will not start after upgrade

[lodonnel]

Please provide as much as possible information to reproduce the issue.

One of Two messages pop up in the console. === message 1 === [2018-10-26 13:59:15] : Mining coin: cryptonight_v7 [2018-10-26 13:59:15] : NVIDIA: try to load library 'xmrstak_cuda_backend_cuda10_0' NVIDIA: found 1 potential device's [2018-10-26 13:59:15] : Starting NVIDIA GPU thread 0, no affinity. GPU -1822427968: invalid device ordinal C:/xmr-stak/xmr-stak-win64-2.5.2/xmrstak/backend/nvidia/nvcc_code/cuda_extra.cu line 499 [2018-10-26 13:59:15] : Setup failed for GPU 0. Exiting.

=== or message 2 === [2018-10-26 14:14:04] : Mining coin: cryptonight_v7 [2018-10-26 14:14:04] : NVIDIA: try to load library 'xmrstak_cuda_backend_cuda10_0' NVIDIA: found 1 potential device's [2018-10-26 14:14:05] : Starting NVIDIA GPU thread 0, affinity: 1074786536. WARNING: Invalid device ID '1074786688'! [2018-10-26 14:14:05] : Setup failed for GPU 0. Exiting.

===========

After Upgrade I noticed that the latest nvidia drivers were also required. Version Installed NVIDIA GEFORCE GTX 1080 Ti Date 10/10/2018 Version 25.21.14.1634

I have appended my config files to the end of this section

Basic information

GEFORCE 1080 Ti

Compile issues

Windows 10

Issue with the execution

No, downloaded from github releases run ./xmr-stak --version-long and add the output here Version: xmr-stak/2.5.2/752fd1e7e/master/win/nvidia-amd-cpu/20

AMD OpenCl issue

  run `clinfo` and add the output here

Stability issue

• Is the CPU or GPU overclocked? No
• Is the Main memory of the CPU or GPU undervolted? No

===================== My Config File ====

/*

• Network timeouts.
• Because of the way this client is written it doesn't need to constantly talk (keep-alive) to the server to make
• sure it is there. We detect a buggy / overloaded server by the call timeout. The default values will be ok for
• nearly all cases. If they aren't the pool has most likely overload issues. Low call timeout values are preferable -
• long timeouts mean that we waste hashes on potentially stale jobs. Connection report will tell you how long the
• server usually takes to process our calls.
• call_timeout - How long should we wait for a response from the server before we assume it is dead and drop the connection.
• retry_time - How long should we wait before another connection attempt.
• Both values are in seconds.
• giveup_limit - Limit how many times we try to reconnect to the pool. Zero means no limit. Note that stak miners
• don't mine while the connection is lost, so your computer's power usage goes down to idle. */ "call_timeout" : 10, "retry_time" : 30, "giveup_limit" : 0,

/*

• Output control.
• Since most people are used to miners printing all the time, that's what we do by default too. This is suboptimal
• really, since you cannot see errors under pages and pages of text and performance stats. Given that we have internal
• performance monitors, there is very little reason to spew out pages of text instead of concise reports.
• Press 'h' (hashrate), 'r' (results) or 'c' (connection) to print reports.
• verbose_level - 0 - Don't print anything.
• 1 - Print intro, connection event, disconnect event
• 2 - All of level 1, and new job (block) event if the difficulty is different from the last job
• 3 - All of level 1, and new job (block) event in all cases, result submission event.
• 4 - All of level 3, and automatic hashrate report printing
• print_motd - Display messages from your pool operator in the hashrate result. */ "verbose_level" : 4, "print_motd" : true,

/*

• Automatic hashrate report
• h_print_time - How often, in seconds, should we print a hashrate report if verbose_level is set to 4.
• This option has no effect if verbose_level is not 4. */ "h_print_time" : 60,

/*

• Manual hardware AES override
• Some VMs don't report AES capability correctly. You can set this value to true to enforce hardware AES or
• to false to force disable AES or null to let the miner decide if AES is used.
• WARNING: setting this to true on a CPU that doesn't support hardware AES will crash the miner. */ "aes_override" : null,

/*

• LARGE PAGE SUPPORT
• Large pages need a properly set up OS. It can be difficult if you are not used to systems administration,
• but the performance results are worth the trouble - you will get around 20% boost. Slow memory mode is
• meant as a backup, you won't get stellar results there. If you are running into trouble, especially
• on Windows, please read the common issues in the README.
• By default we will try to allocate large pages. This means you need to "Run As Administrator" on Windows.
• You need to edit your system's group policies to enable locking large pages. Here are the steps from MSDN
• 1. On the Start menu, click Run. In the Open box, type gpedit.msc.
• 2. On the Local Group Policy Editor console, expand Computer Configuration, and then expand Windows Settings.
• 3. Expand Security Settings, and then expand Local Policies.
• 4. Select the User Rights Assignment folder.
• 5. The policies will be displayed in the details pane.
• 6. In the pane, double-click Lock pages in memory.
• 7. In the Local Security Setting – Lock pages in memory dialog box, click Add User or Group.
• 8. In the Select Users, Service Accounts, or Groups dialog box, add an account that you will run the miner on
• 9. Reboot for change to take effect.
• Windows also tends to fragment memory a lot. If you are running on a system with 4-8GB of RAM you might need
• to switch off all the auto-start applications and reboot to have a large enough chunk of contiguous memory.
• On Linux you will need to configure large page support "sudo sysctl -w vm.nr_hugepages=128" and increase your
• ulimit -l. To do do this you need to add following lines to /etc/security/limits.conf - "* soft memlock 262144"
• and "* hard memlock 262144". You can also do it Windows-style and simply run-as-root, but this is NOT
• recommended for security reasons.
• Memory locking means that the kernel can't swap out the page to disk - something that is unlikely to happen on a
• command line system that isn't starved of memory. I haven't observed any difference on a CLI Linux system between
• locked and unlocked memory. If that is your setup see option "no_mlck". */

/*

• use_slow_memory defines our behaviour with regards to large pages. There are three possible options here:
• always - Don't even try to use large pages. Always use slow memory.
• warn - We will try to use large pages, but fall back to slow memory if that fails.
• no_mlck - This option is only relevant on Linux, where we can use large pages without locking memory.
• It will never use slow memory, but it won't attempt to mlock
• never - If we fail to allocate large pages we will print an error and exit. */ "use_slow_memory" : "warn",

/*

• TLS Settings
• If you need real security, make sure tls_secure_algo is enabled (otherwise MITM attack can downgrade encryption
• to trivially breakable stuff like DES and MD5), and verify the server's fingerprint through a trusted channel.
• tls_secure_algo - Use only secure algorithms. This will make us quit with an error if we can't negotiate a secure algo. */ "tls_secure_algo" : true,

/*

• Daemon mode
• If you are running the process in the background and you don't need the keyboard reports, set this to true.
• This should solve the hashrate problems on some emulated terminals. */ "daemon_mode" : false,

/*

• Buffered output control.
• When running the miner through a pipe, standard output is buffered. This means that the pipe won't read
• each output line immediately. This can cause delays when running in background.
• Set this option to true to flush stdout after each line, so it can be read immediately. */ "flush_stdout" : false,

/*

• Output file
• output_file - This option will log all output to a file.

• */ "output_file" : "",

/*

• Built-in web server
• I like checking my hashrate on my phone. Don't you?
• Keep in mind that you will need to set up port forwarding on your router if you want to access it from
• outside of your home network. Ports lower than 1024 on Linux systems will require root.
• httpd_port - Port we should listen on. Default, 0, will switch off the server. */ "httpd_port" : 443,

/*

• HTTP Authentication
• This allows you to set a password to keep people on the Internet from snooping on your hashrate.
• Keep in mind that this is based on HTTP Digest, which is based on MD5. To a determined attacker
• who is able to read your traffic it is as easy to break a bog door latch.
• http_login - Login. Empty login disables authentication.
• http_pass - Password. */ "http_login" : "", "http_pass" : "",

/*

• prefer_ipv4 - IPv6 preference. If the host is available on both IPv4 and IPv6 net, which one should be choose?
• This setting will only be needed in 2020's. No need to worry about it now. */ "prefer_ipv4" : true,

====== nvidia config file ====

/*

• 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" : 0,
• },
• ],
• If you do not wish to mine with your nVidia GPU(s) then use:
• "gpu_threads_conf" :
• null, */

// "gpu_threads_conf" : // null,

"gpu_threads_conf" : [ // gpu: GeForce GTX 1080 Ti architecture: 61 // memory: 9310/11264 MiB // smx: 28 { "index" : 0, "threads" : 32, "blocks" : 80, "bfactor" : 6, "bsleep" : 25, "affine_to_cpu" : false, "sync_mode" : 3, },

// { // gpu: nVidia Quadro //

//"index" : 1, // "threads" : 32, "blocks" : 80, // "bfactor" : 6, "bsleep" : 25, // "affine_to_cpu" : false, "sync_mode" : 3, //},

],

=== cpu config file ===

/*

• Thread configuration for each thread. Make sure it matches the number above.
• low_power_mode - This can either be a boolean (true or false), or a number between 1 to 5. When set to true,
• this mode will double the cache usage, and double the single thread performance. It will
• consume much less power (as less cores are working), but will max out at around 80-85% of
• the maximum performance. When set to a number N greater than 1, this mode will increase the
• cache usage and single thread performance by N times.
• no_prefetch - Some systems can gain up to extra 5% here, but sometimes it will have no difference or make
• things slower.
• affine_to_cpu - This can be either false (no affinity), or the CPU core number. Note that on hyperthreading
• systems it is better to assign threads to physical cores. On Windows this usually means selecting
• even or odd numbered cpu numbers. For Linux it will be usually the lower CPU numbers, so for a 4
• physical core CPU you should select cpu numbers 0-3.
• 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:
• "cpu_threads_conf" :
• [
• { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 0 },
• { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 1 },
• ],
• If you do not wish to mine with your CPU(s) then use:
• "cpu_threads_conf" :
• null, */

"cpu_threads_conf" : null, /* [ { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 0 }, { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 2 },

], */

==== pools config file ====

/*

• pool_address - Pool address should be in the form "pool.supportxmr.com:3333". Only stratum pools are supported.
• wallet_address - Your wallet, or pool login.
• rig_id - Rig identifier for pool-side statistics (needs pool support).
• pool_password - Can be empty in most cases or "x".
• use_nicehash - Limit the nonce to 3 bytes as required by nicehash.
• use_tls - This option will make us connect using Transport Layer Security.
• tls_fingerprint - Server's SHA256 fingerprint. If this string is non-empty then we will check the server's cert against it.
• pool_weight - Pool weight is a number telling the miner how important the pool is. Miner will mine mostly at the pool
• with the highest weight, unless the pool fails. Weight must be an integer larger than 0.
• We feature pools up to 1MH/s. For a more complete list see M5M400's pool list at www.moneropools.com */

"pool_list" : [ /* { "pool_address" : "etn-pool.proxpool.com:443", "wallet_address" : "etnk3eHvqJkeK3zFGjswpE5EjsSJ5AjNjA2Jz9zWk4RC9RZPyESBKojgvY1uTcnZDDCAuAqtnghx67VgcFStzu1P2Ua5R5S1Lp", "rig_id" : "", "pool_password" : "x", "use_nicehash" : false, "use_tls" : false, "tls_fingerprint" : "", "pool_weight" : 100 },

*/

{ "pool_address" : "paris01.monero.hashvault.pro:443", "wallet_address" : "46a3c69agkcSY445dv6WA32tD9NSX3UWpWnE2AWA1NUHdVBmTWSPr1wMBbXsSKqEUXS3cH1TZE1FcTAqtVW1dTezE3QRqPW", "rig_id" : "", "pool_password" : "Dell-7010:liam.odonnell@dit.ie", "use_nicehash" : false, "use_tls" : false, "tls_fingerprint" : "", "pool_weight" : 200 },

/* { "pool_address" : "frankfurt01.electroneum.hashvault.pro:443", "wallet_address" : "etnk3eHvqJkeK3zFGjswpE5EjsSJ5AjNjA2Jz9zWk4RC9RZPyESBKojgvY1uTcnZDDCAuAqtnghx67VgcFStzu1P2Ua5R5S1Lp", "rig_id" : "", "pool_password" : "x", "use_nicehash" : false, "use_tls" : true, "tls_fingerprint" : "", "pool_weight" : 60 },

{ "pool_address" : "moscow01.electroneum.hashvault.pro:443", "wallet_address" : "etnk3eHvqJkeK3zFGjswpE5EjsSJ5AjNjA2Jz9zWk4RC9RZPyESBKojgvY1uTcnZDDCAuAqtnghx67VgcFStzu1P2Ua5R5S1Lp", "rig_id" : "", "pool_password" : "x", "use_nicehash" : false, "use_tls" : true, "tls_fingerprint" : "", "pool_weight" : 60 }, / / { "pool_address" : "london01.electroneum.hashvault.pro:443", "wallet_address" : "etnk3eHvqJkeK3zFGjswpE5EjsSJ5AjNjA2Jz9zWk4RC9RZPyESBKojgvY1uTcnZDDCAuAqtnghx67VgcFStzu1P2Ua5R5S1Lp", "rig_id" : "", "pool_password" : "x", "use_nicehash" : false, "use_tls" : true, "tls_fingerprint" : "", "pool_weight" : 300 }, / / { "pool_address" : "uk-etn-pool.hashparty.io:443", "wallet_address" : "etnk3eHvqJkeK3zFGjswpE5EjsSJ5AjNjA2Jz9zWk4RC9RZPyESBKojgvY1uTcnZDDCAuAqtnghx67VgcFStzu1P2Ua5R5S1Lp+50000", "rig_id" : "", "pool_password" : "x", "use_nicehash" : false, "use_tls" : true, "tls_fingerprint" : "", "pool_weight" : 50 },

{ "pool_address" : "paris01.sumokoin.hashvault.pro:80", "wallet_address" : "Sumoo1NQeiU3dftZYiNz47aVwZJqDLpgaa7CdNw78cJhUmmpu9rgbAM6r7gkkqxD7BCkdcgwAhC1BT2qBHw2x5Wu5nJb5bLi3ZC+50000", "rig_id" : "", "pool_password" : "x", "use_nicehash" : false, "use_tls" : false, "tls_fingerprint" : "", "pool_weight" : 50 },

*/

],

/*

• Currency to mine. Supported values:
• aeon7 (use this for Aeon's new PoW)
• bbscoin (automatic switch with block version 3 to cryptonight_v7)
• croat
• edollar
• electroneum
• graft
• haven
• intense
• ipbc
• karbo
• masari
• monero7 (use this for Monero's new PoW)
• sumokoin (automatic switch with block version 3 to cryptonight_heavy)
• turtlecoin
• Native algorithms which not depends on any block versions:

• 1MiB scratchpad memory

• cryptonight_lite
• cryptonight_lite_v7
• cryptonight_lite_v7_xor (algorithm used by ipbc)

• 2MiB scratchpad memory

• cryptonight
• cryptonight_v7

• 4MiB scratchpad memory

• cryptonight_heavy */

"currency" : "cryptonight_v7",

=====

[psychocrypt]

do you have cuda 10 installed? If not install cuda 10 or remove the file xmrstak_cuda_backend_cuda10_0 than the miner will fall back to an older cuda

[Spudz76]

Driver 411.64 is CUDA 10 so that is correct. Although 416.34 is latest, I think I had that version also working on GTX970. Did you delete nvidia.txt and regenerate with proper currency set with the new driver installed? I have seen that weird ordinal error before but I'm not sure how I triggered it.

[lodonnel]

What format is the new Nvidia.txt file ... What changes should I look out for.ThanksLiamSent from my Samsung Galaxy smartphone. -------- Original message --------From: Tony Butler notifications@github.com Date: 26/10/2018 16:35 (GMT+00:00) To: fireice-uk/xmr-stak xmr-stak@noreply.github.com Cc: lodonnel liam.odonnell@dit.ie, Author author@noreply.github.com Subject: Re: [fireice-uk/xmr-stak] Miner will not start after upgrade (#2020) Driver 411.64 is CUDA 10 so that is correct. Although 416.34 is latest, I think I had that version also working on GTX970. Did you delete nvidia.txt and regenerate with proper currency set with the new driver installed? I have seen that weird ordinal error before but I'm not sure how I triggered it.

—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread. {"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/fireice-uk/xmr-stak","title":"fireice-uk/xmr-stak","subtitle":"GitHub repository","main_image_url":"https://assets-cdn.github.com/images/email/message_cards/header.png","avatar_image_url":"https://assets-cdn.github.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/fireice-uk/xmr-stak"}},"updates":{"snippets":[{"icon":"PERSON","message":"@Spudz76 in #2020: Driver 411.64 is CUDA 10 so that is correct. Although 416.34 is latest, I think I had that version also working on GTX970.\r\nDid you delete nvidia.txt and regenerate with proper currency set with the new driver installed?\r\nI have seen that weird ordinal error before but I'm not sure how I triggered it."}],"action":{"name":"View Issue","url":"https://github.com/fireice-uk/xmr-stak/issues/2020#issuecomment-433449842"}}} [ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/fireice-uk/xmr-stak/issues/2020#issuecomment-433449842", "url": "https://github.com/fireice-uk/xmr-stak/issues/2020#issuecomment-433449842", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } }, { "@type": "MessageCard", "@context": "http://schema.org/extensions", "hideOriginalBody": "false", "originator": "AF6C5A86-E920-430C-9C59-A73278B5EFEB", "title": "Re: [fireice-uk/xmr-stak] Miner will not start after upgrade (#2020)", "sections": [ { "text": "", "activityTitle": "Tony Butler", "activityImage": "https://assets-cdn.github.com/images/email/message_cards/avatar.png", "activitySubtitle": "@Spudz76", "facts": [

] } ], "potentialAction": [ { "name": "Add a comment", "@type": "ActionCard", "inputs": [ { "isMultiLine": true, "@type": "TextInput", "id": "IssueComment", "isRequired": false } ], "actions": [ { "name": "Comment", "@type": "HttpPOST", "target": "https://api.github.com", "body": "{\n\"commandName\": \"IssueComment\",\n\"repositoryFullName\": \"fireice-uk/xmr-stak\",\n\"issueId\": 2020,\n\"IssueComment\": \"{{IssueComment.value}}\"\n}" } ] }, { "name": "Close issue", "@type": "HttpPOST", "target": "https://api.github.com", "body": "{\n\"commandName\": \"IssueClose\",\n\"repositoryFullName\": \"fireice-uk/xmr-stak\",\n\"issueId\": 2020\n}" }, { "targets": [ { "os": "default", "uri": "https://github.com/fireice-uk/xmr-stak/issues/2020#issuecomment-433449842" } ], "@type": "OpenUri", "name": "View on GitHub" }, { "name": "Unsubscribe", "@type": "HttpPOST", "target": "https://api.github.com", "body": "{\n\"commandName\": \"MuteNotification\",\n\"threadId\": 401661939\n}" } ], "themeColor": "26292E" } ] --

This email originated from DIT. If you received this email in error, please delete it from your system. Please note that if you are not the named addressee, disclosing, copying, distributing or taking any action based on the contents of this email or attachments is prohibited.  www.dit.ie http://www.dit.ie/

Is ó ITBÁC a tháinig an ríomhphost seo. Má fuair tú an ríomhphost seo trí earráid, scrios de do chóras é le do thoil. Tabhair ar aird, mura tú an seolaí ainmnithe, go bhfuil dianchosc ar aon nochtadh, aon chóipeáil, aon dáileadh nó ar aon ghníomh a dhéanfar bunaithe ar an ábhar atá sa ríomhphost nó sna hiatáin seo. www.dit.ie http://www.dit.ie/

Tá ITBÁC ag aistriú go Gráinseach Ghormáin – DIT is on the move to Grangegorman http://www.dit.ie/grangegorman

[Spudz76]

Regenerate the file. Differences are never discussed, because regenerating is how you get the new file format. Hand apply changes if needed, and note the CN2v2 (v8) is totally different than CN1v2 (v7) and none of the old numbers that used to be good will be the same anymore - retune from regenerated brand new file, there are no more lucky numbers from v7 you have to retune.

[r1k0]

Just wanted to say that I've had the same issue since 2.5.* and deleting config files and let them be regenerated fixes the issue. Thanks for the work guys!