[LOCKED] cpuminer-opt v3.12.3, open source optimized multi-algo CPU miner

[neguinho]

Cpu miner for windows 7 i7 2630?
Omo uses a command line
 
cpuminer-aes-avx2.exe -a scrypt -o stratum+tcp://aikapool.com:7962

[1714060229]

1714060229

[1714060229]

1714060229

[1714060229]

1714060229

[joblo]

Cpu miner for windows 7 i7 2630?
Omo uses a command line
 
cpuminer-aes-avx2.exe -a scrypt -o stratum+tcp://aikapool.com:7962

cpuminer-aes-avx.exe

[buckya]

Hey
At first I'd like to thank You for doing great job, keep up the good work.
I'm currently testing monero mining on FX8320 clocked at 4,1 GHz.
With newest cpuminer-aes-avx.exe i've got better hashrate that with cpuminer-multi.
On 8 threads it goes to 312 H/s on iddle (Win7).
And with only 4 threads tweaked in task manager to use only cores 0, 2, 4 and 6 i got this:

[2017-04-03 18:29:17] CPU #2: 863 H, 58.18 H/s
[2017-04-03 18:29:17] CPU #0: 839 H, 57.07 H/s
[2017-04-03 18:29:17] CPU #1: 844 H, 58.12 H/s
[2017-04-03 18:29:17] CPU #3: 905 H, 60.01 H/s
[2017-04-03 18:29:56] Accepted 38/38 (100%), 4898 H, 232.88 H/s - opened browser with 30+ tabs.
On iddle its going to 248 H/s

I wasn't connecting any power meter but i guess there will be much less power draw on 4 cores.
And here i've got a question about  "--cpu-affinity", I don't know how to use it with "--threads 4", so it would direct all work to cores 0, 2, 4, 6 like I'm doing this in Task Manager, but only after launching the .exe
The are some hex parameters which I don't understand like 0xF0F0 or 0x30, I tried use them without effect.
Can You give me some advice ?

[coinbutter]

joblo, trying this version of cpuminer for pool mining dmd-gr - Diamond Coin but my shares keep getting rejected. cpuminer-multi works without problems. Running a Xeon X5687 with the cpuminer-aes-sse42 windows binary. Any suggestions?

Edit: buckya, I use the CPUMiner Affinity Setter at https://www.paulhempshall.com/io/cpuminer-affinity-setter/ to determine my cpu affinity.

[onedeveloper]

Hey
At first I'd like to thank You for doing great job, keep up the good work.
I'm currently testing monero mining on FX8320 clocked at 4,1 GHz.
With newest cpuminer-aes-avx.exe i've got better hashrate that with cpuminer-multi.
On 8 threads it goes to 312 H/s on iddle (Win7).
And with only 4 threads tweaked in task manager to use only cores 0, 2, 4 and 6 i got this:

[2017-04-03 18:29:17] CPU #2: 863 H, 58.18 H/s
[2017-04-03 18:29:17] CPU #0: 839 H, 57.07 H/s
[2017-04-03 18:29:17] CPU #1: 844 H, 58.12 H/s
[2017-04-03 18:29:17] CPU #3: 905 H, 60.01 H/s
[2017-04-03 18:29:56] Accepted 38/38 (100%), 4898 H, 232.88 H/s - opened browser with 30+ tabs.
On iddle its going to 248 H/s

I wasn't connecting any power meter but i guess there will be much less power draw on 4 cores.
And here i've got a question about  "--cpu-affinity", I don't know how to use it with "--threads 4", so it would direct all work to cores 0, 2, 4, 6 like I'm doing this in Task Manager, but only after launching the .exe
The are some hex parameters which I don't understand like 0xF0F0 or 0x30, I tried use them without effect.
Can You give me some advice ?

I can give you that advice. The --cpu-affinity works as a bit mask. The least significant bit is the core 0, the next one is core 1 and so on.

Imagine the cores like:             0 -- 1 -- 2 -- 3 -- 4 -- 5 -- 6 -- 7  (extended to 7 to fill a BYTE, 8 bits)
Now the bits for each core are:  1    0     1    0     1    0    1     0  

This binary value now is encoded with 8th core first, so it becomes => 01010101.

Converting it to hex values (grouping in fours and converting) becomes => 0101 0101 => 0x55

So you must use --cpu-affinity 0x55 in your case.

[joblo]

