Trigger Update kills Maria-DB Server

C:\Program Files\MariaDB 10.1\bin>mysqld.exe --defaults-file="..\data\my.ini" --console

2016-02-17 13:13:27 1724 [Note] mysqld.exe (mysqld 10.1.11-MariaDB-log) starting as process 5020 ...

2016-02-17 13:13:27 1724 [Note] InnoDB: Using mutexes to ref count buffer pool pages

2016-02-17 13:13:27 1724 [Note] InnoDB: The InnoDB memory heap is disabled

2016-02-17 13:13:27 1724 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions

2016-02-17 13:13:27 1724 [Note] InnoDB: Memory barrier is not used

2016-02-17 13:13:27 1724 [Note] InnoDB: Compressed tables use zlib 1.2.3

2016-02-17 13:13:27 1724 [Note] InnoDB: Using generic crc32 instructions

2016-02-17 13:13:27 1724 [Note] InnoDB: Initializing buffer pool, size = 1016.0M

2016-02-17 13:13:28 1724 [Note] InnoDB: Completed initialization of buffer pool

2016-02-17 13:13:28 1724 [Note] InnoDB: Highest supported file format is Barracuda.

2016-02-17 13:13:28 1724 [Note] InnoDB: 128 rollback segment(s) are active.

2016-02-17 13:13:28 1724 [Note] InnoDB: Waiting for purge to start

2016-02-17 13:13:28 1724 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.26-76.0 started; log sequence number 932860601

2016-02-17 13:13:28 7276 [Note] InnoDB: Dumping buffer pool(s) not yet started

2016-02-17 13:13:28 1724 [Note] Plugin 'FEEDBACK' is disabled.

2016-02-17 13:13:28 1724 [Note] Server socket created on IP: '::'.

2016-02-17 13:13:28 1724 [Note] mysqld.exe: ready for connections.

Version: '10.1.11-MariaDB-log'  socket: ''  port: 3309  mariadb.org binary distribution

2016-02-17 13:14:00 652 [ERROR] mysqld.exe: Table '.\c414_w_s\einsaetze_2#P#Current' is marked as crashed and should be repaired

2016-02-17 13:14:00 652 [Warning] Checking table:   '.\c414_w_s\einsaetze_2'

2016-02-17 13:14:00 652 [Warning] Checking table:   '.\c414_w_s\einsaetze_2'

2016-02-17 13:14:00 652 [Warning] Checking table:   '.\c414_w_s\einsaetze_2'

160217 13:17:28 [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 http://kb.askmonty.org/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.1.11-MariaDB-log

key_buffer_size=134217728

read_buffer_size=131072

max_used_connections=25

max_threads=1001

thread_count=25

It is possible that mysqld could use up to

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

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

Thread pointer: 0x0x4d8af048

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!Item_field::switch_to_nullable_fields_processor()[item.cc:2395]

mysqld.exe!switch_to_nullable_trigger_fields()[sql_base.cc:8837]

mysqld.exe!mysql_update()[sql_update.cc:460]

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

mysqld.exe!sp_instr_stmt::exec_core()[sp_head.cc:3215]

mysqld.exe!sp_lex_keeper::reset_lex_and_exec_core()[sp_head.cc:2979]

mysqld.exe!sp_instr_stmt::execute()[sp_head.cc:3131]

mysqld.exe!sp_head::execute()[sp_head.cc:1317]

mysqld.exe!sp_head::execute_trigger()[sp_head.cc:1646]

mysqld.exe!Table_triggers_list::process_triggers()[sql_trigger.cc:2176]

mysqld.exe!mysql_update()[sql_update.cc:860]

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

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

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

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

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

mysqld.exe!io_completion_callback()[threadpool_win.cc:568]

KERNEL32.DLL!BasepAppContainerEnvironmentExtension()

ntdll.dll!TpAllocWait()

ntdll.dll!RtlAcquireSRWLockShared()

KERNEL32.DLL!BaseThreadInitThunk()

ntdll.dll!RtlUserThreadStart()

Trying to get some variables.

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

Query (0x60d0d220): UPDATE EFB_EINSATZ SET PARTITION_ID=NEW.PARTITION_ID WHERE REF_EINSATZ=NEW.ISE_ROWID

Connection ID (thread ID): 10

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=off,table_elimination=on,extended_keys=on,exists_to_in=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.