Bitcoin Forum
July 12, 2024, 09:40:45 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: [HELP] Claymore crashes on startup.  (Read 146 times)
SulliJM1 (OP)
Newbie
*
Offline Offline

Activity: 10
Merit: 0


View Profile
August 14, 2018, 06:09:54 AM
 #1

I'll get right into it.

--run.bat file:
set GPU_FORCE_64BIT_PTR 0
set GPU_MAX_HEAP_SIZE 100
set GPU_USE_SYNC_OBJECTS 1
set GPU_MAX_ALLOC_PERCENT 100
set GPU_SINGLE_ALLOC_PERCENT 100

EthDcrMiner64.exe

--config file:
-eworker [worker name]
-epool eth-asia1.nanopool.org:9999
-epsw x
-ewal [wallet address]
-mode 1
-gser 5
-di 6789ab (set to run my Nvidia cards only)

(Information in [] withheld for privacy purposes)

--log file:
22:56:14:033   1fdc   Check and remove old log files...
22:56:14:111   1fdc   args: -eworker [worker name] -epool eth-asia1.nanopool.org:9999 -epsw x -ewal [wallet address] -mode 1 -gser 5 -di 6789ab
22:56:14:111   1fdc   
22:56:14:111   1fdc   ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
22:56:14:126   1fdc   º                Claymore's Dual GPU Miner - v11.9               º
22:56:14:126   1fdc   º              ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK             º
22:56:14:126   1fdc   ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
22:56:14:126   1fdc   
22:56:14:142   1fdc   b597
22:56:14:376   1fdc   ETH: 1 pool is specified
22:56:14:376   1fdc   Main Ethereum pool is eth-asia1.nanopool.org:9999

(Information in [] withheld for privacy purposes)

--Tried the following:
-Restart (duh)
-Disable/re-enable cards
-Driver is good; cards respond to commands from OC tools.
-Cards are good: been mining with them for over a year now.
-Disabled quick-edit mode in cmd defaults
-Ensured program good by Windows Defender and Windows Firewall
-Ensured integrated GFX disabled
-Removing the di command
-Removing gser command

--Additional info:
-Cards: 6x GTX 1070, 1x RX 580, 5x VEGA 64's. AMD and Nvidia seem to run better in independent cmd windows.
-i5
-Dual Corsair 1200i PSU's, fed by separate household circuits.
-16GB RAM, 32000MB Virtual Memory
-Fault comes after a rig rebuild and a CMOS fault and following reset. Have not checked any BIOS settings since. That being said, rig ran fine off of stock settings when I first started mining.
-Any troubleshooting tips are appreciated. Google didn't find anything.

----------EDIT----------
Started program manually via CMD. Got the following:

C:\Program Files\Claymore\Claymore Nvidia>set GPU_FORCE_64BIT_PTR 0
GPU_FORCE_64BIT_PTR=0

C:\Program Files\Claymore\Claymore Nvidia>set GPU_MAX_HEAP_SIZE 100
GPU_MAX_HEAP_SIZE=100

C:\Program Files\Claymore\Claymore Nvidia>set GPU_USE_SYNC_OBJECTS 1
GPU_USE_SYNC_OBJECTS=1

C:\Program Files\Claymore\Claymore Nvidia>set GPU_MAX_ALLOC_PERCENT 100
GPU_MAX_ALLOC_PERCENT=100

C:\Program Files\Claymore\Claymore Nvidia>set GPU_SINGLE_ALLOC_PERCENT 100
GPU_SINGLE_ALLOC_PERCENT=100

C:\Program Files\Claymore\Claymore Nvidia>EthDcrMiner64.exe

╔════════════════════════════════════════════════════════════════╗
║                Claymore's Dual GPU Miner - v11.9               ║
║              ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK             ║
╚════════════════════════════════════════════════════════════════╝

ETH: 1 pool is specified
Main Ethereum pool is eth-asia1.nanopool.org:9999

C:\Program Files\Claymore\Claymore Nvidia>
edwardceng
Member
**
Offline Offline

Activity: 266
Merit: 50


View Profile
August 14, 2018, 06:28:15 AM
 #2

