Mysqld.exe has stopped working in Xampp

Problems with the Windows version of XAMPP, questions, comments, and anything related.

Mysqld.exe has stopped working in Xampp

Postby piyushupadhyay » 14. November 2014 04:00

I have Windows server 2008 R2 (VMware) and using Xampp control panel V3.2.1. For some reason mysqld.exe keeps stopping whenever we try to create the database.
Following are mysql log files:


2014-11-14 06:32:54 1680 [Note] Plugin 'FEDERATED' is disabled.
2014-11-14 06:32:54 470 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2014-11-14 06:32:54 1680 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-11-14 06:32:54 1680 [Note] InnoDB: The InnoDB memory heap is disabled
2014-11-14 06:32:54 1680 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-11-14 06:32:54 1680 [Note] InnoDB: Memory barrier is not used
2014-11-14 06:32:54 1680 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-11-14 06:32:54 1680 [Note] InnoDB: Not using CPU crc32 instructions
2014-11-14 06:32:54 1680 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-11-14 06:32:54 1680 [Note] InnoDB: Completed initialization of buffer pool
2014-11-14 06:32:54 1680 [Note] InnoDB: Highest supported file format is Barracuda.
2014-11-14 06:32:54 1680 [Note] InnoDB: 128 rollback segment(s) are active.
2014-11-14 06:32:54 1680 [Note] InnoDB: Waiting for purge to start
2014-11-14 06:32:54 1680 [Note] InnoDB: 5.6.20 started; log sequence number 1665234
2014-11-14 06:32:54 1680 [Note] Server hostname (bind-address): '*'; port: 3306
2014-11-14 06:32:54 1680 [Note] IPv6 is available.
2014-11-14 06:32:54 1680 [Note] - '::' resolves to '::';
2014-11-14 06:32:54 1680 [Note] Server socket created on IP: '::'.
2014-11-14 06:32:55 1680 [Note] Event Scheduler: Loaded 0 events
2014-11-14 06:32:55 1680 [Note] e:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.20' socket: '' port: 3306 MySQL Community Server (GPL)
14:40:21 UTC - 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=262144
max_used_connections=2
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 = 133778 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x1b3fcdb8
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...
e49ec2 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
e4aacc mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
e4cf50 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
e4d3be mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
ed7d62 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
e40575 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
bbcdb1 mysqld.exe!?ha_create@handler@@QAEHPBDPAUTABLE@@PAUst_ha_create_information@@@Z()
bc150d mysqld.exe!?ha_create_table@@YAHPAVTHD@@PBD11PAUst_ha_create_information@@_N3@Z()
c9e608 mysqld.exe!?mysql_alter_table@@YA_NPAVTHD@@PAD1PAUst_ha_create_information@@PAUTABLE_LIST@@PAVAlter_info@@IPAUst_order@@_N@Z()
d305ea mysqld.exe!?execute@Sql_cmd_alter_table@@UAE_NPAVTHD@@@Z()
bef1ad mysqld.exe!?mysql_execute_command@@YAHPAVTHD@@@Z()
bef81e mysqld.exe!?mysql_parse@@YAXPAVTHD@@PADIPAVParser_state@@@Z()
bf04e7 mysqld.exe!?dispatch_command@@YA_NW4enum_server_command@@PAVTHD@@PADI@Z()
bf135a mysqld.exe!?do_command@@YA_NPAVTHD@@@Z()
c64e59 mysqld.exe!?do_handle_one_connection@@YAXPAVTHD@@@Z()
c64efd mysqld.exe!handle_one_connection()
fbb8cb mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
e10336 mysqld.exe!win_pthread_mutex_trylock()
1046c00 mysqld.exe!my_mb_ctype_mb()
1046c8a mysqld.exe!my_mb_ctype_mb()
75f2338a kernel32.dll!BaseThreadInitThunk()
77cb9f72 ntdll.dll!RtlInitializeExceptionChain()
77cb9f45 ntdll.dll!RtlInitializeExceptionChain()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (1b4cbc80): alter table ohrm_leave_comment
add constraint foreign key (created_by_emp_number)
references hs_hr_employee(emp_number) on delete cascadeConnection ID (thread ID): 8
Status: 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.
2014-11-14 06:41:14 3228 [Note] Plugin 'FEDERATED' is disabled.
2014-11-14 06:41:14 7f4 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2014-11-14 06:41:14 3228 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-11-14 06:41:14 3228 [Note] InnoDB: The InnoDB memory heap is disabled
2014-11-14 06:41:14 3228 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-11-14 06:41:14 3228 [Note] InnoDB: Memory barrier is not used
2014-11-14 06:41:14 3228 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-11-14 06:41:14 3228 [Note] InnoDB: Not using CPU crc32 instructions
2014-11-14 06:41:14 3228 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-11-14 06:41:14 3228 [Note] InnoDB: Completed initialization of buffer pool
2014-11-14 06:41:14 3228 [Note] InnoDB: Highest supported file format is Barracuda.
2014-11-14 06:41:14 3228 [Note] InnoDB: Log scan progressed past the checkpoint lsn 2327450
2014-11-14 06:41:14 3228 [Note] InnoDB: Database was not shutdown normally!
2014-11-14 06:41:14 3228 [Note] InnoDB: Starting crash recovery.
2014-11-14 06:41:14 3228 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-11-14 06:41:14 3228 [Note] InnoDB: Restoring possible half-written data pages
2014-11-14 06:41:14 3228 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 3189600
2014-11-14 06:41:15 3228 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
2014-11-14 06:41:16 3228 [Note] InnoDB: 128 rollback segment(s) are active.
2014-11-14 06:41:16 3228 [Note] InnoDB: Waiting for purge to start
2014-11-14 06:41:16 3228 [Note] InnoDB: 5.6.20 started; log sequence number 3189600
2014-11-14 06:41:16 3228 [Note] Server hostname (bind-address): '*'; port: 3306
2014-11-14 06:41:16 3228 [Note] IPv6 is available.
2014-11-14 06:41:16 3228 [Note] - '::' resolves to '::';
2014-11-14 06:41:16 3228 [Note] Server socket created on IP: '::'.
2014-11-14 06:41:17 3228 [Note] Event Scheduler: Loaded 0 events
2014-11-14 06:41:17 3228 [Note] e:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.20' socket: '' port: 3306 MySQL Community Server (GPL)
2014-11-14 06:42:22 d2c InnoDB: Assertion failure in thread 3372 in file dict0dict.cc line 283
InnoDB: Failing assertion: s
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
14:42:22 UTC - 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=16777216
read_buffer_size=262144
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 = 133778 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x1b4cf958
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...
145a500 mysqld.exe!my_thread_name()
169392d mysqld.exe!my_mb_ctype_mb()
1490fd7 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
14917e3 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
12ed4bb mysqld.exe!?mysql_prepare_alter_table@@YA_NPAVTHD@@PAUTABLE@@PAUst_ha_create_information@@PAVAlter_info@@PAVAlter_table_ctx@@@Z()
12ee514 mysqld.exe!?mysql_alter_table@@YA_NPAVTHD@@PAD1PAUst_ha_create_information@@PAUTABLE_LIST@@PAVAlter_info@@IPAUst_order@@_N@Z()
13805ea mysqld.exe!?execute@Sql_cmd_alter_table@@UAE_NPAVTHD@@@Z()
123f1ad mysqld.exe!?mysql_execute_command@@YAHPAVTHD@@@Z()
123f81e mysqld.exe!?mysql_parse@@YAXPAVTHD@@PADIPAVParser_state@@@Z()
12404e7 mysqld.exe!?dispatch_command@@YA_NW4enum_server_command@@PAVTHD@@PADI@Z()
124135a mysqld.exe!?do_command@@YA_NPAVTHD@@@Z()
12b4e59 mysqld.exe!?do_handle_one_connection@@YAXPAVTHD@@@Z()
12b4efd mysqld.exe!handle_one_connection()
160b8cb mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
1460336 mysqld.exe!win_pthread_mutex_trylock()
1696c00 mysqld.exe!my_mb_ctype_mb()
1696c8a mysqld.exe!my_mb_ctype_mb()
75f2338a kernel32.dll!BaseThreadInitThunk()
77cb9f72 ntdll.dll!RtlInitializeExceptionChain()
77cb9f45 ntdll.dll!RtlInitializeExceptionChain()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (21095050): alter table ohrm_job_candidate
add constraint foreign key (added_person)
references hs_hr_employee(emp_number) on delete set nullConnection ID (thread ID): 4
Status: 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.
2014-11-14 06:49:16 2532 [Note] Plugin 'FEDERATED' is disabled.
2014-11-14 06:49:16 9e8 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2014-11-14 06:49:16 2532 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-11-14 06:49:16 2532 [Note] InnoDB: The InnoDB memory heap is disabled
2014-11-14 06:49:16 2532 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-11-14 06:49:16 2532 [Note] InnoDB: Memory barrier is not used
2014-11-14 06:49:16 2532 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-11-14 06:49:16 2532 [Note] InnoDB: Not using CPU crc32 instructions
2014-11-14 06:49:16 2532 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-11-14 06:49:16 2532 [Note] InnoDB: Completed initialization of buffer pool
2014-11-14 06:49:16 2532 [Note] InnoDB: Highest supported file format is Barracuda.
2014-11-14 06:49:16 2532 [Note] InnoDB: Log scan progressed past the checkpoint lsn 6982361
2014-11-14 06:49:16 2532 [Note] InnoDB: Database was not shutdown normally!
2014-11-14 06:49:16 2532 [Note] InnoDB: Starting crash recovery.
2014-11-14 06:49:16 2532 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-11-14 06:49:17 2532 [Note] InnoDB: Restoring possible half-written data pages
2014-11-14 06:49:17 2532 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 7272884
2014-11-14 06:49:19 2532 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
2014-11-14 06:49:21 2532 [Note] InnoDB: 128 rollback segment(s) are active.
2014-11-14 06:49:21 2532 [Note] InnoDB: Waiting for purge to start
2014-11-14 06:49:21 2532 [Note] InnoDB: 5.6.20 started; log sequence number 7272884
2014-11-14 06:49:21 2532 [Note] Server hostname (bind-address): '*'; port: 3306
2014-11-14 06:49:21 2532 [Note] IPv6 is available.
2014-11-14 06:49:21 2532 [Note] - '::' resolves to '::';
2014-11-14 06:49:21 2532 [Note] Server socket created on IP: '::'.
2014-11-14 06:49:22 2532 [Note] Event Scheduler: Loaded 0 events
2014-11-14 06:49:22 2532 [Note] e:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.20' socket: '' port: 3306 MySQL Community Server (GPL)
14:52:10 UTC - 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=262144
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 = 133778 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x21284090
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...
1019ec2 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
101aacc mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
101cf50 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
101d3be mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
10a7d62 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
1010575 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
d8cdb1 mysqld.exe!?ha_create@handler@@QAEHPBDPAUTABLE@@PAUst_ha_create_information@@@Z()
d9150d mysqld.exe!?ha_create_table@@YAHPAVTHD@@PBD11PAUst_ha_create_information@@_N3@Z()
e6e608 mysqld.exe!?mysql_alter_table@@YA_NPAVTHD@@PAD1PAUst_ha_create_information@@PAUTABLE_LIST@@PAVAlter_info@@IPAUst_order@@_N@Z()
f005ea mysqld.exe!?execute@Sql_cmd_alter_table@@UAE_NPAVTHD@@@Z()
dbf1ad mysqld.exe!?mysql_execute_command@@YAHPAVTHD@@@Z()
dbf81e mysqld.exe!?mysql_parse@@YAXPAVTHD@@PADIPAVParser_state@@@Z()
dc04e7 mysqld.exe!?dispatch_command@@YA_NW4enum_server_command@@PAVTHD@@PADI@Z()
dc135a mysqld.exe!?do_command@@YA_NPAVTHD@@@Z()
e34e59 mysqld.exe!?do_handle_one_connection@@YAXPAVTHD@@@Z()
e34efd mysqld.exe!handle_one_connection()
118b8cb mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
fe0336 mysqld.exe!win_pthread_mutex_trylock()
1216c00 mysqld.exe!my_mb_ctype_mb()
1216c8a mysqld.exe!my_mb_ctype_mb()
7775338a kernel32.dll!BaseThreadInitThunk()
77c89f72 ntdll.dll!RtlInitializeExceptionChain()
77c89f45 ntdll.dll!RtlInitializeExceptionChain()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (213515d0): alter table ohrm_timesheet_action_log
add constraint foreign key (performed_by)
references ohrm_user(id) on delete cascadeConnection ID (thread ID): 4
Status: 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.
2014-11-14 06:52:55 3952 [Note] Plugin 'FEDERATED' is disabled.
2014-11-14 06:52:55 f74 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2014-11-14 06:52:55 3952 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-11-14 06:52:55 3952 [Note] InnoDB: The InnoDB memory heap is disabled
2014-11-14 06:52:55 3952 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-11-14 06:52:55 3952 [Note] InnoDB: Memory barrier is not used
2014-11-14 06:52:55 3952 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-11-14 06:52:55 3952 [Note] InnoDB: Not using CPU crc32 instructions
2014-11-14 06:52:55 3952 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-11-14 06:52:55 3952 [Note] InnoDB: Completed initialization of buffer pool
2014-11-14 06:52:55 3952 [Note] InnoDB: Highest supported file format is Barracuda.
2014-11-14 06:52:55 3952 [Note] InnoDB: Log scan progressed past the checkpoint lsn 9678450
2014-11-14 06:52:55 3952 [Note] InnoDB: Database was not shutdown normally!
2014-11-14 06:52:55 3952 [Note] InnoDB: Starting crash recovery.
2014-11-14 06:52:55 3952 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-11-14 06:52:56 3952 [Note] InnoDB: Restoring possible half-written data pages
2014-11-14 06:52:56 3952 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 9974664
2014-11-14 06:52:57 3952 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
2014-11-14 06:52:57 3952 [Note] InnoDB: 128 rollback segment(s) are active.
2014-11-14 06:52:57 3952 [Note] InnoDB: Waiting for purge to start
2014-11-14 06:52:57 3952 [Note] InnoDB: 5.6.20 started; log sequence number 9974664
2014-11-14 06:52:57 3952 [Note] Server hostname (bind-address): '*'; port: 3306
2014-11-14 06:52:57 3952 [Note] IPv6 is available.
2014-11-14 06:52:57 3952 [Note] - '::' resolves to '::';
2014-11-14 06:52:57 3952 [Note] Server socket created on IP: '::'.
2014-11-14 06:52:58 3952 [Note] Event Scheduler: Loaded 0 events
2014-11-14 06:52:58 3952 [Note] e:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.20' socket: '' port: 3306 MySQL Community Server (GPL)
14:53:51 UTC - 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=262144
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 = 133778 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x1b364f10
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...
14b9ec2 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
14baacc mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
14bcf50 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
14bd3be mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
1547d62 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
14b0575 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
122cdb1 mysqld.exe!?ha_create@handler@@QAEHPBDPAUTABLE@@PAUst_ha_create_information@@@Z()
123150d mysqld.exe!?ha_create_table@@YAHPAVTHD@@PBD11PAUst_ha_create_information@@_N3@Z()
130e608 mysqld.exe!?mysql_alter_table@@YA_NPAVTHD@@PAD1PAUst_ha_create_information@@PAUTABLE_LIST@@PAVAlter_info@@IPAUst_order@@_N@Z()
13a05ea mysqld.exe!?execute@Sql_cmd_alter_table@@UAE_NPAVTHD@@@Z()
125f1ad mysqld.exe!?mysql_execute_command@@YAHPAVTHD@@@Z()
125f81e mysqld.exe!?mysql_parse@@YAXPAVTHD@@PADIPAVParser_state@@@Z()
12604e7 mysqld.exe!?dispatch_command@@YA_NW4enum_server_command@@PAVTHD@@PADI@Z()
126135a mysqld.exe!?do_command@@YA_NPAVTHD@@@Z()
12d4e59 mysqld.exe!?do_handle_one_connection@@YAXPAVTHD@@@Z()
12d4efd mysqld.exe!handle_one_connection()
162b8cb mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
1480336 mysqld.exe!win_pthread_mutex_trylock()
16b6c00 mysqld.exe!my_mb_ctype_mb()
16b6c8a mysqld.exe!my_mb_ctype_mb()
7775338a kernel32.dll!BaseThreadInitThunk()
77c89f72 ntdll.dll!RtlInitializeExceptionChain()
77c89f45 ntdll.dll!RtlInitializeExceptionChain()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (1b3e47e8): alter table ohrm_leave_comment
add constraint foreign key (created_by_emp_number)
references hs_hr_employee(emp_number) on delete cascadeConnection ID (thread ID): 5
Status: 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.
2014-11-14 06:57:16 1348 [Note] Plugin 'FEDERATED' is disabled.
2014-11-14 06:57:16 98c InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2014-11-14 06:57:16 1348 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-11-14 06:57:16 1348 [Note] InnoDB: The InnoDB memory heap is disabled
2014-11-14 06:57:16 1348 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-11-14 06:57:16 1348 [Note] InnoDB: Memory barrier is not used
2014-11-14 06:57:16 1348 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-11-14 06:57:16 1348 [Note] InnoDB: Not using CPU crc32 instructions
2014-11-14 06:57:16 1348 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-11-14 06:57:16 1348 [Note] InnoDB: Completed initialization of buffer pool
2014-11-14 06:57:16 1348 [Note] InnoDB: Highest supported file format is Barracuda.
2014-11-14 06:57:16 1348 [Note] InnoDB: Log scan progressed past the checkpoint lsn 11907579
2014-11-14 06:57:16 1348 [Note] InnoDB: Database was not shutdown normally!
2014-11-14 06:57:16 1348 [Note] InnoDB: Starting crash recovery.
2014-11-14 06:57:16 1348 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-11-14 06:57:17 1348 [Note] InnoDB: Restoring possible half-written data pages
2014-11-14 06:57:17 1348 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 12353565
2014-11-14 06:57:19 1348 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
2014-11-14 06:57:19 1348 [Note] InnoDB: 128 rollback segment(s) are active.
2014-11-14 06:57:19 1348 [Note] InnoDB: Waiting for purge to start
2014-11-14 06:57:19 1348 [Note] InnoDB: 5.6.20 started; log sequence number 12353565
2014-11-14 06:57:19 1348 [Note] Server hostname (bind-address): '*'; port: 3306
2014-11-14 06:57:19 1348 [Note] IPv6 is available.
2014-11-14 06:57:19 1348 [Note] - '::' resolves to '::';
2014-11-14 06:57:19 1348 [Note] Server socket created on IP: '::'.
2014-11-14 06:57:20 1348 [Note] Event Scheduler: Loaded 0 events
2014-11-14 06:57:20 1348 [Note] e:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.20' socket: '' port: 3306 MySQL Community Server (GPL)
14:57:52 UTC - 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=262144
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 = 133778 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x1b36bbd8
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...
13d9ec2 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
13daacc mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
13dcf50 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
13dd3be mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
1467d62 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
13d0575 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
114cdb1 mysqld.exe!?ha_create@handler@@QAEHPBDPAUTABLE@@PAUst_ha_create_information@@@Z()
115150d mysqld.exe!?ha_create_table@@YAHPAVTHD@@PBD11PAUst_ha_create_information@@_N3@Z()
122e608 mysqld.exe!?mysql_alter_table@@YA_NPAVTHD@@PAD1PAUst_ha_create_information@@PAUTABLE_LIST@@PAVAlter_info@@IPAUst_order@@_N@Z()
12c05ea mysqld.exe!?execute@Sql_cmd_alter_table@@UAE_NPAVTHD@@@Z()
117f1ad mysqld.exe!?mysql_execute_command@@YAHPAVTHD@@@Z()
117f81e mysqld.exe!?mysql_parse@@YAXPAVTHD@@PADIPAVParser_state@@@Z()
11804e7 mysqld.exe!?dispatch_command@@YA_NW4enum_server_command@@PAVTHD@@PADI@Z()
118135a mysqld.exe!?do_command@@YA_NPAVTHD@@@Z()
11f4e59 mysqld.exe!?do_handle_one_connection@@YAXPAVTHD@@@Z()
11f4efd mysqld.exe!handle_one_connection()
154b8cb mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
13a0336 mysqld.exe!win_pthread_mutex_trylock()
15d6c00 mysqld.exe!my_mb_ctype_mb()
15d6c8a mysqld.exe!my_mb_ctype_mb()
7775338a kernel32.dll!BaseThreadInitThunk()
77c89f72 ntdll.dll!RtlInitializeExceptionChain()
77c89f45 ntdll.dll!RtlInitializeExceptionChain()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (1b3dfa38): alter table ohrm_leave_comment
add constraint foreign key (created_by_emp_number)
references hs_hr_employee(emp_number) on delete cascadeConnection ID (thread ID): 3
Status: 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.
2014-11-14 07:20:10 2512 [Note] Plugin 'FEDERATED' is disabled.
2014-11-14 07:20:10 370 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2014-11-14 07:20:10 2512 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-11-14 07:20:10 2512 [Note] InnoDB: The InnoDB memory heap is disabled
2014-11-14 07:20:10 2512 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-11-14 07:20:10 2512 [Note] InnoDB: Memory barrier is not used
2014-11-14 07:20:10 2512 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-11-14 07:20:10 2512 [Note] InnoDB: Not using CPU crc32 instructions
2014-11-14 07:20:10 2512 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-11-14 07:20:10 2512 [Note] InnoDB: Completed initialization of buffer pool
2014-11-14 07:20:10 2512 [Note] InnoDB: Highest supported file format is Barracuda.
2014-11-14 07:20:10 2512 [Note] InnoDB: Log scan progressed past the checkpoint lsn 15321210
2014-11-14 07:20:10 2512 [Note] InnoDB: Database was not shutdown normally!
2014-11-14 07:20:10 2512 [Note] InnoDB: Starting crash recovery.
2014-11-14 07:20:10 2512 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-11-14 07:20:10 2512 [Note] InnoDB: Restoring possible half-written data pages
2014-11-14 07:20:10 2512 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 18039903
2014-11-14 07:20:12 2512 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
2014-11-14 07:20:16 2512 [Warning] InnoDB: Resizing redo log from 2*3072 to 2*320 pages, LSN=18039903
2014-11-14 07:20:16 2512 [Warning] InnoDB: Starting to delete and rewrite log files.
2014-11-14 07:20:16 2512 [Note] InnoDB: Setting log file E:\xampp\mysql\data\ib_logfile101 size to 5 MB
2014-11-14 07:20:16 2512 [Note] InnoDB: Setting log file E:\xampp\mysql\data\ib_logfile1 size to 5 MB
2014-11-14 07:20:16 2512 [Note] InnoDB: Renaming log file E:\xampp\mysql\data\ib_logfile101 to E:\xampp\mysql\data\ib_logfile0
2014-11-14 07:20:16 2512 [Warning] InnoDB: New log files created, LSN=18039903
2014-11-14 07:20:16 2512 [Note] InnoDB: 128 rollback segment(s) are active.
2014-11-14 07:20:16 2512 [Note] InnoDB: Waiting for purge to start
2014-11-14 07:20:16 2512 [Note] InnoDB: 5.6.20 started; log sequence number 18039903
2014-11-14 07:20:16 2512 [Note] Server hostname (bind-address): '*'; port: 3306
2014-11-14 07:20:16 2512 [Note] IPv6 is available.
2014-11-14 07:20:16 2512 [Note] - '::' resolves to '::';
2014-11-14 07:20:16 2512 [Note] Server socket created on IP: '::'.
2014-11-14 07:20:16 2512 [Note] Event Scheduler: Loaded 0 events
2014-11-14 07:20:16 2512 [Note] e:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.20' socket: '' port: 3306 MySQL Community Server (GPL)
15:20:53 UTC - 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=262144
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 = 133778 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x20cf2bc8
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...
14e9ec2 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
14eaacc mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
14ecf50 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
14ed3be mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
1577d62 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
14e0575 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
125cdb1 mysqld.exe!?ha_create@handler@@QAEHPBDPAUTABLE@@PAUst_ha_create_information@@@Z()
126150d mysqld.exe!?ha_create_table@@YAHPAVTHD@@PBD11PAUst_ha_create_information@@_N3@Z()
133e608 mysqld.exe!?mysql_alter_table@@YA_NPAVTHD@@PAD1PAUst_ha_create_information@@PAUTABLE_LIST@@PAVAlter_info@@IPAUst_order@@_N@Z()
13d05ea mysqld.exe!?execute@Sql_cmd_alter_table@@UAE_NPAVTHD@@@Z()
128f1ad mysqld.exe!?mysql_execute_command@@YAHPAVTHD@@@Z()
128f81e mysqld.exe!?mysql_parse@@YAXPAVTHD@@PADIPAVParser_state@@@Z()
12904e7 mysqld.exe!?dispatch_command@@YA_NW4enum_server_command@@PAVTHD@@PADI@Z()
129135a mysqld.exe!?do_command@@YA_NPAVTHD@@@Z()
1304e59 mysqld.exe!?do_handle_one_connection@@YAXPAVTHD@@@Z()
1304efd mysqld.exe!handle_one_connection()
165b8cb mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
14b0336 mysqld.exe!win_pthread_mutex_trylock()
16e6c00 mysqld.exe!my_mb_ctype_mb()
16e6c8a mysqld.exe!my_mb_ctype_mb()
7775338a kernel32.dll!BaseThreadInitThunk()
77c89f72 ntdll.dll!RtlInitializeExceptionChain()
77c89f45 ntdll.dll!RtlInitializeExceptionChain()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (21de1fb0): alter table ohrm_leave_comment
add constraint foreign key (created_by_emp_number)
references hs_hr_employee(emp_number) on delete cascadeConnection ID (thread ID): 4
Status: 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.

================================================================================
There is no mysql in services.msc and following are the screenshots

Image Image

Please help!!

I am new to web development
piyushupadhyay
 
Posts: 1
Joined: 14. November 2014 02:50
Operating System: Windows server 2008 R2 VMWARE

Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 74 guests