joblo, trying this version of cpuminer for pool mining dmd-gr - Diamond Coin but my shares keep getting rejected. cpuminer-multi works without problems. Running a Xeon X5687 with the cpuminer-aes-sse42 windows binary. Any suggestions?

Edit: buckya, I use the CPUMiner Affinity Setter at https://www.paulhempshall.com/io/cpuminer-affinity-setter/ to determine my cpu affinity.

It looks like I broke it, use the legacy version 3.5.9.1 until it's fixed.

I've never played with CPU affinity, the default seems to work well.

[buckya]

That is the Info + Tool that I was looking for, thank you both onedeveloper and coinbutter.

I don't know if affinity is usefull on Intel cpu's, but works just fine for amd modules with shared L3 2MB cache.

going back to testing.

[joblo]

That is the Info + Tool that I was looking for, thank you both onedeveloper and coinbutter.

I don't know if affinity is usefull on Intel cpu's, but works just fine for amd modules with shared L3 2MB cache.

going back to testing.

I'm surprised it's needed on AMD with modular cache. Modular cache only causes a hit if the thread moves to a core supported
by a different cache module. Miner threads should always stay on the same core.

Can you do some testing to find if you can get better performance with a custom affinity?

[coinbutter]

joblo, thanks for the help! I tried the older version and it has the same issue as well.

edit: I also tried it without affinity and priority. No difference unfortunately.

[buckya]

I'meant that affinity makes a thread more energy efficent if it works alone on 2-core piledriver module, for example two threads working on one module, sharing the 2MB cache make max 40H/s each, while one thread working alone on 2-core module has 60H/s and thats because it has all the 2MB L3 for itself.
Efficency depends on algo's demand for memory, CryptoNight works best with 2MB and I realy don't know about other algos.
To make sure I need to plug my rig to power meter.
I will try tomorrow if its really more efficent and post the results.

[joblo]

I'meant that affinity makes a thread more energy efficent if it works alone on 2-core piledriver module, for example two threads working on one module, sharing the 2MB cache make max 40H/s each, while one thread working alone on 2-core module has 60H/s and thats because it has all the 2MB L3 for itself.
Efficency depends on algo's demand for memory, CryptoNight works best with 2MB and I realy don't know about other algos.
To make sure I need to plug my rig to power meter.
I will try tomorrow if its really more efficent and post the results.

Cryptonight is the only algo I'm aware of that performs faster with fewer threads, optimum is L3 cache MB / 2 MB.
The default affinity should assign the threads as you want, just need to confirm it.

Be careful about assumptions about power, lower power often means less efficient because the CPU spends a lot
of time idle waiting for data from memory.

[coinbutter]

joblo, I know this is separate from my issues with dmd-gr. With cryptonight, I get the best rates with my R7 if I run separate instances for each physical core.

[joblo]

joblo, I know this is separate from my issues with dmd-gr. With cryptonight, I get the best rates with my R7 if I run separate instances for each physical core.

I'll look into the groestl problem.

Your experience with the R7 is interesting. How do you set affinity for each instance?
The default affinity assigns thread 0 to CPU 0, thread 1 to CPU 1 etc.
This works with Intel's mapping to assign one thread to each core before a second thread to any core.
If AMD maps differently the default affinity may not be best. You can see the actual thread assignment
using the -D option.

[joblo]

I've retested groestl and it is definitely broken in 3.6.1 but works for me on 3.5.9.1.

[coinbutter]

joblo, I set cpu affinity for each physical core:
cpuminer-aes-avx2 -a cryptonight -o stratum+tcp://xmr-usa.dwarfpool.com:8005 -u x -p x --cpu-affinity 1 --cpu-priority 0 --threads=1 --api-bind 127.0.0.1:4001
cpuminer-aes-avx2 -a cryptonight -o stratum+tcp://xmr-usa.dwarfpool.com:8005 -u x -p x --cpu-affinity 4 --cpu-priority 0 --threads=1 --api-bind 127.0.0.1:4003
cpuminer-aes-avx2 -a cryptonight -o stratum+tcp://xmr-usa.dwarfpool.com:8005 -u x -p x --cpu-affinity 16 --cpu-priority 0 --threads=1 --api-bind 127.0.0.1:4005
etc, all the way to
cpuminer-aes-avx2 -a cryptonight -o stratum+tcp://xmr-usa.dwarfpool.com:8005 -u x -p x --cpu-affinity 16384 --cpu-priority 0 --threads=1 --api-bind 127.0.0.1:4015
Otherwise it'll create 16 threads and totally load the cpu saturating the L3 cache.
I tried two instances loading each core in each CCX as well and got poor performance if both instances were running. Excellent performance on just one CCX.

