080509 2:03:32 [Note] Plugin 'InnoDB' disabled by command line option 0: Cache flush: 33 pages, 13 writes in 0 seconds (33 pps) 080509 2:03:32 [Warning] C:/bk/mysql-6.0-falcon-team/sql/relwithdebinfo/mysqld.exe: unknown option '--loose-skip-ndbcluster' 080509 2:03:32 [Note] Event Scheduler: Loaded 0 events 080509 2:03:32 [Note] C:/bk/mysql-6.0-falcon-team/sql/relwithdebinfo/mysqld.exe: ready for connections. Version: '6.0.6-alpha-log' socket: '' port: 9306 Source distribution 0: Switching log files (512 used) 0: Record chill: transaction 82, 10320 records, 5242560 bytes 1: Record chill: transaction 83, 10300 records, 5242700 bytes 1: Record chill: transaction 83, 10300 records, 5242700 bytes 1: Record chill: transaction 83, 10300 records, 5242700 bytes 2: Record thaw: transaction 83, 10301 records, 5243209 bytes 2: Record thaw: transaction 83, 10301 records, 5243209 bytes 2: Record chill: transaction 84, 10300 records, 5242700 bytes 2: Record chill: transaction 84, 10300 records, 5242700 bytes 2: Record chill: transaction 84, 10300 records, 5242700 bytes 3: Record chill: transaction 84, 10300 records, 5242700 bytes 3: Record chill: transaction 84, 10300 records, 5242700 bytes 3: Record chill: transaction 84, 10300 records, 5242700 bytes 080509 2:03:36 - mysqld got exception 0x80000003 ; 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=1048576 read_buffer_size=131072 max_used_connections=1 max_threads=151 thread_count=1 connection_count=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 60371 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... 00000000775B4EA0 ntdll.dll!DbgBreakPoint() 000000014042E2CE mysqld.exe!Error::error()[error.cpp:71] 000000014042E313 mysqld.exe!Error::assertionFailed()[error.cpp:76] 00000001404A1F22 mysqld.exe!SerialLogControl::nextRecord()[seriallogcontrol.cpp:316] 00000001404CADAA mysqld.exe!SerialLogTransaction::commit()[seriallogtransaction.cpp:87] 00000001404C9CB8 mysqld.exe!Gopher::gopherThread()[gopher.cpp:71] 000000014044C758 mysqld.exe!Thread::thread()[thread.cpp:163] 000000014044CA4E mysqld.exe!Thread::thread()[thread.cpp:141] 000000007746495D kernel32.dll!BaseThreadInitThunk() 0000000077598791 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. Writing a core file Minidump written to C:\bk\mysql-6.0-falcon-team\mysql-test\var\master-data\mysqld.dmp 4: Record thaw: transaction 84, 10301 records, 5243209 bytes