mysqld.exe has stopped working. Trying to start mysql in XAMPP - mysql

Right now I am learning how to code HTML and PHP and use SQL. I am using XAMPP for mysql. Whenever I try to start mysql I always get an error. This is the error log.
2018-02-24 17:22:30 f04 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.
2018-02-24 17:22:30 3844 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
2018-02-24 17:22:31 3844 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-02-24 17:22:31 3844 [Note] InnoDB: The InnoDB memory heap is disabled
2018-02-24 17:22:31 3844 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-02-24 17:22:31 3844 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-02-24 17:22:31 3844 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-02-24 17:22:31 3844 [Note] InnoDB: Using generic crc32 instructions
2018-02-24 17:22:31 3844 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-02-24 17:22:31 3844 [Note] InnoDB: Completed initialization of buffer pool
2018-02-24 17:22:31 3844 [Note] InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist: a new database to be created!
2018-02-24 17:22:31 3844 [Note] InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
2018-02-24 17:22:31 3844 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile101 size to 5 MB
2018-02-24 17:22:31 3844 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile1 size to 5 MB
2018-02-24 17:22:31 f04 InnoDB: Error: Write to file C:\xampp\mysql\data\ib_logfile101 failed at offset 0.
InnoDB: 512 bytes should have been written, only 0 were written.
InnoDB: Operating system error number 87.
InnoDB: Check that your OS and file system support files of this size.
InnoDB: Check also that the disk is not full or a disk quota exceeded.
InnoDB: FormatMessage: Error number 87 means 'The parameter is incorrect.
'.
InnoDB: Error number 87 means 'Unknown error'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2018-02-24 17:22:31 f04 InnoDB: Operating system error number 87 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
InnoDB: Operation os_file_write_func to file D:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 5097
2018-02-24 17:22:31 3844 [ERROR] InnoDB: File C:\xampp\mysql\data\ib_logfile101: 'os_file_write_func' returned OS error 287. Cannot continue operation
180224 17:22:31 [ERROR] 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.
To report this bug, see https://mariadb.com/kb/en/reporting-bugs
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.
Server version: 10.1.30-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787129 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 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...
mysqld.exe!my_parameter_handler()
mysqld.exe!strxnmov()
mysqld.exe!?compare_ulonglong##YAHPB_K0#Z()
mysqld.exe!no_key()
mysqld.exe!no_key()
mysqld.exe!no_key()
mysqld.exe!no_key()
mysqld.exe!no_key()
mysqld.exe!no_key()
mysqld.exe!no_key()
mysqld.exe!?compare_ulonglong##YAHPB_K0#Z()
mysqld.exe!?compare_ulonglong##YAHPB_K0#Z()
mysqld.exe!?str_result#Item##UAEPAVString##PAV2##Z()
mysqld.exe!?ha_initialize_handlerton##YAHPAUst_plugin_int###Z()
mysqld.exe!?plugin_init##YAHPAHPAPADH#Z()
mysqld.exe!?plugin_init##YAHPAHPAPADH#Z()
mysqld.exe!?init_net_server_extension##YAXPAVTHD###Z()
mysqld.exe!?win_main##YAHHPAPAD#Z()
mysqld.exe!?mysql_service##YAHPAX#Z()
mysqld.exe!strxnmov()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlGetAppContainerNamedObjectPath()
ntdll.dll!RtlGetAppContainerNamedObjectPath()
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.
I have tried deleting the ibdata1, ib_logfile1 and ib_logfile0 and the mysql_error in the C:\xampp\mysql\data folder but it hasn't helped. I dont know what to do and how to fix it. I have read other questions on this website and topic but none of the solutions given help me. Please help!

Related

mysql stop working in xampp with error InnoDB: File (unknown): 'read' returned OS error 223

