We have had a high correlation of connecting using mesh and one of our servers crashing. It doesn't happen all the time but seems to happen consistently when connecting to the server using Mesh. What logs can I provide to troubleshoot this?
We use teamviewer or screenconnect and don't have the same issue. Running Server 2016 Standard.

Are you saying the MeshCentral server is crashing? Or the agent on a remote machine is causing the remote machines to crash? If it's the server, what version of NodeJS are you using?
Mesh Central server is fine, it's a remote machine that is crashing. Sorry, I should have been more clear.
Ok, so "happen consistently when connecting to the server using Mesh". What you mean by that is that is happens when you connect Remote Desktop? Or do something else?
Yes, when on Desktop and you click "Connect"
Thanks. Bryan will have to give that a try on a Microsoft Server 2016 Standard.
We have a number of Server 2016 Std. installs. It seems to be just this machine for some reason.
I've had that happen randomly with Server 2016 boxes as well. Seems to be less than it used to be. Now it's rare (thankfully!!) that I see it.
I've had that happen randomly with Server 2016 boxes as well. Seems to be less than it used to be. Now it's rare (thankfully!!) that I see it.
Thanks for the information, that's very helpful!
Sadly, I haven't been able to track down why it happens though. It doesn't seem to happen with Server 2019 from what I can tell. And not all 2016 boxes. If anything it seems to happen more with Lenovo ThinkServers running Server 2016- but that might just be anecdotal because I have more of those out there than anything else.
Mine is also a Lenovo ThinkServer.
In general, it should not be possible to crash any operating system with an application from user space (Ring3). Generally, this happens because of bad drivers, bad hardware or OS kernel bug. Bryan does testing of the MeshAgent in virtual machines for many different operating systems, but it's unlikely he can replicate this since he will not be running the same drivers/hardware. I will look up the stop code and see what I can find.
I have the same issue , Meshcentral Agent crashing with BSOD win32kbase.sys
This happens on Server 2016 (latest patches etc) and also on Server 2019 (latest patches).
And i'm running MeshCentral 0.5.85
I have the same issue , Meshcentral Agent crashing with BSOD win32kbase.sys
This happens on Server 2016 (latest patches etc) and also on Server 2019 (latest patches).
And i'm running MeshCentral 0.5.85
Is that on Lenovo Thinkserver by any chance?
I have the same issue , Meshcentral Agent crashing with BSOD win32kbase.sys
This happens on Server 2016 (latest patches etc) and also on Server 2019 (latest patches).
And i'm running MeshCentral 0.5.85Is that on Lenovo Thinkserver by any chance?
No , i'm running HP DL380 G7 (2016) and 2019 server on a Gigabyte Motherboard i5
Hi, is there any progress on this?
I haven't been able to reproduce it yet... I'll look thru what laptops I have in the lab, to see if I can grab a few to test to see if I can get it to BSOD.
Thanks.
Hi All,
We have been observing this with Server 2016 also.
When a Machine is connected after first boot with Mesh, Ctrl+Alt_Del to log it, it works normally.
If the Machine is accessed via Remote Desktop, it works normally.
If the machine is then access via Mesh, The authentication screen is shown but once authenticated, BSOD.
^Can also occur if accessing via Mesh router & RDP.
Hence this appears to be related to the User Switching Service.
This occurs in Azure also, hence it is not a hardware related issue.
If it helps, issue was seen on version 0.5.0-s, upgraded to version 0.6.62 and still occurs.
Updates on this? Mesh is still crashing servers.
Server 2016 Today.