Ninjastic
Search content
Sort by
Showing 20 of 22 results by ibizastyler
Post
Topic
Board Announcements (Altcoins)
Topic OP
[ANN] Bitcointalk Wallet
by
ibizastyler
on 04/03/2023, 21:47:16 UTC



_______________________________________________________________________________ ______________________


Hello Dear forum users

Our forum has existed for over 10 years. During this time we have done a lot of work, united a lot of people and created an incredible place for communication with thousands of sections and topics.
 Our team would like to thank you very much for staying with us. Together we launched our own Bitcointalk Wallet based on Electrum.

What will it be used for?
The coin will not be mined. You can get it only by participating in special contests, giveaways, creating posts and replying to messages.
Creating a theme -  20 coins
Message - 10 coins

In mid february we will announce the stock exchange on which our coin will be traded. You will be able to exchange it for real money .

How to begin to use a purse?

When generating address EVERY user will get 200 coins.
Send 1 coin to BTLKa5ukEyutshrdMd7m2UHVhShmcSEnwq
In the comment MUST specify your nickname on the forum

An example

https://i.ibb.co/MpV9v6T/Screenshot-3.png

It is necessary to do in order to link your profile on the forum with your purse address. After that you will be automatically credited coins for each action on the forum.


You can download a wallet from the link below


Post
Topic
Board Mining (Altcoins)
Re: PhoenixMiner 2.9e: fastest Ethereum/Ethash miner with lowest devfee (Windows)
by
ibizastyler
on 22/04/2018, 12:18:02 UTC
Quote
Quote from: ibizastyler on April 18, 2018, 08:53:46 PM
Hi Guys,

can someone of you please assist?
My rig doesn't run stable at all.

sys:
win 10 pro
8x GTX 1070 from msi, evga and palit
2x PSU - 1000W and 850W
page file is set to min. 17000MB and max to 57000MB.

Thanks a lot in advance!!

thats my command line:

Code:
:restart
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100

PhoenixMiner.exe -nvidia -rmode 1 -wdog 1 -pool eth-eu1.nanopool.org:9999 -pool2 eth-eu2.nanopool.org:9999 -wal wallet.worker/email -pass x -ftime 10
goto :restart

--- Error message:

Code:
2018.04.18:22:35:18.778: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xfb36ccc","0x833075af975ab8559540aabf67696685bcb2ef98724ba75a312e1b545c049307"]}

2018.04.18:22:35:18.815: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0xaadf04a2431360f4228b2d28ab2fec416f0f508c514f75a095dc22e41a5aa0d3","0x5683748fa7f53897f1e1a80a8a321d3693761838135be37d1d132c0cd3d7d937","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2018.04.18:22:35:19.387: main Eth speed: 263.421 MH/s, shares: 17/0/0, time: 0:06
2018.04.18:22:35:19.387: main GPUs: 1: 32.685 MH/s (3) 2: 32.685 MH/s (3) 3: 32.677 MH/s (2) 4: 32.686 MH/s (1) 5: 32.684 MH/s (0) 6: 32.676 MH/s (3) 7: 34.652 MH/s (1) 8: 32.677 MH/s (4)
2018.04.18:22:35:24.466: main Eth speed: 263.422 MH/s, shares: 17/0/0, time: 0:06
2018.04.18:22:35:24.466: main GPUs: 1: 32.685 MH/s (3) 2: 32.687 MH/s (3) 3: 32.676 MH/s (2) 4: 32.686 MH/s (1) 5: 32.685 MH/s (0) 6: 32.676 MH/s (3) 7: 34.651 MH/s (1) 8: 32.677 MH/s (4)
2018.04.18:22:35:25.426: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0x169cf1c7d1e89f771cc626178603a4c89647bdd91bf2c762b63cce1cf1e0eca4","0x5683748fa7f53897f1e1a80a8a321d3693761838135be37d1d132c0cd3d7d937","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2018.04.18:22:35:25.426: eths Eth: New job #169cf1c7 from eth-eu1.nanopool.org:9999; diff: 10000MH
2018.04.18:22:35:26.163: GPU3 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.18:22:35:26.173: GPU3 GPU3 search error: unspecified launch failure
2018.04.18:22:35:26.185: GPU1 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.18:22:35:26.185: GPU1 GPU1 search error: unspecified launch failure
2018.04.18:22:35:26.200: GPU7 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.18:22:35:26.200: GPU7 GPU7 search error: unspecified launch failure
2018.04.18:22:35:26.201: GPU5 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.18:22:35:26.201: GPU5 GPU5 search error: unspecified launch failure
2018.04.18:22:35:26.216: GPU4 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.18:22:35:26.216: GPU4 GPU4 search error: unspecified launch failure
2018.04.18:22:35:26.216: GPU6 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.18:22:35:26.216: GPU6 GPU6 search error: unspecified launch failure
2018.04.18:22:35:26.232: GPU8 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.18:22:35:26.232: GPU8 GPU8 search error: unspecified launch failure
2018.04.18:22:35:26.263: GPU2 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.18:22:35:26.263: GPU2 GPU2 search error: unspecified launch failure
2018.04.18:22:35:26.404: wdog Thread(s) not responding. Restarting.
2018.04.18:22:35:28.779: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}
   First, if the first GPU to fail is (almost) always the same, lower its memory overclock (your hasrates are pretty high for 1070). Also, the restart loop your .bat file is not a good idea when using anything else than -rmode 0 because if PhoenixMiner.exe restarts by itself, your .bat file will start another instance of the miner and you will have two instances of PhoenixMiner trying to mine using the same GPUs, which obviously will lead to problems. So, either remove goto :restart or use -rmode 0 in your .bat file.

Yesterday I changed all of my riser cards, usb cables, etc. and I increased the fan speed for all cards and lowered the mem clock to 700 as well. The rig is now running stable for about 19 hours. 1900 shares and ZERO stales!!! very nice!!! good job!! Smiley
thanks for your help!!!!!

...but I have another 2 questions:

1st: what is the correct command line for the reboot.bat and the command line for the miner, if I choose the -rmode 2 option?
- The first function should be, when not enough shares can be found, the miner should restart
- if the miner crashes "normal", the miner should restart
- if the crash happens again, the miner should restart the rig
-- is this possible?!

--- miner: "PhoenixMiner.exe -nvNew 1 -stales 1 -rmode 2 -wdog 1 -pool etc-eu1.nanopool.org:19999 -pool2 etc-eu2.nanopool.org:19999 -wal wallet.worker/email -pass x -ftime 10"
--- reboot.bat: "shutdown /r /t 1 /f"?

2nd: is it possible to show some kind of hardware monitor for nvidia cards? especially the watts of each gpu within the miner. I really really would love to have this function!! --- or is it the -qswin (i.e. 15) option?
Post
Topic
Board Mining (Altcoins)
Re: Rig doesn't work anymore - Cuda program
by
ibizastyler
on 22/04/2018, 09:57:46 UTC
Update:

