Show Posts
|
Pages: « 1 [2] 3 »
|
I acquired some GTX 750Ti 2GB but I can't seem to set them up properly. The best I did was : cudaminer.exe -a scrypt-jane:14 -o stratum+tcp -u user -p X -b 4096 -m 1 -i 0 -L 6 -l t96x1 Which gives me only around 2,5 kH/s they should be doing more than 3k at this freq. GPU 1350MHz, MEM 1525MHzI have 5 cards running on 4G of RAM Does anyone have some other settings Try these: cudaminer -s 10 --algo=scrypt-jane:UTC -H 2 -i 0 -m 2 -l t25x4 -L 4 -b 16384 getting around 3.3-3.35 with those settings. 6 cards, win7 64bit, latest drivers, 8 gigs of ram Thanks! I did not found a solution to my problem, but a workaround! It appears for some reason when I go above -l t24x2 with -L 4 the dirver crashes only on my Windows 8 rigs. IDK if it is a bad Windows, or something else, but I could not fix it. I installed Windows 7 + Visual C 2010 + 337.88 drivers, and everything is working perfectly! I am using now: -L 4 -l t60x2 -H 2 -m 1 -i 0 which gives me around 3.6kH/s @ 1222/1500 MHzSo it was somehow windows 8 that caused the issue. Glad you found a way to get around it. By the way - what miner, and version are you using, since my cards do around 3.3 with 1330 core and the latest drivers?
|
|
|
I acquired some GTX 750Ti 2GB but I can't seem to set them up properly. The best I did was : cudaminer.exe -a scrypt-jane:14 -o stratum+tcp -u user -p X -b 4096 -m 1 -i 0 -L 6 -l t96x1 Which gives me only around 2,5 kH/s they should be doing more than 3k at this freq. GPU 1350MHz, MEM 1525MHzI have 5 cards running on 4G of RAM Does anyone have some other settings Try these: cudaminer -s 10 --algo=scrypt-jane:UTC -H 2 -i 0 -m 2 -l t25x4 -L 4 -b 16384 getting around 3.3-3.35 with those settings. 6 cards, win7 64bit, latest drivers, 8 gigs of ram
|
|
|
GLTA, Im out, does not pay to mine this coin anymore. This last fuck up by tumbling block..was the last straw. Not wasting my electric anymore..
More coins for us I guess ...
|
|
|
utc2.tumblingblock.com is working fine on my ATI miners. On NF14 and accepting shares as intended.
|
|
|
The mass changing of the addresses, combined with no lockdown on the accounts point towards a direct database injection (also known as SQL Injection). Chris mentioned that he will be doing some migrating on the website, that of course includes databases migrating. I highly doubt this was malicious database injection and most likely the actuall reason is an error during the migration or some wrong command executed.
|
|
|
Just received payment.
LTC? how much? The payment was in LTC - yes. I'm not comfortable in sharing amounts ... etc.
|
|
|
fully paid by now (except for ref payments, no idea when that is supposed to come through..) Usually - monday.
|
|
|
You received just a fraction maybe because the payment was till 10th of Dec. You can see that in your account - (Dec 4 - Dec 10) referrals payout . Anything past that date is still to be paid.
|
|
|
Start using the other 3 exchanges. Its not good for a coin to be dependent on only one exchange. Remember that ultracoin was not always traded on craptsy!
|
|
|
I'm still waiting for my payout, I'm upset about this and Chris' "news" are no relief. Now it's my fault as my account is suspicious, or what? I didn't change my payout address or payout method for many weeks, but now I'm told the delays are basically my own fault because I made "last hour address changes". True, ltcgear provides a good ROI opportunity, but what is going on here is customer deterrence instead of customer service. If (and I say if) I'll eventually get any of my payout, I will certainly think twice if I'll reinvest here or not. I completely understand you. However, no1 said it is you that did some last minute changes to your account or you made it look suspicious. There are a lot of ppl confirming that they payout addresses were changed somehow, so accounts with such issues were audited manually. Accounts with many login attemps from different IP addresses are being investigated manually aswell. Chris is implementing a mail confirmations upon changing addresses in the accounts. The update will be live soon.
|
|
|
This is relevant aswell:
"Hi,
There are still some payments waiting to be verified and sent.
" share payout while BTC was indicated?" - as I explained earlier, there was suspicion about minute changes before payout, so parameters like address and coinchoice were extracted from backups. If payout was executed in shares, it probably means the user chosen shares then he may have changed his minds and changed to BTC.
What else is left missing (which is narrowed to percents of customer base) - it was really suspicious and requires address setup under new policy / address change mode."
|
|
|
Chris made some posts and answered some questions on litecointalk, for the people that still have no payment - he is doing manual audit on some accounts with suspicious activity and that costs time.
can you pls link that posts? I`ll paste just this one: "Hi david. There is no miss. There was some suspicions regarding last hour address changes so a more safe payment procedure was used. In many cases the payment was manually verified before allowing it to process. Also, delaying payments for new addresses was happening before, it was not used for a while (for certain reasons), but, if suspicious activity is detected, it would be used again. "
|
|
|
Chris made some posts and answered some questions on litecointalk, for the people that still have no payment - he is doing manual audit on some accounts with suspicious activity and that costs time.
|
|
|
UTC dev team have no way to put a pressure on Craptsy devs/support/coders in order to speed up the things. So the only thing we are left with is waiting. Meanwhile all of us can trade on bittrex if needed. I know that the volumes there are not as big as craptsy but still it's an option we have.
|
|
|
Cryptsy is still offline, I think bittrex is updated.
|
|
|
Windows V.733.1 does not work. Worked at first for two days then took an hour but now won't open at all.
Mine works fine since I've updated it. On 5 machines everything is running without issues.
|
|
|
|