Topic: 100 Diamond Bounty for Helping to solve the wallet.dat problem (Read 495 times)

The Solution for other DMD Users and Fans how to recover and solve this kind of problem. To the luck, I have backed up all the files from the roaming folder including all database and log files and of course the wallet.dat.

I have installed the new client and restored all the old files back again. Now the client dont crash anymore and I´ve send some coins to test. Will see later if its ok, but I think that was the solution.

So people, if you change something backup ALL FILES IN ROAMING and NOT ONLY the wallet.dat !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

had that with bitcoin while jumping from .8.2 to .8.5

I reopened the wallet in .8.2, crashed
reopened again -> worked
went to .8.5 -> suddenly worked also

maybe this procedure helps you. make a backup of your wallet before trying

Hello, can anybody help me ? In my wallet are 1000DMD mined and I have also the same problem with the newest client. It crashes on every start after one minute or earlier.

What I´ve done already to try to solve the problem:

-Deleted all data in roaming except the wallet.dat
-Updated the to the new client
-repair-wallet through the debug console -> check was OK
-deleted all nodes in the config.


If I delete my wallet.dat and try to start the client, it works fine, but then my DMD´s are lost.

I give 100 DMD to the Solver of my problem.


this is db.log :

file wallet.dat has LSN 41/7885761, past end of log at 1/1418101
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
DB_ENV->log_flush: LSN of 41/7885761 past current end-of-log of 1/1418101
Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
wallet.dat: unable to flush page: 10
txn_checkpoint: failed to flush the buffer cache: DB_RUNRECOVERY: Fatal error, run database recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery