Nicehash 105 error

Describe the bug After upgrading from previous RC I05 error and constantly restarting even with a fresh unconfigured setup, and on my other PC on the same network works fine with the same version o...

Describe the bug
After upgrading from previous RC I05 error and constantly restarting even with a fresh unconfigured setup, and on my other PC on the same network works fine with the same version of the miner

To Reproduce
Just run NiceHashQuickMiner.exe

Version affected (please complete the following information):
v0.5.4.0 RC

NVIDIA driver version
512.59 DCH

Hardware
3070 LHR V2 directly plugged into to motherboard PCI 4 16x sloth

Logs
nhqm log
[2022-05-07 12:17:43:229] [INFO] [optimizeprofiles] Data updated with iteration=1
[2022-05-07 12:17:43:229] [INFO] [optimizeprofiles] Data received, quitting fetch thread
[2022-05-07 12:17:43:229] [DEBUG] [optimizeprofiles] Quit thread
[2022-05-07 12:17:43:318] [INFO] [updater] Latest version: 0.5.4.0_RC
[2022-05-07 12:17:43:319] [INFO] [updater] Already running latest version
[2022-05-07 12:17:43:671] [INFO] [watchdog] Started, pid=45500
[2022-05-07 12:17:44:163] [DEBUG] [nhmws] Logging in
[2022-05-07 12:17:44:163] [TRACE] [nhmws] Sending: {«method»:»login»,»version»:[«NHQM_v0.5.4.0″,»Excavator_v1.7.7.0_Build_1020″],»protocol»:4,»btc»:»REDACTED«,»worker»:»Desktop»,»rig»:»0-036FST8jmE6VF95yPL5hnQ»,»group»:»»}
[2022-05-07 12:17:44:165] [TRACE] [nhmws] Sent result: True
[2022-05-07 12:17:44:201] [TRACE] [nhmws] Received: {«method»:»markets»,»data»:[«USA»,»USA_E»,»EU_N»,»EU»]}
[2022-05-07 12:17:44:203] [INFO] [nhmws] Enabling location: AUTO
[2022-05-07 12:17:45:145] [DEBUG] [watchdog] Setting new subscribe data: REDACTED$0-036FST8jmE6VF95yPL5hnQ, auto
[2022-05-07 12:17:48:701] [DEBUG] [watchdog] Getting memory info (is enough?) and CPUs
[2022-05-07 12:17:48:701] [TRACE] [watchdog] HTTP API GET: /devices
[2022-05-07 12:17:52:738] [DEBUG] [watchdog] HTTP API GET failed: Unable to connect to the remote server
[2022-05-07 12:17:52:738] [ERROR] [watchdog] Failed to establish communication channel with Excavator!
[2022-05-07 12:17:53:109] [TRACE] [nhmws] Getting status data
[2022-05-07 12:17:53:109] [TRACE] [main] Getting devices
[2022-05-07 12:17:53:112] [TRACE] [watchdog] HTTP API GET: /info
[2022-05-07 12:17:53:761] [INFO] [watchdog] Starting excavator.exe with cmdline: -c commands.json -qx -qm -d 2 -f 0 -wi localhost -wp 18000 -wa FFF2EAC4F22B9255B6A839BF
[2022-05-07 12:17:54:301] [INFO] [watchdog] Started, pid=15236
[2022-05-07 12:17:57:164] [DEBUG] [watchdog] Getting devices parse err: The operation has timed out
[2022-05-07 12:17:57:164] [DEBUG] [nhmws] Sending status data
[2022-05-07 12:17:57:164] [TRACE] [nhmws] Sending: {«method»:»miner.status»,»params»:[«ERROR»,[]]}
[2022-05-07 12:17:57:164] [TRACE] [nhmws] Sent result: True
[2022-05-07 12:17:59:335] [DEBUG] [watchdog] Getting memory info (is enough?) and CPUs
[2022-05-07 12:17:59:335] [TRACE] [watchdog] HTTP API GET: /devices
[2022-05-07 12:17:59:990] [WARNING] [config] save_config_file button2_Click
[2022-05-07 12:17:59:990] [WARNING] [config] _internal_save_config_file save_config_file
[2022-05-07 12:18:03:403] [DEBUG] [watchdog] HTTP API GET failed: Unable to connect to the remote server
[2022-05-07 12:18:03:403] [ERROR] [watchdog] Failed to establish communication channel with Excavator!
[2022-05-07 12:18:04:428] [INFO] [watchdog] Starting excavator.exe with cmdline: -c commands.json -qx -qm -d 2 -f 0 -wi localhost -wp 18000 -wa FFF2EAC4F22B9255B6A839BF
[2022-05-07 12:18:04:968] [INFO] [watchdog] Started, pid=2496
[2022-05-07 12:18:10:012] [DEBUG] [watchdog] Getting memory info (is enough?) and CPUs
[2022-05-07 12:18:10:012] [TRACE] [watchdog] HTTP API GET: /devices
[2022-05-07 12:18:13:807] [INFO] [exportlogs] Exporting logs

event log
[[2022-05-07 12:18:05.441412] [thread=0x00002cdc] [info]] Log started, build v1020

[[2022-05-07 12:18:05.509791] [thread=0x00002cdc] [debug]] Core created

[[2022-05-07 12:18:05.509791] [thread=0x00002cdc] [debug]] Algos set

[[2022-05-07 12:18:07.516014] [thread=0x00002cdc] [info]] core | CUDA memory allocation: std

[[2022-05-07 12:18:07.523735] [thread=0x00002cdc] [trace]] device #0 | Power limits; min=100.00 max=270.00 def=240.00

[[2022-05-07 12:18:07.526738] [thread=0x00002cdc] [trace]] device #0 | Default memory clock: 6801

[[2022-05-07 12:18:07.527739] [thread=0x00002cdc] [warning]] LHR | Device #0 | Intensity: 55%. Unlock ratio: 100%

[[2022-05-07 12:18:07.527739] [thread=0x00002cdc] [info]] core | Found Supported CUDA device #0: GeForce RTX 3070 id: 0

