support

Bitte oder Registrieren, um Beiträge und Themen zu erstellen.

spacedeskConsole.exe crashes intermittently (confirmed via Event Viewer)//

Hi,

I’ve been experiencing recurring freezes with spacedesk since Wednesday, 08/19, and wanted to share detailed findings, including Event Viewer logs, in case it helps the team or other users.

Setup:

  • Setup 1: Windows 11 Pro notebook + Samsung Galaxy Tab S10 FE
  • Setup 2: Windows 11 Home notebook + Samsung Galaxy Tab S6 Lite
  • Each setup connects to a different WiFi network (different routers/ISPs)

Troubleshooting already performed:

  • Tested over WiFi on both setups — freezes on both
  • Tested over USB cable connection — freezes the same way, ruling out network/WiFi as the cause
  • Fully uninstalled and reinstalled the app on both notebooks and both tablets
  • Restarted router/modem
  • Checked Task Manager during freezes — memory usage stayed stable (0–1.6%), not climbing, so it does not appear to be a memory leak

Symptom:
The tablet screen freezes intermittently while connected. Timing is inconsistent — sometimes after 1 minute, sometimes 5 minutes, sometimes up to an hour of use. The only way to recover is to fully close and reopen the app on the notebook; it doesn’t recover on its own.

Root cause found via Windows Event Viewer:
I found repeated crash events confirming spacedeskConsole.exe itself is crashing (not a network or config issue):

Application Error
AppName: spacedeskConsole.exe
AppVersion: 1.1.1733.99
ModuleName: KERNELBASE.dll
ModuleVersion: 10.0.26100.9168
ExceptionCode: c0020001 (and c000041d on a related event)
AppPath: C:\Program Files\datronicsoft\spacedesk\spacedeskConsole.exe

A corresponding .NET Runtime event recorded:

Application: spacedeskConsole.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0020001

This crash pattern was captured on both setups, confirming it’s not isolated to one machine, one network, or one connection method (WiFi vs USB).

I’ve uploaded the full .evtx log file (attached above) in case it’s useful for debugging.

Hoping this helps identify the bug — happy to run any additional tests that could help resolve this issue.

I’d also like to take this opportunity to thank you for the excellent free tool.

Hochgeladene Dateien:
  • Du musst dich anmelden um auf Uploads zugreifen zu können.

Hi @vkapperg,

For further analysis of the issue, please send us the logs of your Primary PC by opening the spacedesk Driver console as administrator and clicking on Diagnostics then follow the steps below:

1. Download the DebugView.
2. Check the Diagnostic Collection box.
3. Reproduce the issue e.g. by connecting the spacedesk Viewer app.
4. Uncheck the Diagnostic Collection box.
5. Click “Save All Information” button (this might take a while to finish).
6. Compress/Zip the folder which contains the logs, then attach to your next reply to this post. If the folder exceeds 512kb, you may upload it to Dropbox or Google Drive then include the download link on your next reply.

Thank you.

Good day.

Just wanted to let you know that I had to uninstall spaceDesk and install the only copy I have of the installer (Ver. 2.2.22) just to make it work again without crashing the android tablet (via USB) external monitor.

It seems to be working now (no crashes on the android external monitor).

Sorry, due to current workload, I do not have time to download DebugView and check. I hope you’ll be able to resolve the problem.

Hi,

I’m sending the DebugView logs from both of my setups (Setup 1: Windows 11 Pro notebook + Galaxy Tab S10 FE – Setup 2: Windows 11 Home notebook + Galaxy Tab S6 Lite) via the Google Drive link below, for your analysis, as you requested.

Setup 1 – 2026-08-24-082523-spacedeskRuntimeDiagnostics.zip

Setup 2 – 2026-08-24-085640-spacedeskRuntimeDiagnostics.zip

As additional context that might be helpful: I’ve been testing another similar app on both setups for the past 3 days, and haven’t experienced any freezing with it so far. I mention this only because it seems to point specifically to something on spacedesk’s side rather than my hardware or network setup — hopefully that helps narrow things down a bit!

Please let me know if you need any additional information or if you’d like me to run further tests — happy to help however I can.

Thank you!

spacedesk Renz hat auf diesen Beitrag reagiert.
spacedesk Renz

Hi @vkapperg,

A fix for the issue has been included in the latest spacedesk Driver Package v2.2.30 which is now available for download in the Downloads page. Please try it and give us your feedback. Thank you.

Hi @vkapperg,

We have released a new spacedesk Driver Package v2.2.31 that includes a fix for an issue where the spacedesk Service crashes upon viewer connection. Even if you didn’t encounter this issue on your end, we encourage you to update to the latest Driver Package to avoid any possible issues. Thank you.

Quote from Vanessa on 24/08/2026, 14:16

Hi,

I’m sending the DebugView logs from both of my setups (Setup 1: Windows 11 Pro notebook + Galaxy Tab S10 FE – Setup 2: Windows 11 Home notebook + Galaxy Tab S6 Lite) via the Google Drive link below, for your analysis, as you requested.

Setup 1 – 2026-08-24-082523-spacedeskRuntimeDiagnostics.zip

Setup 2 – 2026-08-24-085640-spacedeskRuntimeDiagnostics.zipslope

As additional context that might be helpful: I’ve been testing another similar app on both setups for the past 3 days, and haven’t experienced any freezing with it so far. I mention this only because it seems to point specifically to something on spacedesk’s side rather than my hardware or network setup — hopefully that helps narrow things down a bit!

Please let me know if you need any additional information or if you’d like me to run further tests — happy to help however I can.

Thank you!

since you mentioned the crash points to KERNELBASE.dll and an unhandled exception in the .NET Framework, did you notice if any specific background apps or .NET/Windows updates rolled out right around Wednesday, 08/19 that might have triggered it on both notebooks?