I cannot believe it!! My rig is still online since my last post and I did nothing else... look at the Screenshot!

https://ibb.co/m20JUH

Absolutely awesome!! 0 stales!!!
The slower card is the gtx 1080 and the first one is always a bit slower when I am connected via Teamviewer or remote desktop.

Hopefully one last question:
Is it possible to run another miner in parallel? I would like to mine with the 1080 another coin, like zcash, komodo or btg.
I tried it with ewbf and only the last card, but it didn't start.
As far as I know, dual mining is still not possible with Phoenix... Or am I wrong?
Post
Topic
Board Mining (Altcoins)
Re: Rig doesn't work anymore - Cuda program
by
ibizastyler
on 21/04/2018, 20:43:11 UTC
Thanks for your reply!

The strange thing is that it runs now for almost 3,5 hours absolutely stable?!
I will let him hash as long as it works and after the next crash (hopefully not, but if) I will do another try and error...

I will let you know if I find a solution. Thanks again!!
Post
Topic
Board Mining (Altcoins)
Re: Rig doesn't work anymore - Cuda program
by
ibizastyler
on 21/04/2018, 17:05:36 UTC
Thanks for your help guys!!

So here is my update:
- I have changed all of my risers (16x and 1x cards) and the usb cables.
- I removed the drivers with DDU
- I installed the latest nvidia drivers
- I installed one by one. I did also a restart after each graphics card

...and now the 9 gpus are running stable for about an hour and then I get the same error as before, just ~ 60 min. later...

I'm still oc-ing with MSI AB --> thx for the hint, jmigdlc99!
I always try to get a 1500 mhz core clock.

my oc settings:
evga cards:
pt: 70 --> before the reinstallation: 67
cclock: 0  --> before the reinstallation: most of the time between -20 -100
memclock: 700  --> before the reinstallation: between 760 and 800

msi 1070 cards:
pt: 52 --> before the reinstallation: 50
cclock: 0  --> before the reinstallation: most of the time between -80 -100
memclock: 700  --> before the reinstallation: between 760 and 800

palit card:
pt: 65 --> before the reinstallation: 63
cclock: 0  --> before the reinstallation: most of the time between -20 -100
memclock: 700  --> before the reinstallation: between 760 and 850

msi 1080 card:
pt: 50 --> before the reinstallation: 42
cclock: 0  --> before the reinstallation: most of the time between -20 -100
memclock: 700  --> before the reinstallation: between 800 and 880

could it be my "1 to 4 pci-e riser"? unfortunately I cannot change him, because I have only one...

.... now it is crashed again... after about 60 min. as I already mentioned above Sad
Same error message... Threads not responding, etc...

edit:
I just saw that the core clock of the 1st GPU is jumping around..?!

Is there anything else I can do?
Post
Topic
Board Mining (Altcoins)
Re: Rig doesn't work anymore - Cuda program
by
ibizastyler
on 19/04/2018, 18:49:38 UTC
Thanks guys for your help!!

complete sys info:
os: win10 pro
mb: Gigabyte h110-d3a (6 pci-e slots)
cpu: pentium g4400
ram: 8GB hyper fury X 2333
ssd: wd green 120 gb
psu 1: 1000w corisar dark power pro 11 platinum +
psu 2: 850w project 7 platinum +
a normal add2psu adapter
kolink riser
3x evga gtx 1070 sc
4x msi gtx 1070 gaming x 8g
1 palit gtx 1070 gamerock premium editon
pci-e 1 to 4 riser
page file is set to min. 17000MB and max to 57000MB
second last nvidia drivers

everything was working more or less well as long I was using phoenix miner 7c.
the rig was always stable for ~ 3 days. (eth, etc, sometimes zcash mining)

from time to time I was getting the error message "out of memory". that's why I increased the page file size.

Quote
Test first only 1 GPU, this can be a malfunction from riser

I already changed all of them

Quote
What happened before your rig stopped running stable?

unfortunately nothing... :/ it just stopped working...
at the moment I was switching back to etc mining. Same error message and phoenix miner still crashes but if I click ok, it is still mining? at the moment the miner is working for the last 30 min and is also finding shares (luckily no stales)

Quote
Test the cards one by one in the big pciex 16 slot and test them each for more than one hour. After that if no error appears from each of the gpu you have to check the risers,getting 009s version helps a lot in many cases if you haven't that already.

I have bought a lot of these 009s risers, but unfortunately not a single one of them is working (16x riser) - the usb cables and the 1x risers are working fine
--

next steps:
- I will remove the graphics card driver with the DDU tool
- after that I will do a new clean installation with the latest driver and only one gpu --> with or without a riser?!

If I will get them all running as it should be, is it possible to add another card on this rig? I have another gtx 1080 and still a fre usb slot at the "1 to 4 pci-e" riser card.

Why I am asking:
I was reading that the msi after burner doesn't work with 9 gpus...? is this the truth? The next thing is that the IGPU is still active.
Can you guys please recommend a tool which is able to get 9 gpus oc'ed?

thanks a lot in advance again!!
Post
Topic
Board Mining (Altcoins)
Rig doesn't work anymore - Cuda program
by
ibizastyler
on 19/04/2018, 07:09:35 UTC
Hi Guys,

can someone please assist?
My rig doesn't run stable at all. It works for about 10-60 min and then the following error message pops up.

sys:
win 10 pro
8x GTX 1070 from msi, evga and palit
2x PSU - 1000W and 850W
page file is set to min. 17000MB and max to 57000MB.

If you need more information, please let me know.
Thanks a lot in advance!!

thats my command line:

:restart
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100

PhoenixMiner.exe -nvidia -rmode 1 -wdog 1 -pool eth-eu1.nanopool.org:9999 -pool2 eth-eu2.nanopool.org:9999 -wal wallet.worker/email -pass x -ftime 10
goto :restart

--- Error message:

2018.04.18:22:35:18.778: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xfb36ccc","0x833075af975ab8559540aabf67696685bcb2ef98724ba75a312e1b545c049307"]}

