mysql 数据库连接断掉_mysql数据库不知道为什么就断开连接了

我用的是mysql的默认my.ini，当数据库中一个表的数据大概有10W时只要对这个表进行操作mysql服务就自动断开连接。

my.ini：

[mysqld]

basedir = c:\mysql

datadir = c:\mysql/data

[WinMySQLAdmin]

Server=c:\mysql/bin/mysqld-nt.exe

user=root

password=123

[client]

port  = 3306

socket  = /tmp/mysql.sock

[mysqld]

port  = 3306

default-character-set=utf8

default-storage-engine=INNODB

socket  = /tmp/mysql.sock

skip-locking

key_buffer = 256M

max_allowed_packet = 1M

table_cache = 20148

sort_buffer_size = 8M

read_buffer_size = 8M

read_rnd_buffer_size = 32M

myisam_sort_buffer_size = 64M

thread_cache_size = 32

query_cache_size= 256M

thread_concurrency = 32

skip-federated

log-bin=mysql-bin

binlog_format=mixed

server-id = 1

[mysqldump]

quick

max_allowed_packet = 16M

[mysql]

default-character-set = utf8

no-auto-rehash

[isamchk]

key_buffer = 128M

sort_buffer_size = 128M

read_buffer = 2M

write_buffer = 2M

[myisamchk]

key_buffer = 128M

sort_buffer_size = 128M

read_buffer = 2M

write_buffer = 2M

[mysqlhotcopy]

interactive-timeout

错误文件：

InnoDB: The log sequence number in ibdata files does not match

InnoDB: the log sequence number in the ib_logfiles!

101129 18:47:44  InnoDB: Database was not shut down normally!

InnoDB: Starting crash recovery.

InnoDB: Reading tablespace information from the .ibd files...

InnoDB: Restoring possible half-written data pages from the doublewrite

InnoDB: buffer...

InnoDB: Last MySQL binlog file position 0 24919987, file name .\mysql-bin.000207

101129 18:47:44  InnoDB: Started; log sequence number 0 523673363

101129 18:47:44 [Note] Recovering after a crash using mysql-bin

101129 18:47:44 [Note] Starting crash recovery...

101129 18:47:44 [Note] Crash recovery finished.

101129 18:47:44 [Note] Event Scheduler: Loaded 0 events

101129 18:47:44 [Note] MySQL: ready for connections.

Version: '5.1.32-community-log'  socket: ''  port: 3306  MySQL Community Server (GPL)

101129 18:47:52  InnoDB: Error: space id and page n:o stored in the page

InnoDB: read in are 2010513407:2545792693, should be 0:5438!

InnoDB: Database page corruption on disk or a failed

InnoDB: file read of page 5438.

InnoDB: You may have to recover from a backup.

101129 18:47:52  InnoDB: Page dump in ascii and hex (16384 bytes):

len 16384; hex InnoDB: End of page dump

101129 18:47:52  InnoDB: Page checksum 1519369607, prior-to-4.0.14-form checksum 1582900278

InnoDB: stored checksum 3612728661, prior-to-4.0.14-form stored checksum 4294956373

InnoDB: Page lsn 1567979381 3065353909, low 4 bytes of lsn at page end 46773

InnoDB: Page number (if stored to page already) 2545792693,

InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 2010513407

InnoDB: Database page corruption on disk or a failed

InnoDB: file read of page 5438.

InnoDB: You may have to recover from a backup.

InnoDB: It is also possible that your operating

InnoDB: system has corrupted its own file cache

InnoDB: and rebooting your computer removes the

InnoDB: error.

InnoDB: If the corrupt page is an index page

InnoDB: you can also try to fix the corruption

InnoDB: by dumping, dropping, and reimporting

InnoDB: the corrupt table. You can use CHECK

InnoDB: TABLE to scan your table for corruption.

InnoDB: See also http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html

InnoDB: about forcing recovery.

InnoDB: Ending processing because of a corrupt database page.

我不知道是我配置问题还是数据问题