For dmd-gr, I tried both versions with this batch:
cpuminer-aes-avx2 -a dmd-gr -o stratum+tcp://us.miningfield.com:3377 -u x -p x --cpu-affinity 43690 --cpu-priority 0 --threads=8 --api-bind 127.0.0.1:4050
I've tried it even bare with just:
cpuminer-aes-avx2 -a dmd-gr -o stratum+tcp://us.miningfield.com:3377 -u x -p x
and I still get this type of error:

cpuminer-aes-avx2 -a dmd-gr -o stratum+tcp://us.miningfield.com:3377 -u x -p x --cpu-affinity 43690 --cpu-priority 0 --threads=8 --api-bind 127.0.0.1:4050

         **********  cpuminer-opt 3.6.1  ***********
     A CPU miner with multi algo support and optimized for CPUs
     with AES_NI and AVX extensions.
     BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
     Forked from TPruvot's cpuminer-multi with credits
     to Lucas Jones, elmad, palmd, djm34, pooler, ig0tik3d,
     Wolf0, Jeff Garzik and Optiminer.

CPU: AMD Ryzen 7 1800X Eight-Core Processor
CPU features: SSE2 AES AVX AVX2 SHA
SW built on Mar 31 2017 with GCC 4.8.3
SW features: SSE2 AES AVX AVX2
Algo features: SSE2 AES
Start mining with SSE2 AES

[2017-04-03 22:11:34] Binding process to cpu mask aaaa
[2017-04-03 22:11:34] Starting Stratum on stratum+tcp://us.miningfield.com:3377
[2017-04-03 22:11:34] 8 miner threads started, using 'groestl' algorithm.
[2017-04-03 22:11:35] Stratum difficulty set to 2
[2017-04-03 22:11:40] CPU #5: 262.14 kH, 231.76 kH/s
---
[2017-04-03 22:12:08] groestl block 2095709, diff 23.937
[2017-04-03 22:12:08] CPU #7: 4446.27 kH, 229.69 kH/s
---
[2017-04-03 22:12:15] Rejected 1/1 (100.0%), 32.35 MH, 1823.37 kH/s
[2017-04-03 22:12:15] reject reason: low difficulty share of 0.000002147823651040806
[2017-04-03 22:12:15] factor reduced to : 0.67
[2017-04-03 22:12:17] groestl block 2095710, diff 23.937
[2017-04-03 22:12:17] CPU #6: 2005.34 kH, 228.80 kH/s
---
[2017-04-03 22:12:23] Rejected 2/2 (100.0%), 15.32 MH, 1825.43 kH/s
[2017-04-03 22:12:23] reject reason: low difficulty share of 3.377616876539221e-7
[2017-04-03 22:12:23] factor reduced to : 0.44

cpuminer-aes-avx2 -a dmd-gr -o stratum+tcp://us.miningfield.com:3377 -u x -p x --cpu-affinity 43690 --cpu-priority 0 --threads=8 --api-bind 127.0.0.1:4050

         **********  cpuminer-opt 3.5.9.1  ***********
     A CPU miner with multi algo support and optimized for CPUs
     with AES_NI and AVX extensions.
     BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
     Forked from TPruvot's cpuminer-multi with credits
     to Lucas Jones, elmad, palmd, djm34, pooler, ig0tik3d,
     Wolf0, Jeff Garzik and Optiminer.

CPU: AMD Ryzen 7 1800X Eight-Core Processor
CPU features: SSE2 AES AVX AVX2
SW built on Mar  4 2017 with GCC 4.8.3
SW features: SSE2 AES AVX AVX2
Algo features: SSE2 AES
Start mining with SSE2 AES

[2017-04-03 22:14:15] Binding process to cpu mask aaaa
[2017-04-03 22:14:15] Starting Stratum on stratum+tcp://us.miningfield.com:3377
[2017-04-03 22:14:15] 8 miner threads started, using 'groestl' algorithm.
[2017-04-03 22:14:15] Stratum difficulty set to 2
[2017-04-03 22:14:18] groestl block 2095712, diff 25.841
[2017-04-03 22:14:20] CPU #4: 262.14 kH, 232.48 kH/s
-
[2017-04-03 22:14:20] Rejected 1/1 (100.0%), 1871.29 kH, 1841.03 kH/s
[2017-04-03 22:14:20] reject reason: low difficulty share of 1.030424417006305e-7
[2017-04-03 22:14:20] factor reduced to : 0.67

