Claymore's CryptoNote AMD GPU Miner v11.3

[xnbya]

Troubleshooting:
Hey all I have a problem and that I was hoping someone could help me with.  It appears I have done everything right with this miner and it seems to mine but neither my wallet nor my associates ever receives any Monero.  Here’s the code we used, I’m running v9.0 on Windows 7 SP1, none of the cards are overclocked, is rebooted a couple times a week
   
“setx GPU_MAX_ALLOC_PERCENT 100
NsGpuCNMiner.exe -o stratum+tcp://erebor.dwarfpool.com:8050 -u wallet -p hossflat12@gmail.com
-o stratum+tcp://moria.dwarfpool.com:8050 -u wallet -p hossflat12@gmail.com -tt 80 -dbg 1”
Any help would be greatly appreciated

Did you try to use -o stratum+tcp://xmr-eu.dwarfpool.com:8050

I'll try that right now.....not to be a noob but how does that change things?

alright it mine's to my address, which I set up through the windows wallet GUI, but my associates account is through poloniex and does not receive any coin.  Does anybody know if there's something special I have to do with a poloniex wallet in the wallet address?

I do not believe you can mine directly to a Poloniex wallet. Most exchanges do not allow this as they may use different mechanisms internally to credit you account.

For example, Poloniex requires you to also associate a payment ID to ensure your transaction is applied correctly to your account, as seen on the warning by your deposit addresses: "Deposit: You MUST send your deposit using the Payment ID below, or it will not be credited.".

From your postings, it looks like you attempted to append your transaction ID to your wallet address using the "." separator. According to DwarfPool FAQ, this is to allow you to know which rig you are monitoring if you have several rigs using the same wallet address. Per their FAQ:

Code:

Miner example

Command line for TAC with monitoring of 777th rig

sgminer -k nist5 --no-submit-stale -o "stratum+tcp://erebor.dwarfpool.com:3350" -u COIN_WALLET.777 -p your@email.com
 --failover-only -o "stratum+tcp://moria.dwarfpool.com:3350" -u COIN_WALLET.777 -p your@email.com

I do not think this was intended to allow for payment IDs. Your best bet is to continue to mine to your wallet on your PC, as you indicated that works for you, and perform any transfers to exchanges manually.

On minexmr.com you can mine directly to poloniex using EXCHANGE_WALLET_ADDRESS.payment_id as your username, eg
 

Code:

miner -o stratum+tcp://pool.minexmr.com:4444 -p x -u 47sghzufGhJJDQEbScMCwVBimTuq6L5JiRixD8VeGbpjCTA12noXmi4ZyBZLc99e66NtnKff34fHsGRoyZk3ES1s1V4QVcB.db2d0c4047161038b59f5866f2c385a4d3d274984f86791c99f576a3b4265d56

and the payments will be sent directly to the exchange with the specified payment ID once you have reached >10xmr.

[muchoman]

Strange error on latest miner, linking two modules of different data layouts.

[Claymore]

Strange error on latest miner, linking two modules of different data layouts.

Add this to .bat:

setx GPU_FORCE_64BIT_PTR 0

[muchoman]

Strange error on latest miner, linking two modules of different data layouts.

Add this to .bat:

setx GPU_FORCE_64BIT_PTR 0

Still same error.

[mafostedu]

Strange error on latest miner, linking two modules of different data layouts.

Add this to .bat:

setx GPU_FORCE_64BIT_PTR 0

Claymore there is some issue with the version 9 & 9.1 (I mentioned earlier also) I have been testing your miners in several different conditions.
I also mine with my CPUs with your CPU miner (with only 3 threads out of 4 on my i5). So when I use version 6.1 there is no issue with any of my rigs for days, but when I use 9 or 9.1 along with CPU miner, the GPU miner crashes in less than 12 hours most of the time. Also, I must run the GPU miner first & then CPU miner. If I run CPU miner first & GPU miner later, the system crashes in no time. If I run only GPU miner with version 9 & above, usually it works stable without any such issue. Actually I noticed that most of the time GPU miner crashes because CPU miner is already running & GPU miner starts to restart the mining process (through watchdog).

System config for all 5 rigs :: Win 8.1 Pro + 13.2 Catalyst with 8 GB RAM, 4x 290 Trix + Core i5 4670.

[Claymore]

PM me to test an updated debug version.

[buy-black]

Dear Claymore:

Out of the blue my miner stop working version ClaymoreCryptoNoteGPUMinerv61Beta
An error window pops up and says NsGpuCNNMiner.exe application error  The app could not start correctly (0xc000007b).  Click to accept and close the program.
I am sure something change in my system but dont know what.
win 7 16 GB ram i7 950 cpu
amd r9 280x  with 14.9 catalyst.

system had been working for 1 month without any problems...

I can run the cpu miner OK but my GPU will not run..  I can mine x11 with same gpu and sgminer_v5_0_mod without any problems, so gpu is ok.

I updated to new version 9.1 but the same error appears.

Thanks for your help

[abora]

Can anybody convert this to gui miner for me because i am yet to understand the settings for other type of mining.

[bensam123]

So, I'm curious, why would my hashrate fall poolside since 8.0? With 9.0 it went down a little bit, and a little bit more with 9.1... Now it's no where close to what I was getting a month ago. The miners show hashrates about 30% higher then what the pool does, I'm mining on dwarf pool as well.

[Claymore]

An error window pops up and says NsGpuCNNMiner.exe application error  The app could not start correctly (0xc000007b).  Click to accept and close the program.

Usually this error means that Windows cannot start application because some required DLL is missed. Miner does not require any specific DLLs, you can use Dependency Walker to see what DLLs are required:
http://stackoverflow.com/questions/10492037/the-application-was-unable-to-start-correctly-0xc000007b

