Sudden database corruption in v.0.11.2 #7426

1. 
   simplex409 commented at 1:26 pm on January 27, 2016: none

   2016-01-27 13:16:53 UpdateTip: new best=0000000000000021c0fe0496cd1943e7bf25f8c12a212cbc497d88ef006d9e06 height=257552 log2_work=71.857863 tx=23690925 date=2013-09-12 15:27:46 progress=0.101313 cache=64.3MiB(57504tx) 2016-01-27 13:16:54 Corruption: block checksum mismatch 2016-01-27 13:16:54 *** System error while flushing: Database corrupted
2. jonasschnelli added the label Block storage on Jan 27, 2016
3. 
   jonasschnelli commented at 1:27 pm on January 27, 2016: contributor

   Please give us some details.. :)

   OS? Virtualized? storage: spinning / SSD / sdcard?

4. 
   simplex409 commented at 1:30 pm on January 27, 2016: none

   Windows 10 pro not virtual spinning drive
5. 
   simplex409 commented at 1:34 pm on January 27, 2016: none

   ---

   System Information

    0  Time of this report: 1/27/2016, 13:33:18
    1         Machine name: WIBBLE
    2     Operating System: Windows 10 Pro 64-bit (10.0, Build 10240) (10240.th1.160104-1507)
    3             Language: English (Regional Setting: English)
    4  System Manufacturer: System manufacturer
    5         System Model: System Product Name
    6                 BIOS: BIOS Date: 03/08/11 11:43:42 Ver: 08.00.15
    7            Processor: AMD Phenom(tm) II X4 955 Processor (4 CPUs), ~3.2GHz
    8               Memory: 16384MB RAM
    9  Available OS Memory: 16382MB RAM
   10            Page File: 3876MB used, 28890MB available
   11          Windows Dir: C:\WINDOWS
   12      DirectX Version: 11.2
   13  DX Setup Parameters: Not found
   14     User DPI Setting: 96 DPI (100 percent)
   15   System DPI Setting: 96 DPI (100 percent)
   16      DWM DPI Scaling: Disabled
   17             Miracast: Not Available
   

   Microsoft Graphics Hybrid: Not Supported DxDiag Version: 10.00.10240.16384 64bit Unicode

6. 
   pstratem commented at 1:47 pm on January 27, 2016: contributor

   is it overclocked?
7. 
   simplex409 commented at 2:05 pm on January 27, 2016: none

   Nope, just running normally
8. 
   unsystemizer commented at 11:45 am on February 6, 2016: contributor

   You could have a corrupt filesystem or malfunctioning disk.
9. laanwj renamed this:
   Fatal Error, v.0.11.2
   Sudden database corruption in v.0.11.2
   on Feb 8, 2016
10. laanwj added the label Data corruption on Feb 9, 2016
11. fanquake closed this on May 18, 2017

    ---

12. MarcoFalke locked this on Sep 8, 2021

Contributors
simplex409 jonasschnelli pstratem unsystemizer

Labels
Block storage Data corruption