Sorry, But If you get a BSOD then you got driver issus or other HW issues. (often driver)
Not sure why you use a screenshot that is not from you. because then it is useless.
the stopcode information is the only useful info on the BSOD screen. the one that in the screenshot say CRITICAL_PROCES_DIED
but since the screenshot is not from you, that is probably not the same for you. Often it say what driver that caused the crash.
or some hit of it. Sometimes you can find that info in the windows event log. but sometimes it crashed faster then it was enable to log that. (depends on what issue it was)
However. MC is a user mode program. And when you get a BSOD something went bad in the Windows kernel.
A User mode program can not cause a BSOD. Only when a critical error happen inside the Windows Kernel a BSOD is happening.
And no code from MC is run in the kernel. MC possibly call some windows API, Windows does something. load some driver, send data via some HW driver and something happens that it cant correct for and it result in a BSOD. It is out of the control of MC.
(If you can make this happen on more then 1 machine. you should report this to MS, because then it might be a bug in Windows.)
I use MC with RDP with Win10 a lot with no issue. so this is not a generic issue with rdp and win10.
(Doing a quick search online. that kind of BSOD is very very common. )
Edit
Looks like this is a know bug in Windows. and MS have tried to fix it. But it is not fixed yet.
https://social.technet.microsoft.com/Forums/windows/en-US/26691ffa-7b9c-4691-9639-03156a0c6215/windows-10-crashed-when-accessing-tsclient-path-from-remote-desktop-via-far-manager?forum=win10itprosecurity