2018-11-12 11:28:18 8748 [ERROR] [FATAL] InnoDB: The page [page id: space = 6277, page number = 16384] can not be read in the buffer pool after 100 attempts. The most likely cause of this error may be that the table has been corrupted. Or the table was filled with an algorithm that is not supported by this instance. If it is not an unpacking failure, you can try to fix this problem using innodb_force_recovery. We will try our best to get some information that will help diagnose the problem but as we have already failed, something is definitely wrong and this may have failed. Server version: 10.2. 2-MariaDB key_buffer_size = 16777216 read_buffer_size = 262144 max_used_connections = 0 max_threads = 1001 thread_count = 0 It is possible that mysqld can use up key_buffer_size + (read_buffer_size + sort_buffer_size) max_threads = 787136 K bytes of memory I hope it is ok; if not, decrease some variables in the equation. Thread pointer: 0x0x0 Trying to backtrace. You can use the following information to find out where mysqld has died. If you do not see any message after that, something went wrong [Note] InnoDB: Loading buffer pool (s) from C: \ xampp \ mysql \ data \ ib_buffer_pool 2018-11-12 14:23:57 6300 [Note] 'FEEDBACK 'plugin is disabled. 2018-11-12 14:23:57 6300 [Note] Server socket created in IP: '::'. 2018-11-12 14:23:57 1828 [Note] InnoDB: Buffer pool (s) load completed in 181112 14:23:57 mysqld.exe! my_parameter_handler () [my_init.c: 256] mysqld.exe! raise () [winsig.c: 587] mysqld.exe! abort () [abort.c: 75] kernel32.dll! HeapFree () mysqld.exe! free () [free.c: 51] The man page athttp: //dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you figure out what is causing the crash. / p>