2018.04.18:22:35:18.815: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0xaadf04a2431360f4228b2d28ab2fec416f0f508c514f75a095dc22e41a5aa0d3","0x5683748fa7f53897f1e1a80a8a321d3693761838135be37d1d132c0cd3d7d937","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2018.04.18:22:35:19.387: main Eth speed: 263.421 MH/s, shares: 17/0/0, time: 0:06
2018.04.18:22:35:19.387: main GPUs: 1: 32.685 MH/s (3) 2: 32.685 MH/s (3) 3: 32.677 MH/s (2) 4: 32.686 MH/s (1) 5: 32.684 MH/s (0) 6: 32.676 MH/s (3) 7: 34.652 MH/s (1) 8: 32.677 MH/s (4)
2018.04.18:22:35:24.466: main Eth speed: 263.422 MH/s, shares: 17/0/0, time: 0:06
2018.04.18:22:35:24.466: main GPUs: 1: 32.685 MH/s (3) 2: 32.687 MH/s (3) 3: 32.676 MH/s (2) 4: 32.686 MH/s (1) 5: 32.685 MH/s (0) 6: 32.676 MH/s (3) 7: 34.651 MH/s (1) 8: 32.677 MH/s (4)
2018.04.18:22:35:25.426: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0x169cf1c7d1e89f771cc626178603a4c89647bdd91bf2c762b63cce1cf1e0eca4","0x5683748fa7f53897f1e1a80a8a321d3693761838135be37d1d132c0cd3d7d937","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2018.04.18:22:35:25.426: eths Eth: New job #169cf1c7 from eth-eu1.nanopool.org:9999; diff: 10000MH
2018.04.18:22:35:26.163: GPU3 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.18:22:35:26.173: GPU3 GPU3 search error: unspecified launch failure
2018.04.18:22:35:26.185: GPU1 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.18:22:35:26.185: GPU1 GPU1 search error: unspecified launch failure
2018.04.18:22:35:26.200: GPU7 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.18:22:35:26.200: GPU7 GPU7 search error: unspecified launch failure
2018.04.18:22:35:26.201: GPU5 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.18:22:35:26.201: GPU5 GPU5 search error: unspecified launch failure
2018.04.18:22:35:26.216: GPU4 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.18:22:35:26.216: GPU4 GPU4 search error: unspecified launch failure
2018.04.18:22:35:26.216: GPU6 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.18:22:35:26.216: GPU6 GPU6 search error: unspecified launch failure
2018.04.18:22:35:26.232: GPU8 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.18:22:35:26.232: GPU8 GPU8 search error: unspecified launch failure
2018.04.18:22:35:26.263: GPU2 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.18:22:35:26.263: GPU2 GPU2 search error: unspecified launch failure
2018.04.18:22:35:26.404: wdog Thread(s) not responding. Restarting.
2018.04.18:22:35:28.779: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}
Post
Topic
Board Mining (Altcoins)
Re: PhoenixMiner 2.9e: fastest Ethereum/Ethash miner with lowest devfee (Windows)
by
ibizastyler
on 18/04/2018, 20:53:46 UTC
Hi Guys,

can someone of you please assist?
My rig doesn't run stable at all.

sys:
win 10 pro
8x GTX 1070 from msi, evga and palit
2x PSU - 1000W and 850W
page file is set to min. 17000MB and max to 57000MB.

Thanks a lot in advance!!

thats my command line:

:restart
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100

PhoenixMiner.exe -nvidia -rmode 1 -wdog 1 -pool eth-eu1.nanopool.org:9999 -pool2 eth-eu2.nanopool.org:9999 -wal wallet.worker/email -pass x -ftime 10
goto :restart

--- Error message:

2018.04.18:22:35:18.778: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xfb36ccc","0x833075af975ab8559540aabf67696685bcb2ef98724ba75a312e1b545c049307"]}

2018.04.18:22:35:18.815: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0xaadf04a2431360f4228b2d28ab2fec416f0f508c514f75a095dc22e41a5aa0d3","0x5683748fa7f53897f1e1a80a8a321d3693761838135be37d1d132c0cd3d7d937","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2018.04.18:22:35:19.387: main Eth speed: 263.421 MH/s, shares: 17/0/0, time: 0:06
2018.04.18:22:35:19.387: main GPUs: 1: 32.685 MH/s (3) 2: 32.685 MH/s (3) 3: 32.677 MH/s (2) 4: 32.686 MH/s (1) 5: 32.684 MH/s (0) 6: 32.676 MH/s (3) 7: 34.652 MH/s (1) 8: 32.677 MH/s (4)
2018.04.18:22:35:24.466: main Eth speed: 263.422 MH/s, shares: 17/0/0, time: 0:06
2018.04.18:22:35:24.466: main GPUs: 1: 32.685 MH/s (3) 2: 32.687 MH/s (3) 3: 32.676 MH/s (2) 4: 32.686 MH/s (1) 5: 32.685 MH/s (0) 6: 32.676 MH/s (3) 7: 34.651 MH/s (1) 8: 32.677 MH/s (4)
2018.04.18:22:35:25.426: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0x169cf1c7d1e89f771cc626178603a4c89647bdd91bf2c762b63cce1cf1e0eca4","0x5683748fa7f53897f1e1a80a8a321d3693761838135be37d1d132c0cd3d7d937","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2018.04.18:22:35:25.426: eths Eth: New job #169cf1c7 from eth-eu1.nanopool.org:9999; diff: 10000MH
2018.04.18:22:35:26.163: GPU3 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.18:22:35:26.173: GPU3 GPU3 search error: unspecified launch failure
2018.04.18:22:35:26.185: GPU1 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.18:22:35:26.185: GPU1 GPU1 search error: unspecified launch failure
2018.04.18:22:35:26.200: GPU7 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.18:22:35:26.200: GPU7 GPU7 search error: unspecified launch failure
2018.04.18:22:35:26.201: GPU5 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.18:22:35:26.201: GPU5 GPU5 search error: unspecified launch failure
2018.04.18:22:35:26.216: GPU4 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.18:22:35:26.216: GPU4 GPU4 search error: unspecified launch failure
2018.04.18:22:35:26.216: GPU6 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.18:22:35:26.216: GPU6 GPU6 search error: unspecified launch failure
2018.04.18:22:35:26.232: GPU8 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.18:22:35:26.232: GPU8 GPU8 search error: unspecified launch failure
2018.04.18:22:35:26.263: GPU2 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.18:22:35:26.263: GPU2 GPU2 search error: unspecified launch failure
2018.04.18:22:35:26.404: wdog Thread(s) not responding. Restarting.
2018.04.18:22:35:28.779: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}
Post
Topic
Board Mining (Altcoins)
Re: Gigabyte H110-D3A: PCI-e 16x slot doesn't work
by
ibizastyler
on 31/03/2018, 10:55:17 UTC
Hi again!

Sorry for my very late reply... I had a few very bad weeks Sad

But now, I have a few nice updates for you:

- 1st: I was getting all 6 GPUs up and running - stable with only one PSU!
- the next good thing is, I got now 7 GPUs hashing in one rig. Within the three starts with only one PSU, but than I decided to add another PSU.
-- I'm using a 1 to 4 PCI-e riser card and it works perfectly (almost... later more about the issue)

You where asking me about the brand and model of the "RMA-ing" GPU.
It was a MSI GTX 1070 Gaming X 8G.

Yesterday I got the information of the dealer that the graphic card was repaired at MSI and is now on the way back home.
So I guess that the gc could arrive within the next 4-5 days - so directly after easter.

As soon as it arrives I will add it of course to the rig Smiley ... and I hope that it still works!!

