[GH-ISSUE #2140] [BUG] BSOD when using Tactical RMM Agent console on Windows Server 2016 #3272

New issue

Closed

opened 2026-03-14 07:01:14 +03:00 by kerem · 1 comment

kerem commented

2026-03-14 07:01:14 +03:00

Owner

Originally created by @Slouserg on GitHub (Feb 7, 2025).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2140

When using the Tactical RMM Agent on a Windows Server 2016 environment, attempting to take over the machine via the console and logging in causes the system to crash with a blue screen of death (BSOD).

Steps to Reproduce:

Install Tactical RMM Agent on a Windows Server 2016 machine.
Use the console feature to remotely take over the machine.
Log in via the remote session.
The system crashes with a BSOD shortly after logging in.
Expected Behavior:
The console session should allow remote access and login without causing the system to crash.

Actual Behavior:
The server crashes with a BSOD upon login during a console session via Tactical RMM Agent.

Technical Details (from dump analysis):

Bugcheck Code: 0x3B (SYSTEM_SERVICE_EXCEPTION)
Faulting Module: win32kbase.sys
Faulting Function: RawInputManagerObjectCreateKernelHandle
Process at time of crash: MeshAgent.exe

Stack Trace:
win32kbase!RawInputManagerObjectCreateKernelHandle+0x18
win32kfull!CreatePseudoDigitizerDevice+0x86
win32kfull!InitializeTouchInjectionWithQDCData+0x9c
win32kfull!InitializeTouchInjection+0x4c
win32kfull!NtUserInitializeTouchInjection+0x47
nt!KiSystemServiceCopyEnd+0x13

Originally created by @Slouserg on GitHub (Feb 7, 2025). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2140 When using the Tactical RMM Agent on a Windows Server 2016 environment, attempting to take over the machine via the console and logging in causes the system to crash with a blue screen of death (BSOD). Steps to Reproduce: Install Tactical RMM Agent on a Windows Server 2016 machine. Use the console feature to remotely take over the machine. Log in via the remote session. The system crashes with a BSOD shortly after logging in. Expected Behavior: The console session should allow remote access and login without causing the system to crash. Actual Behavior: The server crashes with a BSOD upon login during a console session via Tactical RMM Agent. Technical Details (from dump analysis): Bugcheck Code: 0x3B (SYSTEM_SERVICE_EXCEPTION) Faulting Module: win32kbase.sys Faulting Function: RawInputManagerObjectCreateKernelHandle Process at time of crash: MeshAgent.exe Stack Trace: win32kbase!RawInputManagerObjectCreateKernelHandle+0x18 win32kfull!CreatePseudoDigitizerDevice+0x86 win32kfull!InitializeTouchInjectionWithQDCData+0x9c win32kfull!InitializeTouchInjection+0x4c win32kfull!NtUserInitializeTouchInjection+0x47 nt!KiSystemServiceCopyEnd+0x13