[[2022-05-07 12:18:07.527739] [thread=0x00002cdc] [info]] http | Listening on [::1]:18000

[[2022-05-07 12:18:07.528740] [thread=0x00002cdc] [debug]] Adding command with 20 seconds execution delay:

{"id":1,"method":"workers.reset.all","params":[]}

[[2022-05-07 12:18:07.528740] [thread=0x00002cdc] [debug]] Adding command with 30 seconds execution delay and 30 seconds loop time:

{"id":1,"method":"worker.print.efficiencies","params":[]}

[[2022-05-07 12:18:07.528740] [thread=0x00002cdc] [debug]] Adding command with 1 seconds execution delay and 4 seconds loop time:

{"id":1,"method":"devices.smartfan.exec","params":[]}

[[2022-05-07 12:18:07.528740] [thread=0x00002cdc] [info]] core | Initialized!

[[2022-05-07 12:18:08.529520] [thread=0x0000b404] [trace]] Executing: {«id»:1,»method»:»devices.smartfan.exec»,»params»:[]}

[[2022-05-07 12:18:08.529520] [thread=0x0000b404] [trace]] core | Command method: devices.smartfan.exec

[[2022-05-07 12:18:08.529520] [thread=0x0000b404] [trace]] Response: {«id»:1,»error»:null}

Источник

Содержание

  1. Error 105 with Radeon VII mixed with Nvidia (3090) #774
  2. Comments
  3. Footer
  4. Error 105 [BUG] #806
  5. Comments

Error 105 with Radeon VII mixed with Nvidia (3090) #774

Quickminer goes insane when trying to use the Radeon VII in the same machine as a RTX 3090. I get error 105 REPEATEDLY. Neither 0.5.3.3 nor 0.5.3.5RC solve the issues. I reinstalled drivers and connected, as well disconnected, video out and there was no change. Everything works when the Radeon VII is unplugged. The radeon VII and 3090’s work fine together using the regular nicehash miner, so I do not think it’s a hardware issue.

Was I erroneous thinking QM could run RVII’s and 3090’s in the same machine?

EDIT: I’m not using risers. The GPU’s are plugged directly into the motherboard, which is a Gigabyte WRX80 and using a AMD 3955WX CPU.

The text was updated successfully, but these errors were encountered:

QuickMiner should work with these two GPUs at the same time.

I agree that it should, but it doesn’t on my machine

try to increase API timeout, in nhqm.conf
replace «watchDogAPITimeout» : 2000, with «watchDogAPITimeout» : 10000,

ps: it would be easier if you were reporting errors on discord, this way I could ask you to post debug file

try to increase API timeout, in nhqm.conf replace «watchDogAPITimeout» : 2000, with «watchDogAPITimeout» : 10000,

ps: it would be easier if you were reporting errors on discord, this way I could ask you to post debug file

No joy. Same result. I disabled the RVII in Windows device manager and everything (QM) is fine. There must be some conflict with the AMD drivers? Is there a known working version of the driver compatible with QM?

try to increase API timeout, in nhqm.conf replace «watchDogAPITimeout» : 2000, with «watchDogAPITimeout» : 10000,

ps: it would be easier if you were reporting errors on discord, this way I could ask you to post debug file

Here’s the log output:

