Ok, I see what you mean. Basically, just saying if the coin goes up at some later date, you wouldn't necessarily be mining at a loss at that point, even though it would still be better to purchase the coins during the said time period.

LTC price is directly tied to BTC price so it's going down as well. I don't see the point of getting paid in LTC.

Hmm... $1.84 for 1mh on ltc per daily power cost $1.20, pool fee 0.04$ = profit 0.60 cents/day.

Methink some miners better turn off their mining machines.

Hmm I have a hang too at random times, with very nasty sound effects...
I have been looking at temperatures and both my CPU and GPU were acceptable, possibly some motherboard failure? I don't mind about myself just trying to help you.
You got a MSI motherboard by chance?

This has really been on my mind quite a bit recently as it really feels as if we are shooting ourselves in the foot! I don't know what the solution is though and what we need to watch for to establish wether or not profits will ever increase again.
It's already getting VERY close (few less BTC/Mh/Day) will mean power consumption vs. BTC earned will make this unprofitable and I really wonder if we will ever see an increase or if we are in the last vestiges of mining...
I sure hope not! Please someone give us hope lol.

Yeah, there isn't anything visible at all (this is *with* all processes shown for all users).

However I might be making some headway:
Previous settings:
GPU Clock Offset: 0
Memory Clock Offset: +500

I did this because I read somewhere that the GPU clock offset didn't seem to have much of an impact on hashing speed.

Anyway I just reset the memory clock offset from +500 to 0, and increased the GPU clock offset from 0 to 20. It was stable (but hashing slower). I cancelled Cudminer and it was responsive in closing. The system CPU usage wasn't through the roof after closing either. I repeated this with a GPU Clock Offset of 40. Same result. System fine. CPU usage looking healthy / normal.

I'm going to try to confirm this next, but this appears to suggest increasing the Memory Clock Offset puts a lot more pressure on the system both before and after(?!) mining.

Have you tried to look into the task manager just to see what process was causing that ? (can't be cudaminer if it is closed... could be windows explorer though... had something really strange yesterday while plugging my phone into my computer...)

Whenever I close Cudaminer (2012-02-28), my system becomes extremely sluggish (Win 7 x64). I was going to say that it seems to be MSI Afterburner that is the culprit but that might not be true. Before running Cudaminer it doesn't take up much CPU resource but after quitting Cudaminer, it fluctuates between 10 and 99%. Beforehand it's no more than 4-6%.

Here is the CPU usage after a fresh boot. It settles very quickly and stays low:



And this is minutes after I've closed Cudaminer *and* MSI Afterburner. Lots of spiking to 99% but it doesn't appear visible in the process list from what I can see.



The CPU is a single core AMD 2.8GHz Sempron but they run perfectly well with cgminer/sgminer/vertminer and AMD cards.

Any ideas?

Pass -H 2 aswell

What's your launch config?

Been away from the thread for a while. What's the average hashrate for scrypt on a 750ti atm? I'm getting ~300 on mine.

Check you clock speeds after CudaMiner errors out. When I get errors out of CudaMiner, my GPU goes to "2D" clocks and gets locked there. Another way to get out of that mess is to launch Device Manager and then disable and re-enable the offending GPU.

When Cudaminer does this, attempting to mine afterwards results in a very very low hashrate (usually ~27KH/s on Scrypt). Is there anyway to resolve this without having to reboot the computer?

2014-03-03 15:45:15] GPU #0: cudaError 30 (unknown error) calling 'cudaStreamQu
ery(context_streams[stream][thr_id])' (D:/Christian/Documents/Visual Studio 2010
/Projects/CudaMiner/salsa_kernel.cu line 958)

[2014-03-03 15:45:15] GPU #0: cudaError 30 (unknown error) calling 'cudaStreamWa
itEvent(context_streams[stream][thr_id], context_serialize[(stream+1)&1][thr_id]
, 0)' (D:/Christian/Documents/Visual Studio 2010/Projects/CudaMiner/salsa_kernel
.cu line 946)

[2014-03-03 15:45:15] GPU #0: cudaError 30 (unknown error) calling 'cudaMemcpyAs
ync(hash, context_hash[stream][thr_id], mem_size, cudaMemcpyDeviceToHost, contex
t_streams[stream][thr_id])' (D:/Christian/Documents/Visual Studio 2010/Projects/
CudaMiner/sha256.cu line 446)

6x 750 Ti's (OC'd to stable + BIOS Power Mod)

The bandwidth will also vary depending on the number of installed card.
My motherboard (Z77 G45), will allow one card to run at 16x bandwidth (pcie 3)
but 2 cards will run at 8x bandwidth
3 cards (using the pci-e 2.0) will make the first cards run at 8x bandwidth and the two other at 4x

I've now got 6 750 Ti's running on Win8 x64. I'm pretty disappointed.

1 Cards, OC'd, in x16 slot (running at x16): 320-330 kH/s [Total of 320-330 kH/s]
2 Cards, OC'd, in 2 x16 slots (each running at x8): 300 kH/s each  [Total of ~600KH/s]
4 Cards, OC'd, running on x1-x16 risers (each running at x1): ~270-280 each [Total of ~1100 kH/s]
6 Cards, stock, running on x1-x16 risers (each running at x1): 230-240 each (one runs at ~210 and is operating at PCIe 1.1 x1...whereas all the other cards are running at PCIe 2.0 x1) [Total of ~1430kH/s]

I haven't been able to get 7 Cards to show up in Windows...figure that it could be a MoBo/BIOS address space limitation.

I can't really apply any overclock at all when I have 6 cards loaded. MSI AB, GPU-Z, etc., all feel a little unstable when using. Applying even just +100MHz to MEMCLK will cause cudaminer to crash.

I have also noticed that my little G3220 is way too puny to run -H 1 flag.

Here are the flags I'm running -H 2 -i 0 -l T25x16

Will I see improved scaling in Ubuntu with cudaminer?

I'm thinking of returning all of these cards because 230 kH/s per card is not so great. If I was even hitting 280, I'd maybe be able to swallow this.

What is the primary factor here causing a scalability issue? Is it the PCIe operating mode? Is it Windows 8? Is it the Nvidia Driver? Is cudaminer not written to scale well past 4 GPUs?

Yes, I did try running 2 or 4 cards each in a separate cudaminer instance. While the system stability improved, the results yielded the same aggregate hash rate, and any attempts to boost any clocks cause a quick cudaminer crash.

If I can't get more out of these cards by Monday, I'll have to send them back to Newegg.