edit: Also tried -a groestl

[onedeveloper]

Coinbutter: you can check my messages in this thread on how to make more of your Ryzen CPU and cryptonight algo:

https://bitcointalk.org/index.php?topic=1326803.msg18239788#msg18239788
https://bitcointalk.org/index.php?topic=1326803.msg18240239#msg18240239

Finally, check how this worked for member giagge:

https://bitcointalk.org/index.php?topic=1326803.msg18279882#msg18279882
 

I am sorry I cannot help with groestl algo and your pool ...

[coinbutter]

onedeveloper, your posts about Ryzen are what initially brought me to this forum cpuminer-multi didn't seem very optimized for my hardware and I'm looking for something better. I someone wants me to try out an algorithm or something out I'm happy to give it a try.

[joblo]

onedeveloper, your posts about Ryzen are what initially brought me to this forum cpuminer-multi didn't seem very optimized for my hardware and I'm looking for something better. I someone wants me to try out an algorithm or something out I'm happy to give it a try.

Regarding your groestl/dmd-gr problem, the error you see in v3.5.9.1 is the same as the bug I introduced in a later release
suggesting the Windows binaries were built incorrectly. I will retest that.

Other algos with Ryzen I am curious about:

deep: compute bound, good test of AVX2

sha256t: compute bound without any AVX2 code*

lyra2z330: I/O bound due to large data array

* sha256t would benefit from HW SHA acceleration available with Ryzen but requires a supported Linux compile environment.
   See release announcement for v3.6.1 for details.

https://bitcointalk.org/index.php?topic=1326803.msg18406368#msg18406368

[onedeveloper]

I was piqued with your selection of algos so I decided to try them on my Windows 8.1 machine. This is the result for AVX version of "deep" algo:

Code:

CPU: Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz
CPU features: SSE2 AES AVX AVX2
SW built on Mar 31 2017 with GCC 4.8.3
SW features: SSE2 AES AVX
Algo features: SSE2 AES AVX AVX2
Start mining with SSE2 AES AVX

[2017-04-04 16:31:20] 4 miner threads started, using 'deep' algorithm.
[2017-04-04 16:31:31] CPU #3: 2097.15 kH, 182.74 kH/s
[2017-04-04 16:31:31] Total: 2097.15 kH, 182.74 kH/s
[2017-04-04 16:31:31] CPU #2: 2097.15 kH, 182.49 kH/s
[2017-04-04 16:31:31] CPU #0: 2097.15 kH, 177.66 kH/s
[2017-04-04 16:31:32] CPU #1: 2097.15 kH, 175.57 kH/s
[2017-04-04 16:31:36] CPU #1: 702.27 kH, 171.87 kH/s
[2017-04-04 16:31:36] CPU #2: 912.45 kH, 183.92 kH/s
[2017-04-04 16:31:36] CPU #3: 913.69 kH, 182.45 kH/s
[2017-04-04 16:31:36] Total: 4625.55 kH, 715.90 kH/s
[2017-04-04 16:31:36] CPU #0: 888.29 kH, 180.76 kH/s
[2017-04-04 16:31:41] CPU #1: 859.36 kH, 172.99 kH/s
[2017-04-04 16:31:41] CPU #2: 919.62 kH, 183.39 kH/s
[2017-04-04 16:31:41] CPU #3: 912.25 kH, 183.06 kH/s
[2017-04-04 16:31:41] Total: 3579.51 kH, 720.20 kH/s
[2017-04-04 16:31:41] CPU #0: 903.81 kH, 179.12 kH/s
[2017-04-04 16:31:44] CTRL_C_EVENT received, exiting

And this is the same test using AVX2:

Code:

CPU: Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz
CPU features: SSE2 AES AVX AVX2
SW built on Mar 31 2017 with GCC 4.8.3
SW features: SSE2 AES AVX AVX2
Algo features: SSE2 AES AVX AVX2
Start mining with SSE2 AES AVX2

