100414 10:13:51 [Note] Plugin 'FEDERATED' is disabled. 100414 10:14:01 InnoDB: Started; log sequence number 1 143119171 SSL error: Unable to get certificate from 'C:/OpenSSL/bin/server-cert.pem' 100414 10:14:01 [Warning] Failed to setup SSL 100414 10:14:01 [Warning] SSL error: Unable to get certificate 100414 10:14:02 [Note] Event Scheduler: Loaded 0 events 100414 10:14:02 [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) 100414 10:15:56 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: Normal shutdown 100414 10:15:56 [Note] Event Scheduler: Purging the queue. 0 events 100414 10:15:56 InnoDB: Starting shutdown... 100414 10:16:00 InnoDB: Shutdown completed; log sequence number 1 143119171 100414 10:16:00 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: Shutdown complete 100414 10:16:00 [Note] Plugin 'FEDERATED' is disabled. 100414 10:16:11 InnoDB: Started; log sequence number 1 143119171 100414 10:16:11 [Note] Event Scheduler: Loaded 0 events 100414 10:16:11 [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 18:00:01 - 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=209715200 read_buffer_size=2097152 max_used_connections=47 max_threads=10000 threads_connected=34 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1958544 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x43b42250 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... 0000000140356C20 mysqld.exe!yaSSL::SSL_SESSION::GetBornOn()[yassl_int.cpp:1522] 000000014035BBD3 mysqld.exe!yaSSL::Sessions::lookup()[yassl_int.cpp:1659] 000000014035FAC9 mysqld.exe!yaSSL::ClientHello::Process()[yassl_imp.cpp:1544] 0000000140361382 mysqld.exe!yaSSL::HandShakeHeader::Process()[yassl_imp.cpp:666] 0000000140364FB4 mysqld.exe!yaSSL::DoProcessReply()[handshake.cpp:778] 00000001403650EA mysqld.exe!yaSSL::processReply()[handshake.cpp:792] 000000014034E214 mysqld.exe!yaSSL_accept()[ssl.cpp:337] 0000000140383B4A mysqld.exe!ssl_do()[viossl.c:205] 0000000140097D7F mysqld.exe!check_connection()[sql_connect.cc:805] 000000014009804E mysqld.exe!login_connection()[sql_connect.cc:956] 00000001400981B7 mysqld.exe!handle_one_connection()[sql_connect.cc:1119] 000000014031AE95 mysqld.exe!pthread_start()[my_winthread.c:85] 00000001402E4F67 mysqld.exe!_callthreadstart()[thread.c:295] 00000001402E5035 mysqld.exe!_threadstart()[thread.c:275] 00000000774EBE3D kernel32.dll!BaseThreadInitThunk() 0000000077626A51 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=56664 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. 100422 18:07:20 [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! 100422 18:07:27 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 210501869, file name e:\MySQLBinLog\binlog.000007 100422 18:07:30 InnoDB: Started; log sequence number 2 1814126348 100422 18:07:30 [Note] Recovering after a crash using e:/MySQLBinLog/binlog 100422 18:07:31 [Note] Starting crash recovery... 100422 18:07:31 [Note] Crash recovery finished. 100422 18:07:31 [Note] Event Scheduler: Loaded 0 events 100422 18:07:31 [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) 100423 2:00:02 - 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=209715200 read_buffer_size=2097152 max_used_connections=18 max_threads=10000 threads_connected=8 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1958544 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x3a561fc0 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... 0000000140356C20 mysqld.exe!yaSSL::SSL_SESSION::GetBornOn()[yassl_int.cpp:1522] 000000014035BBD3 mysqld.exe!yaSSL::Sessions::lookup()[yassl_int.cpp:1659] 000000014035FAC9 mysqld.exe!yaSSL::ClientHello::Process()[yassl_imp.cpp:1544] 0000000140361382 mysqld.exe!yaSSL::HandShakeHeader::Process()[yassl_imp.cpp:666] 0000000140364FB4 mysqld.exe!yaSSL::DoProcessReply()[handshake.cpp:778] 00000001403650EA mysqld.exe!yaSSL::processReply()[handshake.cpp:792] 000000014034E214 mysqld.exe!yaSSL_accept()[ssl.cpp:337] 0000000140383B4A mysqld.exe!ssl_do()[viossl.c:205] 0000000140097D7F mysqld.exe!check_connection()[sql_connect.cc:805] 000000014009804E mysqld.exe!login_connection()[sql_connect.cc:956] 00000001400981B7 mysqld.exe!handle_one_connection()[sql_connect.cc:1119] 000000014031AE95 mysqld.exe!pthread_start()[my_winthread.c:85] 00000001402E4F67 mysqld.exe!_callthreadstart()[thread.c:295] 00000001402E5035 mysqld.exe!_threadstart()[thread.c:275] 00000000774EBE3D kernel32.dll!BaseThreadInitThunk() 0000000077626A51 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=582 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. 100423 2:04:33 [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! 100423 2:04:40 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 4485860, file name e:\MySQLBinLog\binlog.000008 100423 2:04:43 InnoDB: Started; log sequence number 2 1922328682 100423 2:04:43 [Note] Recovering after a crash using e:/MySQLBinLog/binlog 100423 2:04:43 [Note] Starting crash recovery... 100423 2:04:43 [Note] Crash recovery finished. 100423 2:04:43 [Note] Event Scheduler: Loaded 0 events 100423 2:04:43 [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) 100428 1:00:02 - 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=209715200 read_buffer_size=2097152 max_used_connections=23 max_threads=10000 threads_connected=8 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1958544 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x3a51c7d0 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... 0000000077648D50 ntdll.dll!RtlFreeHeap() 00000000774FC4CA kernel32.dll!HeapFree() 000000014000581B mysqld.exe!free()[free.c:110] 000000014035A00F mysqld.exe!mySTL::list::pop_front()[list.hpp:246] 000000014035A8BA mysqld.exe!yaSSL::SSL::flushBuffer()[yassl_int.cpp:1123] 000000014034E2B9 mysqld.exe!yaSSL_accept()[ssl.cpp:356] 0000000140383B4A mysqld.exe!ssl_do()[viossl.c:205] 0000000140097D7F mysqld.exe!check_connection()[sql_connect.cc:805] 000000014009804E mysqld.exe!login_connection()[sql_connect.cc:956] 00000001400981B7 mysqld.exe!handle_one_connection()[sql_connect.cc:1119] 000000014031AE95 mysqld.exe!pthread_start()[my_winthread.c:85] 00000001402E4F67 mysqld.exe!_callthreadstart()[thread.c:295] 00000001402E5035 mysqld.exe!_threadstart()[thread.c:275] 00000000774EBE3D kernel32.dll!BaseThreadInitThunk() 0000000077626A51 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=8962 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. 100428 1:04:55 [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! 100428 1:05:01 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 70526585, file name e:\MySQLBinLog\binlog.000009 100428 1:05:04 InnoDB: Started; log sequence number 2 3925835738 100428 1:05:04 [Note] Recovering after a crash using e:/MySQLBinLog/binlog 100428 1:05:04 [Note] Starting crash recovery... 100428 1:05:04 [Note] Crash recovery finished. 100428 1:05:04 [Note] Event Scheduler: Loaded 0 events 100428 1:05:04 [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) 100428 16:00:01 - 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=209715200 read_buffer_size=2097152 max_used_connections=17 max_threads=10000 threads_connected=7 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1958544 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x3a83f400 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... 0000000140356C20 mysqld.exe!yaSSL::SSL_SESSION::GetBornOn()[yassl_int.cpp:1522] 000000014035BBD3 mysqld.exe!yaSSL::Sessions::lookup()[yassl_int.cpp:1659] 000000014035FAC9 mysqld.exe!yaSSL::ClientHello::Process()[yassl_imp.cpp:1544] 0000000140361382 mysqld.exe!yaSSL::HandShakeHeader::Process()[yassl_imp.cpp:666] 0000000140364FB4 mysqld.exe!yaSSL::DoProcessReply()[handshake.cpp:778] 00000001403650EA mysqld.exe!yaSSL::processReply()[handshake.cpp:792] 000000014034E214 mysqld.exe!yaSSL_accept()[ssl.cpp:337] 0000000140383B4A mysqld.exe!ssl_do()[viossl.c:205] 0000000140097D7F mysqld.exe!check_connection()[sql_connect.cc:805] 000000014009804E mysqld.exe!login_connection()[sql_connect.cc:956] 00000001400981B7 mysqld.exe!handle_one_connection()[sql_connect.cc:1119] 000000014031AE95 mysqld.exe!pthread_start()[my_winthread.c:85] 00000001402E4F67 mysqld.exe!_callthreadstart()[thread.c:295] 00000001402E5035 mysqld.exe!_threadstart()[thread.c:275] 00000000774EBE3D kernel32.dll!BaseThreadInitThunk() 0000000077626A51 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=1105 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. 100428 16:04:59 [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! 100428 16:05:05 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 8579387, file name e:\MySQLBinLog\binlog.000010 100428 16:05:08 InnoDB: Started; log sequence number 2 4216592785 100428 16:05:08 [Note] Recovering after a crash using e:/MySQLBinLog/binlog 100428 16:05:08 [Note] Starting crash recovery... 100428 16:05:08 [Note] Crash recovery finished. 100428 16:05:08 [Note] Event Scheduler: Loaded 0 events 100428 16:05:08 [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) 100428 19:00:02 - 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=209715200 read_buffer_size=2097152 max_used_connections=16 max_threads=10000 threads_connected=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1958544 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x3a552f80 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... 0000000140356C20 mysqld.exe!yaSSL::SSL_SESSION::GetBornOn()[yassl_int.cpp:1522] 000000014035BBD3 mysqld.exe!yaSSL::Sessions::lookup()[yassl_int.cpp:1659] 000000014035FAC9 mysqld.exe!yaSSL::ClientHello::Process()[yassl_imp.cpp:1544] 0000000140361382 mysqld.exe!yaSSL::HandShakeHeader::Process()[yassl_imp.cpp:666] 0000000140364FB4 mysqld.exe!yaSSL::DoProcessReply()[handshake.cpp:778] 00000001403650EA mysqld.exe!yaSSL::processReply()[handshake.cpp:792] 000000014034E214 mysqld.exe!yaSSL_accept()[ssl.cpp:337] 0000000140383B4A mysqld.exe!ssl_do()[viossl.c:205] 0000000140097D7F mysqld.exe!check_connection()[sql_connect.cc:805] 000000014009804E mysqld.exe!login_connection()[sql_connect.cc:956] 00000001400981B7 mysqld.exe!handle_one_connection()[sql_connect.cc:1119] 000000014031AE95 mysqld.exe!pthread_start()[my_winthread.c:85] 00000001402E4F67 mysqld.exe!_callthreadstart()[thread.c:295] 00000001402E5035 mysqld.exe!_threadstart()[thread.c:275] 00000000774EBE3D kernel32.dll!BaseThreadInitThunk() 0000000077626A51 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=210 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. 100428 19:04:56 [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! 100428 19:05:02 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 1596284, file name e:\MySQLBinLog\binlog.000011 100428 19:05:05 InnoDB: Started; log sequence number 2 4272012539 100428 19:05:05 [Note] Recovering after a crash using e:/MySQLBinLog/binlog 100428 19:05:05 [Note] Starting crash recovery... 100428 19:05:05 [Note] Crash recovery finished. 100428 19:05:05 [Note] Event Scheduler: Loaded 0 events 100428 19:05:05 [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) 100428 23:00:02 - 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=209715200 read_buffer_size=2097152 max_used_connections=16 max_threads=10000 threads_connected=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1958544 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x3a3d2370 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... 0000000140356C20 mysqld.exe!yaSSL::SSL_SESSION::GetBornOn()[yassl_int.cpp:1522] 000000014035BBD3 mysqld.exe!yaSSL::Sessions::lookup()[yassl_int.cpp:1659] 000000014035FAC9 mysqld.exe!yaSSL::ClientHello::Process()[yassl_imp.cpp:1544] 0000000140361382 mysqld.exe!yaSSL::HandShakeHeader::Process()[yassl_imp.cpp:666] 0000000140364FB4 mysqld.exe!yaSSL::DoProcessReply()[handshake.cpp:778] 00000001403650EA mysqld.exe!yaSSL::processReply()[handshake.cpp:792] 000000014034E214 mysqld.exe!yaSSL_accept()[ssl.cpp:337] 0000000140383B4A mysqld.exe!ssl_do()[viossl.c:205] 0000000140097D7F mysqld.exe!check_connection()[sql_connect.cc:805] 000000014009804E mysqld.exe!login_connection()[sql_connect.cc:956] 00000001400981B7 mysqld.exe!handle_one_connection()[sql_connect.cc:1119] 000000014031AE95 mysqld.exe!pthread_start()[my_winthread.c:85] 00000001402E4F67 mysqld.exe!_callthreadstart()[thread.c:295] 00000001402E5035 mysqld.exe!_threadstart()[thread.c:275] 00000000774EBE3D kernel32.dll!BaseThreadInitThunk() 0000000077626A51 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=284 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. 100428 23:04:56 [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! 100428 23:05:02 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 2174851, file name e:\MySQLBinLog\binlog.000012 100428 23:05:05 InnoDB: Started; log sequence number 3 53200321 100428 23:05:05 [Note] Recovering after a crash using e:/MySQLBinLog/binlog 100428 23:05:05 [Note] Starting crash recovery... 100428 23:05:05 [Note] Crash recovery finished. 100428 23:05:05 [Note] Event Scheduler: Loaded 0 events 100428 23:05:05 [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) 100429 1:00:01 - 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=209715200 read_buffer_size=2097152 max_used_connections=16 max_threads=10000 threads_connected=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1958544 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x3a3139a0 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... 0000000140356C20 mysqld.exe!yaSSL::SSL_SESSION::GetBornOn()[yassl_int.cpp:1522] 000000014035BBD3 mysqld.exe!yaSSL::Sessions::lookup()[yassl_int.cpp:1659] 000000014035FAC9 mysqld.exe!yaSSL::ClientHello::Process()[yassl_imp.cpp:1544] 0000000140361382 mysqld.exe!yaSSL::HandShakeHeader::Process()[yassl_imp.cpp:666] 0000000140364FB4 mysqld.exe!yaSSL::DoProcessReply()[handshake.cpp:778] 00000001403650EA mysqld.exe!yaSSL::processReply()[handshake.cpp:792] 000000014034E214 mysqld.exe!yaSSL_accept()[ssl.cpp:337] 0000000140383B4A mysqld.exe!ssl_do()[viossl.c:205] 0000000140097D7F mysqld.exe!check_connection()[sql_connect.cc:805] 000000014009804E mysqld.exe!login_connection()[sql_connect.cc:956] 00000001400981B7 mysqld.exe!handle_one_connection()[sql_connect.cc:1119] 000000014031AE95 mysqld.exe!pthread_start()[my_winthread.c:85] 00000001402E4F67 mysqld.exe!_callthreadstart()[thread.c:295] 00000001402E5035 mysqld.exe!_threadstart()[thread.c:275] 00000000774EBE3D kernel32.dll!BaseThreadInitThunk() 0000000077626A51 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=142 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. 100429 1:04:55 [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! 100429 1:05:01 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 1057451, file name e:\MySQLBinLog\binlog.000013 100429 1:05:04 InnoDB: Started; log sequence number 3 90803270 100429 1:05:04 [Note] Recovering after a crash using e:/MySQLBinLog/binlog 100429 1:05:04 [Note] Starting crash recovery... 100429 1:05:04 [Note] Crash recovery finished. 100429 1:05:05 [Note] Event Scheduler: Loaded 0 events 100429 1:05:05 [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) 100429 4:00:01 - 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=209715200 read_buffer_size=2097152 max_used_connections=16 max_threads=10000 threads_connected=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1958544 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x3a48cfa0 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... 0000000140356C20 mysqld.exe!yaSSL::SSL_SESSION::GetBornOn()[yassl_int.cpp:1522] 000000014035BBD3 mysqld.exe!yaSSL::Sessions::lookup()[yassl_int.cpp:1659] 000000014035FAC9 mysqld.exe!yaSSL::ClientHello::Process()[yassl_imp.cpp:1544] 0000000140361382 mysqld.exe!yaSSL::HandShakeHeader::Process()[yassl_imp.cpp:666] 0000000140364FB4 mysqld.exe!yaSSL::DoProcessReply()[handshake.cpp:778] 00000001403650EA mysqld.exe!yaSSL::processReply()[handshake.cpp:792] 000000014034E214 mysqld.exe!yaSSL_accept()[ssl.cpp:337] 0000000140383B4A mysqld.exe!ssl_do()[viossl.c:205] 0000000140097D7F mysqld.exe!check_connection()[sql_connect.cc:805] 000000014009804E mysqld.exe!login_connection()[sql_connect.cc:956] 00000001400981B7 mysqld.exe!handle_one_connection()[sql_connect.cc:1119] 000000014031AE95 mysqld.exe!pthread_start()[my_winthread.c:85] 00000001402E4F67 mysqld.exe!_callthreadstart()[thread.c:295] 00000001402E5035 mysqld.exe!_threadstart()[thread.c:275] 00000000774EBE3D kernel32.dll!BaseThreadInitThunk() 0000000077626A51 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=211 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. 100429 4:04:52 [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! 100429 4:04:59 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 1596474, file name e:\MySQLBinLog\binlog.000014 100429 4:05:02 InnoDB: Started; log sequence number 3 147488334 100429 4:05:02 [Note] Recovering after a crash using e:/MySQLBinLog/binlog 100429 4:05:02 [Note] Starting crash recovery... 100429 4:05:02 [Note] Crash recovery finished. 100429 4:05:02 [Note] Event Scheduler: Loaded 0 events 100429 4:05:02 [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) 100429 7:57:16 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: Normal shutdown 100429 7:57:16 [Note] Event Scheduler: Purging the queue. 0 events 100429 7:57:18 [Warning] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: Forcing close of thread 284 user: 'AuthServ' 100429 7:57:18 [Warning] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: Forcing close of thread 10 user: 'root' 100429 7:57:18 [Warning] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: Forcing close of thread 3 user: 'AltosoftMoniTq4o' 100429 7:57:18 [Warning] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: Forcing close of thread 2 user: 'AltosoftMoniTq4o' 100429 7:57:18 InnoDB: Starting shutdown... 100429 7:57:23 InnoDB: Shutdown completed; log sequence number 3 226692402 100429 7:57:23 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: Shutdown complete 100429 7:58:11 [Note] Plugin 'FEDERATED' is disabled. 100429 7:58:20 InnoDB: Started; log sequence number 3 226692402 100429 7:58:21 [Note] Event Scheduler: Loaded 0 events 100429 7:58:21 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: ready for connections. Version: '5.1.46-community-log' socket: '' port: 3306 MySQL Community Server (GPL) 100429 7:58:41 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: Normal shutdown 100429 7:58:41 [Note] Event Scheduler: Purging the queue. 0 events 100429 7:58:43 [Warning] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: Forcing close of thread 3 user: 'AltosoftMoniTq4o' 100429 7:58:43 [Warning] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: Forcing close of thread 1 user: 'AltosoftMoniTq4o' 100429 7:58:43 InnoDB: Starting shutdown... 100429 7:58:49 InnoDB: Shutdown completed; log sequence number 3 226692412 100429 7:58:49 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: Shutdown complete 100429 7:58:49 [Note] Plugin 'FEDERATED' is disabled. 100429 7:58:58 InnoDB: Started; log sequence number 3 226692412 100429 7:58:58 [Note] Event Scheduler: Loaded 0 events 100429 7:58:58 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: ready for connections. Version: '5.1.46-community-log' socket: '' port: 3306 MySQL Community Server (GPL) 100429 7:59:54 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: Normal shutdown 100429 7:59:54 [Note] Event Scheduler: Purging the queue. 0 events 100429 7:59:56 [Warning] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: Forcing close of thread 4 user: 'root' 100429 7:59:56 [Warning] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: Forcing close of thread 3 user: 'AltosoftMoniTq4o' 100429 7:59:56 [Warning] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: Forcing close of thread 2 user: 'AltosoftMoniTq4o' 100429 7:59:56 [Warning] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: Forcing close of thread 1 user: 'AltosoftMoniTq4o' 100429 7:59:56 InnoDB: Starting shutdown... 100429 8:00:02 InnoDB: Shutdown completed; log sequence number 3 226692422 100429 8:00:02 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: Shutdown complete 100429 8:00:02 [Note] Plugin 'FEDERATED' is disabled. 100429 8:00:11 InnoDB: Started; log sequence number 3 226692422 100429 8:00:11 [Note] Event Scheduler: Loaded 0 events 100429 8:00:11 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: ready for connections. Version: '5.1.46-community-log' socket: '' port: 3306 MySQL Community Server (GPL) 100429 15:00:01 - 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=209715200 read_buffer_size=2097152 max_used_connections=27 max_threads=10000 threads_connected=14 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1958544 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x3a5e2420 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... 00000001403578F0 mysqld.exe!yaSSL::SSL_SESSION::GetBornOn()[yassl_int.cpp:1522] 000000014035C8A3 mysqld.exe!yaSSL::Sessions::lookup()[yassl_int.cpp:1659] 0000000140360799 mysqld.exe!yaSSL::ClientHello::Process()[yassl_imp.cpp:1544] 0000000140362052 mysqld.exe!yaSSL::HandShakeHeader::Process()[yassl_imp.cpp:666] 0000000140365C84 mysqld.exe!yaSSL::DoProcessReply()[handshake.cpp:778] 0000000140365DBA mysqld.exe!yaSSL::processReply()[handshake.cpp:792] 000000014034EEE4 mysqld.exe!yaSSL_accept()[ssl.cpp:337] 000000014038481A mysqld.exe!ssl_do()[viossl.c:205] 00000001400981EF mysqld.exe!check_connection()[sql_connect.cc:805] 00000001400984BE mysqld.exe!login_connection()[sql_connect.cc:956] 0000000140098627 mysqld.exe!handle_one_connection()[sql_connect.cc:1119] 000000014031BB65 mysqld.exe!pthread_start()[my_winthread.c:85] 00000001402E5C17 mysqld.exe!_callthreadstart()[thread.c:295] 00000001402E5CE5 mysqld.exe!_threadstart()[thread.c:275] 00000000774EBE3D kernel32.dll!BaseThreadInitThunk() 0000000077626A51 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=698 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. 100429 15:05:02 [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! 100429 15:05:09 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 5096391, file name e:\MySQLBinLog\binlog.000018 100429 15:05:11 InnoDB: Started; log sequence number 3 371024209 100429 15:05:11 [Note] Recovering after a crash using e:/MySQLBinLog/binlog 100429 15:05:11 [Note] Starting crash recovery... 100429 15:05:11 [Note] Crash recovery finished. 100429 15:05:11 [Note] Event Scheduler: Loaded 0 events 100429 15:05:11 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: ready for connections. Version: '5.1.46-community-log' socket: '' port: 3306 MySQL Community Server (GPL)