Crash Issues with MySQL and XAMPP

[SEklogW]

Hello everyone,

I am using XAMPP v3.3.0 on Windows 11. I recently started experiencing issues with XAMPP. The XAMPP screen said to post to the forums with the full log of the crash. To summarize what happened and when, I was working on a .php shopping cart project for a databases assignment for class. I was attempting to create a table in MySQL when the issue began. When I clicked Go to create the table, the issue started. At first the program said I was not connected to MySql, so I attempted to stop and restart the session. I noticed that the port was not showing up next to the MySql area of the XAMPP screen as it usually does. I really do not have more details than that unfortunately, but will post the log below. I apologize for not being able to provide more information. I am currently a student and very new to programming and databases. This is the first issue I have ever had with XAMPP since I started using it for classes back in January. I need access to XAMPP to finish this project, and if anyone could help me solve this issue as soon as possible, it would be greatly appreciated. Log posted below:

2023-04-14 16:22:02 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2023-04-14 16:22:02 0 [Note] InnoDB: Uses event mutexes
2023-04-14 16:22:02 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2023-04-14 16:22:02 0 [Note] InnoDB: Number of pools: 1
2023-04-14 16:22:02 0 [Note] InnoDB: Using SSE2 crc32 instructions
2023-04-14 16:22:02 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2023-04-14 16:22:03 0 [Note] InnoDB: Completed initialization of buffer pool
2023-04-14 16:22:03 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=14893340
2023-04-14 16:22:03 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2023-04-14 16:22:03 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2023-04-14 16:22:03 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2023-04-14 16:22:03 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2023-04-14 16:22:03 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2023-04-14 16:22:03 0 [Note] InnoDB: Waiting for purge to start
2023-04-14 16:22:03 0 [Note] InnoDB: 10.4.27 started; log sequence number 14893349; transaction id 70892
2023-04-14 16:22:03 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2023-04-14 16:22:03 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-04-14 16:22:03 0 [Note] InnoDB: Buffer pool(s) load completed at 230414 16:22:03
2023-04-14 16:22:03 0 [Note] Server socket created on IP: '::'.
2023-04-14 16:55:48 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2023-04-14 16:55:48 0 [Note] InnoDB: Uses event mutexes
2023-04-14 16:55:48 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2023-04-14 16:55:48 0 [Note] InnoDB: Number of pools: 1
2023-04-14 16:55:48 0 [Note] InnoDB: Using SSE2 crc32 instructions
2023-04-14 16:55:48 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2023-04-14 16:55:48 0 [Note] InnoDB: Completed initialization of buffer pool
2023-04-14 16:55:48 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=14893358
2023-04-14 16:55:48 0 [Note] InnoDB: Starting final batch to recover 13 pages from redo log.
2023-04-14 16:55:48 0 [ERROR] [FATAL] InnoDB: Trying to read page number 65537 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)
230414 16:55:48 [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.27-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 = 20302 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!??$_Construct@$00PEBD@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAXQEBD_K@Z()
mysqld.exe!?_Assign_grow@?$_Hash_vec@V?$allocator@V?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@std@@@std@@@std@@QEAAX_KV?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@2@@Z()
mysqld.exe!?_Assign_grow@?$_Hash_vec@V?$allocator@V?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@std@@@std@@@std@@QEAAX_KV?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@2@@Z()
mysqld.exe!?_Assign_grow@?$_Hash_vec@V?$allocator@V?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@std@@@std@@@std@@QEAAX_KV?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@2@@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Assign_grow@?$_Hash_vec@V?$allocator@V?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@std@@@std@@@std@@QEAAX_KV?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@2@@Z()
mysqld.exe!?_Assign_grow@?$_Hash_vec@V?$allocator@V?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@std@@@std@@@std@@QEAAX_KV?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@2@@Z()
mysqld.exe!?_Assign_grow@?$_Hash_vec@V?$allocator@V?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@std@@@std@@@std@@QEAAX_KV?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@2@@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Xlen_string@std@@YAXXZ()
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 https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
information that should help you find out what is causing the crash.
Writing a core file at C:\xampp\mysql\data\
Minidump written to C:\xampp\mysql\data\mysqld.dmp
2023-04-14 16:57:26 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2023-04-14 16:57:26 0 [Note] InnoDB: Uses event mutexes
2023-04-14 16:57:26 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2023-04-14 16:57:26 0 [Note] InnoDB: Number of pools: 1
2023-04-14 16:57:26 0 [Note] InnoDB: Using SSE2 crc32 instructions
2023-04-14 16:57:26 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2023-04-14 16:57:26 0 [Note] InnoDB: Completed initialization of buffer pool
2023-04-14 16:57:26 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=14893358
2023-04-14 16:57:26 0 [Note] InnoDB: Starting final batch to recover 13 pages from redo log.
2023-04-14 16:57:26 0 [ERROR] [FATAL] InnoDB: Trying to read page number 65537 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)
230414 16:57:26 [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.27-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 = 20302 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!??$_Construct@$00PEBD@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAXQEBD_K@Z()
mysqld.exe!?_Assign_grow@?$_Hash_vec@V?$allocator@V?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@std@@@std@@@std@@QEAAX_KV?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@2@@Z()
mysqld.exe!?_Assign_grow@?$_Hash_vec@V?$allocator@V?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@std@@@std@@@std@@QEAAX_KV?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@2@@Z()
mysqld.exe!?_Assign_grow@?$_Hash_vec@V?$allocator@V?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@std@@@std@@@std@@QEAAX_KV?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@2@@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Assign_grow@?$_Hash_vec@V?$allocator@V?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@std@@@std@@@std@@QEAAX_KV?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@2@@Z()
mysqld.exe!?_Assign_grow@?$_Hash_vec@V?$allocator@V?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@std@@@std@@@std@@QEAAX_KV?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@2@@Z()
mysqld.exe!?_Assign_grow@?$_Hash_vec@V?$allocator@V?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@std@@@std@@@std@@QEAAX_KV?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@2@@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Xlen_string@std@@YAXXZ()
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 https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
information that should help you find out what is causing the crash.
Writing a core file at C:\xampp\mysql\data\
Minidump written to C:\xampp\mysql\data\mysqld.dmp
2023-04-14 17:06:16 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2023-04-14 17:06:16 0 [Note] InnoDB: Uses event mutexes
2023-04-14 17:06:16 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2023-04-14 17:06:16 0 [Note] InnoDB: Number of pools: 1
2023-04-14 17:06:16 0 [Note] InnoDB: Using SSE2 crc32 instructions
2023-04-14 17:06:16 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2023-04-14 17:06:16 0 [Note] InnoDB: Completed initialization of buffer pool
2023-04-14 17:06:16 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=14893358
2023-04-14 17:06:16 0 [Note] InnoDB: Starting final batch to recover 13 pages from redo log.
2023-04-14 17:06:16 0 [ERROR] [FATAL] InnoDB: Trying to read page number 65537 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)
230414 17:06:16 [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.27-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 = 20302 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!??$_Construct@$00PEBD@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAXQEBD_K@Z()
mysqld.exe!?_Assign_grow@?$_Hash_vec@V?$allocator@V?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@std@@@std@@@std@@QEAAX_KV?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@2@@Z()
mysqld.exe!?_Assign_grow@?$_Hash_vec@V?$allocator@V?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@std@@@std@@@std@@QEAAX_KV?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@2@@Z()
mysqld.exe!?_Assign_grow@?$_Hash_vec@V?$allocator@V?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@std@@@std@@@std@@QEAAX_KV?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@2@@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Assign_grow@?$_Hash_vec@V?$allocator@V?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@std@@@std@@@std@@QEAAX_KV?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@2@@Z()
mysqld.exe!?_Assign_grow@?$_Hash_vec@V?$allocator@V?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@std@@@std@@@std@@QEAAX_KV?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@2@@Z()
mysqld.exe!?_Assign_grow@?$_Hash_vec@V?$allocator@V?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@std@@@std@@@std@@QEAAX_KV?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@2@@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Xlen_string@std@@YAXXZ()
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 https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
information that should help you find out what is causing the crash.
Writing a core file at C:\xampp\mysql\data\
Minidump written to C:\xampp\mysql\data\mysqld.dmp
2023-04-14 17:46:55 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2023-04-14 17:46:55 0 [Note] InnoDB: Uses event mutexes
2023-04-14 17:46:55 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2023-04-14 17:46:55 0 [Note] InnoDB: Number of pools: 1
2023-04-14 17:46:55 0 [Note] InnoDB: Using SSE2 crc32 instructions
2023-04-14 17:46:55 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2023-04-14 17:46:55 0 [Note] InnoDB: Completed initialization of buffer pool
2023-04-14 17:46:55 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=14893358
2023-04-14 17:46:55 0 [Note] InnoDB: Starting final batch to recover 13 pages from redo log.
2023-04-14 17:46:55 0 [ERROR] [FATAL] InnoDB: Trying to read page number 65537 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)
230414 17:46:55 [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.27-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 = 20302 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!??$_Construct@$00PEBD@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAXQEBD_K@Z()
mysqld.exe!?_Assign_grow@?$_Hash_vec@V?$allocator@V?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@std@@@std@@@std@@QEAAX_KV?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@2@@Z()
mysqld.exe!?_Assign_grow@?$_Hash_vec@V?$allocator@V?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@std@@@std@@@std@@QEAAX_KV?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@2@@Z()
mysqld.exe!?_Assign_grow@?$_Hash_vec@V?$allocator@V?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@std@@@std@@@std@@QEAAX_KV?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@2@@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Assign_grow@?$_Hash_vec@V?$allocator@V?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@std@@@std@@@std@@QEAAX_KV?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@2@@Z()
mysqld.exe!?_Assign_grow@?$_Hash_vec@V?$allocator@V?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@std@@@std@@@std@@QEAAX_KV?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@2@@Z()
mysqld.exe!?_Assign_grow@?$_Hash_vec@V?$allocator@V?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@std@@@std@@@std@@QEAAX_KV?$_List_unchecked_iterator@V?$_List_val@U?$_List_simple_types@U?$pair@QEAU_iobuf@@PEAX@std@@@std@@@std@@@2@@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!?_Xlen_string@std@@YAXXZ()
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 https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
information that should help you find out what is causing the crash.
Writing a core file at C:\xampp\mysql\data\
Minidump written to C:\xampp\mysql\data\mysqld.dmp

[Altrea]

Hi.

I never have had that issue and never read that here at this forums as far as i know.
I did a google search and find this. Maybe this helps:
https://dba.stackexchange.com/questions ... g-table-wi

[SEklogW]

Thanks for the response. I will check out the stack exchange post. Since I am unable to launch MySQL at all, is my best bet to just uninstall and reinstall? I have the DDL saved in a file for this particular database, and luckily the other ones saved on this PC are all test databases for class. I have exact copies on my macbook, but for some reason I get a 403 Error when trying to launch the .php files through my htdocs folder using localhost/fileFolder/filename.php.