mysqld got exception 0x80000003

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

mysqld got exception 0x80000003

Postby av_admin_1984 » 25. January 2020 19:34

Hello everyone
I have problem in Starting mysql , the error code : mysqld got exception 0x80000003
The log file information :
InnoDB: using atomic writes.
2020-01-25 21:57:57 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2020-01-25 21:57:57 0 [Note] InnoDB: Uses event mutexes
2020-01-25 21:57:57 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-01-25 21:57:57 0 [Note] InnoDB: Number of pools: 1
2020-01-25 21:57:57 0 [Note] InnoDB: Using generic crc32 instructions
2020-01-25 21:57:57 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2020-01-25 21:57:57 0 [Note] InnoDB: Completed initialization of buffer pool
2020-01-25 21:57:57 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=1025789160
2020-01-25 21:57:58 0 [ERROR] [FATAL] InnoDB: Trying to read page number 4294967294 in space 0, space name innodb_system, which is outside the tablespace bounds. Byte offset 0, len 16384Please check that the configuration matches the InnoDB system tablespace location (ibdata files)
200125 21:57:58 [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.4.8-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=65537
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 20287 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()
ucrtbase.DLL!raise()
ucrtbase.DLL!abort()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!parse_user()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!?ha_initialize_handlerton@@YAHPEAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPEAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPEAPEAD@Z()
mysqld.exe!?mysql_service@@YAXPEAX@Z()
mysqld.exe!?mysqld_main@@YAHHPEAPEAD@Z()
mysqld.exe!strxnmov()
kernel32.dll!BaseThreadInitThunk()
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 at D:\xampp\mysql\data\

How to fix that ?
av_admin_1984
 
Posts: 1
Joined: 25. January 2020 19:31
XAMPP version: XAMPP Version: 7.3.10
Operating System: Win 7 X64

Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 145 guests