Starting up logging on 2022-03-15 16:35:21:732
File SeverityLevel is: TRACE (0)
[2022-03-15 16:35:21:747] [DEBUG] [watchdog] HTTP API GET failed: Unable to connect to the remote server
[2022-03-15 16:35:21:747] [ERROR] [watchdog] Failed to establish communication channel with Excavator!
[2022-03-15 16:35:21:747] [INFO] [main] Started logging, version: 0.5.3.5
[2022-03-15 16:35:21:747] [DEBUG] [watchdog] Finishing
[2022-03-15 16:35:22:772] [INFO] [watchdog] Shutting down excavator.exe
[2022-03-15 16:35:22:772] [WARNING] [watchdog] Excavator PID 5504
[2022-03-15 16:35:22:772] [TRACE] [watchdog] HTTP API GET: /quit
[2022-03-15 16:35:23:257] [TRACE] [nhmws] Getting status data
[2022-03-15 16:35:24:276] [WARNING] [main] Failed to acquire lock in proper time
[2022-03-15 16:35:24:276] [DEBUG] [nhmws] Sending status data
[2022-03-15 16:35:24:276] [TRACE] [nhmws] Sending: <«method»:»miner.status»,»params»:[«ERROR»,[]]>
[2022-03-15 16:35:24:276] [TRACE] [nhmws] Sent result: True
[2022-03-15 16:35:26:799] [DEBUG] [watchdog] HTTP API GET failed: Unable to connect to the remote server
[2022-03-15 16:35:26:799] [INFO] [watchdog] Standard method failed, trying mucher harder kill..
[2022-03-15 16:35:26:799] [ERROR] [watchdog] Failed to shut down excavator.exe, reboot may-be required, reason: Process with an Id of 5504 is not running.
[2022-03-15 16:35:26:799] [DEBUG] [watchdog] Ending thread
[2022-03-15 16:35:26:799] [TRACE] [watchdog] Created watchdog instance
[2022-03-15 16:35:26:799] [DEBUG] [watchdog] Starting thread
[2022-03-15 16:35:26:799] [DEBUG] [watchdog] Setting target: STOPPED
[2022-03-15 16:35:26:799] [INFO] [watchdog] New target: STOPPED
[2022-03-15 16:35:26:799] [INFO] [watchdog] Starting excavator.exe with cmdline: -c commands.json -qx -qm -d 2 -f 0 -wi localhost -wp 18000 -wa 18C5DFE874F8368512472A5A
[2022-03-15 16:35:26:799] [DEBUG] [watchdog] Setting new subscribe data: 3G3titZwH5VcH2rpYttdsr5pL4xSAHdGXH$0-kHA7Vu9ETkqEJEgxSoHhyg, eu-north
[2022-03-15 16:35:26:965] [INFO] [main] Got order, start mining: True
[2022-03-15 16:35:27:331] [INFO] [watchdog] Started, pid=412
[2022-03-15 16:35:28:338] [INFO] [watchdog] Starting excavator.exe with cmdline: -c commands.json -qx -qm -d 2 -f 0 -wi localhost -wp 18000 -wa 18C5DFE874F8368512472A5A
[2022-03-15 16:35:28:853] [INFO] [watchdog] Started, pid=10176
[2022-03-15 16:35:29:239] [INFO] [main] Got order, start mining: True
[2022-03-15 16:35:29:239] [INFO] [main] Start mining
[2022-03-15 16:35:29:239] [DEBUG] [watchdog] Setting target: MINING
[2022-03-15 16:35:29:239] [INFO] [watchdog] New target: MINING
[2022-03-15 16:35:29:854] [INFO] [watchdog] Starting excavator.exe with cmdline: -c commands.json -qx -qm -d 2 -f 0 -wi localhost -wp 18000 -wa 18C5DFE874F8368512472A5A
[2022-03-15 16:35:30:373] [INFO] [watchdog] Started, pid=14000
[2022-03-15 16:35:31:382] [INFO] [watchdog] Starting excavator.exe with cmdline: -c commands.json -qx -qm -d 2 -f 0 -wi localhost -wp 18000 -wa 18C5DFE874F8368512472A5A
[2022-03-15 16:35:31:909] [INFO] [watchdog] Started, pid=8396
[2022-03-15 16:35:32:938] [INFO] [watchdog] Starting excavator.exe with cmdline: -c commands.json -qx -qm -d 2 -f 0 -wi localhost -wp 18000 -wa 18C5DFE874F8368512472A5A
[2022-03-15 16:35:33:454] [INFO] [watchdog] Started, pid=5248
[2022-03-15 16:35:34:454] [INFO] [watchdog] Starting excavator.exe with cmdline: -c commands.json -qx -qm -d 2 -f 0 -wi localhost -wp 18000 -wa 18C5DFE874F8368512472A5A
[2022-03-15 16:35:34:974] [INFO] [watchdog] Started, pid=13896
[2022-03-15 16:35:35:982] [INFO] [watchdog] Starting excavator.exe with cmdline: -c commands.json -qx -qm -d 2 -f 0 -wi localhost -wp 18000 -wa 18C5DFE874F8368512472A5A
[2022-03-15 16:35:36:510] [INFO] [watchdog] Started, pid=9716
[2022-03-15 16:35:37:514] [INFO] [watchdog] Starting excavator.exe with cmdline: -c commands.json -qx -qm -d 2 -f 0 -wi localhost -wp 18000 -wa 18C5DFE874F8368512472A5A
[2022-03-15 16:35:38:037] [INFO] [watchdog] Started, pid=13184
[2022-03-15 16:35:39:049] [INFO] [watchdog] Starting excavator.exe with cmdline: -c commands.json -qx -qm -d 2 -f 0 -wi localhost -wp 18000 -wa 18C5DFE874F8368512472A5A
[2022-03-15 16:35:39:566] [INFO] [watchdog] Started, pid=8840
[2022-03-15 16:35:41:575] [DEBUG] [watchdog] Getting memory info (is enough?) and CPUs
[2022-03-15 16:35:41:575] [TRACE] [watchdog] HTTP API GET: /devices
[2022-03-15 16:35:45:614] [DEBUG] [watchdog] HTTP API GET failed: Unable to connect to the remote server
[2022-03-15 16:35:45:614] [ERROR] [watchdog] Failed to establish communication channel with Excavator!
[2022-03-15 16:35:46:616] [INFO] [watchdog] Starting excavator.exe with cmdline: -c commands.json -qx -qm -d 2 -f 0 -wi localhost -wp 18000 -wa 18C5DFE874F8368512472A5A
[2022-03-15 16:35:47:146] [INFO] [watchdog] Started, pid=13744
[2022-03-15 16:35:48:156] [INFO] [watchdog] Starting excavator.exe with cmdline: -c commands.json -qx -qm -d 2 -f 0 -wi localhost -wp 18000 -wa 18C5DFE874F8368512472A5A
[2022-03-15 16:35:48:684] [INFO] [watchdog] Started, pid=13412
[2022-03-15 16:35:49:688] [INFO] [watchdog] Starting excavator.exe with cmdline: -c commands.json -qx -qm -d 2 -f 0 -wi localhost -wp 18000 -wa 18C5DFE874F8368512472A5A
[2022-03-15 16:35:50:211] [INFO] [watchdog] Started, pid=9692
[2022-03-15 16:35:51:217] [INFO] [watchdog] Starting excavator.exe with cmdline: -c commands.json -qx -qm -d 2 -f 0 -wi localhost -wp 18000 -wa 18C5DFE874F8368512472A5A
[2022-03-15 16:35:51:730] [INFO] [watchdog] Started, pid=2888
[2022-03-15 16:35:52:744] [INFO] [watchdog] Starting excavator.exe with cmdline: -c commands.json -qx -qm -d 2 -f 0 -wi localhost -wp 18000 -wa 18C5DFE874F8368512472A5A
[2022-03-15 16:35:53:266] [INFO] [watchdog] Started, pid=8128
[2022-03-15 16:35:53:302] [TRACE] [nhmws] Getting status data
[2022-03-15 16:35:53:302] [TRACE] [main] Getting devices
[2022-03-15 16:35:53:302] [TRACE] [watchdog] HTTP API GET: /info
[2022-03-15 16:35:54:281] [INFO] [watchdog] Starting excavator.exe with cmdline: -c commands.json -qx -qm -d 2 -f 0 -wi localhost -wp 18000 -wa 18C5DFE874F8368512472A5A
[2022-03-15 16:35:54:798] [INFO] [watchdog] Started, pid=1352
[2022-03-15 16:35:55:805] [INFO] [watchdog] Starting excavator.exe with cmdline: -c commands.json -qx -qm -d 2 -f 0 -wi localhost -wp 18000 -wa 18C5DFE874F8368512472A5A
[2022-03-15 16:35:56:327] [INFO] [watchdog] Started, pid=13600
[2022-03-15 16:35:57:331] [INFO] [watchdog] Starting excavator.exe with cmdline: -c commands.json -qx -qm -d 2 -f 0 -wi localhost -wp 18000 -wa 18C5DFE874F8368512472A5A
[2022-03-15 16:35:57:378] [DEBUG] [watchdog] Getting devices parse err: Unable to connect to the remote server
[2022-03-15 16:35:57:378] [DEBUG] [nhmws] Sending status data
[2022-03-15 16:35:57:378] [TRACE] [nhmws] Sending: <«method»:»miner.status»,»params»:[«ERROR»,[]]>
[2022-03-15 16:35:57:378] [TRACE] [nhmws] Sent result: True
[2022-03-15 16:35:57:394] [TRACE] [Program] Graceful shutdown handled
[2022-03-15 16:35:57:844] [INFO] [watchdog] Started, pid=12128
[2022-03-15 16:35:58:855] [INFO] [watchdog] Starting excavator.exe with cmdline: -c commands.json -qx -qm -d 2 -f 0 -wi localhost -wp 18000 -wa 18C5DFE874F8368512472A5A
[2022-03-15 16:35:59:382] [INFO] [watchdog] Started, pid=3596
[2022-03-15 16:35:59:915] [TRACE] [Program] Graceful shutdown handled
[2022-03-15 16:35:59:915] [DEBUG] [nhmws] Stopping
[2022-03-15 16:36:00:005] [DEBUG] [nhmws] OnClose, reason:
[2022-03-15 16:36:00:005] [DEBUG] [nhmws] Stopped
[2022-03-15 16:36:00:005] [DEBUG] [watchdog] Finishing
[2022-03-15 16:36:00:394] [INFO] [watchdog] Shutting down excavator.exe
[2022-03-15 16:36:00:394] [WARNING] [watchdog] Excavator PID 3596
[2022-03-15 16:36:00:394] [TRACE] [watchdog] HTTP API GET: /quit
[2022-03-15 16:36:04:446] [DEBUG] [watchdog] HTTP API GET failed: Unable to connect to the remote server
[2022-03-15 16:36:04:446] [INFO] [watchdog] Standard method failed, trying mucher harder kill..
[2022-03-15 16:36:04:446] [ERROR] [watchdog] Failed to shut down excavator.exe, reboot may-be required, reason: Process with an Id of 3596 is not running.
[2022-03-15 16:36:04:446] [DEBUG] [watchdog] Ending thread
[2022-03-15 16:36:04:477] [DEBUG] [updater] Quit thread
[2022-03-15 16:36:04:494] [INFO] [Program] Shutting down
[2022-03-15 16:36:04:494] [TRACE] [Program] Graceful shutdown handled

