mysqld got exception 0x80000003

2020-12-17 14:27:20 0x19ac  InnoDB: Assertion failure in file D:\winx64-packages\build\src\storage\innobase\row\row0sel.cc line 3966

InnoDB: We intentionally generate a memory trap.

InnoDB: Submit a detailed bug report to https://jira.mariadb.org/

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: https://mariadb.com/kb/en/library/innodb-recovery-modes/

InnoDB: about forcing recovery.

201217 14:27:20 [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.13-MariaDB

key_buffer_size=134217728

read_buffer_size=131072

max_used_connections=14

max_threads=65537

thread_count=9

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 136384 K  bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x1d921397fe8

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_sigabrt_handler()[my_thr_init.c:485]

ucrtbase.dll!raise()

ucrtbase.dll!abort()

mysqld.exe!ut_dbg_assertion_failed()[ut0dbg.cc:60]

mysqld.exe!row_search_idx_cond_check()[row0sel.cc:3966]

mysqld.exe!row_search_mvcc()[row0sel.cc:5266]

mysqld.exe!ha_innobase::general_fetch()[ha_innodb.cc:9546]

mysqld.exe!handler::ha_index_prev()[handler.cc:2967]

mysqld.exe!join_read_prev_same()[sql_select.cc:21213]

mysqld.exe!sub_select()[sql_select.cc:20385]

mysqld.exe!do_select()[sql_select.cc:19904]

mysqld.exe!JOIN::exec_inner()[sql_select.cc:4459]

mysqld.exe!JOIN::exec()[sql_select.cc:4242]

mysqld.exe!mysql_select()[sql_select.cc:4675]

mysqld.exe!handle_select()[sql_select.cc:410]

mysqld.exe!execute_sqlcom_select()[sql_parse.cc:6359]

mysqld.exe!mysql_execute_command()[sql_parse.cc:3898]

mysqld.exe!mysql_parse()[sql_parse.cc:7904]

mysqld.exe!dispatch_command()[sql_parse.cc:1844]

mysqld.exe!do_command()[sql_parse.cc:1359]

mysqld.exe!threadpool_process_request()[threadpool_common.cc:365]

mysqld.exe!tp_callback()[threadpool_common.cc:192]

ntdll.dll!RtlInitializeCriticalSection()

ntdll.dll!RtlAcquireSRWLockExclusive()

KERNEL32.DLL!BaseThreadInitThunk()

ntdll.dll!RtlUserThreadStart()

Trying to get some variables.

Some pointers may be invalid and cause the dump to abort.

Query (0x1d92322d050): select v.log_view_id, r.mysql_process_id from redcap_log_view_requests r, redcap_log_view v 

                where v.log_view_id = r.log_view_id and r.script_execution_time is null 

                and r.ui_id = 2823 and v.ts > '2020-12-17 14:22:20' and v.session_id = 'pntgb8kr3ce4t6414650ut1qai'

                and v.page = 'DataEntry/record_home.php' and r.mysql_process_id != '86276'

                order by v.log_view_id desc

Connection ID (thread ID): 86276

Status: KILL_CONNECTION

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 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:\MariaDB\data\

Minidump written to D:\MariaDB\data\mysqld.dmp

InnoDB: using atomic writes.

Faulting application name: mysqld.exe, version: 10.4.13.0, time stamp: 0x5eb7245c

Faulting module name: mysqld.exe, version: 10.4.13.0, time stamp: 0x5eb7245c

Exception code: 0x80000003

Fault offset: 0x0000000000653ea2

Faulting process id: 0xb94

Faulting application start time: 0x01d6d32f72d3a2e4

Faulting application path: C:\Program Files\MariaDB 10.4\bin\mysqld.exe

Faulting module path: C:\Program Files\MariaDB 10.4\bin\mysqld.exe

Report Id: 68585755-7716-4b4b-a9cb-fc371383bfad

Faulting package full name: 

Faulting package-relative application ID: