Latest posts of: zimpixa

Show Posts
Pages: [1]

Alternate cryptocurrencies / Mining (Altcoins) / Re: [CMD] FarmWatchBot Ewbf, Claymore, Bminer, Dstm, CC, Eth, CastXMR, Phoenix

on: August 02, 2018, 02:07:56 PM

EWBF bug report
If those messages are detected in log watchbot crashes

Code:

20.07.2018 08:19:21 CUDA: Device: 0 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
02.08.2018 15:33:25 CUDA: Device: 1 Thread exited with message: "an illegal memory access was encountered"

Error written in watchbot log

Code:

[2018-08-02][15:36:27] CUDA-capable

It happens on every detected line that contains "

Code:

>> %~n0.log ECHO [%Date%][%Time:~-11,8%] reports:%reports% 3:%~3 Chat:%chatid%
prints
reports:0 3:02.08.2018 15:33:25 CUDA: Device: 1 Thread exited with message: "an Chat:0

When I added REM to lines 796 and 797 watchbot works fine
I've tried to edit those lines, to just write to log simple message, but it also didn't work

Also I see this version is still missing current server and queue number

Alternate cryptocurrencies / Mining (Altcoins) / Re: [CMD] FarmWatchBot Ewbf, Claymore, Bminer, Dstm, CC, Eth, CastXMR, Phoenix

on: July 19, 2018, 08:55:32 AM

What I found already concerning ewbf 0.4 Message output was changed, there is timestamp in front of every message To override false positive last share timeout I've changed 659 line to Code: FOR /F "tokens=3 delims=: " %%A IN ('findstr.exe /R /C:".INFO. share .*" %log%') DO SET lastsharemin=1%%A To properly find error messages Ive changed every entry of %lasterror% to !lasterror! So far it seems working Every line number was checked on version 2.0

Alternate cryptocurrencies / Mining (Altcoins) / Re: EWBF's Cuda Equihash Miner 0.4

on: July 18, 2018, 12:15:20 PM

Hello, since version 0.4 I'm having problems with stability.

Code:

18.07.2018 09:57:52 Temp: GPU0 54C GPU1 55C 
18.07.2018 09:57:52 GPU0: 48 Sol/s GPU1: 27 Sol/s 
18.07.2018 09:57:52 Total speed: 75 Sol/s
18.07.2018 09:57:57 CUDA: Device: 1 Thread exited with message: "an illegal memory access was encountered"
18.07.2018 09:57:57 CUDA: Device: 0 Thread exited with message: "an illegal memory access was encountered"
18.07.2018 09:57:57 WARNING: Looks like GPU0 are stopped. Restarting...
18.07.2018 09:57:57 INFO: GPU0 are restarted.
18.07.2018 09:57:58 WARNING: Looks like GPU1 are stopped. Restarting...
18.07.2018 09:57:58 INFO: GPU1 are restarted.
18.07.2018 09:57:58 CUDA: Device: 0 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
18.07.2018 09:57:58 CUDA: Device: 1 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
18.07.2018 09:57:59 WARNING: Looks like GPU0 are stopped. Restarting...

After this message autorestarting loops until manual restart.

I'm using same OC settings as with v0.3 which were rock solid (up to 16 days of continous mining)

ATM I lowered OC a bit and testing if problem still occurs.

Alternate cryptocurrencies / Mining (Altcoins) / Re: [CMD] FarmWatchBot (Watchdog) for Ewbf, Claymore, Dstm, CC, B, Eth miners

on: May 24, 2018, 09:40:00 AM

Bug report

Code:

