Just to let you know, the latest version 22.0 has fixed the wallet problem, no more crashes on incoming transactions from anywhere.
Thanks again to everyone here in the forum and of course to the github guys!

That is exactly what surprises me too.
Anyway, I reported the issue on Github and someone already investigate. It seems that this is a new problem and nobody is using Bitcoincore for Win64 as an external wallet with Nicehash ... except me

Anyway, thank you very much for your support, I'll keep you informed!

Yes exactly, v0.21.0 and tx from a source other than NH goes through without problems.

That's because I didn't have BitcoinCore running for the week when I wasn't home, and when I knew that the tx from NH had been received, I started BitcoinCore with first attempt v0.21.1 and after crash with v0.20.1. Then of course the previous days will be processed first.

Correct, just to show that v0.21.0 runs without problems after I had previously syncronized the NH tx with v.0.20.1

line:
514 - start v0.21.1 attempt to sync NH tx
623 - crash just before NH tx 
2021-05-21T02:38:23Z UpdateTip: new best=000000000000000000076abd974283d6f1ac6ee46e6275289b919a0b72578fb9 height=684340 version=0x3fffe004 log2_work=92.890824 tx=643673329 date='2021-05-20T18:13:01Z' progress=0.999835 cache=22.4MiB(168883txo)

629 - restart with v0.20.1   
733 - same entry as above but no crash
2021-05-21T02:42:49Z UpdateTip: new best=000000000000000000076abd974283d6f1ac6ee46e6275289b919a0b72578fb9 height=684340 version=0x3fffe004 log2_work=92.890824 tx=643673329 date='2021-05-20T18:13:01Z' progress=0.999843 cache=22.4MiB(168885txo) warning='89 der letzten 100 Blöcke haben eine unerwartete Version'

734-735 - incoming tx from NH
806 - shut down

812-839 start - run - shutdown v0.21.1 without tx

The lines in second attempt are longer because a warning is appended to each line (unfortunately in German): warning = '89 of the last 100 blocks have an unexpected version'

Just transferred from an exchange and successfully synchronized with v0.21.1 ... so the problem is always and only with Nicehash transactions in connection with v0.21.x
 
txid
row 109

Thanks for pointing me to the right place, just opened a new issue.
Nothing I can find in windows event related to BitcoinQT.
I still hesitate with a tx from an exchange, waiting for an opportunity to stock up

just to confirm after I ran BitcoinCore 0.21.1 without any problems for the entire last week until the next transaction from Nicehash arrived yesterday.
After the crash and several attempts with the same error at the same position (program closes when synchronizing the Nicehash transaction without a message) I pushed v0.20.1 into the program directory, started it and synchronized everything without problems.
Then switched back to the current v0.21.1 and its up and running again.

If you are interested, you can have a look at the last two days below, don't think I need to comment again

Transaction from NH is:

Debug log:

I am currently running v0.21.1 and am waiting for a transaction from somewhere else.
Let's see if it goes smoothly...

oh sorry yeah of course you are right 7kb vs few hundred byte.

Nicehash:
https://abload.de/img/snap2nljmn.jpg

other:
https://abload.de/img/snap319jxf.jpg

Could it related to my wallet address, because I use an older format address for Nicehash like 156... not bc1...?

Thanks for your support, I will try my luck...


I really thought the latest BitcoinCore versions has a bug and someone might have the same problem or can tell what exactly is the difference from latest to previous versions so this problem could occur.
Can't imagine that it is due to my hardware or SW, since the problem is only with the incoming transactions from Nicehash and that only since Januar this year and since v0.21.0. This is for sure because if I re-syncronize the entire chain with latest BitcoinCore Version, it runs through all the years (many transaction over the past 4 years also incom from NH) until Januar 2021 without any problems and then always crashes on the same transaction from Nicehash dad0f505c7c9697e1b7b79ecc7133701fd0a4424993ec27770191bfb6a290763 (as in my first post). Then I revert to v0.20.1, sync this transaction (no problem), after that revert again to v0.21 and run until next transaction from Nicehash with same problem...
Maybe it has really to do with the size of transactions, because those from Nicehash are much larger than other, 7MB compared to usually a few hundred kb.
Now running with previous v0.20.1 and it works like a charm without any problems.

