Nexus - Pure SHA3 + CPU/GPU + nPoS + 15 Active Innovations + More to Come

[dbt1033]

As someone else mentioned your hashrate is low, a 280x gets 42mh.  I think u need to use different dll's as suggested, Mummus posted details somewhere around page 80 of this thread.

I downloaded this - https://mega.nz/#!4Ydz1S6D!byZ_Q1IrtfQMi_TBGssvfJtEmwyeBEoKdpJjMk0CIJA recommended by COOLERbyPSP and was told to put in the root of the gpu miner, but all it did was crash the miner when i ran it.

Are they the right dll's and am I meant to put them else where?

What you have downloaded is similar to what I downloaded, here is the link to the post I used https://bitcointalk.org/index.php?topic=657601.msg9991629#msg9991629

I'll check that out when I get home from work... thank you


Update:  All it did was crash my miner.  Maybe the kernel isn't optimized for tonga based gpus yet...

I've played with thread concurrency, threads, worksize, etc...  to no avail.  Stuck at 50 mh/s with 2 R9 380's.  Maybe it's the best they've got

[dbt1033]

Is there a GPU miner for prime clusters?

[cestballot]

Happy One Year Anniversary to Nexus aka Coinshield !

 

We are Nexus

[merc84]

R9 380's got 24 mh/s each (pretty disappointed in this figure)
FX 9590 Pulled around 300 PPS in the cpu channel

Which driver, version really does matter. You can add the dll's to the same folder as the miner to save re-installing drivers.

[calem]

I'll try https://mega.nz/#!6c1zTarR!qzIYqEMj-LclQUO-Ykv59Mc1w64nPOZEVbHkbBavBQU and see if that works.

[calem]

Is there a GPU miner for prime clusters?

Not to the best of my knowledge.

[Conqueror]

Happy One Year Anniversary to Nexus aka Coinshield !

 

We are Nexus

What the hell, Nexus was Coinshield before?

[bittamak]

Happy One Year Anniversary to Nexus aka Coinshield !

 

We are Nexus

What the hell, Nexus was Coinshield before?

Yes...it got rebranded as Nexus.

[calem]

Which driver, version really does matter. You can add the dll's to the same folder as the miner to save re-installing drivers.

I dropped the 14.9 amldocl64.dll into the root suggested my mummus and once again it crashed the miner. I'm guessing it wont try use it if I put it into any sub folders like resources etc.

There's no flags needed in the batch in right?

I could try simply reverting the systems drivers as opposed to dropping into the miner. Might be a windows 10 thing?

[dbt1033]

R9 380's got 24 mh/s each (pretty disappointed in this figure)
FX 9590 Pulled around 300 PPS in the cpu channel

Which driver, version really does matter. You can add the dll's to the same folder as the miner to save re-installing drivers.

I did add the dll's to the same folder as the miner...  i dunno about what version, it's late, and I've been drinking lol

Whatever the newest driver for windows 10 is.

[dbt1033]

Happy One Year Anniversary to Nexus aka Coinshield !

 

We are Nexus

What the hell, Nexus was Coinshield before?

Development goals outgrew the scope of the coinshield project...where you been?!

[calem]

R9 380's got 24 mh/s each (pretty disappointed in this figure)
FX 9590 Pulled around 300 PPS in the cpu channel

Which driver, version really does matter. You can add the dll's to the same folder as the miner to save re-installing drivers.

I did add the dll's to the same folder as the miner...  i dunno about what version, it's late, and I've been drinking lol

Whatever the newest driver for windows 10 is.

I dropped in the 14.9 amd_opencl64.dll on its own, no other drivers, and now it actually runs.. But theres no increase in performance beyond my reported ~16.1MH/s

I'll try messing around with other combinations of drivers, but so far this is the only one ive seen not crash.

[calem]

Well, I think I've found the sweet spot for the Gigabyte R9 270 OC edition. The drivers suggested in this thread have done nothing but made the miner crash with the exception of the singular 14.9 amd_opencl64.dll (which I'm leaving in there just cause).

Using GPU-z to match "gpu-engine" : "975", "gpu-memclock" : "1400" and "gpu-shaders" : "1280" and lowering "intensity" : "21" with all other values default, the miner runs at 16.2MH/s with a variance of +-0.1

I'm ready to move onto the 780ti now.. This should be interesting.. xD

[COOLERbyPSP]

Might be a windows 10 thing?

Yes

[calem]

Might be a windows 10 thing?

Yes

Maybe dropping the dll's into the root of the miner is causing the issue.. Damn you microsoft. This is why I moved to ubuntu on my new main machine when you killed my old one.. Literally.. Killed the hdd, I even though said no to the update but it shoved it down my throat in case i would say yes and put win 8.1 into an ilod.. woot :/

I think I will need to rollback the actual systems amd drivers to 14.9 then.. Meh, I'll be moving to 780ti anyways, I just wanted to see what I could pull from the 270. Never should have bothered swappin out to the spare card to begin with.

Well movin on. Up next, CUDA fun!

[dbt1033]

Well, I think I've found the sweet spot for the Gigabyte R9 270 OC edition. The drivers suggested in this thread have done nothing but made the miner crash with the exception of the singular 14.9 amd_opencl64.dll (which I'm leaving in there just cause).

Using GPU-z to match "gpu-engine" : "975", "gpu-memclock" : "1400" and "gpu-shaders" : "1280" and lowering "intensity" : "21" with all other values default, the miner runs at 16.2MH/s with a variance of +-0.1

I'm ready to move onto the 780ti now.. This should be interesting.. xD

All you're doing in GPU-z is discovering the stock clocks of your cards....

Not exactly the best for max hashrate. 

[calem]

All you're doing in GPU-z is discovering the stock clocks of your cards....

Not exactly the best for max hashrate. 

What cards do you have and what is your best rates you get from them?

[dbt1033]

All you're doing in GPU-z is discovering the stock clocks of your cards....

Not exactly the best for max hashrate. 

What cards do you have and what is your best rates you get from them?

R9 380s... about 25 mh/s.

I would increase your gpu-engine.  Mem-clock doesn't matter too much with this hashing algo.  Underclocking memory might actually help with heat.

You may also want to set gpu-powertune if you increase the engine.

[merc84]

All you're doing in GPU-z is discovering the stock clocks of your cards....

Not exactly the best for max hashrate.  

What cards do you have and what is your best rates you get from them?

R9 380s... about 25 mh/s.

I would increase your gpu-engine.  Mem-clock doesn't matter too much with this hashing algo.  Underclocking memory might actually help with heat.

You may also want to set gpu-powertune if you increase the engine.

25Mh/s still seems low for r9 380.

[dbt1033]

All you're doing in GPU-z is discovering the stock clocks of your cards....

Not exactly the best for max hashrate.  

What cards do you have and what is your best rates you get from them?

R9 380s... about 25 mh/s.

I would increase your gpu-engine.  Mem-clock doesn't matter too much with this hashing algo.  Underclocking memory might actually help with heat.

You may also want to set gpu-powertune if you increase the engine.

25Mh/s still seems low for r9 380.

My thoughts exactly.  Miners aren't optimized for tonga architecture yet...maybe they will never be.

If you have any thoughts as to what I can do to boost this, I'm all ears