选择一个表正在关闭我的MySQL服务器（错误2013）

Question

在我的Moodle数据库中，每次选择mdl_certificate表时，MySQL服务器都会关闭。我认为它可能是PHPMyAdmin的一个问题，但我安装了MySQL Workbench并且仍然发生了同样的情况。

所以我尝试了控制台。问题依然存在。我有两张照片：

我从未见过这个。我该如何解决？

谢谢！

更新： 这是显示错误时的日志：

130411  8:51:20 [Note] Plugin 'FEDERATED' is disabled.
130411  8:51:20 InnoDB: The InnoDB memory heap is disabled
130411  8:51:20 InnoDB: Mutexes and rw_locks use Windows interlocked functions
130411  8:51:20 InnoDB: Compressed tables use zlib 1.2.3
130411  8:51:20 InnoDB: Initializing buffer pool, size = 128.0M
130411  8:51:20 InnoDB: Completed initialization of buffer pool
130411  8:51:20 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
130411  8:51:20  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
130411  8:51:20  InnoDB: Operating system error number 1392 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
InnoDB: File name .\prestashopprod
InnoDB: File operation call: 'readdir_next_file'.
InnoDB: Error: os_file_readdir_next_file() returned -1 in
InnoDB: directory .\prestashopprod
InnoDB: Crash recovery may have failed for some .ibd files!
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Last MySQL binlog file position 0 4793, file name .\mysql-bin.000062
130411  8:51:33  InnoDB: Waiting for the background threads to start
130411  8:51:34 InnoDB: 1.1.8 started; log sequence number 795429719
130411  8:51:34 [Note] Recovering after a crash using mysql-bin
130411  8:51:34 [Note] Starting crash recovery...
130411  8:51:34 [Note] Crash recovery finished.
130411  8:51:34 [Note] Event Scheduler: Loaded 0 events
130411  8:51:34 [Note] wampmysqld: ready for connections.
Version: '5.5.20-log'  socket: ''  port: 3306  MySQL Community Server (GPL)

Answer 1

解决方案是删除表并重新创建它们。幸运的是，他们是空的。