After searching a lot for the error, could not found a solution.
I am getting the below error when trying to start Mysql in Xampp
2019-01-30 8:24:11 6428 [ERROR] InnoDB: File (unknown): 'read'
returned OS error 223. Cannot continue operation 190130 8:24:11
[ERROR] mysqld got exception 0x80000003 ;
2019-01-30 8:23:30 6428 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-01-30 8:23:30 6428 [Note] InnoDB: The InnoDB memory heap is disabled
2019-01-30 8:23:30 6428 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2019-01-30 8:23:30 6428 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2019-01-30 8:23:30 6428 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-01-30 8:23:30 6428 [Note] InnoDB: Using generic crc32 instructions
2019-01-30 8:23:30 6428 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2019-01-30 8:23:30 6428 [Note] InnoDB: Completed initialization of buffer pool
2019-01-30 8:23:30 6428 [Note] InnoDB: Highest supported file format is Barracuda.
2019-01-30 8:23:30 6428 [Note] InnoDB: The log sequence numbers 1835037 and 1835037 in ibdata files do not match the log sequence number 3178968401 in the ib_logfiles!
2019-01-30 8:23:30 6428 [Note] InnoDB: Database was not shutdown normally!
2019-01-30 8:23:30 6428 [Note] InnoDB: Starting crash recovery.
2019-01-30 8:23:30 6428 [Note] InnoDB: Reading tablespace information from the .ibd files...
2019-01-30 08:24:11 191c InnoDB: Operating system error number 23 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
InnoDB: Operation read to file D:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 3203
2019-01-30 8:24:11 6428 [ERROR] InnoDB: File (unknown): 'read' returned OS error 223. Cannot continue operation
190130 8:24:11 [ERROR] 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.
Additional info with error-log-file
Server version: 10.1.21-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787106 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 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...
mysqld.exe!my_parameter_handler()
mysqld.exe!my_wildcmp_mb_bin()
mysqld.exe!??2Item_change_record##SAPAXIPAX#Z()
mysqld.exe!??2Item_change_record##SAPAXIPAX#Z()
mysqld.exe!?get_trg_event_map#Update_rows_log_event##UAEEXZ()
mysqld.exe!?get_trg_event_map#Update_rows_log_event##UAEEXZ()
mysqld.exe!?get_trg_event_map#Update_rows_log_event##UAEEXZ()
mysqld.exe!?get_trg_event_map#Update_rows_log_event##UAEEXZ()
mysqld.exe!?get_trg_event_map#Update_rows_log_event##UAEEXZ()
mysqld.exe!?get_trg_event_map#Update_rows_log_event##UAEEXZ()
mysqld.exe!?set_required_privilege#Settable_routine_parameter##UAEX_N#Z()
mysqld.exe!?ha_initialize_handlerton##YAHPAUst_plugin_int###Z()
mysqld.exe!?plugin_init##YAHPAHPAPADH#Z()
mysqld.exe!?plugin_init##YAHPAHPAPADH#Z()
mysqld.exe!?init_net_server_extension##YAXPAVTHD###Z()
mysqld.exe!?win_main##YAHHPAPAD#Z()
mysqld.exe!?mysql_service##YAHPAX#Z()
mysqld.exe!my_wildcmp_mb_bin()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!VerSetConditionMask()
ntdll.dll!VerSetConditionMask()
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
Tried many similar solution, but could not solved my problem.
Thanks.
Once I had same issue.
Try doing this :
Open up your XAMPP directory and go to XAMPP/mysql/Data .
ibdata*, auto.cnf, mysql.pid to another folder '
STOP mysql and START it again
if mysql starts then move ibdata back to original folder
And repeat Second Step again.
This worked for me. ibdata* file contains all your database and tables data. Where * is any number given to the ibdata* file. So keep this in mind , whatever happens never delete that file or you'll suffer from Huge amount of important data loss.
I would suggest to put mysql on force_recovery mode by putting below conf in configuration file my.cnf.
[mysqld]
innodb_force_recovery = 1
Restart mysql and exported the entire database.
After exporting is completed, remove the force_recovery option from my.cnf and restarted the service.

mysqld.exe has stopped working in xampp windows?

