;InnoDB: End of page dump 090304 20:02:08  InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432                                                                     InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0               InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0                          InnoDB: Page number (if stored to page already) 0,                              InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0          InnoDB: Page may be a freshly allocated page                                    090304 20:02:08InnoDB: Error: trying to access a stray pointer 82463FF8         InnoDB: buf pool start is at 02454000, end at 04154000                          InnoDB: Probable reason is database corruption or memory                        InnoDB: corruption. If this happens in an InnoDB database recovery, see         InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html            InnoDB: how to force recovery.                                                  090304 20:02:08  InnoDB: Assertion failure in thread 7828 in file G:\mysql-5.1.31-winbuild\mysql-community-nt-5.1.31-build\storage\innobase\include\buf0buf.ic line 264                                                                         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.                                                 090304 20:02:08 - 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=16777216                                                        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 = 49014 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...                                                               006E82E0    mysqld.exe!buf_frame_align()[buf0buf.ic:264]                        006CDD0C    mysqld.exe!page_dir_slot_get_rec()[page0page.ic:503]                007189B6    mysqld.exe!page_cur_search_with_match()[page0cur.c:311]             006D3FDC    mysqld.exe!btr_cur_search_to_nth_level()[btr0cur.c:520]             006FD860    mysqld.exe!btr_pcur_open()[btr0pcur.ic:494]                         006FE536    mysqld.exe!btr_pcur_open_on_user_rec()[btr0pcur.c:550]              006F3FBA    mysqld.exe!dict_load_indexes()[dict0load.c:610]                     006F4327    mysqld.exe!dict_load_sys_table()[dict0load.c:1015]                  00706448    mysqld.exe!dict_boot()[dict0boot.c:389]                             006BC72A    mysqld.exe!innobase_start_or_create_for_mysql()[srv0start.c:1521]   006AAB56    mysqld.exe!innobase_init()[ha_innodb.cc:1751]                       00442C78    mysqld.exe!ha_initialize_handlerton()[handler.cc:434]               00563043    mysqld.exe!plugin_initialize()[sql_plugin.cc:1003]                  005678E4    mysqld.exe!plugin_init()[sql_plugin.cc:1212]                        004CFD09    mysqld.exe!init_server_components()[mysqld.cc:3848]                 004D0426    mysqld.exe!win_main()[mysqld.cc:4315]                               004D086D    mysqld.exe!mysql_service()[mysqld.cc:4490]                          004D0B10    mysqld.exe!main()[mysqld.cc:4663]                                   0072809D    mysqld.exe!__tmainCRTStartup()[crt0.c:327]                          00382F2B                                                                        2D00646C                                                                        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.                                                                                            C:\Program Files\MySQL\MySQL Server 5.1\bin>