• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Cryptocoin Mining?

Page 269 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Anyone know why this could be happening while LTC mining? Temps are definitely fine as shown in pic 2.

It's a power tune issue. The card is throttling due to not enough power. Looks like a 290 or 290X, try either lowering the clocks or reducing the intensity.
 
^disable crossfire

CCC shows it as being disabled. Plus I have no monitor connected usually so it won't let me turn it on anyway.

It's a power tune issue. The card is throttling due to not enough power. Looks like a 290 or 290X, try either lowering the clocks or reducing the intensity.

They are 290s. I have set Powertune to +50% in Afterburner. Is that not effective? These 3 cards are running on a Corsair AX1200i PSU.
 
Last edited:
CCC shows it as being disabled. Plus I have no monitor connected usually so it won't let me turn it on anyway.



They are 290s. I have set Powertune to +50% in Afterburner. Is that not effective? These 3 cards are running on a Corsair AX1200i PSU.

I am going to assume that the 290s work similar to the 7000 series but I don't have one so I don't know. When I overclock my 7950s to 1100/1500 I see that behavior when there is no adjustments to powertune. If I set it to +20% it goes away and GPU usage is 100%.

I would think 50% is way to high, maybe even for that power supply with 3 cards. Mining is extremely power intensive. I would try playing around with powertune and maybe even removing one of the cards from the system temporarily.

Setting all this up is sort of like an art, I have multiple 7000 series cards, some same chips and some identical cards from the same manufacturer. They almost all take different settings for Engine and Memory clock and intensity to produce the best hash rate with the least problems.

Edit: I can guarantee you it's a power problem, you just need to track down where.
 
Last edited:
Disable ULPS?

I did that in Afterburner. No idea if it actually works.

Is there any way to disable ULPS in CCC?

EDIT: Apparently it could be a GPU usage bug with Afterburner. i think Silverforce mentioned this before. Will report back if I manage to fix it.

EDIT2: For me it turned out that a CPU intensive task I was running was causing that. Stopped the task and GPU usage is reading 100% continuously now. Although clocks still fluctuate.
 
Last edited:
It is a known bug with afterburner and R290s.

Edit: GPU usage readings sometimes dont work, its on the MSI afterburner forum as a known bug, to be fixed soon.
 
Last edited:
It is a known bug with afterburner and R290s.

Edit: GPU usage readings sometimes dont work, its on the MSI afterburner forum as a known bug, to be fixed soon.

Thanks for the info.

For me it turned out that a CPU intensive task I was running was causing that. Stopped the task and GPU usage is reading 100% continuously now. Although clocks still fluctuate.

Thanks everyone for the suggestions! 🙂
 
also make sure on your power supply that has a splitter make sure you don't use the split power. You need two separate power connecter going to the card.

Asked before but how do you get your coinbase btc -> to your bank?
 
Unless you're accepting Bitcoin as payment for your business, just go to Buy/Sell > Sell Bitcoin and enter the amount you wish to sell from your Coinbase balance.

Love your sig ... lol

Is there a simple way to just send BTC to my Coinbase account? I'm not seeing an actual BTC address to send it to anywhere in here. Is the best way just to create an invoice and send to my self?

Just setup another miner with a single Sapphire 7970 on a dual PCI-X motherboard. Bought another Gigabyte 7950 to match my first miner. Will transfer both to the new motherboard once it gets here. Even built a wood/aluminum open air case for it! Nice portable space heater....LMAO.
 
Hey guys I was helping my neighbor set up a mining rig and he only had a thin monitor power cord laying around in the garage. He used that for the PSU cord even though I told him the gauge wasn't right for that much power. Well luckily I checked that wire before I left because it was way too dangerously hot in only 1 hour. Got him a spare thick gauge power cord and that stays nice and cool. So if you are running a lot of power through it please use a nice heavy gauge wire the thin ones are not safe for this much power.
 
Mining dogecoins right now... Apparently a guy made $100 on his first day.

Same here. I mined around 1 million yesterday on 2 MH/s and I've seen them trade as high as 0.17 BTC / million. That's almost $150 in a day.

A lot of people seem to be jumping on it now, diff doubled today still very low though.
 
Same here. I mined around 1 million yesterday on 2 MH/s and I've seen them trade as high as 0.17 BTC / million. That's almost $150 in a day.

A lot of people seem to be jumping on it now, diff doubled today still very low though.

What pool are you guys using? Or are you using pools at all?
 
If you are getting HW errors, your intensity is too high for the -thread concurrency.

--intensity XX

Just like in bitcoin mining, scrypt mining takes an intensity, however the
scale goes from 0 to 20 to mimic the "Aggression" used in mtrlt's reaper. The
reason this is crucial is that too high an intensity can actually be
disastrous with scrypt because it CAN run out of ram. Intensities over 13
start writing over the same ram and it is highly dependent on the GPU, but they
can start actually DECREASING your hashrate, or even worse, start producing
garbage with HW errors skyrocketing. The low level detail is that intensity is
only guaranteed up to the power of 2 that most closely matches the thread
concurrency. i.e. a thread concurrency of 6144 has 8192 as the nearest power
of two above it, thus as 2^13=8192, that is an intensity of 13.


--thread-concurrency:
This tunes the optimal size of work that scrypt can do. It is internally tuned
by cgminer to be the highest reasonable multiple of shaders that it can
allocate on your GPU. Ideally it should be a multiple of your shader count.
vliw5 architecture (R5XXX) would be best at 5x shaders, while VLIW4 (R6xxx and
R7xxx) are best at 4x. Setting thread concurrency overrides anything you put
into --shaders.

Lower intensity or increase -thread concurrency

Thanks!

Manually setting thread concurrency according to 4x the number of shaders made one cards errors go to 0.

The other card is still getting ~1/3 errors.
 
How can you setup two batch files, or two different settings in one for two different cards?

I've tried running two cgminers and disabling one in each but the startup is a little strange so I'd like to start them running only the intended card, or with different settings for each. They are not the same card so I'd like to fine tune them a bit since the lower card is topping the upper card by 5x.
 
How can you setup two batch files, or two different settings in one for two different cards?

I've tried running two cgminers and disabling one in each but the startup is a little strange so I'd like to start them running only the intended card, or with different settings for each. They are not the same card so I'd like to fine tune them a bit since the lower card is topping the upper card by 5x.

Just put commas between the settings.

-I 13,20 --gpu-memclock 1650,1650 --gpu-engine 1100,1100
 
Just put commas between the settings.

-I 13,20 --gpu-memclock 1650,1650 --gpu-engine 1100,1100

Thanks, I had tried that earlier but I had a setting in there (-g?) that it didn't like so it crashed. I had assumed it was due to the multiple settings, but now I tried it with less settings and it worked. :thumbsup:
 
Thanks, I had tried that earlier but I had a setting in there (-g?) that it didn't like so it crashed. I had assumed it was due to the multiple settings, but now I tried it with less settings and it worked. :thumbsup:

I actually only use a couple of settings as threads and workers are automatically determined and fan speed isn't a concern as my cars stay around 70c.
 
Back
Top