[2018-05-23][21:13:28] Miner was started. Script v.2.0.0.
[2018-05-23][22:06:58]  Received new job 1c                          
[2018-05-23][22:06:58] Miner restarting, please wait... Miner ran for *00:54:02*.
[2018-05-23][22:07:05] Process bminer.exe was successfully killed.
[2018-05-23][22:07:35] miner.log moved to Logs folder as miner_5.23_22.7.log
[2018-05-23][22:07:38] Miner was started. Script v.2.0.0.
[2018-05-23][22:29:58]  Received new job 2c                          
[2018-05-23][22:29:58] Miner restarting, please wait... Miner ran for *00:22:52*.
[2018-05-23][22:30:05] Process bminer.exe was successfully killed.
[2018-05-23][22:30:35] miner.log moved to Logs folder as miner_5.23_22.30.log
[2018-05-23][22:30:38] Miner was started. Script v.2.0.0.
[2018-05-23][22:31:23]  Received new job 2c                          
[2018-05-23][22:31:23] Miner restarting, please wait... Miner ran for *00:01:17*.
[2018-05-23][22:31:30] Process bminer.exe was successfully killed.
[2018-05-23][22:32:00] miner.log moved to Logs folder as miner_5.23_22.31.log
[2018-05-23][22:32:03] Miner was started. Script v.2.0.0.
[2018-05-23][22:36:18]  Received new job 2c                          
[2018-05-23][22:36:18] Too many errors. Threshold of 5 runtime errors reached. A restart of the computer to clear GPU cache is required. Restarting... Miner ran for *00:04:47*.
[2018-05-23][22:36:21] Computer restarting...
[2018-05-23][22:38:10] Config_Bmnr.ini loaded.
[2018-05-23][22:38:40] miner.log moved to Logs folder as miner_5.23_22.38.log
[2018-05-23][22:38:43] Miner was started. Script v.2.0.0.
[2018-05-23][22:59:48]  Received new job 3c                          
[2018-05-23][22:59:48] Miner restarting, please wait... Miner ran for *00:21:33*.
[2018-05-23][22:59:56] Process bminer.exe was successfully killed.

Script badly recognised new job ending with C as error

Alternate cryptocurrencies / Mining (Altcoins) / Re: [CMD] Equihash Miner Autorun (Autorestart / Watchdog) for Ewbf & Claymore & Dstm

on: November 10, 2017, 04:31:02 PM

Why whenever I'm trying to delete lines in ECHO script stops working. I just wanted to keep summary window as simple as possible, but deleting lines like "IF %MidnightAutoRestart% LEQ 0 ECHO Autorestart at 00:00: Disabled" or "ECHO ZEC: t1S8HRoMoyhBhwXq6zY5vHwqhd9MHSiHWKv ECHO BTC: 1wdJBYkVromPoiYk82JfSGSSVVyFJnenB" makes script unusable (it auto quit in a milisecond after starting).

Alternate cryptocurrencies / Mining (Altcoins) / Re: [CMD] Equihash Miner Autorun (Autorestart / Watchdog) for Ewbf & Claymore & Dstm

on: November 02, 2017, 02:57:06 PM

Quote from: zorvalth on November 02, 2017, 08:15:20 AM Is there an option to skip Clean log confirmation? U can, edit CHOICE /C:yn /T:30 /D:n /M "Clean Logs folder now" to CHOICE /C:yn /T:0 /D:n /M "Clean Logs folder now" /T is timeout of confirmation, where 0 automaticly takes default setting, which is /D Would it be possible to add 'run bat file' at miner startup or add ability to OC via Nvidia Inspector? Sometimes when GPU crashes, clocks are restored to default. I'm setting my OC via InvidiaInspector. It's super easy to set GPU profiles via batch files. Example bat file Quote set gpu0coreclock=175 set gpu1coreclock=210 set gpu0memclock=870 rem g1:230/590 g0:175/870 575 set gpu1memclock=565 set targetpower0=104 set targetpower1=114 :CLOCKS (start "" "C:\Users\Zimpixa\Desktop\nvidia insp\nvidiaInspector.exe" -setBaseClockOffset:0,0,%gpu0coreclock% -setMemoryClockOffset:0,0,%gpu0memclock% -setPowerTarget:0,%targetpower0% -setfanspeed:0,%gpu0fan% -setBaseClockOffset:1,0,%gpu1coreclock% -setMemoryClockOffset:1,0,%gpu1memclock% -setPowerTarget:1,%targetpower1% -setfanspeed:1,%gpu1fan%) I can't use 'start additional program' feature, because script is checking, if program actually runs, while batch just executes and exits.

Pages: [1]