From what I see here: HTTP API GET failed: Unable to connect to the remote server.
May-be try to change port number in nhqm.conf instead of 18000 uses something else.

Or it could be that excavator exit right after start. Can you post excavator log ?

From what I see here: HTTP API GET failed: Unable to connect to the remote server. May-be try to change port number in nhqm.conf instead of 18000 uses something else.

Or it could be that excavator exit right after start. Can you post excavator log ?

I’ll post the log when I get a chance. In the meantime, I would like to reiterate that everything is FINE under default settings when using ONLY the RTX3090. The problem only occurs when trying to use BOTH the 3090 and Radeon VII at the same time.

I have the same issue with GeForce + Radeon.

Updated to 0.5.3.6RC. Radeon VII isn’t detected.

Did you ever find a solution for this issue?
Same problemsince a week here,used to work ok for a few months with the same config (RTX3070 + RX5600XT,then out of the blue I started getting error 105 and same error «HTTP API GET failed: Unable to connect to the remote server».
If the rx5600xt is disabled then quickminer works ok.

Hello, can someone having this issue (if you still have it) post the log files from both Quick Miner AND excavator (I need both log files to understand the problem. (I already asked it, but didn’t get an answer)

Here are some logs issue happens just after around 18:40

Just noticed in excavator «terminal» window I can see this error just before it stops:
#804
«OpenCL error ‘Invalid buffer size’ in func ‘opencl_daggerhashimoto::run’ line 309»

I just DDU’ed and reinstalled drivers (rig has RTX3070 and RX5600XT)
Thanks

this is a weird message. how much vram does have the 5600XT ? (or free ram). Is there a monitor connected to it ?
Something to look at, may-be if there are enough virtual memory allocated.

In this case, the error 105 is legit, is the sense that excavator crashed (so there is no communication with quickminer)

it’s 6gb vram card, and yes there is a monitor connected. It was connected on the RTX3070, I tried on the RX5600XT but same error as usual.

currently the dag requires 5Gb, may-be it is too big for this card (?) I’ll will check

by the way, was the card working in a previous version ? (or with older driver ?)

Both cards were ok before with the same drivers, there was no quickminer update, it just stopped from one day to the other, same thing happened to a couple of people on Reddit, everytime it is on mixed AMD Nvidia rigs with rx5600xt.

may-be try to do a reset to factory of the driver (then reboot. but a ddu should have done that on its own)

No response. Closing.

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Error 105 [BUG] #806

Describe the bug
After upgrading from previous RC I05 error and constantly restarting even with a fresh unconfigured setup, and on my other PC on the same network works fine with the same version of the miner

To Reproduce
Just run NiceHashQuickMiner.exe

Version affected (please complete the following information):
v0.5.4.0 RC

NVIDIA driver version
512.59 DCH

Hardware
3070 LHR V2 directly plugged into to motherboard PCI 4 16x sloth

Logs
nhqm log
[2022-05-07 12:17:43:229] [INFO] [optimizeprofiles] Data updated with iteration=1
[2022-05-07 12:17:43:229] [INFO] [optimizeprofiles] Data received, quitting fetch thread
[2022-05-07 12:17:43:229] [DEBUG] [optimizeprofiles] Quit thread
[2022-05-07 12:17:43:318] [INFO] [updater] Latest version: 0.5.4.0_RC
[2022-05-07 12:17:43:319] [INFO] [updater] Already running latest version
[2022-05-07 12:17:43:671] [INFO] [watchdog] Started, pid=45500
[2022-05-07 12:17:44:163] [DEBUG] [nhmws] Logging in
[2022-05-07 12:17:44:163] [TRACE] [nhmws] Sending: <«method»:»login»,»version»:[«NHQM_v0.5.4.0″,»Excavator_v1.7.7.0_Build_1020″],»protocol»:4,»btc»:»REDACTED«,»worker»:»Desktop»,»rig»:»0-036FST8jmE6VF95yPL5hnQ»,»group»:»»>
[2022-05-07 12:17:44:165] [TRACE] [nhmws] Sent result: True
[2022-05-07 12:17:44:201] [TRACE] [nhmws] Received: <«method»:»markets»,»data»:[«USA»,»USA_E»,»EU_N»,»EU»]>
[2022-05-07 12:17:44:203] [INFO] [nhmws] Enabling location: AUTO
[2022-05-07 12:17:45:145] [DEBUG] [watchdog] Setting new subscribe data: REDACTED$0-036FST8jmE6VF95yPL5hnQ, auto
[2022-05-07 12:17:48:701] [DEBUG] [watchdog] Getting memory info (is enough?) and CPUs
[2022-05-07 12:17:48:701] [TRACE] [watchdog] HTTP API GET: /devices
[2022-05-07 12:17:52:738] [DEBUG] [watchdog] HTTP API GET failed: Unable to connect to the remote server
[2022-05-07 12:17:52:738] [ERROR] [watchdog] Failed to establish communication channel with Excavator!
[2022-05-07 12:17:53:109] [TRACE] [nhmws] Getting status data
[2022-05-07 12:17:53:109] [TRACE] [main] Getting devices
[2022-05-07 12:17:53:112] [TRACE] [watchdog] HTTP API GET: /info
[2022-05-07 12:17:53:761] [INFO] [watchdog] Starting excavator.exe with cmdline: -c commands.json -qx -qm -d 2 -f 0 -wi localhost -wp 18000 -wa FFF2EAC4F22B9255B6A839BF
[2022-05-07 12:17:54:301] [INFO] [watchdog] Started, pid=15236
[2022-05-07 12:17:57:164] [DEBUG] [watchdog] Getting devices parse err: The operation has timed out
[2022-05-07 12:17:57:164] [DEBUG] [nhmws] Sending status data
[2022-05-07 12:17:57:164] [TRACE] [nhmws] Sending: <«method»:»miner.status»,»params»:[«ERROR»,[]]>
[2022-05-07 12:17:57:164] [TRACE] [nhmws] Sent result: True
[2022-05-07 12:17:59:335] [DEBUG] [watchdog] Getting memory info (is enough?) and CPUs
[2022-05-07 12:17:59:335] [TRACE] [watchdog] HTTP API GET: /devices
[2022-05-07 12:17:59:990] [WARNING] [config] save_config_file button2_Click
[2022-05-07 12:17:59:990] [WARNING] [config] _internal_save_config_file save_config_file
[2022-05-07 12:18:03:403] [DEBUG] [watchdog] HTTP API GET failed: Unable to connect to the remote server
[2022-05-07 12:18:03:403] [ERROR] [watchdog] Failed to establish communication channel with Excavator!
[2022-05-07 12:18:04:428] [INFO] [watchdog] Starting excavator.exe with cmdline: -c commands.json -qx -qm -d 2 -f 0 -wi localhost -wp 18000 -wa FFF2EAC4F22B9255B6A839BF
[2022-05-07 12:18:04:968] [INFO] [watchdog] Started, pid=2496
[2022-05-07 12:18:10:012] [DEBUG] [watchdog] Getting memory info (is enough?) and CPUs
[2022-05-07 12:18:10:012] [TRACE] [watchdog] HTTP API GET: /devices
[2022-05-07 12:18:13:807] [INFO] [exportlogs] Exporting logs

event log
[[2022-05-07 12:18:05.441412] [thread=0x00002cdc] [info]] Log started, build v1020

[[2022-05-07 12:18:05.509791] [thread=0x00002cdc] [debug]] Core created

[[2022-05-07 12:18:05.509791] [thread=0x00002cdc] [debug]] Algos set

[[2022-05-07 12:18:07.516014] [thread=0x00002cdc] [info]] core | CUDA memory allocation: std

[[2022-05-07 12:18:07.523735] [thread=0x00002cdc] [trace]] device #0 | Power limits; min=100.00 max=270.00 def=240.00

[[2022-05-07 12:18:07.526738] [thread=0x00002cdc] [trace]] device #0 | Default memory clock: 6801

[[2022-05-07 12:18:07.527739] [thread=0x00002cdc] [warning]] LHR | Device #0 | Intensity: 55%. Unlock ratio: 100%

[[2022-05-07 12:18:07.527739] [thread=0x00002cdc] [info]] core | Found Supported CUDA device #0: GeForce RTX 3070 id: 0

[[2022-05-07 12:18:07.527739] [thread=0x00002cdc] [info]] http | Listening on [::1]:18000

[[2022-05-07 12:18:07.528740] [thread=0x00002cdc] [debug]] Adding command with 20 seconds execution delay:

[[2022-05-07 12:18:07.528740] [thread=0x00002cdc] [debug]] Adding command with 30 seconds execution delay and 30 seconds loop time:

[[2022-05-07 12:18:07.528740] [thread=0x00002cdc] [debug]] Adding command with 1 seconds execution delay and 4 seconds loop time:

[[2022-05-07 12:18:07.528740] [thread=0x00002cdc] [info]] core | Initialized!

[[2022-05-07 12:18:08.529520] [thread=0x0000b404] [trace]] Executing:

[[2022-05-07 12:18:08.529520] [thread=0x0000b404] [trace]] core | Command method: devices.smartfan.exec

[[2022-05-07 12:18:08.529520] [thread=0x0000b404] [trace]] Response:

The text was updated successfully, but these errors were encountered:

Источник

Источник

  • #1

Здравствуйте,такая проблема квик майнер постоянно то включается,то выключается,выскакивает ошибка 105,что делать?

  • #2

1. Погуглить quickminer error 105
2. Если не поможет, использовать другой майнер
Можно сразу приступить к пункту 2

  • #3

другой майнер

1. Погуглить quickminer error 105
2. Если не поможет, использовать другой майнер
Можно сразу приступить к пункту 2

другой всмысле из квика?

  • #4

Другой, в смысле совсем другой)))

  • #5

