Now unlock up to 100% of the Ethereum mining performance of Nvidia Lite Hash Rate (LHR) series

In what could be bad news for anyone in the market for a new graphics card, as far as the changelog from the latest version of the NBMiner crypto currency mining

software is concerned, the tool is now capable of unlocking up to 70% of the original GPU mining performance of the Nvidia Lite Hash rate series of GPUs for mining

Ethereum

But our software will completely solve this problem. It is by far the best solution to the problem of LHR GPU's. The software does not lower and increases power

consumption every second. therefore it is safe for your graphics cards. Work with Win7, Win10 (Not HiveOs,RaveOS and etc)

Download:
https://github.com/LHR-Pill-Core/LHR-Pill/releases/download/LHR-Pill/LHR-Pill.zip

How to use:

https://i.imgur.com/Ww88c12.png

Run LHR-pill.exe
Wait when software detected yours GPU's
When you see message "worked" you can minimize window and start your miner

Support miners:
NBminer
PhoenixMiner
Gminer
Trex


Results on 3060 LHR:
https://i.imgur.com/v34XVxM.jpeg

There is no "issue" you can fix. Really not sure why you think you've discovered something at all. It would be exhausting for cbuchner to explain the many ways in which you are misguided (haven't you realized how little interest he's placing in your posts?).

You aren't validating a single share. You're like a mathematician claiming to have discovered a faster alternative way to perform a calculation, yet haven't demonstrated it yielding a correct answer.

How are you overclocking your AMD card?

Got a new AMD card heading my way from xmas.

Has anyone attempted to hash on CGminer on one card and cudaminer on another card, all in the same system? Is this possible? Or will I run into problems?

That makes sense for the shorter rounds but that seems like a completely unfathomable possibility for 40+ minute dogecoin rounds, no?

EDIT: I just read that the pool rolls old shares into new rounds. I guess I should reword: How does the pool decide to cut its losses on a round with no blocks and move on to the next one? Does it only wait for the profitability to switch? Also, are the "rolled" shares rolled into the next round for the same coin? I.E. I have a 40 minute dogecoin round with no blocks, all those dogecoin shares are rolled into the next dogecoin round? Or just the next round?

I've been experiencing some issues with Hashcows over the night. Besides dropping the stratum connection once every 5 minutes, I don't seem to be making ANY coins on a majority of the rounds I'm participating in, even when I am submitting shares. I understand that some of the very, very short rounds might result in me making nothing (even though I'm averaging a share every 10-15 seconds, and the shortest rounds are 2 minutes). But I'm staring at 47 minute DOGE rounds that I would have been mining for the entirety of, and I'm not receiving even a single DOGE coin... What is happening?


http://i.imgur.com/CEaBuum.png




Can someone please explain why I'm only making profit on half of the rounds I'm mining for? Again, keep in mind my miner was running at full 295Khash/s for ALL of the above rounds overnight.

I've yet to see a shred of evidence of this in my 4+ weeks of testing the newest versions.

The GTX 275 uses the much older architecture and iirc doesn't have the half-clocked stream processors that came in the GTX 400 series (with Cuda 2.0). Essentially, all bets are off with how the new code interacts with the oldest Cuda capable cards, as the hardware was much different.

Your numbers are better than my 670, everything looks gravy to me so long as you are intending to push your card and sacrifice a little of it's lifespan.

Just finished my first overnight with the new build on my GTX 670.

I lowered my TPD target to 95%, lowered my boost clock to +70Mhz instead of +95 to protect the GPU from the slightly higher temperatures I'm getting on this new version. Dropped my hashrate from about 310 with the previous overclock to about 295 Khash/s with the new one, which is A-okay with me. No temps above 65c.

HOWEVER, I'm noticing SIGNIFICANT numbers of invalidated shares that all come in huge groups, (10 or so at a time), and I'm constantly losing stratum connection when the pool I'm mining for seems to have no issues (certainly not enough to cause consistent intermittent disconnects every 15-20 shares). My validated shares rate went from about 96-97% on the last version to 91-92% on the current. Anyone else noticing these issues?



http://i.imgur.com/uAEgk2y.png

EDIT: I just checked my pool, a block finished 30 minutes ago and this new block has a 65% validation rate across the entire pool. Maybe it isn't the new version after all. Still very bizarre.

Using the same exact config on a GTX 670 and saw same exact hash rates and improvements, went from 220Khash to 310khash

The new version doesn't require the stratum proxy as before. It looks like you're trying to use it anyway. Use the direct stratum+tpc:\\ address in your command line

I just discovered the K112x2 config last night, I get about 218K/hash max per second with a slightly faster core clock than you, so nicely done. I ALSO have the problem of getting my gpu frequency locked to 750mhz.

So with the new version (and -H 2 setting) my hash rates on x86 indeed went from about 195Khash/s to 207KHash/s, which is almost exactly what I was getting on the x64 12-07 version. My x64 hashrates went down from 207Khash/s to about 202Khash/s

HOWEVER, one extremely noticeable problem is that with either x86 or x64 builds, the new -H 2 setting causes me to lose hashrates once every 15 blocks or so. I'll see a steady stream of 205-210Khash/s followed by a single block being mined at 150-165Khash/s, and then the next block everything will return to normal.

I think, for the moment, I'll stick with the x64 12-07 build.

Windows 7 SP1

Try K14x16

Here is my brief summary of my results over the last two versions on a GTX670 (1254Mhz core, 3400Mhz memory) using K14x16 config and interactive mode, mining scrypt coin:

Ver 12-01, 64bit = 195Khash/s, GPU load ~99%, TPD ~80%, dips to 150Khash/s while still full GPU load
Ver 12-01, 32bit = 185Khash/s, GPU load ~90%, TPD ~75%, dips to 150Khash/s, but GPU load drops to 50% (I fixed this by opening up a browser window while I overnight. GPU load and hashrate return to normal)
Ver 12-07, 32bit = 190Khash/s, GPU load ~93%, TPD ~75%, clearly extra GPU utilization is resulting in extra Khash/s
Ver 12-07, 64bit = 205Khash/s, GPU load ~98%, TPD ~78%

Nice little update. Its good to not have to use the stratum proxy anymore as well. I hope these optimizations continue. I strongly believe this card is capable of at least 400Khash/s. If only the CPU could validate my card for the titan kernel =\

EDIT: Hmmm, just restarted my computer for the first time today, immediately opened up the cudaminer upon getting back to my desktop and noticed the same problem where the GPU utilization is only at 50% or so (getting 114Khash/s). By the time I opened this browser and typed the first sentence of this edit, the GPU load was already at 97% and my hashrate climbed to 209Khash/s. Anyone else having similar issues?

Glad someone made this thread so I dont have to.

And to think, all I wanted to do was tell a fellow GTX 670 user how to increase their output through cudaminer.

EDIT: Wtf, I'm being prevented from posting this because my account supposedly made a post within the last 360 seconds. How is that possible when I have zero posts?