190205 14:33:43 [ERROR] mysqld got exception 0xe06d7363 ;
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.3.12-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=4
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 = 135358 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0xd069da10
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...

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0xd01275b8): Select * from fmsndcmd where command = 'Insert into PRD_Fournisseurs (FournCodeProduit, FournPrix, odbcLienFournAcomba, zkf_PRD) values ( ''30414100YSP6074'', 0.0648, 90, 5490)'
Connection ID (thread ID): 71
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,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=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.
2019-02-05 14:46:01 0 [Note] CONNECT: Version 1.06.0008 Jan  4 2019 15:42:59
2019-02-05 14:46:01 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2019-02-05 14:46:01 0 [Note] InnoDB: Uses event mutexes
2019-02-05 14:46:01 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-02-05 14:46:01 0 [Note] InnoDB: Number of pools: 1
2019-02-05 14:46:01 0 [Note] InnoDB: Using SSE2 crc32 instructions
2019-02-05 14:46:01 0 [Note] InnoDB: Initializing buffer pool, total size = 1.5G, instances = 12, chunk size = 128M
2019-02-05 14:46:01 0 [Note] InnoDB: Completed initialization of buffer pool
2019-02-05 14:46:01 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=1630914
2019-02-05 14:46:02 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2019-02-05 14:46:02 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2019-02-05 14:46:02 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-02-05 14:46:02 0 [Note] InnoDB: Setting file '.\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-02-05 14:46:02 0 [Note] InnoDB: File '.\ibtmp1' size is now 12 MB.
2019-02-05 14:46:02 0 [Note] InnoDB: Waiting for purge to start
2019-02-05 14:46:02 0 [Note] InnoDB: 10.3.12 started; log sequence number 1630923; transaction id 21
2019-02-05 14:46:02 0 [Note] InnoDB: Loading buffer pool(s) from C:\Program Files (x86)\MariaDB 10.3\data\ib_buffer_pool
2019-02-05 14:46:02 0 [Note] InnoDB: Buffer pool(s) load completed at 190205 14:46:02
2019-02-05 14:46:02 0 [Note] Plugin 'FEEDBACK' is disabled.
2019-02-05 14:46:02 0 [Note] Server socket created on IP: '::'.
2019-02-05 14:46:02 0 [Note] Reading of all Master_info entries succeded
2019-02-05 14:46:02 0 [Note] Added new Master_info '' to hash table