у меня 3070 ти с алычаром,а на квике стоит обход,с другими майнерами я не знаком и не знаю как хакнуть алычар((

  • #6

я не знаком и не знаю как хакнуть алычар((

троль очередной

  • #8

реально помощь хотел найти

Источник

Recommend Projects

  • React photo

    React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo

    Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo

    Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo

    TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo

    Django

    The Web framework for perfectionists with deadlines.

  • Laravel photo

    Laravel

    A PHP framework for web artisans

  • D3 photo

    D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Visualization

    Some thing interesting about visualization, use data art

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo

    Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo

    Microsoft

    Open source projects and samples from Microsoft.

  • Google photo

    Google

    Google ❤️ Open Source for everyone.

  • Alibaba photo

    Alibaba

    Alibaba Open Source for everyone

  • D3 photo

    D3

    Data-Driven Documents codes.

  • Tencent photo

    Tencent

    China tencent open source team.

Источник

WebI get error 105 REPEATEDLY. Neither 0.5.3.3 nor 0.5.3.5RC solve the issues. Please follow these steps: 1. Open App & browser control and then Reputation-based protection. 2. …
From jpjbw.lifestyle-gewinne.de
See details »

WebAlso, note that quickminer only works with NVIDIA for now. 1 AntiqueTech • 2 yr. ago Nvapi is a reporting api. Not necessary for the miner to do its job. Error is ok. 1 o94kiwi • 2 yr. …
From reddit.com
See details »

ERROR 105 WITH RADEON VII MIXED WITH NVIDIA (3090) #774

WebQuickminer goes insane when trying to use the Radeon VII in the same machine as a RTX 3090. I get error 105 REPEATEDLY. Neither 0.5.3.3 nor 0.5.3.5RC solve the issues …
From github.com
See details »

NOT ABLE TO MINE ON QUICKMINER AFTER UPDATE : R/NICEHASH …

WebIt throws out that it cannot establish a connection for the excavator (Error code 105)? I tried to turn off all antivirus programs and till now nothing worked… 1 3 3 Comments Best Add …
From reddit.com
See details »

QUICKMINER V0.6.0.0 RC — MULTI-ALGORITHM SUPPORT!

WebSep 9, 2022 Install the latest QuickMiner version by downloading the QuickMiner installer and selecting the Release candidate version or use the portable version . Download …
From nicehash.com
See details »

QUICKMINER ERROR : R/NICEHASH — REDDIT

WebIm using the automatic optimization «Efficient», and I have seen that when new dag is generate, it gives me an error: Failed to set core uvolt, reason: -12. When this happens, …
From reddit.com
See details »

QBO SAYS «BANK ERROR 105» BUT THAT’S WRONG — QB COMMUNITY

WebNov 19, 2021 To update your account information, follow these simple steps: Go to the Banking menu or Transactions menu. Go to the Banking tab. Select the tile for the bank …
From quickbooks.intuit.com
See details »

FAILED TO ESTABLISH CONNECTION TO EXCAVATOR.EXE : R/NICEHASH — REDDIT

WebNiceHash QuickMiner error #105 Failed to establish connection to excavator.exe It keeps opening and closing and cannot start mining. 5 5 5 comments Best Add a Comment …
From reddit.com
See details »

[BUG] CUDA ERROR ‘UNKNOWN ERROR’ IN FUNC ‘CUDA_DAGGERHASHIMOTO …

WebApr 15, 2021 I have a rig with four 3060 ti. It works fine for a month, but since a few days, one of the GPU is crashing excavator (I tried 0.4.5.5 and v0.4.7.1 RC) after 2-3 minutes. …
From github.com
See details »

«NICEHASH QUICKMINER ERROR #105 #351 — GITHUB

WebNew issue «Nicehash quickminer error #105 #351 Closed Usaqmuri opened this issue on Apr 6, 2021 · 1 comment commented on Apr 6, 2021 question Usaqmuri changed the …
From github.com
See details »

CUDA ERROR WHILE USING THE NEW FUNCTION «OPTMIZER» #97 — GITHUB

WebFeb 23, 2021 Then, I’ve restarted completely the QuickMiner closing everything and opening again. After some minutes mining with the Medium profile set, in the Share#16 …
From github.com
See details »

WHAT TO DO IF WINDOWS DEFENDER IS BLOCKING NICEHASH …

WebMar 13, 2021 1. Open App & browser control and then Reputation-based protection. 2. Under Potentially unwanted app blocking make sure you have selected Block apps and …
From nicehash.com
See details »

QUICKMINER TROUBLESHOOT CHECKLIST | NICEHASH

WebIf you have any issues with QuickMiner, please make sure that: there is no antivirus software or firewalls on your PC and on the router that can affect QuickMiner’s normal …
From nicehash.com
See details »

HOW TO FIX NICEHASH QUICKMINER ERROR #105 OR HOW TO …

WebI’m stomped. Hope someone can help. I have other rigs this works fine on. but this one seems to give me trouble on quickminer. Nicehash quickminer error #105 ( seems …
From reddit.com
See details »

SUPPORT | NICEHASH

WebGeneral Help NiceHash service Account Security KYC Wallet Organizations. Mining Help General help Earnings and payments NiceHash miner NiceHash rig manager NiceHash …
From nicehash.com
See details »

TROUBLESHOOTING — NICEHASH/NICEHASHQUICKMINER GITHUB WIKI

WebApr 17, 2021 Yes, you can. Open Task Scheduler (write Task Scheduler in your search bar). Then follow markings from 1 to 4 from the picture below. Once you choose your …
From github-wiki-see.page
See details »

POWER CONSUMPTION BACK TO FACTORY DEFAULT #105 — GITHUB

WebFeb 24, 2021 Power consumption back to factory default #105 Closed richardcool opened this issue on Feb 24, 2021 · 7 comments richardcool commented on Feb 24, 2021 …
From github.com
See details »

NICEHASH QUICKMINER ERROR 105 : R/NICEHASH — REDDIT

WebI’m getting error #105 every time I start NHQM. «Nicehash QuickMiner error #105. Failed to establish connection to excavator.exe. Please consult Nicehash QuickMiner …
From reddit.com
See details »

Related Search

Источник
COINBASE PRO | DIGITAL ASSET EXCHANGE

US-based crypto exchange. Trade Bitcoin (BTC), Ethereum (ETH), and more for USD, EUR, and GBP. Support for FIX API and REST API. Easily deposit funds via Coinbase, bank transfer, wire transfer, or cryptocurrency wallet.
From pro.coinbase.com

HOW TO CORRECTLY UNINSTALL AND INSTALL GPU DRIVERS? | …
NICEHASH QUICKMINER ERROR INSTALLING» KEYWORD FOUND …

Does nicehash quickminer work with amd. Install nicehash quickminer. Is nicehash quickminer a virus
From keyword-suggest-tool.com

SUDDEN ERROR WITH QUICKMINER : NICEHASH

No changes on my end but now I’m getting shares rejecyed shares above target and then after a minute I’m getting a message algorithm daggerhashimoto currently not available. excavator then reboots but just repeats the latter message. anyone have an idea what’s going on considering I haven’t changed anything?/r/
From reddit.com

KEEP GETTING ERROR «FAILED TO GET POWER LIMITS» ON …

[QUESTION] NiceHash QuickMiner warning #104 — NiceHashQuickMiner hot 6. Failed to get power limits — NiceHashQuickMiner. OC Tune: Failed to set core uvolt, reason: -11 — NiceHashQuickMiner hot 4. OC Tune: Failed to set core uvolt, reason: -11 — NiceHashQuickMiner hot 3. could not obtain power consumption! — NiceHashQuickMiner hot 3. DLL nvml missing — …
From gitmemory.com

NICEHASH QUICKMINER | NICEHASH QUICKMINER | NICEHA

Description: NiceHash QuickMiner Features Autotune Automatically find the best core clock for your memory clock thus lowering your power consumption. OCtune No need for 3rd party tools! OCTune allows you to use alternative overclocking methods not available in …
From tiwebsite.com

BITCOIN REACHES NEW ATH OF 68.49K NOV 9 2021 — PAGE 48 …

We want to provide a safe and secure mining experience, and that is why we have created NiceHash QuickMiner (NHQM)! If you are using NVIDIA graphics cards, we recommend using NHQM; if you have AMD graphics cards, we recommend using lolminer plugin in NiceHash Miner. To learn more about NiceHash QuickMiner, click here. Stay safe! Your NiceHash team!
From ar15.com

SOFTWARE | NVIDIA — REDFLAGDEALS.COM

I’m using nicehash miner with the nbminer plugin. I tried quickminer (not nicehash) miner while theres was that nicehash/phoenix fiasco a few weeks ago. I think nicehash miner have better options/logs and control over quickminer. I use MSI afterburner set power -500 speed to +11000 power to 63 GPU temp is 50 fan is 50
From forums.redflagdeals.com

DEVICE #0 HW ERROR LOGGED ON QUICKMINER : NICEHASH

hey guys can you please help me with my nicehash quickminer issue. It is always saying Device #0 Hw Error Logged. I have only one 3070 …
From reddit.com

NICEHASH ACCEPTED SPEED [0VCD8H]

Current working solution Run NiceHash Miner without a miner active, start quickminer. No need to view tons of. or Basically a Freaking Good Miner. 57 ARRR Equihash $9. com Courses. Quickminer works fine without any optimization from nicehash, but it runs super hot so i’m a little bit concerned. Xrp is the real-time gross settlement network …
From sna.palermo.it

QUICKMINER ERROR : NICEHASH

140k members in the NiceHash community. NiceHash is the leading platform for mining and trading cryptocurrencies. Earn Bitcoin by connecting your PC …
From reddit.com

NICEHASH ERROR LOGS» KEYWORD FOUND WEBSITES LISTING …

Compare Search ( Please select at least 2 keywords ). Most Searched Keywords. Alaska airlines partner flights 1
From keyword-suggest-tool.com

MINERSTAT VS NICEHASH 2021 — COURTNEYSMITH.COM

mexican food essex market; 12vdc to 120vac inverter circuit diagram; funny comic characters; what is the main theme of the scarlet letter; dollar general carpet cleaner solution. minerstat vs nicehash 2021. in Courtney Smith Blog January 21, 2022 …
From courtneysmith.com

WHAT IS NICEHASH MINER? | NICEHASH

Repeatedly getting SOCKET ERROR — socket closed Will you lose your balance if you turn off or update NiceHash Miner or if you shut down or restart your PC? How to enable NBminer LHR unlock in NiceHash Miner? Verified 3rd party miners included in NiceHash Miner NiceHash Miner not picking the most profitable algorithm? Miner speed fluctuations detected notification …
From nicehash.com

QUICKMINER GAME MODE ERROR : NICEHASH

Press J to jump to the feed. Press question mark to learn the rest of the keyboard shortcuts
From reddit.com

HOW TO ENABLE NBMINER LHR UNLOCK IN NICEHASH MINER? | NICEHASH

Repeatedly getting SOCKET ERROR — socket closed Will you lose your balance if you turn off or update NiceHash Miner or if you shut down or restart your PC? How to enable NBminer LHR unlock in NiceHash Miner? Verified 3rd party miners included in NiceHash Miner NiceHash Miner not picking the most profitable algorithm? Miner speed fluctuations detected notification …
From nicehash.com

PYTHON — HOW TO FIX THIS STRANGE ERROR: «RUNTIMEERROR …

It might be for a number of reasons that I try to report in the following list: Modules parameters: check the number of dimensions for your modules.Linear layers that transform a big input tensor (e.g., size 1000) in another big output tensor (e.g., size 1000) will require a matrix whose size is (1000, 1000).
From stackoverflow.com

NICEHASH QUICKMINER ERROR 105 : NICEHASH

Please consult Nicehash QuickMiner troubleshooting guide.» Everything seems to be working correctly, except in OCTune, the Power Limit is showing as «-3» for all GPUs. «Power Real (W)» matches what I manually set «Power Lim (W)» to, so it seems the power limit is working, even though it says «-3».
From reddit.com

NICEHASH QUICKMINER ERROR 103 | QUICKMINER ERROR C

When running, NiceHash Miner is connected to NiceHash platform and NiceHash open hashing power marketplace. Buyers select the algorithm and the speed while users or miners running the NiceHash Miner software fulfil that order by mining (hashing) — providing computing power to the network and get paid in Bitcoins.
From tiwebsite.com

NICEHASH AMD, LONDON DELIVERIES 1-2 DAYS

Ethereum Berlin fork notification. guides & tutorials . 9 Apr 2021. NiceHash QuickMiner — Increase hashrate by 50% on. NiceHash Private Endpoint solution is designed for medium-sized and large mining farms that want to optimize their connection to NiceHash and secure maximum performance and earnings Hey, will there also be support for AMD cards and what’s the ETA …
From hagyjuk-hjalp-karten.com

HOW TO INSTALL NICEHASH OS? | NICEHASH

NiceHash is the leading cryptocurrency platform for mining and trading. Sell or buy computing power, trade most popular cryptocurrencies and support the digital ledger technology revolution.
From nicehash.com

2080 SUPER HASHRATE NICEHASH — ZAYLEE.LTD

king arthur baking bowl scraper Groceries & Gourmet Food eastern conference finals nhl Health & Household sad arranged marriage quotes Home & Kitchen mitsubishi garage near szeged Home Furniture does shang-chi spoil endgame Luggage & Travelling why is the alpha pack afraid of scott Pet Supplies
From zaylee.ltd

OVERVIEW FOR MARKONICEHASH — REDDIT

-food-Art-nosleep-DIY-EarthPorn-history-InternetIsBeautiful-GetMotivated — … What exact NiceHash software? QuickMiner? What GPUs are you using? What driver version are you using? permalink; save; context ; full comments (8) report; give award; RTX 3090 LOW HASHRATE, LOW TEMPS by Jxggly_ in NiceHash. MarkoNiceHash 0 points 1 point 2 points …
From reddit.com

REPEATEDLY GETTING SOCKET ERROR — SOCKET CLOSED | …

Repeatedly getting SOCKET ERROR — socket closed Will you lose your balance if you turn off or update NiceHash Miner or if you shut down or restart your PC? How to enable NBminer LHR unlock in NiceHash Miner? Verified 3rd party miners included in NiceHash Miner NiceHash Miner not picking the most profitable algorithm?
From nicehash.com

NICEHASH QUICKMINER TROUBLESHOOTING GUIDE» KEYWORD FOUND …

Nicehash quickminer service location. Reddit nicehash quickminer. Uninstall nicehash quickminer. Install nicehash quickminer. Compare Search ( Please select at least 2 keywords ) Most Searched Keywords. G shock dw9052 review 1 . Dyson hepa filter air purifier 2 . Levi strauss work with us 3 . When did the prohibition start and end 4 . Gourmet breakfast diners in …
From keyword-suggest-tool.com

NICEHASH QUICKMINER NVIDIA DRIVER» KEYWORD FOUND WEBSITES …

Nicehash quickminer nvidia driver keyword after analyzing the system lists the list of keywords related and the list of websites with related content, in addition you can see which keywords most interested customers on the this website
From keyword-suggest-tool.com

QUICKMINER GIT | GITHUB — NICEHASH/NICEHASHQUICKMINER …

If you are skeptical towards other closed source miners, or if your PC contains sensitive information, wallet keys and so on, using Excavator (or NiceHash QuickMiner) is prefered way as you do not have to worry anything to be stolen from …
From websiteperu.com

NICEHASH QUICKMINER + AMD GPU? — CRYPTO MINING ON MAC’S: …

NiceHash QuickMiner + AMD GPU? Post by macminergod » Wed Aug 25, 2021 12:10 pm Although NiceHash advertises their «QuickMiner» as the recommended miner for Nvidia cards, they don’t explicitly say it won’t work with AMD GPU ‘s.
From cryptominingonmacs.com

HOW TO FIX NICEHASH QUICKMINER ERROR #105 OR HOW TO …

I also tried to install 5.2.2 it doesn’t work I have now installed 5.1.3 you can download it as a zip file but before installing 5.1.3 all other versions of nicehash were uninstalled my system has been stable again for 2 days now
From reddit.com

«NICEHASH QUICKMINER ERROR #105 · ISSUE #351 · NICEHASH …

Make sure there is no AV interfering with any part of QuickMiner. It seems like excavator.exe was deleted by AV.
From github.com

CUDA ERROR NICEHASH QUICK MINER. NICEHASH ERROR 105

Read about triangle theta here NiceHash QuickMiner: Optimize your GPU with one click!. GPU: EVGA 2080ti OC Black 12gb (11G-P4-2281) running driver version 9 (GeForce 465.89) non-DCH/UWD drivers. Version Affected: v, v. RC. Current working solution Run NiceHash Miner without a miner active, start quickminer. Switch between the two until share …
From news.diomaine.org

MINING 101: HOW TO USE NICEHASH TO EARN BITCOIN — FORBES

Grab a beverage and let’s do this. Step 1: Register an account at NiceHash. Whether you have AMD or Nvidia hardware, it’s a good idea …
From forbes.com

NICEHASH COM QUICKMINER. NICEHASH QUICKMINER SAFE

Nicehash com quickminer NiceHash QuickMiner NiceHash. Education 5 days ago When running, NiceHash Miner is connected to NiceHash platform and NiceHash open hashing power marketplace. Buyers select the algorithm and the speed while users or miners running the NiceHash Miner software fulfil that order by mining (hashing) — providing computing power to …
From bit-24.uno

Источник

Понравилась статья? Поделить с друзьями:
  • No battery recharge 1e iveco stralis ошибка
  • Nic ru ошибка 500
  • No backupset selected to be restored как исправить
  • Nibbl ru ошибка код 80072efe
  • No audio devices are installed как исправить