You could try switching the optimizations off -
optimineraes=0 and optimineravx2=0
are you comparing 78h/s x1 on v2 against 60h/s x 4 on the new machine? You might just be seeing better performance taking up more cpu. you could try just running on 1 or 2 processors - genproclimit=1
I was not intending to compare the performance of the i7 vs the AMD processors. I mentioned the performance of the i7 to try to give some insight into the performance of that machine and yet note the freezing on the i7 regardless of whether mining was enabled or not. I did actually try using genproclimit=1 on the i7 but again the wallet (and nothing else on the machine) is freezing up regardless of mining on/off.
On the AMD, I was unable to get a hash reading while 3.0 was installed because the wallet crashed every time mining was engaged so thus far I don't have anything to compare to the 78h/s on 2.0 on the AMD. I suppose the next thing I'll try is genproclimit on that one with another fresh install of 3.0.
In general though, if I have to turn off the optimizations (and perhaps limit the threads) to make it work then there really is no point in solo mining with the 3.0 wallet. I'll get much better performance simply staying with the Optiminer pool (assuming it stays online after the switch). I would very much like to be able to solo mine both to support network diversity and to have a backup option when/if a pool goes down.
Speaking of the optiminer pool, I've been able to successfully mine with the pool (which is certainly using the optimizations) with both machines without freezing up the machines.
Am I really the only one seeing issues with the 3.0 wallet?
@WiseBC you might want to take a look at
https://github.com/HOdlcoin/HOdlcoin/issues/90 You're not the only one with the issue and work is already in progress to get it sorted out
I would be curious to see what your event viewer is reporting and on my box that's hanging it's an access violation error and it occurs just as the AES data is being created.