Mysqld.exe has stopped working in xampp windows.
I started my computer while the XAMPP software was running in the background, MySQL will not start!
2017-11-20 11:05:36 14f4 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.
2017-11-20 11:05:36 5364 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of
small buffer pool size. In order to use backoff, increase buffer pool
at least up to 20MB.
2017-11-20 11:05:36 5364 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-11-20 11:05:36 5364 [Note] InnoDB: The InnoDB memory heap is disabled
2017-11-20 11:05:36 5364 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-11-20 11:05:36 5364 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-11-20 11:05:36 5364 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-11-20 11:05:36 5364 [Note] InnoDB: Using generic crc32 instructions
2017-11-20 11:05:36 5364 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-11-20 11:05:36 5364 [Note] InnoDB: Completed initialization of buffer pool
2017-11-20 11:05:37 5364 [Note] InnoDB: Highest supported file format is Barracuda.
2017-11-20 11:05:37 5364 [Note] InnoDB: The log sequence number 1835037 in ibdata file do not match the log sequence number
11035100176 in the ib_logfiles!
2017-11-20 11:05:37 14f4 InnoDB: Operating system error number 38 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
InnoDB: Operation read to file D:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line
3174
2017-11-20 11:05:37 5364 [ERROR] InnoDB: File (unknown): 'read' returned OS error 238. Cannot continue operation
171120 11:05:37 [ERROR] 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.
To report this bug, see https://mariadb.com/kb/en/reporting-bugs
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.
Server version: 10.1.25-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787107 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 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...
mysqld.exe!my_parameter_handler()
mysqld.exe!strxnmov()
mysqld.exe!?element_index#Item##UAEPAV1#I#Z()
mysqld.exe!?element_index#Item##UAEPAV1#I#Z()
mysqld.exe!?element_index#Item##UAEPAV1#I#Z()
mysqld.exe!?element_index#Item##UAEPAV1#I#Z()
mysqld.exe!?element_index#Item##UAEPAV1#I#Z()
mysqld.exe!?element_index#Item##UAEPAV1#I#Z()
mysqld.exe!?element_index#Item##UAEPAV1#I#Z()
mysqld.exe!?element_index#Item##UAEPAV1#I#Z()
mysqld.exe!?element_index#Item##UAEPAV1#I#Z()
mysqld.exe!?fix_length_and_dec#subselect_partial_match_engine##UAEXPAPAVItem_cache###Z()
mysqld.exe!?ha_initialize_handlerton##YAHPAUst_plugin_int###Z()
mysqld.exe!?plugin_init##YAHPAHPAPADH#Z()
mysqld.exe!?plugin_init##YAHPAHPAPADH#Z()
mysqld.exe!?init_net_server_extension##YAXPAVTHD###Z()
mysqld.exe!?win_main##YAHHPAPAD#Z()
mysqld.exe!?mysql_service##YAHPAX#Z()
mysqld.exe!strxnmov()
kernel32.dll!BaseThreadInitThunk()
ntdll.dll!RtlInitializeExceptionChain()
ntdll.dll!RtlInitializeExceptionChain()
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.
I've also come across this problem recently when I was trying to install XAMPP to my computer running Windows 10.
If you read the warnings that is given by the program you can see that it return a lot of errors regarding OS. Given "D:\win32-packages\build\src\storage\xtradb\os\os0file.cc" I'm assuming that your computer has several disks hence it's not C: drive.
You should try installing XAMPP on your C:/ drive along with the Windows system. This solved the problem for me, previously I had it on my E: drive and I was not able to run mysql, but Apache worked fine.
2LDR: INSTALL XAMPP to your C:/ drive along with your OS and return with feedback :)

mysql large tables (>4Gb) corrupt after local server restart

