Tips & tricks
Open nhqm.conf (NiceHash QuickMiner right click notification icon and choose Settings -> Edit config file) and modify "serviceLocation". Following locations are possible:
- Europe (Belgium):
0, - USA (California):
1.
In the near future, more locations will be possible to choose from. After saving the config file, your mining location will be updated almost instantly. Observe latencies from accepted shares in Excavator console.
The numbers marked with red squares must be as low as possible. Experiment with serviceLocation until you get the best result.
If you have more mining PCs, you can set name for each one. You can do this online through Rig Manager or locally through config. Open nhqm.conf (NiceHash QuickMiner right click notification icon and choose Settings -> Edit config file) and modify "workerName". Name should only contain alphanumeric characters of English alphabet and max length is 15 characters.
Mining by itself is very unstable process because hardware is pushed to the limits. Something can always go wrong. NiceHash QuickMiner will in most cases take care of all the issues, but sometimes, it cannot do on it's own and needs your command. There are two scenarios that can happen and three possibilities how NiceHash QuickMiner can react.
| Scenario | Possible action | Config name | Default action |
|---|---|---|---|
| Excavator shows abnormally high speed | Do nothing 1Restart Excavator 2Restart PC 3
|
"whenDeviceSpeedTooHigh" |
2 |
| Excavator shows speed zero | Do nothing 1Restart Excavator 2Restart PC 3
|
"whenDeviceSpeedZero" |
1 |
When device is malfunction and not mining, Error will be displayed in Rig Manager as visible on the following picture.
We suggest you to try to set action to number 2 (Restart Excavator). If that does not help and resolve the issue automatically, then set this to number 3. The above mentioned config values can be found in nhqm.conf (NiceHash QuickMiner right click notification icon and choose Settings -> Edit config file).
When something does go wrong, it can be fixed in most cases, but enough information is needed. We suggest you to enable file logging when you have problems. You can do this by modifying nhqm.conf (NiceHash QuickMiner right click notification icon and choose Settings -> Edit config file). Set "fileLogLevel" to 0 and also change "launchCommandLine" for Excavator to "-wp 18000 -d 2 -f 0" (note the last number changed to zero). This will enable both (NiceHash QuickMiner and Excavator full file logging). When submitting issue here, it is strongly suggested to also provide these logs so the issue can be identified and resolved faster. Do not forget to remove your personal information from logs (such as your Mining Address) before you submit them.
| Log level number | Log what? |
|---|---|
| 0 | log everything (TRACE) |
| 1 | log debug (DEBUG) |
| 2 | standard (INFO) |
| 3 | warnings (WARNING) |
| 4 | errors (ERROR) |
| 5 | fatal (FATAL) |
| 6 | no logging (disabled) |
OCTune tips & tricks can be found here.
When you are running cards over risers, this adds extra instability factor to your configuration. You need to make sure your risers (comm link between CPU and GPU) are max stable. To achieve this, you need to set PCI Generation to 1 in BIOS (or at least 2). Having higher Generation introduce more instability because communication between CPU and GPU is faster and there are more chances for something to go wrong. There is no speed penalty when running Gen1 - your cards will hash at the same speed.
If one of your cards crashes during mining and you see device ERROR it most likely means riser instability. This is especially true, if it happens when your card is not overclocked. In this case replace riser, cable and set PCIE gen1 in BIOS.
When running more than 4 video cards, you will also have to set Above 4G decoding to Enabled in your motherboard's BIOS.
If you would like to receive RC updates as soon as they are available, then in config file nhqm.conf flip the switch "bUpdateRCVersion" to true. If you decide to participate in testing of early new versions, please, submit all found bugs here. Thank you!