[2017-04-04 16:30:52] 4 miner threads started, using 'deep' algorithm.
[2017-04-04 16:31:01] CPU #3: 2097.15 kH, 230.87 kH/s
[2017-04-04 16:31:01] Total: 2097.15 kH, 230.87 kH/s
[2017-04-04 16:31:01] CPU #2: 2097.15 kH, 228.12 kH/s
[2017-04-04 16:31:01] CPU #1: 2097.15 kH, 219.54 kH/s
[2017-04-04 16:31:02] CPU #0: 2097.15 kH, 206.06 kH/s
[2017-04-04 16:31:06] CPU #0: 824.23 kH, 225.80 kH/s
[2017-04-04 16:31:06] CPU #3: 1154.34 kH, 229.71 kH/s
[2017-04-04 16:31:06] Total: 6172.87 kH, 903.17 kH/s
[2017-04-04 16:31:06] CPU #2: 1140.60 kH, 226.97 kH/s
[2017-04-04 16:31:06] CPU #1: 1097.69 kH, 226.17 kH/s
[2017-04-04 16:31:11] CPU #0: 1129.01 kH, 221.69 kH/s
[2017-04-04 16:31:11] CPU #3: 1148.54 kH, 231.20 kH/s
[2017-04-04 16:31:11] Total: 4515.84 kH, 906.03 kH/s
[2017-04-04 16:31:11] CPU #2: 1134.87 kH, 229.17 kH/s
[2017-04-04 16:31:11] CPU #1: 1130.86 kH, 220.70 kH/s
[2017-04-04 16:31:13] CTRL_C_EVENT received, exiting

This shows that the AVX2 optimized version is 25.83% faster than AVX-only version in the same architecture. Ryzen is said it only have AVX2 emulation, not real 256 bits, so it will be interesting to see the results there.

Doing the same tests, this time with the "sha256t" algo, I got these results. AVX-only version:

Code:

CPU: Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz
CPU features: SSE2 AES AVX AVX2
SW built on Mar 31 2017 with GCC 4.8.3
SW features: SSE2 AES AVX
Algo features: SSE2 SHA
Start mining with SSE2

[2017-04-04 16:35:52] 4 miner threads started, using 'sha256t' algorithm.
[2017-04-04 16:35:53] CPU #1: 262.14 kH, 321.25 kH/s
[2017-04-04 16:35:53] CPU #2: 262.14 kH, 321.25 kH/s
[2017-04-04 16:35:53] CPU #3: 262.14 kH, 321.25 kH/s
[2017-04-04 16:35:53] Total: 786.43 kH, 963.75 kH/s
[2017-04-04 16:35:53] CPU #0: 262.14 kH, 293.18 kH/s
[2017-04-04 16:35:57] CPU #0: 1172.72 kH, 297.42 kH/s
[2017-04-04 16:35:57] CPU #2: 1284.99 kH, 315.88 kH/s
[2017-04-04 16:35:57] CPU #3: 1284.99 kH, 315.88 kH/s
[2017-04-04 16:35:57] Total: 4004.85 kH, 1250.43 kH/s
[2017-04-04 16:35:57] CPU #1: 1284.99 kH, 313.47 kH/s
[2017-04-04 16:36:02] CPU #3: 1579.41 kH, 316.94 kH/s
[2017-04-04 16:36:02] Total: 5322.12 kH, 1243.72 kH/s
[2017-04-04 16:36:02] CPU #0: 1487.11 kH, 294.72 kH/s
[2017-04-04 16:36:02] CPU #2: 1579.41 kH, 312.05 kH/s
[2017-04-04 16:36:02] CPU #1: 1567.37 kH, 305.89 kH/s
[2017-04-04 16:36:06] CPU #0: 1473.59 kH, 303.84 kH/s
[2017-04-04 16:36:07] CPU #2: 1560.23 kH, 314.61 kH/s
[2017-04-04 16:36:07] CPU #3: 1584.69 kH, 313.62 kH/s
[2017-04-04 16:36:07] Total: 6185.88 kH, 1237.96 kH/s
[2017-04-04 16:36:07] CPU #1: 1529.45 kH, 301.75 kH/s
[2017-04-04 16:36:07] CTRL_C_EVENT received, exiting

And now the AVX2-optimized version:

Code:

CPU: Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz
CPU features: SSE2 AES AVX AVX2
SW built on Mar 31 2017 with GCC 4.8.3
SW features: SSE2 AES AVX AVX2
Algo features: SSE2 SHA
Start mining with SSE2