done already in the beginning, changed SSD, RAM and Power supply, only MB with CPU not.
But I can use this PC with Xeon CPU over days running 24/7, even CPU mining XMonero withhout any problem.
Also funny that this problem has only occured since and with BitcoinCore v0.21.0 or above... and only with Nicehash incoming transactions, others are fine

Unfortunately  same problem with the last Nicehash transaction today...

Transaction ID:

debug.log

v0.21.1
row 114 last entry before nicehash transaction and programm crashes

v020.1
row 240 same position as above but no crash
row 241 Nicehash transaction


Beside this problem with incomming transaction from nicehash v0.21.1 works without problem...

Thank you so much for the hint!
I was not aware of that and sounds very conclusive.
Now it looks like this:
I will post feedback here after receiving the next Nicehash transaction.
What I notice already, the synchronization is much faster with this setting...

still the same problem with version 0.21.1 whenever a new transaction comes in from Nicehash.
Bitcoin Core closes by itself without error message while synchronizing the latest transaction from Nicehash

Bitcoin Transaction: 6f8b84e3312abb77a95e5cb37c200cd564c6d4eb872b5d6a652fcb6eab70c5e9

debug.log

start program new version 0.21.1
entry 169 programm closed without error message exactly with the latest transaction from nicehash

reinstall v0.20.1
entry 345 transaction from nicehash sync without problem...


any idea?

yes I know there is a db.log but its empty

0.20.1 is now synchronized and runs without problem.
I will keep it for now as it is also faster connecting and syncing on startup, I just want to report this error.

its definitly related to the last transaction from nicehash in combination with v0.21.0, the problem just start after that transaction.
Transaction ID:
v0.20.1 worked just fine for me again, but I reinstalled v0.21.0 to verify the problem.
Clean dbug.log and start with -reindex and -rescan.
After running for a couple of hours I went for dinner, synching sometime in 2017, when I came back Bitcon Core was shutdown.
Restart 2 times with same resault, the programm crashes without any error messege.

look at the debug.log, especially the entries in 800 and 1016 when programm crashes:

its the transaction from nicehash....

Now running v0.20.1 again, debug.log so far below, look at 206, its still synching without problem:

yes I know nothing much wrong, thats one of the reason why I open this thread.
The content of debug.log is shorten because of limited space.
Actually I leave 2 part in the log;
Uper section when starting version 0.21.0 untill closed from alone while synching, always on same block without error message.
Lower section when starting bitcoin core older version 0.20.1 without problem.

Anyhow I reinstalled 0.21.0 again and start with -reindex and -rescan, now waiting for finish synching....

Thx a lot for your support, I will give feedback later

Sorry, above Transaction ID was given by Nicehash, maybe just an internal ID.

The correct ID is:

And yes, 0.21.0 it is working fine if I create a new wallet.dat.
It was working for a week or so untill this morning, the issue popup after reciving the first transaction last night to my wallet running Core version 0.21.0
I have also tried this way arround and import my wallet.dat after finished synching with a new wallet, but during inilizing my old wallet the same issue comes back, Bitcoin Core just shutdown without an error message and at same step in debug.log

I have a issue loading my wallet.dat and found that the problem is with Core v0.21.0

Issue started yesterday when I opened Bitcoin Core, after receiving last payment from nicehash.
Always while loading the same block, I think the one in which the Nicehash transfer is located, Bitcoin Core was closed without an error message.
After trying several times to reinitialize, even from an older backup of my wallet.dat, I reinstalled v0.20.1 and the problem was resolved.



In the debug report shows 2 section
-v0.21.0 always the same issue and report
-v0.20.1 after reinstall without issue

I have a problem inilizing my wallet.dat and found that the problem is with Core v0.21.0
Yesterday, after I received the last payment from nicehash, I open Bitcoin Core, but always while loading the same block, I think that the one in which the transfer from Nicehash is located, Bitcoin Core just closed without any error message.
After trying several times and reinitializing the wallet.dat, I installed v0.20.1 and the problem was solved ...

was wo nachlesen?

so wie Vitalik Buterin und Nick Szabo?