Spurious crashes on NBMiner 40.1 on startup

[ByteJuggler]

Possibly related issue: #697

I have a 6900XT that has occasional issues under 40.1, specifically I sometimes get:

(code 4294967295 (0xFFFFFFFF))

This is similar to this: microsoft/WSL#4904

Note that 4294967295 (0xFFFFFFFF) is two's complement representation of -1, and suggests that someone tried to return a value outside of signed int boundary, which would get converted to -1 (e.g. the above). This is discussed in this SO question.

Next I also sometimes get:

(code 3221225477 (0xc0000005))

As per MSDN, 0xc0000005 is access violation, pointing to some invalid pointer dereference, e.g. a software bug of some sort most probably.

I should note that the card in my question is entirely stock, and even at stock settings (usually), meaning I've even resorted to resetting things to try and determine whether it's clocks or whatever; the fact that this happens even at stock, along with your experience above, suggests to me there may well be some problems in respect of AMD cards and NBMiner in 40.1, at least maybe. I should also note that these issues usually occur for me on startup, and that after a restart everything is quite fine. So there seems to be something about startup that is flaky, sometimes.

[Abdulrahmanxd]

I recommend use another miner i have a-lot problem when use amd with nb miner so i try all miner the better one for amd card its gminer for me so try to use it I think that help you