XAMPP的MYSQL無法開啟

目前用XAMPP來架WORDPRESS
第一次架設成功 wordpress也可操作設定
但重開機後 XAMPP的MYSQL就無法開啟
期間有修改wordpress檔案上限
在 php.ini 中修改以下的設定
max_execution_time = 300
max_input_time = 600
memory_limit = 160M
post_max_size = 500M
upload_max_filesize = 600M
之後再重開XANPP控制面板卻無法開啟MYSQL
之後又把php.ini 數職還原
還是無法開啟MYSQL
怎麼處理能開起MYSQL

MYSQL的日誌資訊
2013-08-20 10:41:12 4824 [Note] Plugin 'FEDERATED' is disabled.
2013-08-20 10:41:12 1260 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.
2013-08-20 10:41:12 4824 [Note] InnoDB: The InnoDB memory heap is disabled
2013-08-20 10:41:12 4824 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-08-20 10:41:12 4824 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-08-20 10:41:12 4824 [Note] InnoDB: Not using CPU crc32 instructions
2013-08-20 10:41:12 4824 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-08-20 10:41:12 4824 [Note] InnoDB: Completed initialization of buffer pool
2013-08-20 10:41:12 4824 [Note] InnoDB: Highest supported file format is Barracuda.
2013-08-20 10:41:12 4824 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 2819520 in the ib_logfiles!
2013-08-20 10:41:12 4824 [Note] InnoDB: Database was not shutdown normally!
2013-08-20 10:41:12 4824 [Note] InnoDB: Starting crash recovery.
2013-08-20 10:41:12 4824 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-08-20 10:41:12 4824 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace wordpress/wp_terms which uses space ID: 3 at filepath: .\wordpress\wp_terms.ibd
InnoDB: Error: could not open single-table tablespace file .\wordpress\wp_terms.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.