Well, it crashed around 3am. I was running pill and will stop that for today's testing.
George, you get 13.6 Mh/s for one 1080ti? If true, that is more than I am getting for 2x 1080ti & 2x 1080s... presently I'm at about 12.7 Mh/s for all 4 cards running. I'd love to hear the rest of your setup, including any of your nvidia settings.
Thanks!
|
|
|
Try also without the pill. It makes no difference with CD (-i 8 ), but can make a rig much more stable.
CD tops out with -i 6 though... ? At least that's what the readme says... Do you set CPU priority or leave it at 3?
|
|
|
Sometimes (not everytime), while the tree is being created, the clock jumps up in a matter of a second. If your overclock isn't stable enough and can't handle such spikes (or your PSU), your rig will crash. Open Afterburner or similar and make sure these jumps will not exeed 2050 core on your 1080 Ti. The 1080 you have to test by your own, my are fine with 2050 and some with 2100.
You can test your settings with CCMiner, it will crash here way faster than CD. If all is rock stable, switch back to CD and enjoy more $.
Edit: And dont split your virtual memory. Only use one SSD, not 4.
My core never exceeds 1810 on my ti's - great tip to watch for though. Hadn't heard or even had an issue with each drive having a page file... I'll condense to one to see if I gain anything. Thanks for that tip! I went ahead and DDU'd my drivers as well as uninstalled Visual Studio. I reinstalled the drivers, CUDA 10, VS kept my clocking the same and used pill. I've been running for a couple hours with a *slight* hashrate increase (somewhere around 4% which I won't sneeze at) and it hasn't faulted yet. I'll run her this way until tomorrow just to test it down. I'll post stats tomorrow.
|
|
|
Just for shytes and giggles, I went ahead and ran MTP on CD and it faulted and reboot within a few minutes. I ran TT Miner for 12 hours, same settings and it didn't reboot, however I got several refused shares due to the difficulty not being high enough supposedly. I ran CC Miner and it also didn't have a reboot, although I did find I ended up with several refused shares as well.
I ran these tests on a 4 card rig, 2x 1080s and 2x 1080tis. I was also using pill and a slight OC +125 Core / +100 Mem on the ti's and +100 / +100 on the 1080s. None of the voltage was changed.
i'm newbie in mining, but i tested CD on 1080s *1080ti-s, no crashes/reboot (only problem i faced was fluctuating Kh/s) and that was bc i used intensity 8, and the highest recommended intensity is 6. did u upgrade ur driver to 417.71? r u using Cuda 10? r u using lastest CD 0.16.1 ? did u change any settings on Nvidia control panel? did u use the recommended virtual memory by the developer ? @echo off title mtp (Zcoin) - 2minersPool CryptoDredge -a mtp -o stratum+tcp://xzc.2miners.com:8080 -u address.worker -p x -i 8 pause
All valid questions! I'm not a newbie and have been mining longer than I should (according to my wife). Drivers are updated. Cuda 10 running. Latest version of CD. Control panel settings are standard mining settings, including performance over quality. I have 8GB physical mem and over 100gb of virtual mem over 4 SSD cards on that rig.
|
|
|
Just for shytes and giggles, I went ahead and ran MTP on CD and it faulted and reboot within a few minutes. I ran TT Miner for 12 hours, same settings and it didn't reboot, however I got several refused shares due to the difficulty not being high enough supposedly. I ran CC Miner and it also didn't have a reboot, although I did find I ended up with several refused shares as well.
I ran these tests on a 4 card rig, 2x 1080s and 2x 1080tis. I was also using pill and a slight OC +125 Core / +100 Mem on the ti's and +100 / +100 on the 1080s. None of the voltage was changed.
|
|
|
Heloo !! v0.16.1 released- Fix MTP issue related to many rejected shares
Is the software optimized for Maxwell architecture (GTX 980 TI) or only Pascal (GTX 1070, etc...) ? That's how it looks with me: [19:50:46] INFO - GPU0 Gigabyte GTX 1070 : 2003KH/s (Avr 1689KH/s) : 16,20KH/W : T=54C Fan=26% [19:50:46] INFO - GPU1 Gigabyte GTX 1070 : 2003KH/s (Avr 1978KH/s) : 17,88KH/W : T=53C Fan=25% [19:50:46] INFO - GPU2 Gigabyte GTX 980 Ti : 260,7KH/s (Avr 257,8KH/s) : 2353H/W : T=58C Fan=31% [19:50:46] INFO - GPU3 Gigabyte GTX 980 Ti : 253,5KH/s (Avr 250,3KH/s) : 1994H/W : T=60C Fan=31% [19:50:46] INFO - GPU4 Zotac GTX 980 Ti : 252,1KH/s (Avr 249,9KH/s) : 2013H/W : T=58C Fan=0% [19:50:56] INFO - 12/0 Accepted : diff=0.0993187 : 4431KH/s
Hashing in other algorithms 980 TI and 1070 is similar. Each algorithm will hash differently.
|
|
|
I'm losing hashrate after devfee session on MTP. after devfee session hashrate is down about 3.5% right after user session begins, about 100 blocks later hashrate is still about 2.2% lower than before devfee..... what is going on? I have to resrtart miner to get hash back up to normal
you're not losing any hashrate. the miner shows you your effective hashrate without dev fee time. no, that doesn't make sense, i was coming here to report the same problem, to find that u guys already talking about it. dev fee sessions starts for 1-2 minutes many times, idk may be like 2 minutes for each 100 minutes online (2% for mtp). u can see that on the miner (dev session starts) and 1-2 minutes after it stops and followed by ( user session started) but after this KH/s drops from 2800 to about 2600 and keep rising up by 1kh untill it reach about 2670 , and it keep on that rate till the next dev session What they are saying is you're looking at an average hashrate in the miner and when it cuts out for the dev session, of course that number would appear to drop. Given enough time running, the reported hashrate in the miner should normalize. The problem I see isn't the hashrate... it's the shares submitted. I notice that it becomes sporadic after a dev fee session.
|
|
|
I'd love a command that tells the miner to mine the Dev fee for a 24 hour period all at once. Every miner that I've ever used that splits out for a dev fee always suffers what appears to be a submitted share decline after it returns to the user session. It will just about get back to speed and then goes right back into the dev fee schedule.
Also, a command to either lengthen the interval of GPU Info or to subdue it altogether would be splendid.
Perhaps, if you could quantify a "lifetime member" fee, one that would "unlock" the miner to be free from the dev session, that might be a thing too.
Great miner! Keep up the great work!
|
|
|
Sure, for almost 2% and I have to wait the entire 100 block confirmation... or I could mine at VIABTC for 1% and get paid after 10 confirmations. Until BSOD lowers their pretty high fee, I'll look elsewhere. Thanks for the suggestion though.
|
|
|
Guess there will be no response. I'll have to plan something accordingly I suppose... maybe a pool with 0.49% fee and an actual OP who responds to miners.
|
|
|
4 days later and no response from an OP. I see previous posts going back for months with similar situations and no response. I would take comfort seeing that a block hasn't been hit since I hit it last except that just means my fellow miners haven't had a good run lately either, which sucks.
I'm going to say the Mining Gods are unpleased with this pool at this point and they've whammied it... but again, that's not a lot of comfort. What would be comforting would be to see the coins I earned sent to me.
|
|
|
It would be great if the OP of the pool would respond. I've actually been mining to this pool for a good little bit and I've hit plenty of blocks. I made the mistake of updating a payment address away from a Legacy address and hit a block. I've changed it back to my original Legacy address but mining at this pool will not be the same if I lost out on a block that was genuinely mined by me and the pool gobbled up. Especially when it says nothing about new addresses not being recognized by the pool AND the name didn't display red. The email addresses on each block is proof enough of ownership of the block. http://ltc.tbdice.org/blocks.htm - it's currently the last block hit. #1556261 - Shows as MN.Miner - 2 blocks before I hit using the Legacy address and it shows LN.Miner - The DOGE wallet addresses never changed as one last bit of proof. The block gobbled up by the pool is: https://chain.so/api/v2/block/LTC/ae1a88664ce964270ba997ff4e8e7d4ce67c7441da50928786b915268c833d31/Which shows the null data and the pool accepting the coins for 24.87586745 Please either pay out to the original address or send to the Legacy address (if you need it again or for verification, I'll send it to you dm)... either way is fine. Thank you!
|
|
|
Used a new LTC address and my coins went to the pool instead... Any help here would be appreciated.
I did forget to mention that this isn't my first block at this pool... and I've had my blocks notifying via email to the same email address. I know the coins went to the pool when you look at the block itself and when you pull up the pool's address. The help is definitely appreciated!!
|
|
|
Used a new LTC address and my coins went to the pool instead... Any help here would be appreciated.
|
|
|
Happy Birthday LUX!!! This is by far one of the best alt-coin gems around! Can't wait for Mercury to finish the technical marvels of this project! Imagine a world where exchanges are no longer needed!!! DECENTRALIZED! BOOM! Brought to you by LUXCORE! Here's a *great* article about Lux that everyone should take the time to read. It's brief but chock full of great info! https://www.entrepreneur.com/article/321482HAPPY BIRTHDAY LUX!!
|
|
|
Hello, I just got an ASUS MAXIMUS VIII HERO Z170 chipset motherboard. https://www.asus.com/Motherboards/MAXIMUS-VIII-HERO/This HERO has 6 GPU slots and one M.2 port on it. This a a tutorial to explain how to connect 6 GPU or even 7 if you use m.2 port with converter. This is my setup's screensot. 6pcs AMD RX470 with 179 MH/s performance. https://prnt.sc/io4xl4The most important thing is to use 6th generation CPU with it. Which also called as Skylake. I suggest G4400 but you can choose others too, whole list is in below. https://ark.intel.com/products/series/77772/Intel-Pentium-Processor-G-Series1. Put only 1 GPU to X16 port (the big and closest to CPU) 2. Connect your monitor's HDMI cable to MOTHERBOARD's HDMI port. 3. Start PC and enter BIOS. (press F2 when starting) 4. Apply BIOS settings in below. 5. Install AMD blockchain driver. Download from here6. Turn off PC and connect other GPU's to MB. Turn on again. 7. Wait few minutes, relax BIOS SettingsADVANCED -System Agent (SA) Configuration --Graphic Configuration ---Primary Display => IGFX
ADVANCED -System Agent (SA) Configuration --DMI/OPI Configuration ---DMI Max Link Speed => Gen2
ADVANCED -System Agent (SA) Configuration --PEG Port Configuration ---PCIEX16/X8_1 Link Speed => Gen2 ---PCIEX16/X8 Link Speed => Gen2
ADVANCED -PCH Configuration ---PCI Express Configuration ----PCIe Speed => Gen2
ADVANCED -Onboard Devices Configuration --HD Audio Controller => Disabled
ADVANCED -APM Configuration --Restore AC Power Loss => Power On
BOOT -Above 4D Decoding => Enabled First off, *thank you so much*! This was a great guide for a motherboard I had and was only able to get two cards on to. A few things I found while doing this that should help the next person: ---PCIEX16/X8 _2 Link Speed => Gen2 - *typo that was easy to identify* When you're adding your cards after your first card, add them one by one, starting up the system each newly added card. Let it get in to your system and verify the newly added card has been recognized and that you can use it. If you're OC'ing it ultimately, apply your OC each time to test that its accepting it. Good luck!
|
|
|
Has anyone watched the block explorer? This network is sad...
It talks about being PoW/PoS... but it's 98% PoS... 2 blocks an hour going to PoW.
No wonder why it's so slow. Every pool listed as a mining pool (with exception to their own!) has moved away from this coin. 4 hours to confirm a block? Wow...
|
|
|
Can anyone supply a list of addnodes for the wallet?
|
|
|
About 3 hours ago I requested a BTC withdrawal. I confirmed it immediately from email and everything seemed normal. An hour, still processing... sent a support ticket... another hour and no response. I sent a follow up message on the same ticket and just received an email saying the wait time is.......
15 *DAYS*!
Cryptopia is more like a Crypt it seems. Things deposited there dont apparently leave.
Anyone else having issues or am I the lucky one?
LOL 3 minutes after I post this and 3.25 hours in, the transfer has initiated! Thank you BitCoinTalk Gods for listening to your humble servant's pleas for help!
|
|
|
|