Topic: [ETH] Claymore Miner Crashes on Startup (Read 490 times)

miracle!
with phoenix miner everyting is ok!

don't you see in my log it is already 12.0 ((((

here is what i discovered:
gpu-z says no opencl is found??? thats why claymore crashas before gpu is found
https://imgur.com/a/XVQvszC
https://i.imgur.com/UkSzFzZ.png

You have to update your miner to the latest 12.0 version. There is too big DAG size at the moment and older versions don't work.

Hi guys I have the same problem.
Claymore crashes after

17:58:50:765   5f0   Check and remove old log files...
17:58:50:765   5f0   args: -epool eth-eu1.nanopool.org:9999 -ewal 0xdcf7**********/20-570/********@gmail.com -epsw x -etht 1000 -mode 1 -ftime 1 -gser 2 -r 1
17:58:50:766   5f0   
17:58:50:767   5f0   г================================================================¬
17:58:50:767   5f0   ¦                Claymore's Dual GPU Miner - v12.0               ¦
17:58:50:768   5f0   ¦              ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK             ¦
17:58:50:769   5f0   L================================================================-
17:58:50:769   5f0   
17:58:50:770   5f0   b615
17:58:50:972   5f0   ETH: 1 pool is specified
17:58:50:973   5f0   Main Ethereum pool is eth-eu1.nanopool.org:9999

I have 4 same rigs with Saphire Nitro+ 570
The problem is only on one of them
Some say it is because of windows update but it is the same on all 4 rigs

Hey guys, I just had a similar problem with my mining rig. I managed to fix it by disabling the integrated graphics in Device Manager in Windows. I was playing around with uninstalling/reinstalling drivers (with DDU) and I suspect that Claymore must trip up on this somehow.

Hope this helps!

Honestly I am in doubt about this, I never heard of a defective card especially on 6 items on a brand new from the box not unless its mishandled by users otherwise its a used one, care to share what are the test have done aside from mining? its already installed successfully by your OS and I highly doubt if sapphire would accept it as a default product defect due to mining issue.

You can try re-downloading Claymore from different source. Don’t forget to turn off your windows defender or any kind of antivirus. It should work fine.

6 defective GPUs, what are the odds for this happening. You got incredibly lucky or was extremely unlucky . Nice that your problem got solved though.

Hey everyone, thanks for your help and advice. Unfortunately it turns out that I was sent 6 defective GPUs by Sapphire, which I will be returning. I have no idea how this happened, but I thank you all for your support in this matter
 

I don't think it's claymore, but rather my GPU. I noticed that the GPU isn't computing OpenCLL like it should be when I opened up GPU-Z (how I missed it before idfk). I'm reinstalling drivers to try to fix that. If it brings back that functionality I'll try Claymore and if that doesn't work I'll follow your suggestion.

To rule out a problem with Claymore, try a different mining program and see if it recognizes the cards.  When dealing with computer troubles, you often have to figure out what it's not to figure out what it is!

Try to switch the GPU

I switched the risers and nothing has changed. I'm really unsure what is going wrong here.

Only 1 card rn. I have 6 total. I'll try to switch the riser and see if that helps, but everything is still detected properly on device manager so idk if that is the problem.

For reference, here is the beginning of one of my log files:

09:02:57:362   e60   args: -epool stratum+tcp://daggerhashimoto.usa.nicehash.com:3353 -ewal xxxxxxx.worker1 -epsw x -esm 3 -allpools 1 -estale 0 -dcri 6 -mport 0 -dpool stratum+tcp://decred.usa.nicehash.com:3354 -dwal xxxxxxxxxxx.worker1
09:02:57:362   e60   
09:02:57:362   e60   ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
09:02:57:362   e60   º                Claymore's Dual GPU Miner - v11.5               º
09:02:57:362   e60   º              ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK             º
09:02:57:362   e60   ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
09:02:57:362   e60   
09:02:57:362   e60   b541
09:02:57:581   e60   ETH: 1 pool is specified
09:02:57:581   e60   Main Ethereum pool is daggerhashimoto.usa.nicehash.com:3353
09:02:57:581   e60   DCR: 1 pool is specified
09:02:57:581   e60   Main Decred pool is decred.usa.nicehash.com:3354
09:02:57:863   e60   OpenCL platform: AMD Accelerated Parallel Processing
09:02:57:863   e60   OpenCL initializing...

09:02:57:863   e60   AMD Cards available: 2
09:02:57:863   e60   GPU #0: Ellesmere (AMD Radeon (TM) RX 570), 4096 MB available, 32 compute units (pci bus 9:0:0)
09:02:57:863   e60   GPU #0 recognized as Radeon RX 470/570
09:02:57:863   e60   GPU #1: Ellesmere (AMD Radeon (TM) RX 570), 4096 MB available, 32 compute units (pci bus 10:0:0)
09:02:57:863   e60   GPU #1 recognized as Radeon RX 470/570
09:02:57:863   e60   POOL/SOLO version
09:02:57:863   e60   Platform: Windows
09:02:57:910   e60   start building OpenCL program for GPU 0...
09:02:58:300   e60   done

Yeah I thought a bit of the same. However when I go into Device Manager I can see the card is just fine and It says that it is working nominally. Do you have any idea of how I can allow claymore to detect the cards?

Just comparing your log file to some of mine, your machine is craping out right before OpenCL initializes... just a thought.  Almost like Claymore is not seeing your cards.

How many cards in the rig?

Start your rig with only one GPU installed. If everything works, shut down your rig and add another one. Maybe one of the cards/ risers is just acting up.

So, what else possible? have you check Risers? Or may try to plug your card directly to PCIe 16x without Risers?

Or maybe you still run your cmd.exe (Command Prompt) in quick edit mode. Just check it, open your Command Prompt then right-click, properties and make sure uncheck quick edit mode.

Sapphire Nitro+ Radeon RX580