Never thought I would be posting here because I thought I've ran into every issue ever while mining for the past year. This is the first time this has stumped me. Please note that this miner has been running with no issues for over 8 months on the given drivers/claymore until this point.
Claymore miner (10.0 and 9.
will open, identify the pool, and then immediately closes. Typically this triggers me to reinstall video driver and all works well. So I used driver sweeper and removed the Nvidia and AMD driver, and freshly installed the same drivers I have been using since day one. Windows defender is completely not enabled. -mode 1 and pause are being used in my coding. ALL GPUS are detected and running according to windows devices. Claymore will still not spit out an error in the log so I am kinda lost here....
Does anyone have any suggestions for next steps? Below is an screen shot of windows devices, claymore error log, and drivers used (keep in mind these are the drivers I've always used).
https://ibb.co/ebhvXyhere is miner log text:
08:17:38:613 2348 args: -epool us1.ethermine.org:4444 -ewal 0xAF69c954a7Cddc9D3BDD4dDF04FDC4870c851825 -epsw x -mode 1 -ftime 10
08:17:38:613 2348
08:17:38:613 2348 ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
08:17:38:613 2348 º Claymore's Dual ETH + DCR/SC/LBC/PASC GPU Miner v9.8 º
08:17:38:613 2348 ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
08:17:38:613 2348
08:17:38:816 2348 ETH: 2 pools are specified
08:17:38:816 2348 Main Ethereum pool is us1.ethermine.org:4444
I just started experiencing this issue yesterday. I shut off all my miners due to a huge thunderstorm crossing my area, and when I turned them all back on, the ones I have with AMD GPUs continued working as normal, but the ones with Nvidia cards exhibited the issue above.
I tried reinstalling drivers, applying all windows 10 updates, re-downloading Claymore, checking for the Exception from the Windows virus thing, and so far no luck whatsoever.
How can that be? They were working fine for weeks and a simple shut-down (not forced), on 2 similar rigs (not exact same MoBo and GPUs), have the same issue.
UPDATE:I fixed my issue by booting into the BIOS and forcing the default GPU to be the iGPU, switched my monitor to the iGPU connectors and bingo.