[Claymore]

So, I'm curious, why would my hashrate fall poolside since 8.0? With 9.0 it went down a little bit, and a little bit more with 9.1... Now it's no where close to what I was getting a month ago. The miners show hashrates about 30% higher then what the pool does, I'm mining on dwarf pool as well.

1. Make sure you don't use any proxy or pools that remove dev fee, check readme for details.
2. Try some other big pool.
3. If pool supports fixed diff, set it to 10000-20000 and see hashrate on the pool. Many pools set very high target diff to reduce server load, for example 250000. Such high target means that miner will send shares very rarely, for example, if your hashrate is 2KH/s it will take >2 minutes to find a share at 250K target diff. Pool calculates hashrate within some time, at too high target diff this time is similar to average time to find share and becomes inaccurate, as result sometimes you see low hashrate and sometimes you see too high hashrate, it depends on miner luck for this time period.

[buy-black]

An error window pops up and says NsGpuCNNMiner.exe application error  The app could not start correctly (0xc000007b).  Click to accept and close the program.

Usually this error means that Windows cannot start application because some required DLL is missed. Miner does not require any specific DLLs, you can use Dependency Walker to see what DLLs are required:
http://stackoverflow.com/questions/10492037/the-application-was-unable-to-start-correctly-0xc000007b

I used the Dependency Walker and found that IESHIMS.DLL and GPSVC.DLL are missing.  I recently unistalled some nvidia drivers that I dont use so maybe this is the cause of these missing dll?
I am scanning the computer for viruses etc.  Later I will uninstall and re-install the amd drivers to see if this fixes the problem.
Thanks

[buy-black]

An error window pops up and says NsGpuCNNMiner.exe application error  The app could not start correctly (0xc000007b).  Click to accept and close the program.

Usually this error means that Windows cannot start application because some required DLL is missed. Miner does not require any specific DLLs, you can use Dependency Walker to see what DLLs are required:
http://stackoverflow.com/questions/10492037/the-application-was-unable-to-start-correctly-0xc000007b

I used the Dependency Walker and found that IESHIMS.DLL and GPSVC.DLL are missing.  I recently unistalled some nvidia drivers that I dont use so maybe this is the cause of these missing dll?
I am scanning the computer for viruses etc.  Later I will uninstall and re-install the amd drivers to see if this fixes the problem.
Thanks

Re-installed amd drivers.  Problem fixed. Thanks

[phzi]

V9.1 and V7 both segfault on my gentoo machine with v13.12 drivers.

It mines for a seemingly randomly amount of time before this happens (typically 3-10 seconds).

dmesg snip:
[   40.414308] miner[3190]: segfault at 204a000 ip 00007f6bd45223a6 sp 00007f6bb5ffa288 error 4 in libc-2.16.so[7f6bd43ed000+19e000]
[  105.256506] traps: miner[3226] general protection ip:7f60d85f54e7 sp:7f60b3ffe060 error:0 in ld-2.16.so[7f60d85ec000+22000]
[  122.109788] miner[3245]: segfault at 204a000 ip 00007f7d652053a6 sp 00007f7d2bffe288 error 4 in libc-2.16.so[7f7d650d0000+19e000]
[  145.624938] miner[3268]: segfault at 204a000 ip 00007fbf96ace3a6 sp 00007fbf5bffe288 error 4 in libc-2.16.so[7fbf96999000+19e000]

Logs always show this last before the crash:
10:38:50:408    ea7fc700        Share accepted
10:38:50:408    ea7fc700        remove first packet -1

I presume -1 is an error, because normally this is a positive numeric value.

---
Update/edit:
I switched to another pool, and I haven't seen a segfaults yet.  I was initially testing with backup-pool.com with very low starting share target.  There's definitely a bug in the miner causing crashes, but it seems you can mitigate it (or at least, cause it to occur significantly less frequently) with higher share targets (less shares sent/received).  backup-pool on a higher starting difficulty port is running for 15min now.

[bensam123]

Putting aside hashrate increases, is any work being done to reduce power usage / increase efficiency?

[Vanderi]

Putting aside hashrate increases, is any work being done to reduce power usage / increase efficiency?

Hey good question, I think the code could be improved.

[Claymore]

V9.1 and V7 both segfault on my gentoo machine with v13.12 drivers.

It mines for a seemingly randomly amount of time before this happens (typically 3-10 seconds).

PM me the log, I'll check it.

[BitmoreCoin]

Putting aside hashrate increases, is any work being done to reduce power usage / increase efficiency?

Power usage is the same as before.

[phzi]

V9.1 and V7 both segfault on my gentoo machine with v13.12 drivers.

It mines for a seemingly randomly amount of time before this happens (typically 3-10 seconds).

PM me the log, I'll check it.

As I wrote above, the logs look totally normal up until:
remove first packet -1

And that is always the last line in the log when this happens.  You see tons of other "remove first packet" lines before, but all list positive numbers.  Without ever seeing the code, I would wager that null/false/-1 is being returned somewhere.

Putting aside hashrate increases, is any work being done to reduce power usage / increase efficiency?

Power usage is the same as before.

Curiously, on my R9 290s running the STILT's custom mining, the -a 2 "low power consumption mode" actually produces slightly better hashrates, that are MUCH more stable, AND drops the power consumption.

Pretty cool, mining XMR is actually profitable vs power right now for me.  Cheers to Claymore.

[bensam123]

I've used -2 and while it used to produce relatively similar hashrates at less power, it produces almost identical hashrates of -1 or -4 and the power consumption is almost identical using a kill-a-watt meter.

I wasn't asking about the current version though, I was wondering if Claymore was considering working on power consumption.