2.5.0 crashing computer when compiling and getting banned for invalid shares

[xavierx66]

I am upgrading rigs previously all working on 2.4.7 to 2.5.0. 4 rigs so far successful out of 8

1st problem rig :

Biostar TA320-BTC, Ryzen 1600 cpu, 3x RX570 1x RX580 (currently stock speeds while setting up) AMD driver : Blockchain 17.30.1029 Windows 10 64bit Coin "monero" (previously "monero7" on 2.4.7)

Problem:

4 out of 5 times, running xmr-stak 2.5.0, when trying to compile open cl code, the whole computer will crash and reboot, and I have to go to C:\Users\xxx\AppData\Local.openclcache and delete the precompiled files and try again

Eventually, the compile will succeed, and xmr-stak will start hashing, and then I will get banned from Support-XMR for submitting invalid shares.

After waiting for the unban, I can go back to xmr-stak 2.4.7 and it will work fine as previous

Trying to use 2.5.0 again will result in the computer crashing and rebooting

Thanks for any help

[psychocrypt]

Mostly you get banned because you send wrong hashes. Please post your pools.cfg to be sure you selected the correct currency. The compiler crash sounds strange. Is your hdd full or do you have a low amount of ram?

[psychocrypt]

do you run xmr-stak as root/admin. If so try to keep it as user.

[xavierx66]

8gb ram, 20GB diskspace free. xmr-stak is running as a user

pools config to follow

[xavierx66]

// generated by xmr-stak/2.5.0/90125127/master/win/nvidia-amd-cpu/20

/*

• pool_address - Pool address should be in the form "pool.supportxmr.com:3333". Only stratum pools are supported.
• wallet_address - Your wallet, or pool login.
• rig_id - Rig identifier for pool-side statistics (needs pool support).
• pool_password - Can be empty in most cases or "x".
• use_nicehash - Limit the nonce to 3 bytes as required by nicehash.
• use_tls - This option will make us connect using Transport Layer Security.
• tls_fingerprint - Server's SHA256 fingerprint. If this string is non-empty then we will check the server's cert against it.
• pool_weight - Pool weight is a number telling the miner how important the pool is. Miner will mine mostly at the pool
• with the highest weight, unless the pool fails. Weight must be an integer larger than 0.
• We feature pools up to 1MH/s. For a more complete list see M5M400's pool list at www.moneropools.com */

"pool_list" : [ {"pool_address" : "pool.supportxmr.com:7777", "wallet_address" : "walletaddress", "rig_id" : "", "pool_password" : "myrig.mypass", "use_nicehash" : false, "use_tls" : false, "tls_fingerprint" : "", "pool_weight" : 1 }, ],

/*

• Currency to mine. Supported values:
• aeon7 (use this for Aeon's new PoW)
• bbscoin (automatic switch with block version 3 to cryptonight_v7)
• bittube (uses cryptonight_bittube2 algorithm)
• graft
• haven (automatic switch with block version 3 to cryptonight_haven)
• intense
• masari
• monero (use this to support Monero's Oct 2018 fork)
• qrl - Quantum Resistant Ledger
• ryo
• turtlecoin
• Native algorithms which not depends on any block versions:

• 1MiB scratchpad memory

• cryptonight_lite
• cryptonight_lite_v7
• cryptonight_lite_v7_xor (algorithm used by ipbc)

• 2MiB scratchpad memory

• cryptonight
• cryptonight_v7
• cryptonight_v8

• 4MiB scratchpad memory

• cryptonight_bittube2
• cryptonight_haven
• cryptonight_heavy */

"currency" : "monero",

[xavierx66]

I have been unable to resolve this one.

As a summary, this is Windows 10 with blockchain drivers, using known good pool, the computer will keep crashing during compiling the cache, and I have to delete the corrupted cache files after restarting. I have been unable to get valid shares

[xavierx66]

1 day to go, has anyone else managed to get RX570 / RX580's working with the blockchain driver?

I have all other rigs working now, just 2 RX rigs I am stuck on that crash when compiling the cache

Thanks

[xavierx66]

Update, if I install 18.5.2 AMD driver, then xmr-stak 2.5.0 will compile and hash fine, but the hash rate is super low (which I knew already and why I was running the blockchain drivers)

If I re-install the blockchain drivers then it goes back to crashing and failing to compile the cache.