Windows Server 2019 Datacenter

Can you provide which MariaDB version you are using?

Is there more to the log?

MDEV-22761 looks similar in crash location (and Windows)

Yes I am running 10.5.5 on Windows Server 2019 Datacenter with 32 Cores and 256G RAM.

Here is everything related to the error:

2020-09-27 16:00:15 0x30b4 InnoDB: Assertion failure in file D:\winx64-packages\build\src\storage\innobase\row\row0sel.cc line 3961
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.
200927 16:00:15 [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.5.5-MariaDB-log
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=20
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 = 136409 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x16188eaeb28
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...
server.dll!my_parameter_handler()[my_init.c:281]
ucrtbase.dll!raise()
ucrtbase.dll!abort()
server.dll!ut_dbg_assertion_failed()[ut0dbg.cc:60]
server.dll!row_search_idx_cond_check()[row0sel.cc:3961]
server.dll!row_search_mvcc()[row0sel.cc:5207]
server.dll!ha_innobase::general_fetch()[ha_innodb.cc:9047]
server.dll!handler::ha_index_prev()[handler.cc:3191]
server.dll!QUICK_SELECT_DESC::get_next()[opt_range.cc:12499]
server.dll!rr_quick()[records.cc:395]
server.dll!sub_select()[sql_select.cc:20660]
server.dll!do_select()[sql_select.cc:20175]
server.dll!JOIN::exec_inner()[sql_select.cc:4450]
server.dll!JOIN::exec()[sql_select.cc:4232]
server.dll!mysql_select()[sql_select.cc:4657]
server.dll!handle_select()[sql_select.cc:417]
server.dll!execute_sqlcom_select()[sql_parse.cc:6210]
server.dll!mysql_execute_command()[sql_parse.cc:3932]
server.dll!mysql_parse()[sql_parse.cc:7998]
server.dll!dispatch_command()[sql_parse.cc:1870]
server.dll!do_command()[sql_parse.cc:1348]
server.dll!threadpool_process_request()[threadpool_common.cc:354]
server.dll!tp_callback()[threadpool_common.cc:194]
ntdll.dll!RtlInitializeCriticalSection()
ntdll.dll!RtlReleaseSRWLockExclusive()
KERNEL32.dll!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.

Thanks vpilling, that confirms this bug as identical to MDEV-22761 (stack trace).

If you have further information please provide it there.

My bug appears very often. Sometimes >20+ per day. The interval seems very random.

Ouch.

Per other bug, seem to be rowid_filter. Disabling this should avoid this bug until next release. I'm fairly sure I have a fix for this.

https://mariadb.com/kb/en/rowid-filtering-optimization/