Error: MySQL shutdown unexpectedly.

[BlairS]

Hi.

Just installed Xampp on my new Windows Box. Got Apache up, but when I start MySQL I get the following :

1:11:40 PM [mysql] Error: MySQL shutdown unexpectedly.
1:11:40 PM [mysql] This may be due to a blocked port, missing dependencies,
1:11:40 PM [mysql] improper privileges, a crash, or a shutdown by another method.
1:11:40 PM [mysql] Press the Logs button to view error logs and check
1:11:40 PM [mysql] the Windows Event Viewer for more clues
1:11:40 PM [mysql] If you need more help, copy and post this
1:11:40 PM [mysql] entire log window on the forums

Mysql_error.log:

2023-12-05 13:11:38 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 18480
2023-12-05 13:11:38 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2023-12-05 13:11:38 0 [Note] InnoDB: Uses event mutexes
2023-12-05 13:11:38 0 [Note] InnoDB: Compressed tables use zlib 1.3
2023-12-05 13:11:38 0 [Note] InnoDB: Number of pools: 1
2023-12-05 13:11:38 0 [Note] InnoDB: Using SSE2 crc32 instructions
2023-12-05 13:11:38 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2023-12-05 13:11:38 0 [Note] InnoDB: Completed initialization of buffer pool
2023-12-05 13:11:38 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=300423
2023-12-05 13:11:38 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2023-12-05 13:11:38 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2023-12-05 13:11:38 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2023-12-05 13:11:38 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2023-12-05 13:11:38 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2023-12-05 13:11:38 0 [Note] InnoDB: Waiting for purge to start
2023-12-05 13:11:38 0 [Note] InnoDB: 10.4.32 started; log sequence number 300432; transaction id 170
2023-12-05 13:11:38 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2023-12-05 13:11:38 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-12-05 13:11:38 0 [Note] Server socket created on IP: '127.0.0.1'.
2023-12-05 13:11:38 0 [Note] InnoDB: Buffer pool(s) load completed at 231205 13:11:38
231205 13:11:38 [ERROR] mysqld got exception 0xc0000005 ;
Sorry, we probably made a mistake, and this is a bug.

Your assistance in bug reporting will enable us to fix this for the next release.
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.32-MariaDB source revision: c4143f909528e3fab0677a28631d10389354c491
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=65537
thread_count=6
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 20304 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x17ed3d19f68
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...
VCRUNTIME140.dll!memcpy()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!?ha_rnd_next@handler@@QEAAHPEAE@Z()
mysqld.exe!?rr_sequential@@YAHPEAUREAD_RECORD@@@Z()
mysqld.exe!?acl_init@@YA_N_N@Z()
mysqld.exe!?acl_reload@@YA_NPEAVTHD@@@Z()
mysqld.exe!?acl_init@@YA_N_N@Z()
mysqld.exe!?win_main@@YAHHPEAPEAD@Z()
mysqld.exe!?mysql_service@@YAXPEAX@Z()
ucrtbase.dll!_crt_at_quick_exit()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x0):
Connection ID (thread ID): 0
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=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on

The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ 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

Event Viewer Application Log:

Faulting application name: mysqld.exe, version: 10.4.32.0, time stamp: 0x653fa81d
Faulting module name: VCRUNTIME140.dll, version: 14.36.32532.0, time stamp: 0xc94bf788
Exception code: 0xc0000005
Fault offset: 0x000000000000142c
Faulting process id: 0x0x4830
Faulting application start time: 0x0x1DA27A67D49E9B2
Faulting application path: C:\xampp\mysql\bin\mysqld.exe
Faulting module path: C:\xampp\mysql\bin\VCRUNTIME140.dll
Report Id: c1de7e39-aaff-41db-9aa8-4aaa261b5927
Faulting package full name:
Faulting package-relative application ID:

Anyone have any insights?