--Tried the following:
-Restart (duh)
-Disable/re-enable cards
-Driver is good; cards respond to commands from OC tools.
-Cards are good: been mining with them for over a year now.
-Disabled quick-edit mode in cmd defaults
-Ensured program good by Windows Defender and Windows Firewall
-Ensured integrated GFX disabled
-Removing the di command
-Removing gser command
have tried replacing the USB Riser?

have tried mining only one brand that is the same, indeed mixed of the brand on one Rig is a little tricky.

or you can check official thread claymore

SulliJM1 (OP)
Newbie
*
Offline Offline

Activity: 10
Merit: 0


View Profile
August 14, 2018, 06:31:12 AM
 #3

--Tried the following:
-Restart (duh)
-Disable/re-enable cards
-Driver is good; cards respond to commands from OC tools.
-Cards are good: been mining with them for over a year now.
-Disabled quick-edit mode in cmd defaults
-Ensured program good by Windows Defender and Windows Firewall
-Ensured integrated GFX disabled
-Removing the di command
-Removing gser command
have tried replacing the USB Riser?

have tried mining only one brand that is the same, indeed mixed of the brand on one Rig is a little tricky.

or you can check official thread claymore

Yessir I have, all risers verified golden.
leonix007
Sr. Member
****
Offline Offline

Activity: 1008
Merit: 297


Grow with community


View Profile
August 14, 2018, 06:34:54 AM
 #4

Create .bat file and name it to anything

then edit it containing this parameters

set GPU_FORCE_64BIT_PTR 0
set GPU_MAX_HEAP_SIZE 100
set GPU_USE_SYNC_OBJECTS 1
set GPU_MAX_ALLOC_PERCENT 100
set GPU_SINGLE_ALLOC_PERCENT 100

EthDcrMiner64.exe -epool eth-asia1.nanopool.org:9999 -ewal ETHWALLET.Worker -epsw x -mode 1 -gser 5 -di 6789ab


save then run bat file
edwardceng
Member
**
Offline Offline

Activity: 266
Merit: 50


View Profile
August 14, 2018, 06:43:07 AM
Last edit: August 14, 2018, 08:07:02 AM by edwardceng
 #5

yes, try for what @leonix says and for additional can try Pixel clock Patcher and use / replace dummy output. I hope you have patience in dealing with problems with the mining rig Grin

Edit
I will monitor it, I hope the problem is resolved quickly and adds to my insight about the Rig problem

SulliJM1 (OP)
Newbie
*
Offline Offline

Activity: 10
Merit: 0


View Profile
August 14, 2018, 06:55:12 AM
Last edit: August 14, 2018, 07:06:05 AM by SulliJM1
 #6

@leonix007:

Tried that, no change in fault, besides cmd will actually run for about 3 seconds longer than before. Still aborts on its own w/ no warning, fault codes, or alerts from Windows Defender/Firewall.

@edwardceng

Never heard of that before, I'll try it out and get back to you on that. Might take me a moment though. As far as patience... I've worked on cars my whole life. If it weren't for that, I'd have given up and sold off my mining equipment forever ago!
----EDIT----
Looked it up and all, but that's currently un-related. As of right now, I'm just trying to get the Nvidia cards to run. If the AMD cards give me hell later, I'll try it out.
leonix007
Sr. Member
****
Offline Offline

Activity: 1008
Merit: 297


Grow with community


View Profile
August 14, 2018, 07:09:39 AM
 #7

@leonix007:

Tried that, no change in fault, besides cmd will actually run for about 3 seconds longer than before. Still aborts on its own w/ no warning, fault codes, or alerts from Windows Defender/Firewall.

@edwardceng

Never heard of that before, I'll try it out and get back to you on that. Might take me a moment though. As far as patience... I've worked on cars my whole life. If it weren't for that, I'd have given up and sold off my mining equipment forever ago!

EDIT: I would suggest, to unplugged all other GPU's and install only 1 NVIDIA using pci-e x16 only

Uninstall drivers using DDU

then install latest drivers

this is for troubleshooting purpose and if does work

install all other GPU's

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!