I hope someone can help me with this problem I'm having (I'm a newbie to Mysql and Stackoverflow, so it's probably something silly I'm missing)...
Whenever I build a large table in MySQL and then restart xampp's local MySQL server, the table then becomes unreadable under code runs that consider the 'whole' table - e.g. I can't drop it, run mySQLCheck on it or run any aggregation functions like sum / count.
This only happens after a server restart. It is fine when I build the table and then, without restarting, I run the 'whole table' codes on it I mentioned above.
Also, even after a server restart I can still do things like see the indexes in place, or sample the first x rows using Limit.
The error thrown is 'mysqld.exe has stopped working' - 'a problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available'
I stop and restart my server using the xampp start / stop control panel buttons
This only seems to happen when the table is more than 4gb. I'm using innodb
Thank you in advance!
Paul
===============================
An example of the error log result is below. This table (wikivisitstable10) was created by adding an index to the prior table. There are no crash issues with the prior table, just this one - and any similar tables >4gb:
`2016-08-25 0:22:57 6804 [Warning] option
'innodb-max-dirty-pages-pct': value 0 adjusted to 0.001
2016-08-25 0:22:57 6804 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-08-25 0:22:57 6804 [Note] InnoDB: The InnoDB memory heap is disabled
2016-08-25 0:22:57 6804 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2016-08-25 0:22:57 6804
[Note] InnoDB: Memory barrier is not used 2016-08-25 0:22:57 6804
[Note] InnoDB: Compressed tables use zlib 1.2.3
2016-08-25 0:22:57 6804 [Note] InnoDB: Using generic crc32 instructions
2016-08-25 0:22:57 6804 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-08-25 0:22:57 6804 [Note] InnoDB: Completed initialization of
buffer pool
2016-08-25 0:22:57 6804 [Note] InnoDB: Highest supported
file format is Barracuda.
2016-08-25 0:22:57 6804 [Note] InnoDB: The log sequence numbers 400931068139 and 400931068139 in ibdata files do not match the log sequence number 400931068159 in the ib_logfiles!
2016-08-25 0:22:57 6804 [Note] InnoDB: Database was not shutdown
normally!
2016-08-25 0:22:57 6804 [Note] InnoDB: Starting crash
recovery.
2016-08-25 0:22:57 6804 [Note] InnoDB: Reading tablespace
information from the .ibd files...
2016-08-25 0:22:58 6804 [Note] InnoDB: Restoring possible half-written data pages
2016-08-25 0:22:58 6804 [Note] InnoDB: from the doublewrite buffer...
2016-08-25 00:22:59 1a94 InnoDB: Error: table 'revil2/page'
InnoDB: in InnoDB data dictionary has tablespace id 180, InnoDB: but a tablespace with that id does not exist. There is InnoDB: a tablespace of name revil2/page and id 181, though. Have InnoDB: you deleted or moved .ibd files?
InnoDB: Please refer to InnoDB: DATADICT LINK (REMOVED)
InnoDB: for how to resolve the issue.
2016-08-25 0:22:59 6804 [ERROR] InnoDB: Table revil2/wikipages7 in the InnoDB data dictionary has tablespace id 175, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to InnoDB: DATA DICT LINK (REMOVED)
InnoDB: for how to resolve the issue.
2016-08-25 0:22:59 6804 [Note] InnoDB: 128 rollback segment(s) are active.
2016-08-25 0:22:59 6804 [Note] InnoDB: Waiting for purge to start
2016-08-25 0:22:59 6804 [Note] InnoDB: Percona XtraDB (PERCONA
WEBSITE (REMOVED)) 5.6.28-76.1 started; log sequence number
400931068159
2016-08-25 0:22:59 5820 [Note] InnoDB: Dumping buffer pool(s) not yet started
2016-08-25 00:22:59 16bc InnoDB: Loading buffer pool(s) from .\\ib_buffer_pool
2016-08-25 0:22:59 6804 [Note] Plugin 'FEEDBACK' is disabled.
2016-08-25 0:22:59 6804 [Note] Server socket created on IP: '::'.
2016-08-25 00:22:59 16bc InnoDB: Buffer pool(s) load completed at 160825 0:22:59
2016-08-25 0:23:00 6804 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections. Version: '10.1.13-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
InnoDB: Error: trying to access page number 1794 in space 299, InnoDB: space name revil2/wikivisitstable10, InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server.
2016-08-25 00:23:46 1388 InnoDB: Assertion failure in thread 5000 in file fil0fil.cc line 5866
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: FORCING INNODB RECOVERY LINK (REMOVED)
InnoDB: about forcing recovery. 160825 0:23:46
[ERROR] 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.
Server version: 10.1.13-MariaDB
key_buffer_size=268435456
read_buffer_size=268435456
max_used_connections=1
max_threads=1001
thread_count=1
It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 788380 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0x1c172e20 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...
mysqld.exe!my_parameter_handler() mysqld.exe!my_mb_ctype_mb()
mysqld.exe!?get_ctx#MDL_ticket##QBEPAVMDL_context##XZ()
mysqld.exe!?get_ctx#MDL_ticket##QBEPAVMDL_context##XZ()
mysqld.exe!?functype#Item_func_dyncol_create##UBE?AW4Functype#Item_func##XZ()
mysqld.exe!?get_ctx#MDL_ticket##QBEPAVMDL_context##XZ()
mysqld.exe!?get_ctx#MDL_ticket##QBEPAVMDL_context##XZ()
mysqld.exe!?get_trg_event_map#Update_rows_log_event##UAEEXZ()
mysqld.exe!?ha_check#handler##QAEHPAVTHD##PAUst_ha_check_opt###Z()
mysqld.exe!??_9handler##$BBAE#AE()
mysqld.exe!?execute#Sql_cmd_check_table##UAE_NPAVTHD###Z()
mysqld.exe!?mysql_execute_command##YAHPAVTHD###Z()
mysqld.exe!?mysql_parse##YAXPAVTHD##PADIPAVParser_state###Z()
mysqld.exe!?dispatch_command##YA_NW4enum_server_command##PAVTHD##PADI#Z()
mysqld.exe!?do_command##YA_NPAVTHD###Z()
mysqld.exe!?threadpool_process_request##YAHPAVTHD###Z()
mysqld.exe!?tp_end##YAXXZ() KERNEL32.DLL!SetUserGeoID()
ntdll.dll!TpSimpleTryPost() ntdll.dll!EtwNotificationRegister()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUnicodeStringToInteger()
ntdll.dll!RtlUnicodeStringToInteger()
Trying to get some variables. Some pointers may be invalid and cause
the dump to abort. Query (0x1c232750): CHECK TABLE
`wikivisitstable10` Connection ID (thread ID): 2 Status: NOT_KILLED`
Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on