But now to another problem:
From time to time - so roundabout 3 to 24 hours - I got the error message "CUDA ..xyz... out of memory".

Unfortunately, I cannot really fix this issue.
After increasing the size of the win 10 page file to "minimum 17000 MB and maximum 57000 MB (amount of gpus (7) * 8 GB memory per card +1 GB)" it runs a bit better, but no smoothly as it should.

Do you have any idea maybe?
Thanks a lot in advance for your help!!!

...and here a few screenshots:
https://imgur.com/Dv1nXAf
https://imgur.com/19e5Hv6
https://imgur.com/DCS1ayO
Post
Topic
Board Mining (Altcoins)
Re: Gigabyte H110-D3A: PCI-e 16x slot doesn't work
by
ibizastyler
on 13/03/2018, 09:20:03 UTC
thx for your support p337miner!

unfortunately one of my new graphic cards is broken. Therefore I cannot test it atm, because the other 5 cards are finding a lot of shares and I don't want to quit the miner xD

do you know how many cards are usable atm? is the limit still 8 or is it now possible to connect more? I was reading that windows has a limit of 8 at all and especially a maximum of 8 cards of the same model.
if I would like to connect more I have to use linux. is this correct so far?
Why I am asking:
I bought today a pic-e 1x to 4x riser card... xD it would be nice to get it up and running. the m.2 slot is unfortunately only for another ssd and cannot be used as a pci-e slot.

Quote
I also have a Gigabyte mobo, not your model, but I spent the same amount of time trying to get pcie slots to recognise a MSI 1060 or recognising the gpu. The only way I've gotten it to work was option 2. I talked to a tech friend who has lots of mining experience about why the board is picky in that way and he said it must have something internally about the way the mobo chipset assigns the pcie lanes. The only thing I can think of in your case is that it won't assign lanes to the 16x if the others are filled first. This explanations makes no sense to me - because I literally tried everything to get mine set up, but there must be some logic behind why it will only recognise them in a particular order/assigns them. What order is anyone guess.

In my experience, I always fill the 16x first, then fill the others. The first GPU plugged straight into the mobo - then if you're lucky swap it out for a riser and it should still be ok. If not - my only other guess is that the riser cards have some compatibility or recognition issue on the mobo.

this was also my guess. I started with the x16 as well - directly plugged in the graphic card into the MB - but unfortunately nothing happened.
I tried this with 4 different cards (3 different manufacturers).

Quote
Hope this helps - also let us know if you've fixed it I want to know how you got it to recognise because I want that board.

I will definitely give you feedback... but the strange thing is still that other guys do not have a single problem with the MB and 6 graphic cards. They plugged the cards in and it worked...
Post
Topic
Board Mining (Altcoins)
Re: Gigabyte H110-D3A: PCI-e 16x slot doesn't work
by
ibizastyler
on 11/03/2018, 17:43:50 UTC
could you please give me a hint which option it could be?

these are my current settings:
--- Mining mode "enabled"
--- above 4G decoding "enabled"
--- Max. link speed "Gen2"
--- OS Mode: Windows 8/10
--- CSM off
--- initial display "IGFX"
--- internal graphics "enabled"
--- super IO config: Parallel and serial "disabled"
Post
Topic
Board Mining (Altcoins)
Re: Claymore Miner ETH for nvidia crashes after ~ 10 min.
by
ibizastyler
on 11/03/2018, 13:18:01 UTC
As I mentioned... I am new to mining and still learning Grin
Thanks for the hint!
Post
Topic
Board Mining (Altcoins)
Gigabyte H110-D3A: PCI-e 16x slot doesn't work
by
ibizastyler
on 11/03/2018, 12:58:06 UTC
Hi Guys!

I'm new to mining and I was building up my very first rig a few days ago.
It tooks me roundabout 14 days to get it up and running as it should.... but unfortunately not with 6 gpus, because the PCI-e 16x slot is not working at all.

What I already did:
- bios update to F25a
- different bios settings - but mainly:
--- Mining mode "enabled"
--- above 4G decoding "enabled"
--- Max. link speed "Gen2"
--- OS Mode: Windows 8/10
--- CSM off
--- initial display "IGFX"
--- internal graphics "enabled"
--- super IO config: Parallel and serial "disabled"

- I tried 6 different graphic cards (4x MSI, 1x EVGA and 1x Palit)
- ~ 12 different riser cards from three different manufacturers
- 2 PSUs togehter and one by one
- different power cabling for the risers (switching SATA cables, etc)

... and then I bought a second GB H110-D3A mainboard, because I thought that the pci-e 16x slot must be broken, but I guess it wasn't... so to say: "same shit, different card" Wink

I was also following this guide - step by step:
https://www.gigabyte.com/MicroSite/462/mining.html

system cfg:
CPU: Intel pentium G4400 boxed
Ram: 8GB Hyperfury X DDR4 2133
PSU: BeQuiet Dark Pro 11 1000W
Risers: Kolink and Elegant
SSD: WD Green 128GB
OS: Win 10 Pro - the virtual outsourcing file was increased to "17 - 21 GB"

Does anyone had the same problem and got it fixed?

Thx in advance for your help!!

BR,
Andi
Post
Topic
Board Mining (Altcoins)
Re: Claymore Miner ETH for nvidia crashes after ~ 10 min.
by
ibizastyler
on 11/03/2018, 12:33:07 UTC
Thanks a lot guys!
I tuned every single gpu again and now it is now stable for roundabout 16 hours...
Post
Topic
Board Mining (Altcoins)
Re: Claymore Miner ETH for nvidia crashes after ~ 10 min.
by
ibizastyler
on 10/03/2018, 17:09:52 UTC
thx for your reply!

I already lowered the values, but is there any possibility to find the "faulty" gpu in a first step?
Post
Topic
Board Mining (Altcoins)
Claymore Miner ETH for nvidia crashes after ~ 10 min.
by
ibizastyler
on 10/03/2018, 16:50:44 UTC
Hi Guys,

I was building up my very first rig and it tooks me about 10 days to get it up and running...  Grin
It is a rig with 5 nvidia GTX 1070 cards at the moment, because one is broken.

Everything works now nice and smoothly, but unfortunately only for roundabout 10 min...
The ETH (claymore eth only via nanopool) miner just crashes...

Is it because of the undervolting and overclocking? If yes, how can I find the faulty or the "to much overclocked" gpu?
I also tried to read and understand the log file... but yes... as I already mentioned... I am still a "mining/config noob".

I would really appreciate if someone can help me!!

Thanks a lot in advance and BR,
Andi

Quote
17:26:48:589   f10   ETH: checking pool connection...
17:26:48:589   f10   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

