090106 7:22:11 - 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=2 max_threads=235 threads_connected=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 93067 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x2eeb0048 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... 7C82B583 ntdll.dll!wcscpy() 7C82BA81 ntdll.dll!RtlTimeFieldsToTime() 7C82B646 ntdll.dll!wcscpy() 00722257 mysqld.exe!free()[free.c:110] 0062F65F mysqld.exe!free_root()[my_alloc.c:355] 0052727E mysqld.exe!open_tables()[sql_base.cc:4732] 0052773A mysqld.exe!open_and_lock_tables_derived()[sql_base.cc:4956] 00542A4D mysqld.exe!mysql_insert()[sql_insert.cc:613] 004B366E mysqld.exe!wait_if_global_read_lock()[lock.cc:1525] 00556753 mysqld.exe!mysql_parse()[sql_parse.cc:5791] 00557234 mysqld.exe!dispatch_command()[sql_parse.cc:1202] 00558017 mysqld.exe!do_command()[sql_parse.cc:861] 005DA441 mysqld.exe!handle_one_connection()[sql_connect.cc:1115] 006401FB mysqld.exe!pthread_start()[my_winthread.c:85] 00724593 mysqld.exe!_callthreadstart()[thread.c:293] F773E900 Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 2CBF08C8=Insert into usuarios_actividad (idusuario, fecha, idactividad) values('2795', '2009-01-06 08:22:11', 6) thd->thread_id=586 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. InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 090106 7:25:38 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... 090106 7:25:38 InnoDB: Started; log sequence number 0 16843950 090106 7:25:39 [Note] Event Scheduler: Loaded 0 events 090106 7:25:39 [Note] D:\Archivos de programa\MySQL\MySQL Server 5.1\bin\mysqld: ready for connections. Version: '5.1.30-community' socket: '' port: 3306 MySQL Community Server (GPL)