XAMPP MySQL won't start error 1217

I recently got a virus in my computer, and had to reinstall windows. Luckily I have everything on separate HDDs, so I thought it was just to reformat and start XAMPP again. But apparently it wasn't that easy, I keep getting this error message when I try to start MySQL
2014-04-18 10:26:35 3200 [Note] Plugin 'FEDERATED' is disabled.
2014-04-18 10:26:35 bb4 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-04-18 10:26:35 3200 [Note] InnoDB: The InnoDB memory heap is disabled
2014-04-18 10:26:35 3200 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-04-18 10:26:35 3200 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-04-18 10:26:35 3200 [Note] InnoDB: Not using CPU crc32 instructions
2014-04-18 10:26:35 3200 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2014-04-18 10:26:35 3200 [Note] InnoDB: Completed initialization of buffer pool
2014-04-18 10:26:43 3200 [Note] InnoDB: Highest supported file format is Barracuda.
2014-04-18 10:26:45 bb4 InnoDB: Operating system error number 1117 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2014-04-18 10:26:45 3200 [ERROR] InnoDB: File D:\xampp\mysql\data\ib_logfile0: 'Windows aio' returned OS error 1217. Cannot continue operation
What can i do to fix it? I don't want to lose the data I have in my MySQL server.
please test this method,copy mysql/data/ibdata1 to another place, if windows couldnt copy that file, this means file crashed with Unwanted windows shutdown.so ibdata1 i/o error Happened. you simlpy must run windows drive error checking on xampp drive. windows automaticaly recover your ibdata1 file.

Starting MySQL. ERROR! Manager of pid-file quit without updating file

I have a Centos and discovered my MySQL wouldn't start after it suddenly failed. I have tried all possible research in google to no avail. Here is the log details
root#27583 [~]# tail -200 /var/log/mysql.log
18:53:49 UTC - mysqld got signal 6 ;
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=134217728
read_buffer_size=2097152
max_used_connections=0
max_threads=500
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2184911 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 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...
stack_bottom = 0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7dad25]
/usr/sbin/mysqld(handle_fatal_signal+0x3e1)[0x693c61]
/lib64/libpthread.so.0[0x7ffa00611ca0]
/lib64/libc.so.6(gsignal+0x35)[0x7ff9ff8112c5]
/lib64/libc.so.6(abort+0x110)[0x7ff9ff812d70]
/usr/sbin/mysqld[0x8deb95]
/usr/sbin/mysqld[0x8b66c9]
/usr/sbin/mysqld[0x8b6c07]
/usr/sbin/mysqld[0x8a87e7]
/usr/sbin/mysqld[0x87eae2]
/usr/sbin/mysqld[0x874ef9]
/usr/sbin/mysqld[0x875514]
/usr/sbin/mysqld[0x876ab1]
/usr/sbin/mysqld[0x8643ba]
/usr/sbin/mysqld[0x82d2a9]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x46)[0x695c66]
/usr/sbin/mysqld[0x587e7c]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0xcf6)[0x58aac6]
/usr/sbin/mysqld[0x5051e3]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x8ad)[0x50829d]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x7ff9ff7fe9c4]
/usr/sbin/mysqld[0x4ff119]
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.
130209 19:53:49 mysqld_safe mysqld from pid file /var/lib/mysql/deepserver.netaviva.net.pid ended
130209 19:58:50 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
130209 19:58:50 [Warning] The syntax '--log-slow-queries' is deprecated and will be removed in a future release. Please use '--slow-query-log'/'--slow-query-log-file' instead.
130209 19:58:50 [Note] Plugin 'FEDERATED' is disabled.
130209 19:58:50 InnoDB: The InnoDB memory heap is disabled
130209 19:58:50 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130209 19:58:50 InnoDB: Compressed tables use zlib 1.2.3
130209 19:58:50 InnoDB: Using Linux native AIO
130209 19:58:50 InnoDB: Initializing buffer pool, size = 128.0M
130209 19:58:50 InnoDB: Completed initialization of buffer pool
130209 19:58:50 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
130209 19:58:50 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...
130209 19:58:50 InnoDB: Error: page 7 log sequence number 7922893671086
InnoDB: is in the future! Current system log sequence number 6086292560908.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
InnoDB: Error: trying to access page number 939544476 in space 0,
InnoDB: space name ./ibdata1,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
130209 19:58:50 InnoDB: Assertion failure in thread 139796076951264 in file fil0fil.c line 4436
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
Please i would greatly appreciate any help to get this working again.