Windows Server 2016 Standard, 64 bit, 32GB Ram

ErrorFile.rar contains a text file that contains the following stack trace of a crashing thread:

mysqld.exe!std::locale::_Init()[locale0.cpp:162]

mysqld.exe!std::basic_ios<char,std::char_traits<char> >::init()[ios:164]

mysqld.exe!std::basic_ostringstream<char,std::char_traits<char>,std::allocator<char> >::basic_ostringstream<char,std::char_traits<char>,std::allocator<char> >()[sstream:568]

mysqld.exe!sync_array_print_long_waits_low()[sync0arr.cc:1006]

mysqld.exe!sync_array_print_long_waits()[sync0arr.cc:1073]

mysqld.exe!srv_error_monitor_thread()[srv0srv.cc:1814]

Without a .dmp file of the crash, it is hard to tell what exactly is wrong. There are some preceding messages that indicate that something is holding dict_operation_lock for more than 6 minutes.

Let me know where I can find .dmp file or How I can find out what is holding dict_operation_lock.

Also as I checked, I am unable to find above mentioned lines in given file.

You'll need to run MariaDB server with core-file option. The minidump should be created in the datadir.
See https://mariadb.com/kb/en/enabling-core-dumps/#minidump-files-on-windows for more information.