XAMPP MySQL在系统崩溃后不会启动

Question

我在处理项目时遇到了系统崩溃。现在XAMPP v3.2.1中的MySQL不再启动了。请帮忙，我什至不知道在哪里寻找解决方案。

2015-06-30 13:33:16 828 [Note] Plugin 'FEDERATED' is disabled. 
2015-06-30 13:33:16 530 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator. 
2015-06-30 13:33:16 828 [Note] InnoDB: Using atomics to ref count buffer pool pages 
2015-06-30 13:33:16 828 [Note] InnoDB: The InnoDB memory heap is disabled 
2015-06-30 13:33:16 828 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 
2015-06-30 13:33:16 828 [Note] InnoDB: Memory barrier is not used 
2015-06-30 13:33:16 828 [Note] InnoDB: Compressed tables use zlib 1.2.3 
2015-06-30 13:33:16 828 [Note] InnoDB: Not using CPU crc32 instructions 
2015-06-30 13:33:16 828 [Note] InnoDB: Initializing buffer pool, size = 16.0M 
2015-06-30 13:33:16 828 [Note] InnoDB: Completed initialization of buffer pool 
2015-06-30 13:33:17 828 [Note] InnoDB: Restoring page 0 of tablespace 0 
2015-06-30 13:33:17 828 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0 
2015-06-30 13:33:17 828 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\xampp\mysql\data\ibdata1 
2015-06-30 13:33:17 828 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data! 
2015-06-30 13:33:17 828 [ERROR] Plugin 'InnoDB' init function returned error. 
2015-06-30 13:33:17 828 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 
2015-06-30 13:33:17 828 [ERROR] Unknown/unsupported storage engine: InnoDB 
2015-06-30 13:33:17 828 [ERROR] Aborting 

Answer 1

重新安装解决了这个问题。