100422 11:06:50 [Note] Plugin 'FEDERATED' is disabled.
100422 11:06:50  InnoDB: Error: page 7 log sequence number 0 9425
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 1 log sequence number 363 3852580593
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 3 log sequence number 353 1384268271
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 2 log sequence number 363 3855260946
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 4 log sequence number 363 3859689774
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 11 log sequence number 317 2954419044
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 14459 log sequence number 311 3944632671
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 6 log sequence number 0 9647
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 80445 log sequence number 0 9647
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 65537 log sequence number 363 3843138441
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 231753 log sequence number 363 3860177329
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 229377 log sequence number 363 3854607585
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 99776 log sequence number 0 9647
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 98305 log sequence number 363 3849145021
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 94676 log sequence number 363 3846693058
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 81921 log sequence number 363 3849150915
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 173924 log sequence number 0 8359
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 163841 log sequence number 363 3848229396
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 63280 log sequence number 363 3771906169
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 49153 log sequence number 363 3833035575
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 63040 log sequence number 363 3555908716
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 53623 log sequence number 363 3216823323
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 239333 log sequence number 363 3220090099
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 99675 log sequence number 363 3860171331
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 1 row operations to undo
InnoDB: Trx id counter is 7 698775040
100422 11:06:50  InnoDB: Error: page 8 log sequence number 363 3802775274
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 164131 log sequence number 363 3852317659
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 41500 log sequence number 311 4091853043
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 32769 log sequence number 363 3859689774
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 41285 log sequence number 363 3846865971
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 99497 log sequence number 363 3852326435
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 116812 log sequence number 363 3852217940
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 114689 log sequence number 363 3851276144
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 62708 log sequence number 363 3850395817
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 62336 log sequence number 363 3850395817
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 94629 log sequence number 363 3852304050
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 118346 log sequence number 316 2915798125
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 0 log sequence number 0 9236
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 9 log sequence number 362 4021348113
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 10 log sequence number 363 3856148425
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 12 log sequence number 311 3944689259
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 13 log sequence number 0 36808
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 15 log sequence number 0 36808
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 14 log sequence number 0 36808
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
InnoDB: Starting in background the rollback of uncommitted transactions
InnoDB: Cleaning up trx with id 7 698427752
100422 11:06:50  InnoDB: Error: page 274 log sequence number 311 3940211659
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Rollback of non-prepared transactions completed
100422 11:06:50  InnoDB: Error: page 29834 log sequence number 311 3944632665
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 16385 log sequence number 363 3836027157
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 47 log sequence number 311 3944654806
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 101144 log sequence number 311 3944654806
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 48 log sequence number 6 3940576952
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Error: page 116770 log sequence number 311 3944483530
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:50  InnoDB: Started; log sequence number 0 8214
100422 11:06:50 [Note] Event Scheduler: Loaded 0 events
100422 11:06:50 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: ready for connections.
Version: '5.1.45-community-log'  socket: ''  port: 3306  MySQL Community Server (GPL)
100422 11:06:51  InnoDB: Error: page 52 log sequence number 363 3859936640
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:51  InnoDB: Error: page 80395 log sequence number 363 3827958507
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:51  InnoDB: Error: page 80402 log sequence number 363 3827958749
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:51  InnoDB: Error: page 80412 log sequence number 363 3827959007
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:51  InnoDB: Error: page 80438 log sequence number 363 3827959340
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:51  InnoDB: Error: page 138095 log sequence number 363 3860175749
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:51  InnoDB: Error: page 131073 log sequence number 363 3859689710
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:51  InnoDB: Error: page 101995 log sequence number 311 4091869139
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:51  InnoDB: Error: page 107492 log sequence number 317 2948307043
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:51  InnoDB: Error: page 239326 log sequence number 363 3852327040
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:51  InnoDB: Error: page 101184 log sequence number 311 3944687808
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:51  InnoDB: Error: page 46 log sequence number 311 3941063325
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:51  InnoDB: Error: page 94641 log sequence number 311 3944575679
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:51  InnoDB: Error: page 49 log sequence number 193 1519274000
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:51  InnoDB: Error: page 97691 log sequence number 311 3944575887
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:51  InnoDB: Error: page 62661 log sequence number 311 3944574127
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:51  InnoDB: Error: page 235675 log sequence number 363 3827962169
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:51  InnoDB: Error: page 235676 log sequence number 363 3827962184
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:51  InnoDB: Error: page 235677 log sequence number 363 3827962199
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:51  InnoDB: Error: page 235656 log sequence number 363 3827962248
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:51  InnoDB: Error: page 97920 log sequence number 0 9236
InnoDB: is in the future! Current system log sequence number 0 8214.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
100422 11:06:51  InnoDB: Assertion failure in thread 3732 in file .\fsp\fsp0fsp.c line 3314
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.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
100422 11:06:51 - mysqld got exception 0xc0000005 ;
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.
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.

key_buffer_size=30408704
read_buffer_size=65536
max_used_connections=1
max_threads=800
threads_connected=1
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 292833 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
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...
0000000140250D17    mysqld.exe!fseg_free_step_not_header()[fsp0fsp.c:3314]
0000000140276839    mysqld.exe!trx_purge_free_segment()[trx0purge.c:367]
0000000140276B60    mysqld.exe!trx_purge_truncate_rseg_history()[trx0purge.c:506]
0000000140276E50    mysqld.exe!trx_purge_truncate_history()[trx0purge.c:561]
0000000140276E8E    mysqld.exe!trx_purge_truncate_if_arr_empty()[trx0purge.c:580]
000000014027781C    mysqld.exe!trx_purge_fetch_next_rec()[trx0purge.c:958]
00000001402A665A    mysqld.exe!row_purge()[row0purge.c:599]
00000001402A6778    mysqld.exe!row_purge_step()[row0purge.c:672]
0000000140261408    mysqld.exe!que_thr_step()[que0que.c:1256]
0000000140261A40    mysqld.exe!que_run_threads_low()[que0que.c:1322]
0000000140261BCF    mysqld.exe!que_run_threads()[que0que.c:1357]
0000000140277C4D    mysqld.exe!trx_purge()[trx0purge.c:1116]
0000000140219B22    mysqld.exe!srv_master_thread()[srv0srv.c:2589]
0000000077D6B71A    kernel32.dll!BaseThreadStart()
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.
InnoDB: Thread 4840 stopped in file G:\mysql-5.1.45-winbuild\mysql-community-nt-5.1.45-build\storage\innobase\include\sync0sync.ic line 115
InnoDB: Thread 2624 stopped in file G:\mysql-5.1.45-winbuild\mysql-community-nt-5.1.45-build\storage\innobase\include\sync0sync.ic line 115