17:26:48:636   f10   got 243 bytes
17:26:48:636   f10   buf: {"jsonrpc":"2.0","id":0,"result":["0xe572a34723830cdb069eb7dfd78e93099d76773becbf059f639c4db945d11685","0x32a2478e57a4b36e5f5e5420e5443a5a82dac6ff01a0548737fada91d743d7d0","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

17:26:48:636   f10   parse packet: 242
17:26:48:636   f10   ETH: job is the same
17:26:48:636   f10   new buf size: 0
17:26:53:246   f10   got 243 bytes
17:26:53:246   f10   buf: {"jsonrpc":"2.0","id":0,"result":["0xb9d202d08ab464e3223bf50595d70e269c86bbbe62d11ec6b0775ee2776dd9f9","0x32a2478e57a4b36e5f5e5420e5443a5a82dac6ff01a0548737fada91d743d7d0","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

17:26:53:246   f10   parse packet: 242
17:26:53:246   f10   ETH: job changed
17:26:53:246   f10   new buf size: 0
17:26:53:262   f10   ETH: 03/10/18-17:26:53 - New job from eth-eu1.nanopool.org:9999
17:26:53:262   f10   target: 0x000000006df37f67 (diff: 10000MH), epoch 174(2.36GB)
17:26:53:262   f10   ETH - Total Speed: 162.088 Mh/s, Total Shares: 10, Rejected: 0, Time: 00:11
17:26:53:277   f10   ETH: GPU0 32.552 Mh/s, GPU1 31.685 Mh/s, GPU2 30.567 Mh/s, GPU3 32.677 Mh/s, GPU4 34.608 Mh/s
17:26:57:622   1098   GPU0 t=60C fan=50%, GPU1 t=59C fan=50%, GPU2 t=45C fan=50%, GPU3 t=51C fan=50%, GPU4 t=40C fan=50%
17:26:57:637   1098   em hbt: 0, fm hbt: 46,
17:26:57:637   1098   watchdog - thread 0 (gpu0), hb time 187
17:26:57:637   1098   watchdog - thread 1 (gpu0), hb time 78
17:26:57:653   1098   watchdog - thread 2 (gpu1), hb time 187
17:26:57:653   1098   watchdog - thread 3 (gpu1), hb time 62
17:26:57:653   1098   watchdog - thread 4 (gpu2), hb time 172
17:26:57:653   1098   watchdog - thread 5 (gpu2), hb time 47
17:26:57:653   1098   watchdog - thread 6 (gpu3), hb time 203
17:26:57:668   1098   watchdog - thread 7 (gpu3), hb time 94
17:26:57:668   1098   watchdog - thread 8 (gpu4), hb time 219
17:26:57:668   1098   watchdog - thread 9 (gpu4), hb time 110
17:26:58:028   f10   send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x9b67f18", "0x000000000000000000000000000000000000000000000000000000005ff1b969"]}

17:26:58:606   f10   ETH: checking pool connection...
17:26:58:606   f10   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

17:26:58:700   f10   got 243 bytes
17:26:58:700   f10   buf: {"jsonrpc":"2.0","id":0,"result":["0xb9d202d08ab464e3223bf50595d70e269c86bbbe62d11ec6b0775ee2776dd9f9","0x32a2478e57a4b36e5f5e5420e5443a5a82dac6ff01a0548737fada91d743d7d0","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

17:26:58:700   f10   parse packet: 242
17:26:58:700   f10   ETH: job is the same
17:26:58:700   f10   new buf size: 0
17:27:00:731   f10   got 243 bytes
17:27:00:731   f10   buf: {"jsonrpc":"2.0","id":0,"result":["0x525ea23a0b7d2a1efeed1ea4b2141f0d2a6b31cbc52f223ea49edd5ac8551346","0x32a2478e57a4b36e5f5e5420e5443a5a82dac6ff01a0548737fada91d743d7d0","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

17:27:00:731   f10   parse packet: 242
17:27:00:731   f10   ETH: job changed
17:27:00:731   f10   new buf size: 0
17:27:00:747   f10   ETH: 03/10/18-17:27:00 - New job from eth-eu1.nanopool.org:9999
17:27:00:747   f10   target: 0x000000006df37f67 (diff: 10000MH), epoch 174(2.36GB)
17:27:00:747   f10   ETH - Total Speed: 163.766 Mh/s, Total Shares: 10, Rejected: 0, Time: 00:12
17:27:00:763   f10   ETH: GPU0 32.720 Mh/s, GPU1 32.716 Mh/s, GPU2 30.952 Mh/s, GPU3 32.713 Mh/s, GPU4 34.666 Mh/s
17:27:03:450   f10   got 243 bytes
17:27:03:450   f10   buf: {"jsonrpc":"2.0","id":0,"result":["0xfd7e158e1382ca055c3272426f9a95d950548f99924171d0ec32327b69a26dd6","0x32a2478e57a4b36e5f5e5420e5443a5a82dac6ff01a0548737fada91d743d7d0","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

17:27:03:450   f10   parse packet: 242
17:27:03:450   f10   ETH: job changed
17:27:03:450   f10   new buf size: 0
17:27:03:466   f10   ETH: 03/10/18-17:27:03 - New job from eth-eu1.nanopool.org:9999
17:27:03:466   f10   target: 0x000000006df37f67 (diff: 10000MH), epoch 174(2.36GB)
17:27:03:466   f10   ETH - Total Speed: 163.467 Mh/s, Total Shares: 10, Rejected: 0, Time: 00:12
17:27:03:466   f10   ETH: GPU0 32.694 Mh/s, GPU1 32.722 Mh/s, GPU2 30.713 Mh/s, GPU3 32.679 Mh/s, GPU4 34.659 Mh/s
17:27:08:623   f10   ETH: checking pool connection...
17:27:08:623   f10   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

17:27:08:670   f10   got 243 bytes
17:27:08:670   f10   buf: {"jsonrpc":"2.0","id":0,"result":["0xfd7e158e1382ca055c3272426f9a95d950548f99924171d0ec32327b69a26dd6","0x32a2478e57a4b36e5f5e5420e5443a5a82dac6ff01a0548737fada91d743d7d0","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

17:27:08:670   f10   parse packet: 242
17:27:08:670   f10   ETH: job is the same
17:27:08:670   f10   new buf size: 0
17:27:13:920   22f0   GPU 1, GpuMiner cu_k1 failed 4, unspecified launch failure
17:27:13:936   2378   GPU 3, GpuMiner cu_k1 failed 4, unspecified launch failure
17:27:13:951   22f0   GPU 1, GpuMiner kx failed 1
17:27:13:998   2378   GPU 3, GpuMiner kx failed 1
17:27:14:014   22c0   GPU 0, GpuMiner cu_k1 failed 4, unspecified launch failure
17:27:14:030   22c0   GPU 0, GpuMiner kx failed 1
17:27:13:998   22f0   Set global fail flag, failed GPU1
17:27:14:045   22f0   GPU 1 failed
17:27:14:014   2378   Set global fail flag, failed GPU3
17:27:14:076   2378   GPU 3 failed
17:27:14:123   2368   GPU 2, GpuMiner cu_k1 failed 4, unspecified launch failure
17:27:14:155   22ec   GPU 1, GpuMiner cu_k1 failed 4, unspecified launch failure
17:27:14:030   22c0   Set global fail flag, failed GPU0
17:27:14:186   22c0   GPU 0 failed
17:27:14:201   2370   GPU 3, GpuMiner cu_k1 failed 4, unspecified launch failure
17:27:14:217   2368   GPU 2, GpuMiner kx failed 1
17:27:14:248   22ec   GPU 1, GpuMiner kx failed 1
17:27:14:311   1c3c   GPU 4, GpuMiner cu_k1 failed 4, unspecified launch failure
17:27:14:326   1ef8   GPU 0, GpuMiner cu_k1 failed 4, unspecified launch failure
17:27:14:326   1ef8   GPU 0, GpuMiner kx failed 1
17:27:14:342   1ef8   Set global fail flag, failed GPU0
17:27:14:342   1ef8   GPU 0 failed
17:27:14:373   2370   GPU 3, GpuMiner kx failed 1
17:27:14:498   1c3c   GPU 4, GpuMiner kx failed 1
17:27:14:498   1c3c   Set global fail flag, failed GPU4
17:27:14:498   1c3c   GPU 4 failed
17:27:14:248   2368   Set global fail flag, failed GPU2
17:27:14:514   2368   GPU 2 failed
17:27:14:514   236c   GPU 2, GpuMiner cu_k1 failed 4, unspecified launch failure
17:27:14:498   2370   Set global fail flag, failed GPU3
17:27:14:530   2370   GPU 3 failed
17:27:14:311   22ec   Set global fail flag, failed GPU1
17:27:14:561   22ec   GPU 1 failed
17:27:14:608   1350   GPU 4, GpuMiner cu_k1 failed 4, unspecified launch failure
17:27:14:623   1350   GPU 4, GpuMiner kx failed 1
17:27:14:639   236c   GPU 2, GpuMiner kx failed 1
17:27:14:639   1350   Set global fail flag, failed GPU4
17:27:14:639   1350   GPU 4 failed
17:27:14:639   236c   Set global fail flag, failed GPU2
17:27:14:655   236c   GPU 2 failed
17:27:18:046   f10   send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0", "0x000000000000000000000000000000000000000000000000000000005ff1b969"]}

17:27:18:639   f10   ETH: checking pool connection...
17:27:18:639   f10   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

17:27:18:733   f10   got 243 bytes
17:27:18:733   f10   buf: {"jsonrpc":"2.0","id":0,"result":["0xfd7e158e1382ca055c3272426f9a95d950548f99924171d0ec32327b69a26dd6","0x32a2478e57a4b36e5f5e5420e5443a5a82dac6ff01a0548737fada91d743d7d0","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

17:27:18:733   f10   parse packet: 242
17:27:18:733   f10   ETH: job is the same
17:27:18:733   f10   new buf size: 0
17:27:28:656   f10   ETH: checking pool connection...
17:27:28:656   f10   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

17:27:28:703   f10   got 243 bytes
17:27:28:703   f10   buf: {"jsonrpc":"2.0","id":0,"result":["0xfd7e158e1382ca055c3272426f9a95d950548f99924171d0ec32327b69a26dd6","0x32a2478e57a4b36e5f5e5420e5443a5a82dac6ff01a0548737fada91d743d7d0","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

17:27:28:703   f10   parse packet: 242
17:27:28:703   f10   ETH: job is the same
17:27:28:703   f10   new buf size: 0
17:27:30:563   1098   GPU0 t=55C fan=50%, GPU1 t=54C fan=50%, GPU2 t=41C fan=50%, GPU3 t=46C fan=50%, GPU4 t=36C fan=50%
17:27:30:578   1098   em hbt: 16, fm hbt: 16,
17:27:30:578   1098   watchdog - thread 0 (gpu0), hb time 16734
17:27:30:578   1098   watchdog - thread 1 (gpu0), hb time 16859
17:27:30:578   1098   watchdog - thread 2 (gpu1), hb time 16688
17:27:30:578   1098   watchdog - thread 3 (gpu1), hb time 16828
17:27:30:594   1098   watchdog - thread 4 (gpu2), hb time 16813
17:27:30:594   1098   watchdog - thread 5 (gpu2), hb time 16688
17:27:30:594   1098   watchdog - thread 6 (gpu3), hb time 16704
17:27:30:594   1098   watchdog - thread 7 (gpu3), hb time 16829
17:27:30:609   1098   watchdog - thread 8 (gpu4), hb time 16750
17:27:30:609   1098   watchdog - thread 9 (gpu4), hb time 16875
17:27:30:609   1098   WATCHDOG: GPU error, you need to restart miner Sad
17:27:31:766   1098   Restarting OK, exit...

Post
Topic
Board Mining (Altcoins)
Re: Mainboard (GB H110-D3A) doesn't find a graphic card... PLEASE HELP!!
by
ibizastyler
on 10/03/2018, 16:43:34 UTC
just a short update:

the rig is running now, but only with 5 gpus. the 6th one is broken - time for the next RMA.
so far so good...

The main issue were the riser cards... I bought a few other riser cards for testing and ... "oh nice, it is working" Grin

But now I have another problem.
Everything works nice and smoothly, but unfortunately only 10 min...
The ETH (claymore eth only via nanopool) miner just crashes...

Is it because of the undervolting and overclocking? If yes, how can I find the faulty gpu?
Also tried to read and understand the log file, but yes... hm.. GPU 0 and then the other 4  Cry

I would really appreciate if someone can help me again!!

Quote
17:26:48:589   f10   ETH: checking pool connection...
17:26:48:589   f10   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

17:26:48:636   f10   got 243 bytes
17:26:48:636   f10   buf: {"jsonrpc":"2.0","id":0,"result":["0xe572a34723830cdb069eb7dfd78e93099d76773becbf059f639c4db945d11685","0x32a2478e57a4b36e5f5e5420e5443a5a82dac6ff01a0548737fada91d743d7d0","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

17:26:48:636   f10   parse packet: 242
17:26:48:636   f10   ETH: job is the same
17:26:48:636   f10   new buf size: 0
17:26:53:246   f10   got 243 bytes
17:26:53:246   f10   buf: {"jsonrpc":"2.0","id":0,"result":["0xb9d202d08ab464e3223bf50595d70e269c86bbbe62d11ec6b0775ee2776dd9f9","0x32a2478e57a4b36e5f5e5420e5443a5a82dac6ff01a0548737fada91d743d7d0","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

17:26:53:246   f10   parse packet: 242
17:26:53:246   f10   ETH: job changed
17:26:53:246   f10   new buf size: 0
17:26:53:262   f10   ETH: 03/10/18-17:26:53 - New job from eth-eu1.nanopool.org:9999
17:26:53:262   f10   target: 0x000000006df37f67 (diff: 10000MH), epoch 174(2.36GB)
17:26:53:262   f10   ETH - Total Speed: 162.088 Mh/s, Total Shares: 10, Rejected: 0, Time: 00:11
17:26:53:277   f10   ETH: GPU0 32.552 Mh/s, GPU1 31.685 Mh/s, GPU2 30.567 Mh/s, GPU3 32.677 Mh/s, GPU4 34.608 Mh/s
17:26:57:622   1098   GPU0 t=60C fan=50%, GPU1 t=59C fan=50%, GPU2 t=45C fan=50%, GPU3 t=51C fan=50%, GPU4 t=40C fan=50%
17:26:57:637   1098   em hbt: 0, fm hbt: 46,
17:26:57:637   1098   watchdog - thread 0 (gpu0), hb time 187
17:26:57:637   1098   watchdog - thread 1 (gpu0), hb time 78
17:26:57:653   1098   watchdog - thread 2 (gpu1), hb time 187
17:26:57:653   1098   watchdog - thread 3 (gpu1), hb time 62
17:26:57:653   1098   watchdog - thread 4 (gpu2), hb time 172
17:26:57:653   1098   watchdog - thread 5 (gpu2), hb time 47
17:26:57:653   1098   watchdog - thread 6 (gpu3), hb time 203
17:26:57:668   1098   watchdog - thread 7 (gpu3), hb time 94
17:26:57:668   1098   watchdog - thread 8 (gpu4), hb time 219
17:26:57:668   1098   watchdog - thread 9 (gpu4), hb time 110
17:26:58:028   f10   send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x9b67f18", "0x000000000000000000000000000000000000000000000000000000005ff1b969"]}

17:26:58:606   f10   ETH: checking pool connection...
17:26:58:606   f10   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

17:26:58:700   f10   got 243 bytes
17:26:58:700   f10   buf: {"jsonrpc":"2.0","id":0,"result":["0xb9d202d08ab464e3223bf50595d70e269c86bbbe62d11ec6b0775ee2776dd9f9","0x32a2478e57a4b36e5f5e5420e5443a5a82dac6ff01a0548737fada91d743d7d0","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

17:26:58:700   f10   parse packet: 242
17:26:58:700   f10   ETH: job is the same
17:26:58:700   f10   new buf size: 0
17:27:00:731   f10   got 243 bytes
17:27:00:731   f10   buf: {"jsonrpc":"2.0","id":0,"result":["0x525ea23a0b7d2a1efeed1ea4b2141f0d2a6b31cbc52f223ea49edd5ac8551346","0x32a2478e57a4b36e5f5e5420e5443a5a82dac6ff01a0548737fada91d743d7d0","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

17:27:00:731   f10   parse packet: 242
17:27:00:731   f10   ETH: job changed
17:27:00:731   f10   new buf size: 0
17:27:00:747   f10   ETH: 03/10/18-17:27:00 - New job from eth-eu1.nanopool.org:9999
17:27:00:747   f10   target: 0x000000006df37f67 (diff: 10000MH), epoch 174(2.36GB)
17:27:00:747   f10   ETH - Total Speed: 163.766 Mh/s, Total Shares: 10, Rejected: 0, Time: 00:12
17:27:00:763   f10   ETH: GPU0 32.720 Mh/s, GPU1 32.716 Mh/s, GPU2 30.952 Mh/s, GPU3 32.713 Mh/s, GPU4 34.666 Mh/s
17:27:03:450   f10   got 243 bytes
17:27:03:450   f10   buf: {"jsonrpc":"2.0","id":0,"result":["0xfd7e158e1382ca055c3272426f9a95d950548f99924171d0ec32327b69a26dd6","0x32a2478e57a4b36e5f5e5420e5443a5a82dac6ff01a0548737fada91d743d7d0","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

17:27:03:450   f10   parse packet: 242
17:27:03:450   f10   ETH: job changed
17:27:03:450   f10   new buf size: 0
17:27:03:466   f10   ETH: 03/10/18-17:27:03 - New job from eth-eu1.nanopool.org:9999
17:27:03:466   f10   target: 0x000000006df37f67 (diff: 10000MH), epoch 174(2.36GB)
17:27:03:466   f10   ETH - Total Speed: 163.467 Mh/s, Total Shares: 10, Rejected: 0, Time: 00:12
17:27:03:466   f10   ETH: GPU0 32.694 Mh/s, GPU1 32.722 Mh/s, GPU2 30.713 Mh/s, GPU3 32.679 Mh/s, GPU4 34.659 Mh/s
17:27:08:623   f10   ETH: checking pool connection...
17:27:08:623   f10   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

17:27:08:670   f10   got 243 bytes
17:27:08:670   f10   buf: {"jsonrpc":"2.0","id":0,"result":["0xfd7e158e1382ca055c3272426f9a95d950548f99924171d0ec32327b69a26dd6","0x32a2478e57a4b36e5f5e5420e5443a5a82dac6ff01a0548737fada91d743d7d0","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

17:27:08:670   f10   parse packet: 242
17:27:08:670   f10   ETH: job is the same
17:27:08:670   f10   new buf size: 0
17:27:13:920   22f0   GPU 1, GpuMiner cu_k1 failed 4, unspecified launch failure
17:27:13:936   2378   GPU 3, GpuMiner cu_k1 failed 4, unspecified launch failure
17:27:13:951   22f0   GPU 1, GpuMiner kx failed 1
17:27:13:998   2378   GPU 3, GpuMiner kx failed 1
17:27:14:014   22c0   GPU 0, GpuMiner cu_k1 failed 4, unspecified launch failure
17:27:14:030   22c0   GPU 0, GpuMiner kx failed 1
17:27:13:998   22f0   Set global fail flag, failed GPU1
17:27:14:045   22f0   GPU 1 failed
17:27:14:014   2378   Set global fail flag, failed GPU3
17:27:14:076   2378   GPU 3 failed
17:27:14:123   2368   GPU 2, GpuMiner cu_k1 failed 4, unspecified launch failure
17:27:14:155   22ec   GPU 1, GpuMiner cu_k1 failed 4, unspecified launch failure
17:27:14:030   22c0   Set global fail flag, failed GPU0
17:27:14:186   22c0   GPU 0 failed
17:27:14:201   2370   GPU 3, GpuMiner cu_k1 failed 4, unspecified launch failure
17:27:14:217   2368   GPU 2, GpuMiner kx failed 1
17:27:14:248   22ec   GPU 1, GpuMiner kx failed 1
17:27:14:311   1c3c   GPU 4, GpuMiner cu_k1 failed 4, unspecified launch failure
17:27:14:326   1ef8   GPU 0, GpuMiner cu_k1 failed 4, unspecified launch failure
17:27:14:326   1ef8   GPU 0, GpuMiner kx failed 1
17:27:14:342   1ef8   Set global fail flag, failed GPU0
17:27:14:342   1ef8   GPU 0 failed
17:27:14:373   2370   GPU 3, GpuMiner kx failed 1
17:27:14:498   1c3c   GPU 4, GpuMiner kx failed 1
17:27:14:498   1c3c   Set global fail flag, failed GPU4
17:27:14:498   1c3c   GPU 4 failed
17:27:14:248   2368   Set global fail flag, failed GPU2
17:27:14:514   2368   GPU 2 failed
17:27:14:514   236c   GPU 2, GpuMiner cu_k1 failed 4, unspecified launch failure
17:27:14:498   2370   Set global fail flag, failed GPU3
17:27:14:530   2370   GPU 3 failed
17:27:14:311   22ec   Set global fail flag, failed GPU1
17:27:14:561   22ec   GPU 1 failed
17:27:14:608   1350   GPU 4, GpuMiner cu_k1 failed 4, unspecified launch failure
17:27:14:623   1350   GPU 4, GpuMiner kx failed 1
17:27:14:639   236c   GPU 2, GpuMiner kx failed 1
17:27:14:639   1350   Set global fail flag, failed GPU4
17:27:14:639   1350   GPU 4 failed
17:27:14:639   236c   Set global fail flag, failed GPU2
17:27:14:655   236c   GPU 2 failed
17:27:18:046   f10   send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0", "0x000000000000000000000000000000000000000000000000000000005ff1b969"]}

17:27:18:639   f10   ETH: checking pool connection...
17:27:18:639   f10   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

17:27:18:733   f10   got 243 bytes
17:27:18:733   f10   buf: {"jsonrpc":"2.0","id":0,"result":["0xfd7e158e1382ca055c3272426f9a95d950548f99924171d0ec32327b69a26dd6","0x32a2478e57a4b36e5f5e5420e5443a5a82dac6ff01a0548737fada91d743d7d0","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

17:27:18:733   f10   parse packet: 242
17:27:18:733   f10   ETH: job is the same
17:27:18:733   f10   new buf size: 0
17:27:28:656   f10   ETH: checking pool connection...
17:27:28:656   f10   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

17:27:28:703   f10   got 243 bytes
17:27:28:703   f10   buf: {"jsonrpc":"2.0","id":0,"result":["0xfd7e158e1382ca055c3272426f9a95d950548f99924171d0ec32327b69a26dd6","0x32a2478e57a4b36e5f5e5420e5443a5a82dac6ff01a0548737fada91d743d7d0","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

17:27:28:703   f10   parse packet: 242
17:27:28:703   f10   ETH: job is the same
17:27:28:703   f10   new buf size: 0
17:27:30:563   1098   GPU0 t=55C fan=50%, GPU1 t=54C fan=50%, GPU2 t=41C fan=50%, GPU3 t=46C fan=50%, GPU4 t=36C fan=50%
17:27:30:578   1098   em hbt: 16, fm hbt: 16,
17:27:30:578   1098   watchdog - thread 0 (gpu0), hb time 16734
17:27:30:578   1098   watchdog - thread 1 (gpu0), hb time 16859
17:27:30:578   1098   watchdog - thread 2 (gpu1), hb time 16688
17:27:30:578   1098   watchdog - thread 3 (gpu1), hb time 16828
17:27:30:594   1098   watchdog - thread 4 (gpu2), hb time 16813
17:27:30:594   1098   watchdog - thread 5 (gpu2), hb time 16688
17:27:30:594   1098   watchdog - thread 6 (gpu3), hb time 16704
17:27:30:594   1098   watchdog - thread 7 (gpu3), hb time 16829
17:27:30:609   1098   watchdog - thread 8 (gpu4), hb time 16750
17:27:30:609   1098   watchdog - thread 9 (gpu4), hb time 16875
17:27:30:609   1098   WATCHDOG: GPU error, you need to restart miner Sad
17:27:31:766   1098   Restarting OK, exit...

Post
Topic
Board Mining (Altcoins)
Re: Mainboard (GB H110-D3A) doesn't find a graphic card... PLEASE HELP!!
by
ibizastyler
on 08/03/2018, 09:54:55 UTC
Ok, then I will ignore this step with formatting the ssd with GPT.

Quote
So the GPU is alive huh.. what if you disable on board graphics just to isolate, if it messed up, just set to default settings Cheesy

All of them must be alive, because I tried four different cards on this MB and in my gaming pc as well:
EVGA GTX 1070 SC
Palit GTX 1070 Gamerock PE <- it is the old one of my gaming pc
MSI GTX 1070 Gaming X 8G
MSI GTX 1080 Gaming X 8G <- it is the new one in my gaming pc, because the 1080 is not as good as the 1070 when it comes to mining (I did a lot of tests with my gaming pc - nice hash, ewdf, etc)

It is unfortunately always the same result Sad Black screen, but it boots into windows. I have checked that with the Remote Desktop connection from my gaming pc.
The next step is always cmos reset and "start at zero".

Quote
yeah its somewhat a challenge, but i tell you, once it got work, the feeling is great Cool

I already got this feeling in my bones, but paired with a potion of frustration!!  Grin Grin

Quote
they are pointing out to same input power with different connectors available, you need to power at least one of them, 6pin is the safest as has more thick wires.

Thanks for lighting up my brain!!  Cheesy
Post
Topic
Board Mining (Altcoins)
Re: Mainboard (GB H110-D3A) doesn't find a graphic card... PLEASE HELP!!
by
ibizastyler
on 08/03/2018, 07:56:33 UTC
Thx for your help!!

I will give it another try this evening with one molex which is directly plugged into the MB and the gc as well.
After this I will try another PSU as well. Unfortunately there was no time to "play around with it".

But another question:
I was reading a lot of "how to's..." within the last days.
In one of them they were talking about the Windows installation. They formatted the ssd with GPT?!
1st - I don't know how to do it, because I just plugged in the usb stick and did the installation as usual.

I have also tried the other pci-e slots but nothing happen as I would wish to.
The fans are spinning around and the LED lights are on too.

This is really frustrating ...  Angry Cry To be honest it is very first "pc build" which is faulty since 1993. I never had issues like this

Edit:
Another question regarding the riser card:
There are a lot of power connections on this card.
What are they for?
There is also another 6-Pin connector with following description: "PCI-e 1x to 16x"
I haven't had giving them a try yet
Post
Topic
Board Mining (Altcoins)
Re: Mainboard (GB H110-D3A) doesn't find a graphic card... PLEASE HELP!!
by
ibizastyler
on 08/03/2018, 06:49:42 UTC
Here are the images:

https://ibb.co/bGc9cn
https://ibb.co/kamD3S
https://ibb.co/hC62xn
https://ibb.co/mC4Bq7
https://ibb.co/it0jA7

any suggestions?

PS: sorry... the thumbnails of the pictures are not working... I don't know why...