Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 243. (Read 6590565 times)

my Claymore's is stuck and my pool is nanopool, what the problem ? any one help? im not the only one who have this problem. thanks!

https://ibb.co/eVNsO8

This is a weird request, did you actually look at the timestamp in the claymore log?
Or even look at the log?
Here is an example.

11:09:18:605   218c   
11:09:18:605   218c   ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
11:09:18:605   218c   º                Claymore's Dual GPU Miner - v11.7               º
11:09:18:620   218c   º              ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK             º
11:09:18:620   218c   ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
11:09:18:620   218c   
11:09:18:620   218c   b581
11:09:18:839   218c   ETH: 10 pools are specified
11:09:18:839   218c   Main Ethereum pool is eth-eu.maxhash.org:11011
11:09:20:668   218c   OpenCL platform: AMD Accelerated Parallel Processing
11:09:20:683   218c   OpenCL initializing...

11:09:20:683   218c   AMD Cards available: 8

As you see, Claymore took an ENTIRE TWO SECONDS to tell me how many GPU are present.
I defy you to better that by running some pointless info-only batchfile, read the output, e.g. all gpu present and accounted for, then run the actual start batch file. (in under 2 seconds).

Why don't you investigate why your rig is so unstable, that it needs stop, start, fail, reboot, before mining, THAT is indeed wasted time, it also indicates far more serious underlying issues with your rig, issues likely to cause stoppages, crashes, and forcing you to reboot, THAT is time worth saving, but is not solved, assisted or aided by this request imho.

Send some info on your rig, os, versions, hardware, check your system event logs, follow best practise guidelines, (no updates unless there is specific mention of a "something" you need, a problem YOU HAVE, that is specified solved etc), disable all services not relevant to mining, remove all scheduled tasks, lean-rig philosophy etc.

Ignore everyone who gives advice such as "update your driver" without actually specifying WHAT version they mean you to use, (moronic in the extreme!)

Read the claymore readme, especially the last sections.

If all else fails, divide and conquer, (remove half your GPUs/risers,cables, power cables, headers, and run the rig, if it exhibits the same issues of instability, remove that half of the hardware, and add back the other half. If that is stable, you can narrow down by adding back, half the other half removed hardware, (1/4 etc), keep dividing order/half, and eventually you will find the cause. Systematic, quantifiable testing and analysis.
Working by halves exponentially increases the odds you'll find the cause, (faster than one by one etc), and it also covers situations like too much load on psu for example.

Work with all clocks and powers at the factory settings, until you're confident it's stable.
THEN start the OC, and hard-core stuff.

Remember, if you're overclocking, you're pushing it. Some hardware is more tolerant than others, equally, you're possibly shortening the MTBF, so don't assume stability is a permanent situation, given time, there will be degradation, THAT is an absolute certainty.  

Good luck.

Feature request

In Phoenix miner, I can do
Phoenixminer.exe -list to get a list of GPUs and exit, NO MINING at all.
So I wrote a script to auto check if all GPUs boot up after windows start. If gpus are missing then reboot before start mining.
Can Claymore add something similar to list all gpus and exit w/o mining?

What's the difference: time to shutdown
When no mining operation is runing, shutdown /r /f /t 1 can take place right away.
When mining operation starts, even force kill the process can take a few seconds to minute to complete before reboot.

Since all the reboots are just fix errors and do not earn coins, the shorter the better.

Thanks

try to update also your driver

like this 376.33 Version for Nvidias

Yup, I lowered it to 600 and will see how it goes. Next step will be to switch back to 11.5 and maybe roll back the video card drivers as well. Not sure what to do after that.


I have 4GB of system memory. The virtual memory is set to 50,000. I used to have it at 16,000 and after all the updates, I started getting a cuda 11 error when starting the miner. Raised it to 50,000 and that error was resolved.

Three Options:

Monero
Zcash

or just use Nicehash

 

You need to increase the memory or change the OS.

me too #188

Claymore 11.7
Nvidia 376.33 Driver
3Gb 1060

CUDA error 11 - cannot write buffer for DAG.
SAD Life

GPU 1: too high epoch number for 3GB card in Windows 10, consider using Windows 7 or Linux to reduce memory that is allocated internally by OS. Miner will try to extend available memory now...
Setting DAG epoch #188 for GPU1
GPU 2: too high epoch number for 3GB card in Windows 10, consider using Windows 7 or Linux to reduce memory that is allocated internally by OS. Miner will try to extend available memory now...

Looks like only libcurl3 is installed

Thanks for info
I know it is my end problem, my ISP is blocking some ports and protocols.
Switched to dwarfpool and problem solved.

How much ram do you have exactly?

By ram I am talking about the system memory not the video card memory.

You might have to up your ram or up your virtual memory.

I got a similiar error such as this but it was on the XMR miner however the errors look identical.

hello, i want to take output like first blue text but always taking output dark green. What is identify this? i have both amd and nvidia cards and i take this output only 1 rig.. I like it. How can i change?

https://ibb.co/jxx0ao
https://ibb.co/jxx0ao

lower memory clock try 600, 580,560 etc

Does anyone have any idea what could be causing this error? I've been dual mining XVG and ETH since 11.0 came out with 6 1070Ti's at +100/+650 OC. The rig ran for weeks at a time without any issues. A week ago I updated Windows to 1803 and the miner to 11.7, switched to mining ETH only and started getting this error after 70-80 hours of mining. Current OC settings are -200/+650. No rejected or incorrect shares. I've mined ETH only before at these OC settings and didn't have any issues.

The price attracts the talk 

Thanks for the data, good to know!

Have you all had any official security code reviews or application pen-tests in order to have more confidence that these types of trivial issues won't be found again?

from a shell:

dpkg -l libcurl4
dpkg -l libcurl3

The one that is installed will list the version.  The one that is not will simply say "" for version.

Well I'm very new to ubuntu, but I'm moving to it permanently now.
Honestly I'm not sure what I did to get it working eventually, a heck of a lot googling and installing packages.