2022-03-29 13:52:14 0 [Warning] No argument was provided to --log-bin and neither --log-basename or --log-bin-index where used; This may cause repliction to break when this server acts as a master and has its hostname changed! Please use '--log-basename=MDB-10-5-15-W2016-88' or '--log-bin=MDB-10-5-15-W2016-88-bin' to avoid this problem. 2022-03-29 13:52:15 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2022-03-29 13:52:15 0 [Note] InnoDB: Number of pools: 1 2022-03-29 13:52:15 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2022-03-29 13:52:15 0 [Note] InnoDB: Initializing buffer pool, total size = 2147483648, chunk size = 134217728 2022-03-29 13:52:15 0 [Note] InnoDB: Completed initialization of buffer pool 2022-03-29 13:52:15 0 [Note] InnoDB: 128 rollback segments are active. 2022-03-29 13:52:15 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2022-03-29 13:52:15 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2022-03-29 13:52:15 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2022-03-29 13:52:15 0 [Note] InnoDB: 10.6.7 started; log sequence number 820720325; transaction id 4145720 2022-03-29 13:52:15 0 [Note] Plugin 'FEEDBACK' is disabled. 2022-03-29 13:52:15 0 [Note] InnoDB: Loading buffer pool(s) from C:\Program Files\MariaDB 10.6\data\ib_buffer_pool 220329 13:52:15 [ERROR] 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. 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.6.7-MariaDB-log key_buffer_size=134217728 read_buffer_size=131072 max_used_connections=0 max_threads=65537 thread_count=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 142742881 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x1cafc940098 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... ntdll.dll!RtlpUnWaitCriticalSection() ntdll.dll!RtlEnterCriticalSection() 2022-03-29 13:52:15 0 [Note] InnoDB: Buffer pool(s) load completed at 220329 13:52:15 ntdll.dll!RtlEnterCriticalSection() server.dll!mysql_manager_submit()[sql_manager.cc:51] server.dll!rpl_slave_state::update()[rpl_gtid.cc:360] server.dll!rpl_load_gtid_slave_state()[rpl_rli.cc:1935] server.dll!binlog_background_thread()[log.cc:10472] server.dll!pfs_spawn_thread()[pfs.cc:2204] server.dll!pthread_start()[my_winthread.c:62] ucrtbase.dll!_o__realloc_base() 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): 1 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,not_null_range_scan=off 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:\Program Files\MariaDB 10.6\data\ Minidump written to C:\Program Files\MariaDB 10.6\data\mysqld.dmp