Massive AUsb Nonpaged Pool Memory Leak with Android Digital Signage (USB Connection)
Zitat von datronicsoft Marcel am 04/12/2025, 16:33 UhrThe issue was replicated and fixed in spacedesk Driver v.2.2.12
Please update spacedesk Driver to v.2.2.12 on your Windows Primary Machine and let us know if this fix works on your machine.
The issue was replicated and fixed in spacedesk Driver v.2.2.12
Please update spacedesk Driver to v.2.2.12 on your Windows Primary Machine and let us know if this fix works on your machine.
Zitat von Kazushige am 05/12/2025, 01:58 UhrHi @spacedesk-renz @datronicsoft-marcel
I have tested the new v2.2.12 driver for several days, and I can confirm that the AUsb nonpaged pool memory leak is completely gone.
The system remains stable with no abnormal pool growth.
Thank you very much for the fast response and the fix!
Hi @spacedesk-renz @datronicsoft-marcel
I have tested the new v2.2.12 driver for several days, and I can confirm that the AUsb nonpaged pool memory leak is completely gone.
The system remains stable with no abnormal pool growth.
Thank you very much for the fast response and the fix!
- Du musst dich anmelden um auf Uploads zugreifen zu können.
Zitat von spacedesk Renz am 05/12/2025, 02:02 UhrHi @kazushige,
Thank you also for reporting the issue and confirming the fix on your end.
Hi @kazushige,
Thank you also for reporting the issue and confirming the fix on your end.
Zitat von Adam am 06/12/2025, 14:56 UhrThis issue looks like a significant nonpaged pool memory leak tied to the AUsb driver when using Android digital-signage devices over USB, and your detailed report helps narrow it down. Since nonpaged pool cannot be freed or paged out, the rapid buildup you’re seeing explains the system freeze after long uptime. It’s useful that you confirmed HDMI-audio routing didn’t change the behaviour, which suggests the leak is more related to USB data handling than audio. It’s also good that the SpaceDesk team managed to reproduce the problem and requested your diagnostics for deeper analysis. Until a patch is released, the safest workaround is reducing continuous USB-display runtime or scheduling regular system restarts to prevent memory exhaustion.
This issue looks like a significant nonpaged pool memory leak tied to the AUsb driver when using Android digital-signage devices over USB, and your detailed report helps narrow it down. Since nonpaged pool cannot be freed or paged out, the rapid buildup you’re seeing explains the system freeze after long uptime. It’s useful that you confirmed HDMI-audio routing didn’t change the behaviour, which suggests the leak is more related to USB data handling than audio. It’s also good that the SpaceDesk team managed to reproduce the problem and requested your diagnostics for deeper analysis. Until a patch is released, the safest workaround is reducing continuous USB-display runtime or scheduling regular system restarts to prevent memory exhaustion.
Zitat von Adam am 06/12/2025, 15:05 UhrIt’s clear from your report that this AUsb nonpaged pool memory leak is a serious problem, especially since the memory consumption keeps climbing until the system becomes unstable. The fact that switching audio output to HDMI didn’t change the behaviour strongly points toward a deeper USB data-streaming or driver-level issue rather than anything audio related. It’s reassuring that the SpaceDesk team has already been able to reproduce the leak and is reviewing your diagnostic files, as that should help isolate where the driver is failing. Hopefully a fix or updated driver will follow soon, but in the meantime, limiting long continuous USB sessions or rebooting periodically seems like the only way to avoid the memory buildup.
It’s clear from your report that this AUsb nonpaged pool memory leak is a serious problem, especially since the memory consumption keeps climbing until the system becomes unstable. The fact that switching audio output to HDMI didn’t change the behaviour strongly points toward a deeper USB data-streaming or driver-level issue rather than anything audio related. It’s reassuring that the SpaceDesk team has already been able to reproduce the leak and is reviewing your diagnostic files, as that should help isolate where the driver is failing. Hopefully a fix or updated driver will follow soon, but in the meantime, limiting long continuous USB sessions or rebooting periodically seems like the only way to avoid the memory buildup.