100720 10:43:16 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
100720 10:43:18  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...
100720 10:43:20  InnoDB: ERROR: We were only able to scan the log up to
InnoDB: 49 3404001280, but a checkpoint was at 49 3404001438.
InnoDB: It is possible that the database is now corrupt!
InnoDB: Error: trying to access page number 38292274 in space 0,
InnoDB: space name .\ibdata1,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
100720 10:43:20  InnoDB: Assertion failure in thread 2424 in file .\fil\fil0fil.c line 4078
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.
100720 10:43:21 - 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=603979776
read_buffer_size=65536
max_used_connections=0
max_threads=100
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 622728 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...
000000014025FEFC    mysqld.exe!fil_io()[fil0fil.c:4078]
00000001402A81E1    mysqld.exe!buf_read_page_low()[buf0rea.c:136]
00000001402A857A    mysqld.exe!buf_read_page()[buf0rea.c:322]
0000000140265619    mysqld.exe!buf_page_get_gen()[buf0buf.c:1207]
000000014027ACD3    mysqld.exe!trx_undo_page_get()[trx0undo.ic:141]
000000014027D5AB    mysqld.exe!trx_undo_mem_create_at_db_start()[trx0undo.c:1279]
000000014027D872    mysqld.exe!trx_undo_lists_init()[trx0undo.c:1354]
00000001402A6292    mysqld.exe!trx_rseg_mem_create()[trx0rseg.c:164]
00000001402A6456    mysqld.exe!trx_rseg_list_and_array_init()[trx0rseg.c:217]
0000000140258F50    mysqld.exe!trx_sys_init_at_db_start()[trx0sys.c:917]
000000014022D336    mysqld.exe!innobase_start_or_create_for_mysql()[srv0start.c:1509]
0000000140217479    mysqld.exe!innobase_init()[ha_innodb.cc:1986]
0000000140099D1F    mysqld.exe!ha_initialize_handlerton()[handler.cc:435]
0000000140032E7C    mysqld.exe!plugin_initialize()[sql_plugin.cc:1019]
00000001400372E9    mysqld.exe!plugin_init()[sql_plugin.cc:1246]
000000014001DAE6    mysqld.exe!init_server_components()[mysqld.cc:3952]
000000014001E2A5    mysqld.exe!win_main()[mysqld.cc:4421]
000000014001E63F    mysqld.exe!mysql_service()[mysqld.cc:4597]
00000001402E6997    mysqld.exe!_callthreadstart()[thread.c:295]
00000001402E6A65    mysqld.exe!_threadstart()[thread.c:275]
0000000076C1BE3D    kernel32.dll!BaseThreadInitThunk()
0000000076E26A51    ntdll.dll!RtlUserThreadStart()
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.
100720 11:13:39 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
100720 11:13:42  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...
100720 11:13:44  InnoDB: ERROR: We were only able to scan the log up to
InnoDB: 49 3404001280, but a checkpoint was at 49 3404001438.
InnoDB: It is possible that the database is now corrupt!
100720 11:13:45  InnoDB: Started; log sequence number 49 3404001438
InnoDB: !!! innodb_force_recovery is set to 5 !!!
100720 11:13:46  InnoDB: Assertion failure in thread 1432 in file .\dict\dict0load.c line 377
InnoDB: Failing assertion: btr_pcur_is_on_user_rec(&pcur, &mtr)
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.
100720 11:13:46 - 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=603979776
read_buffer_size=65536
max_used_connections=0
max_threads=100
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 622728 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x46184c60
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...
InnoDB: Thread 1204 stopped in file G:\mysql-5.1.48-winbuild\mysql-community-nt-5.1.48-build\storage\innobase\include\sync0sync.ic line 115
InnoDB: Thread 1740 stopped in file G:\mysql-5.1.48-winbuild\mysql-community-nt-5.1.48-build\storage\innobase\include\sync0sync.ic line 115
0000000140272018    mysqld.exe!dict_load_columns()[dict0load.c:377]
0000000140274097    mysqld.exe!dict_load_table()[dict0load.c:861]
000000014023419B    mysqld.exe!dict_table_get_low()[dict0dict.ic:610]
0000000140221C7E    mysqld.exe!row_drop_table_for_mysql()[row0mysql.c:3041]
00000001402141C1    mysqld.exe!ha_innobase::delete_table()[ha_innodb.cc:5902]
0000000140076541    mysqld.exe!mysql_rm_tmp_tables()[sql_base.cc:8426]
000000014001E349    mysqld.exe!win_main()[mysqld.cc:4451]
000000014001E63F    mysqld.exe!mysql_service()[mysqld.cc:4597]
00000001402E6997    mysqld.exe!_callthreadstart()[thread.c:295]
00000001402E6A65    mysqld.exe!_threadstart()[thread.c:275]
0000000076C1BE3D    kernel32.dll!BaseThreadInitThunk()
0000000076E26A51    ntdll.dll!RtlUserThreadStart()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0000000000000000=(null)
thd->thread_id=0
thd->killed=NOT_KILLED
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.
100720 11:14:51 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The user has set SRV_FORCE_NO_LOG_REDO on
InnoDB: Skipping log redo
100720 11:14:54  InnoDB: Started; log sequence number 0 0
InnoDB: !!! innodb_force_recovery is set to 6 !!!
100720 11:14:54  InnoDB: Assertion failure in thread 2476 in file .\dict\dict0load.c line 377
InnoDB: Failing assertion: btr_pcur_is_on_user_rec(&pcur, &mtr)
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.
100720 11:14:54 - 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=603979776
read_buffer_size=65536
max_used_connections=0
max_threads=100
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 622728 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x46024c60
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...
0000000140272018    mysqld.exe!dict_load_columns()[dict0load.c:377]
0000000140274097    mysqld.exe!dict_load_table()[dict0load.c:861]
000000014023419B    mysqld.exe!dict_table_get_low()[dict0dict.ic:610]
0000000140221C7E    mysqld.exe!row_drop_table_for_mysql()[row0mysql.c:3041]
00000001402141C1    mysqld.exe!ha_innobase::delete_table()[ha_innodb.cc:5902]
0000000140076541    mysqld.exe!mysql_rm_tmp_tables()[sql_base.cc:8426]
000000014001E349    mysqld.exe!win_main()[mysqld.cc:4451]
000000014001E63F    mysqld.exe!mysql_service()[mysqld.cc:4597]
00000001402E6997    mysqld.exe!_callthreadstart()[thread.c:295]
00000001402E6A65    mysqld.exe!_threadstart()[thread.c:275]
0000000076C1BE3D    kernel32.dll!BaseThreadInitThunk()
0000000076E26A51    ntdll.dll!RtlUserThreadStart()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0000000000000000=(null)
thd->thread_id=0
thd->killed=NOT_KILLED
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.
100720 11:26:02 [Note] Plugin 'FEDERATED' is disabled.
100720 11:26:04  InnoDB: Log file .\ib_logfile0 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile0 size to 224 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB: 100 200
100720 11:26:28  InnoDB: Log file .\ib_logfile1 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile1 size to 224 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB: 100 200
InnoDB: The user has set SRV_FORCE_NO_LOG_REDO on
InnoDB: Skipping log redo
100720 11:26:52  InnoDB: Started; log sequence number 0 0
InnoDB: !!! innodb_force_recovery is set to 6 !!!
100720 11:26:52  InnoDB: Assertion failure in thread 2300 in file .\dict\dict0load.c line 377
InnoDB: Failing assertion: btr_pcur_is_on_user_rec(&pcur, &mtr)
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.
100720 11:26:52 - 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=603979776
read_buffer_size=65536
max_used_connections=0
max_threads=100
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 622728 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x46154c60
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...
InnoDB: Thread 200 stopped in file G:\mysql-5.1.48-winbuild\mysql-community-nt-5.1.48-build\storage\innobase\include\sync0sync.ic line 115
InnoDB: Thread 2524 stopped in file G:\mysql-5.1.48-winbuild\mysql-community-nt-5.1.48-build\storage\innobase\include\sync0sync.ic line 115
0000000140272018    mysqld.exe!dict_load_columns()[dict0load.c:377]
0000000140274097    mysqld.exe!dict_load_table()[dict0load.c:861]
000000014023419B    mysqld.exe!dict_table_get_low()[dict0dict.ic:610]
0000000140221C7E    mysqld.exe!row_drop_table_for_mysql()[row0mysql.c:3041]
00000001402141C1    mysqld.exe!ha_innobase::delete_table()[ha_innodb.cc:5902]
0000000140076541    mysqld.exe!mysql_rm_tmp_tables()[sql_base.cc:8426]
000000014001E349    mysqld.exe!win_main()[mysqld.cc:4451]
000000014001E63F    mysqld.exe!mysql_service()[mysqld.cc:4597]
00000001402E6997    mysqld.exe!_callthreadstart()[thread.c:295]
00000001402E6A65    mysqld.exe!_threadstart()[thread.c:275]
0000000076C1BE3D    kernel32.dll!BaseThreadInitThunk()
0000000076E26A51    ntdll.dll!RtlUserThreadStart()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0000000000000000=(null)
thd->thread_id=0
thd->killed=NOT_KILLED
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.