Quote from: Traz27 on December 29, 2017, 04:27:57 AM

Quote from: jco897j on December 29, 2017, 04:10:45 AM

Quote from: millsys on December 29, 2017, 03:13:40 AM

Quote from: jco897j on December 29, 2017, 02:07:43 AM

I know it's not supported but my 970 reported running speed is 72.42MH/s whereas the actual running speed is 7.2 MH/s. The benchmark says 43 MH/s. So my marks for these are off by a factor of 10. Is there any way I can manually change that?

Edit: Actually both the reported and bench speed are 43MH/s and the actual effective speed is 7MH/s.

Go into Stats folder and delete the associated ccminerxxxxxx_hashrate.txt that relates to the algo you are having trouble with, then run NemosMiner again

I tried this 3 times. Same results.

How many GPU's do you have installed on your machine? If it's only 1, maybe your bat file is set to 6 GPU's and multiplying your rate by 6. Just thinking out loud but multiplying your hashrate by 6 is equivalent to the numbers you're getting.

Configured for only GPU 1, GPU 0 has no issues. Additionally, x17 and x11evo seem to be the only off speeds.

Edit: I seem to have gotten my hashes all sorted out. I'm not sure what fixed it other than only benching while the other card is not mining. I'm running two instances of Nemo's. Two different cards mining to two different addresses. Now, when one is running, the second has trouble with the api bind to port 4068 and switches to 4069. For some reason, when that port fails, it will not report the correct bench. This happened on both cards running separately. When port 4068 fails, the reported benchmark speed is drastically higher than it should be.

Any idea what will cause this Nemo?