We both have the same version of Windows server but I'm on .18970 but I have not had any issues with this on any lower build anyway. So the CHR build in it self should not be the issue.
Are you running any other VM in the Hyper-V and do they have any issues?
This is a tricky one but I would start with firmware and drivers for the Hyper-V server and see if this helps. I have seen weird behavior of VM's under Hyper-V with bad drivers before. Also try to get the latest patches for Windows Server and see if this + firmware and drivers help.
We have another CHR running in our HyperV but there's no error like this. Last we do a latest windows update is on June 2018, so we should update the windows again ?