Quick note for anyone wondering about my config that I tested this miner on:Windows 7 x64 Ultimate
Latest AMD Driver (Crimson 16.10)
GTX 1080 and RX 480 installed (1080 attached to display, RX 480 not connected to display, platform 1)
RADEON 7970 are MURDERING this coin at 800MH/S
what intensity?
Everything is default.
Doesn't work on RX470/RX480
Does it give any kind of an error, or just crash?
I can get it to mine with 1 GPU, but the other 3 don't run. Trying to set up another user account now and syncing the wallet to test if it will work for targeting the 2nd GPU. Opening multiple miners with different device targets didn't work on an account together. The first card runs at 100%, but the others are at 0% doing nothing. Also noticed when I find a nonce it finds and submits the same nonce 6 or 7 times in a row.
If you're seeing duplicated nonces, try decreasing intensity and/or cyclesize.
So the benchmark only works on 1 GPU, cant test on any other GPUs.
Good catch--unfortunately probably can't fix for the next few days, since I'm traveling. If anyone else has Visual Studio or similar set up to compile AMD OpenCL host code (aka AMD app sdk installed, IDE configured), they could follow the instructions in the readme to make the benchmark version. Additionally, anyone can open the .cl file and change the single F in the targetY = 0xF0000000 line, which will make shares go 16x faster. Then mine with the normal miner, and divide the output number by 16 to get actual hashrate (but shares will be fast enough to work for benchmarking purposes, just not as nice).
This coin is very good with Tahiti based GPUs like 7950 / 7970 / 280X
Bad for 290 / 470 / 480 / Any Pitcairns
That's really weird--I developed and tested the miner only on an RX 480 system. Maybe those GPUs had better instruction sets for mining, or the compilers from OpenCL to device kernels were better optimized for mining on older devices where SHA-256 mining was more relevant and AMD developers wanted to get more of an edge for their cards to increase sales?
@Vorksholk
Hey mate , My 480s are crashing all the time , Ive tried everything ( underclock , undervolt , etc) , bur did not try change the driver.
Which driver you are using ?
Crimson 16.10, does it give any kind of error or just crash? Did you make sure your device and platform arguments were correct?
Thanks, Vorksholk!
My R9290X (Hawaii) crashed quickly for all intensities from 23 down to 10. It seems to be stable at intensity 4, running cool at over 80% GPU usage.
I'll start working intensity back upwards again Real Soon Now to find a sweet spot.
Edit: Update - intensity 9 looks stable, whereas 10 was not in an earlier test. I'll do more careful checking as time permits, but for now the sweet spot for this rig seems to be i9.
Huh, what hash rate are you getting at intensity 9 on that card?
help me please
![](https://ip.bitcointalk.org/?u=http%3A%2F%2Fimages.vfl.ru%2Fii%2F1477214551%2F63591036%2F14631546.jpg&t=665&c=PUXLRmAmB2LewA)
i don't understand that characters..read the readme file of the miner.
install the latest java run time environment so you can run "PascalProxyv2.jar" and input the right syntax (it is in the readme.txt file)
![](https://ip.bitcointalk.org/?u=http%3A%2F%2Fimages.vfl.ru%2Fii%2F1477222462%2F83c968a4%2F14633070.jpg&t=665&c=iZCyfxxbxS65bw)
I did everything according to the instructions but I did not start out miner
Yeah, the miner name you set in the Pascal Wallet needs to be 8 characters, it's not the name of the miner .exe file itself.
I can only assume someone is attacking us again with huge hashing power. 4X increase in less than 3 hours. I put 6,000 MHs on mining and haven't gotten a block in 3 hours...
Attacking... or just mining a ton for their own benefit. Probably just someone with a large AMD farm who wants some Pascal
![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
------------------------------------------------------------------------------
For anyone interested, the current difficulty (2Cxxxxxx) implies a network hashrate of ~58 GH/s, and the current blockrate at this difficulty implies a hashrate of ~100 GH/s. That's about 512x the speed of a few weeks ago.