piHashVal = (uint64_t*)(result.bResult + 24);
result.bResult is a pointer to some data structure, it's storing the memory address at which the structure begins. We're not interested in the beginning of that data blob, but want to access some 64-bits starting at offset 24. The above expression increments the address by offset 24 and casts the result to ...
Try the following:
brew install openssl libmicrohttpd
git clone -b dev https://github.com/fireice-uk/xmr-stak-amd
mkdir build && cd build
cmake -DOPENSSL_ROOT_DIR=/usr/local/opt/openssl -DOPENSSL_INCLUDE_DIR=/usr/local/opt/openssl/include/ ..
It may be necessary to insert the following line in CMakeLists.txt:
Usually you don't need a Payment ID anymore nowadays for new Wallet addresses. The Payment ID is now included in your Wallet address.
Worker ID is a label you can assign freely. Like MyWorker1.
Pool password is usally just x
So the whole string should look like:
"pool_address" : "xmr-eu1.nanopool.org:14444",
"wallet_address" : "...
According to xmr-stak 2.3.0 release notes, config files from 2.2.0 are NOT compatible with the new version. If you still used them, you can get 'restarts' for this reason.
Also, between xmr-stak issues you can find that less aggressive 'intensity' values prevent crashes and restarts. I'm a newbie about Monero, but usually too high overclocking can also ...
At this time, with cryptonight_v7 you're not mining Monero. You should use the cryptonight_v8 algorithm with the latest xmr-stak 2.7.1 to mine Monero, but when the question was posted probably there was no v8.
Anyway, the new algo (before the v7 and now the v8) is more hungry with power consumption and you must use different settings to find a good sweet ...
try taking the vega56 out of the equation; I had the same problem with my rig 5xVega64 + 1xVega56. Having the vega 56 in there made the whole rig very unstable. I tried both cast-xmr and xmr-stack
Removing the Vega56 solved things for me...
idk anything about monero source code but:
first thing is that if you mean byte 0 as first then say byte 7 is 8th ,not 7th .
second is that when you deal with structures it has alignment.And my bet is that it's not 1 here. It's not so complex stuff if use it in structure you know.But it's complex to understand abstract.
to tell long story short: if you ...
Whilst your CPU may have the ability to run 8 threads, it may not have enough cache for mining with 8 threads. With Monero, you need 2MB CPU cache per thread. So for 8 threads you'd need a CPU cache of 16MB available.
If you run more threads than you have cache for, it will slow down the hashing.
At this time, no way to make xmr-stak (xmr-stak-amd is legacy) with the open-source AMD Linux driver.
Apart from that, the latest xmr-stak works like a charm with new Ubuntu 18.04 LTS version and the AMD Linux proprietary driver.
Did you try a different Address or checked your Address if it is correct? I tested it using an invalid address and I got almost the same error. However, valid address works!
[2017-04-18 00:38:10] : MEMORY ALLOC FAILED: VirtualAlloc failed.
[2017-04-18 00:38:10] : Starting single thread, affinity: 0.
[2017-04-18 00:38:10] : Starting single thread, affinity: ...
Ok, I figured this out for myself. The built in microhttp server runs when the port number is set in the config.txt file. Had I read all the way through the config file the first time I would have seen the comment at the end.