MySQL crash on start

12752 [ERROR] InnoDB: Database page corruption on disk or a failed

12752 [ERROR] InnoDB: Space 0 file \xampp\mysql\data\ibdata1 read of page 410.

2017-01-14 10:54:41 

12752 [ERROR] InnoDB: You may have to recover from a backup.

12752 [ERROR] InnoDB: It is also possible that your operatingsystem has corrupted its own file cache.

2017-01-14 10:54:41 12752 [ERROR] InnoDB: and rebooting your computer removes the error.

2017-01-14 10:54:41 12752 [ERROR] InnoDB: If the corrupt page is an index page you can also try to

2017-01-14 10:54:41 12752 [ERROR] InnoDB: fix the corruption by dumping, dropping, and reimporting

2017-01-14 10:54:41 12752 [ERROR] InnoDB: the corrupt table. You can use CHECK

2017-01-14 10:54:41 12752 [ERROR] InnoDB: TABLE to scan your table for corruption.

2017-01-14 10:54:41 12752 [ERROR] InnoDB: See also http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html about forcing recovery.

2017-01-14 10:54:41 12752 [ERROR] InnoDB: Ending processing because of a corrupt database page.

2017-01-14 10:54:41 31d0  InnoDB: Assertion failure in thread 12752 in file buf0buf.cc line 4877

InnoDB: We intentionally generate a memory trap.

InnoDB: Submit a detailed bug report to http://bugs.mysql.com.

InnoDB: If you get repeated assertion failures or crashes, even

InnoDB: immediately after the mysqld startup, there may be

InnoDB: corruption in the InnoDB tablespace. Please refer to

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

InnoDB: about forcing recovery.

170114 10:54:41 [ERROR] mysqld got exception 0x80000003 ;

This could be because you hit a bug. It is also possible that this binary

or one of the libraries it was linked against is corrupt, improperly built,

or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help

diagnose the problem, but since we have already crashed, 

something is definitely wrong and this may fail.

Server version: 10.1.19-MariaDB

key_buffer_size=16777216

read_buffer_size=262144

max_used_connections=6

max_threads=1001

thread_count=2

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787105 K  bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x11b08780

Attempting backtrace. You can use the following information to find out

where mysqld died. If you see no messages after this, something went

terribly wrong...

mysqld.exe!my_parameter_handler()

mysqld.exe!my_wildcmp_mb_bin()

mysqld.exe!??0PARAM@@QAE@XZ()

mysqld.exe!??0PARAM@@QAE@XZ()

mysqld.exe!no_key()

mysqld.exe!??0PARAM@@QAE@XZ()

mysqld.exe!??0PARAM@@QAE@XZ()

mysqld.exe!??0PARAM@@QAE@XZ()

mysqld.exe!no_key()

mysqld.exe!no_key()

mysqld.exe!??0PARAM@@QAE@XZ()

mysqld.exe!??0PARAM@@QAE@XZ()

mysqld.exe!??0PARAM@@QAE@XZ()

mysqld.exe!??0PARAM@@QAE@XZ()

mysqld.exe!??0PARAM@@QAE@XZ()

mysqld.exe!??0PARAM@@QAE@XZ()

mysqld.exe!no_key()

mysqld.exe!no_key()

mysqld.exe!?ha_write_row@handler@@QAEHPAE@Z()

mysqld.exe!?write_record@@YAHPAVTHD@@PAUTABLE@@PAUst_copy_info@@@Z()

mysqld.exe!?mysql_insert@@YA_NPAVTHD@@PAUTABLE_LIST@@AAV?$List@VItem@@@@AAV?$List@V?$List@VItem@@@@@@22W4enum_duplicates@@_N@Z()

mysqld.exe!?mysql_execute_command@@YAHPAVTHD@@@Z()

mysqld.exe!?mysql_parse@@YAXPAVTHD@@PADIPAVParser_state@@@Z()

mysqld.exe!?dispatch_command@@YA_NW4enum_server_command@@PAVTHD@@PADI@Z()

mysqld.exe!?do_command@@YA_NPAVTHD@@@Z()

mysqld.exe!?threadpool_process_request@@YAHPAVTHD@@@Z()

mysqld.exe!?init_io@@YAHPAUconnection_t@@PAVTHD@@@Z()

kernel32.dll!GetCPInfoExW()

ntdll.dll!WinSqmStartSession()

ntdll.dll!TpSetTimer()

kernel32.dll!BaseThreadInitThunk()

ntdll.dll!RtlInitializeExceptionChain()

ntdll.dll!RtlInitializeExceptionChain()

Attempting backtrace. You can use the following information to find out

where mysqld died. If you see no messages after this, something went

terribly wrong...

mysqld.exe!my_parameter_handler()

mysqld.exe!my_wildcmp_mb_bin()

mysqld.exe!??0PARAM@@QAE@XZ()

mysqld.exe!??0PARAM@@QAE@XZ()

mysqld.exe!no_key()

mysqld.exe!??0PARAM@@QAE@XZ()

mysqld.exe!??0PARAM@@QAE@XZ()

mysqld.exe!no_key()

mysqld.exe!no_key()

mysqld.exe!no_key()

mysqld.exe!no_key()

mysqld.exe!?print@subselect_partial_match_engine@@UAEXPAVString@@W4enum_query_type@@@Z()

mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()

mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()

mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()

mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z()

mysqld.exe!?win_main@@YAHHPAPAD@Z()

mysqld.exe!?mysql_service@@YAHPAX@Z()

mysqld.exe!my_wildcmp_mb_bin()

kernel32.dll!BaseThreadInitThunk()

ntdll.dll!RtlInitializeExceptionChain()

ntdll.dll!RtlInitializeExceptionChain()

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains

information that should help you find out what is causing the crash.