Quote from: pokeytex on September 19, 2018, 11:57:31 AM

Quote from: maxocoin on September 19, 2018, 11:10:35 AM

Quote from: shveicar on September 19, 2018, 05:19:31 AM

Quote from: maxocoin on September 19, 2018, 12:46:28 AM

Quote from: shveicar on September 18, 2018, 03:05:12 PM

Quote from: stillontop on September 18, 2018, 01:15:10 PM

Regarding the wallet crash problem after a PC shutdown, it is possible to block a shutdown until an application has been closed in a clean manner.
More about this function is here: https://docs.microsoft.com/en-us/windows/desktop/api/Winuser/nf-winuser-shutdownblockreasoncreate

Blocks corruption is only possible if the computer suddenly shuts down and synchronization is not yet complete.
If the wallet sync has reached 100% then the sudden power off does not harm the blockchain.
In other cases, any other causes of corruption are related to the automatic updates feature, which roughly terminates many system processes.

The easiest way to protect against this is to use a properly configured computer with UPS and disabled automatic updates.

For safety net, you can always create your archive with the folders blocks and chainstate and in case of damage to the blockchain, just to replace the data.
Delete old folders and unpack new ones to their place.
Then the re-sync process will only take a few minutes.

Sorry but not...

In my case, EVERY TIME I do a proper windows 10 shutdown, if I forgot to shutdown the wallet first, I get a wallet corruption error and it has to "re-verify" the whole 50 weeks. That is after been stacking for days (meaning, the wallet is fully synchronised)

I have 3 other stacking wallets running on that computer and this is the only one affected...
There is clearly something going on...

Doesn't have windows something similar to the Unix signals that you can subscribe to and close all the files as soon you you get the "shooting down signal"?

Actually thing jut got worst, since it last happened, every time I try to run it now, it aborts with the typical "Windows had encountered an error in this application..."

Any one knows a way to fix that?

Cheers
MC

2018-09-19 00:53:38 DMD version v3.0.1.2-gcbcb549 (Tue, 9 Feb 2016 16:54:57 -0500) 2018-09-19 00:53:38 Using OpenSSL version OpenSSL 1.0.1l 15 Jan 2015 2018-09-19 00:53:38 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2018-09-19 00:53:38 Default data directory C:\Users\user\AppData\Roaming\DMDV3 2018-09-19 00:53:38 Using data directory C:\Users\user\AppData\Roaming\DMDV3 2018-09-19 00:53:38 Using config file C:\Users\user\AppData\Roaming\DMDV3\diamond.conf 2018-09-19 00:53:38 Using at most 125 connections (2048 file descriptors available) 2018-09-19 00:53:38 Using 0 threads for script verification 2018-09-19 00:53:38 Old backup deleted: "C:\Users\user\AppData\Roaming\DMDV3\backups\wallet.dat.2018-08-27-15-33" 2018-09-19 00:53:38 Using wallet wallet.dat 2018-09-19 00:53:38 init message: Verificando monedero... 2018-09-19 00:53:38 CDBEnv::Open: LogDir=C:\Users\user\AppData\Roaming\DMDV3\database ErrorFile=C:\Users\user\AppData\Roaming\DMDV3\db.log 2018-09-19 00:53:38 Bound to [::]:17771 2018-09-19 00:53:38 Bound to 0.0.0.0:17771 2018-09-19 00:53:38 init message: Cargando el Ãndice de bloques... 2018-09-19 00:53:38 Opening LevelDB in C:\Users\user\AppData\Roaming\DMDV3\blocks\index 2018-09-19 00:53:38 Opened LevelDB successfully 2018-09-19 00:53:38 Opening LevelDB in C:\Users\user\AppData\Roaming\DMDV3\chainstate 2018-09-19 00:53:38 Opened LevelDB successfully 2018-09-19 00:53:38 LoadBlockIndexDB: last block file = 0 2018-09-19 00:53:38 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=0, size=0, heights=0...0, time=1970-01-01...1970-01-01) 2018-09-19 00:53:38 Checking all blk files are present... 2018-09-19 00:53:38 LoadBlockIndexDB: Last shutdown was prepared: false 2018-09-19 00:53:38 LoadBlockIndexDB(): transaction index enabled 2018-09-19 00:53:38 Initializing databases... 2018-09-19 00:53:38 init message: Verificando bloques... 2018-09-19 00:53:38 block index 37ms 2018-09-19 00:53:38 Read 100 fee samples and 100 priority samples 2018-09-19 00:53:38 Read 47 fee samples and 32 priority samples 2018-09-19 00:53:38 Read 0 fee samples and 1 priority samples 2018-09-19 00:53:38 Read 0 fee samples and 1 priority samples 2018-09-19 00:53:38 Read 0 fee samples and 1 priority samples 2018-09-19 00:53:38 init message: Cargando monedero... 2018-09-19 00:53:38 nFileVersion = 3000102 2018-09-19 00:53:38 Keys: 0 plaintext, 3073 encrypted, 3073 w/ metadata, 3073 total 2018-09-19 00:53:38 wallet 158ms 2018-09-19 00:53:38 Waiting for genesis block to be imported... 2018-09-19 00:53:38 Reindexing block file blk00000.dat... 2018-09-19 00:53:38 CheckBlock: block=0000029b550c0095513d9bb9dd14f88442573baca94d70e49018a510979c0f9b is proof of stake=0

if you constantly have these problems, perhaps something with your system settings.
Try using a different location for the DMDv3 folder.
For example, another disk or removable device.
23. Q: Alternative way https://diamond-info.github.io/#q23-altway

It could be that my particular configuration is more prone than others...

BUT that doesn't take away the fact that there is a Fault in the wallet's programming.

I know that this kind of things happen, specially if you are writing something to the disk and the system freezes or the power is cut, but it shouldn't happen if you close the system the right way.

It shouldn't happen because the OS notifies all the programs that it is going to shutdown and they should trap this notification for do their "clean up".

I think there is one of two options; or the wallet is not trapping this signal for "committing" the pending work and close the open files. Or this "cleanup" is taking too long.. Both are a programming issue.

As I said, I stake more coins on the same system and Diamond is the only that gets corrupted when I shutdown the system properly

MC

For what it is worth - I also run Windows 10 64 bit and never have a problem with the wallet corrupting. Whenever I get the update notice, I shut down all of my wallets, then I restart the computer in update mode. When I come back, I restart all my wallets with no issues whatsoever. Try that technique first before just choosing shutdown from the start button. Also, do you store your wallet.dat and other files on the C: drive or another location? Mine are saved to the default directory on the C: drive.

Yep, but that shouldn't be needed. I use that machine for more things and it needs to restart from time to time. If you follow the proper OS shutdown procedure you shouldn't break anything. Even Word asks you if you want to save stuff, if you have an unsaved document.

Yes, my walled is in the default folder as well.

Cheers
MC