[2017-04-04 16:36:14] 4 miner threads started, using 'sha256t' algorithm.
[2017-04-04 16:36:15] CPU #2: 262.14 kH, 430.18 kH/s
[2017-04-04 16:36:15] CPU #1: 262.14 kH, 419.43 kH/s
[2017-04-04 16:36:15] CPU #0: 262.14 kH, 409.20 kH/s
[2017-04-04 16:36:15] CPU #3: 262.14 kH, 399.46 kH/s
[2017-04-04 16:36:15] Total: 1048.58 kH, 1658.27 kH/s
[2017-04-04 16:36:19] CPU #3: 1597.83 kH, 422.56 kH/s
[2017-04-04 16:36:19] Total: 2384.26 kH, 1681.37 kH/s
[2017-04-04 16:36:19] CPU #1: 1677.72 kH, 416.17 kH/s
[2017-04-04 16:36:19] CPU #0: 1636.80 kH, 404.45 kH/s
[2017-04-04 16:36:19] CPU #2: 1720.74 kH, 417.14 kH/s
[2017-04-04 16:36:24] CPU #3: 2112.80 kH, 420.91 kH/s
[2017-04-04 16:36:24] Total: 7148.05 kH, 1658.68 kH/s
[2017-04-04 16:36:24] CPU #0: 2022.27 kH, 409.25 kH/s
[2017-04-04 16:36:24] CPU #2: 2085.72 kH, 419.44 kH/s
[2017-04-04 16:36:24] CPU #1: 2080.86 kH, 409.45 kH/s
[2017-04-04 16:36:29] CPU #3: 2104.57 kH, 422.75 kH/s
[2017-04-04 16:36:29] Total: 8293.42 kH, 1660.89 kH/s
[2017-04-04 16:36:29] CPU #0: 2046.24 kH, 414.94 kH/s
[2017-04-04 16:36:29] CPU #2: 2097.18 kH, 417.33 kH/s
[2017-04-04 16:36:29] CPU #1: 2047.27 kH, 406.14 kH/s
[2017-04-04 16:36:29] CTRL_C_EVENT received, exiting

This time I went from 1245 kH/s to 1660 kH/s, a surprising 33.33% increase on speed!

With this algorithm, I really will like to see the performance with native HW SHA acceleration

[joblo]

cpuminer-aes-avx2 -a dmd-gr -o stratum+tcp://us.miningfield.com:3377 -u x -p x --cpu-affinity 43690 --cpu-priority 0 --threads=8 --api-bind 127.0.0.1:4050

         **********  cpuminer-opt 3.5.9.1  ***********
     A CPU miner with multi algo support and optimized for CPUs
     with AES_NI and AVX extensions.
     BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
     Forked from TPruvot's cpuminer-multi with credits
     to Lucas Jones, elmad, palmd, djm34, pooler, ig0tik3d,
     Wolf0, Jeff Garzik and Optiminer.

CPU: AMD Ryzen 7 1800X Eight-Core Processor
CPU features: SSE2 AES AVX AVX2
SW built on Mar  4 2017 with GCC 4.8.3
SW features: SSE2 AES AVX AVX2
Algo features: SSE2 AES
Start mining with SSE2 AES

[2017-04-03 22:14:15] Binding process to cpu mask aaaa
[2017-04-03 22:14:15] Starting Stratum on stratum+tcp://us.miningfield.com:3377
[2017-04-03 22:14:15] 8 miner threads started, using 'groestl' algorithm.
[2017-04-03 22:14:15] Stratum difficulty set to 2
[2017-04-03 22:14:18] groestl block 2095712, diff 25.841
[2017-04-03 22:14:20] CPU #4: 262.14 kH, 232.48 kH/s
-
[2017-04-03 22:14:20] Rejected 1/1 (100.0%), 1871.29 kH, 1841.03 kH/s
[2017-04-03 22:14:20] reject reason: low difficulty share of 1.030424417006305e-7
[2017-04-03 22:14:20] factor reduced to : 0.67

edit: Also tried -a groestl

I retested v3.5.9.1 using the Windows AVX2 binary on Win 8.1 at suprnova groestlcoin and it works.
I can't explain your rejects.

Can you (or maybe someone else) try with another CPU and/or another pool like suprnova?
I want to get to the bottom of this before releasing the next version.

Use the AES builds in the legacy release here https://drive.google.com/file/d/0B0lVSGQYLJIZT0tlY3o4ZjEycXM/view?usp=sharing,
v3.6.1 is broken. The non-AES builds of 3.5.9.1 are likely broken as well.