If you take time to run mysqldump, even with all default arguments, you will see that triggers in the dump file are created after all insert statements that populate your tables. So no, there will be no duplication, your data after restoring the dump will be the same as in the source database.
[Lots of] Other things can get in the way.
SELinux can cause all sorts of problems, making really basic things fail for no apparent [or announced] reason.
ACL's in the file system can cause confusion, sneakily "tweaking" permissions without you realising it.
Is it possible that the MySQL configuration is different?
These days, a clean install of MySQL ...
I have dealt with this in the past.
Jan 04, 2018 : MySQL - MySQLDump problems with large table
Jan 12, 2012 : Client times out, while MySQL query remains running?
There are three(3) aspects you need to consider
ASPECT #1 : Table Corruption
Please take note of the row number 36705562. If that row number comes back in the error message every single time ...
MariaDB [theDBName]> SOURCE C:\Users\myUserName\theDBName_data.dump
Either of the following should be correct:
MariaDB [theDBName]> SOURCE C:\\Users\\myUserName\\theDBName_data.dump
MariaDB [theDBName]> SOURCE C:/Users/myUserName/theDBName_data.dump
By this script you can backup all of mysql's users except root:
mysql -BNe "select concat('\'',user,'\'@\'',host,'\'') from mysql.user where user != 'root'" | \
while read uh; do mysql -BNe "show grants for $uh" | sed 's/$/;/; s/\\\\/\\/g'; done > grants.sql
So, if you just need to export a specific user like (u_1)
mysql -BNe "select concat('\'',user,'\...