Jump to content
Welcome to our new Citrix community!
  • 0

rpm.dll, version : crashes event ID 1000 VDA 2305 / 2308

gwendal lamballais


Hi All !

We are facing random crashes on our windows 2019 vda servers. 2308.

The only workaround is to hard reboot the VM.

The event is present on 2305.1 and 2308 vda.

Our windows servers are up to date.

Our event log extract in french (sorry) :


Nom de l’application défaillante svchost.exe_TermService, version : 10.0.17763.3346, horodatage : 0xb6a0daab
Nom du module défaillant : rpm.dll, version :, horodatage : 0x64fbc2a3
Code d’exception : 0xc0000005
Décalage d’erreur : 0x000000000001c471
ID du processus défaillant : 0x774
Heure de début de l’application défaillante : 0x01da1c5743296da2
Chemin d’accès de l’application défaillante : C:\Windows\System32\svchost.exe
Chemin d’accès du module défaillant: C:\Program Files\Citrix\HDX\bin\rpm.dll
ID de rapport : cc58458d-73bc-4cac-bf53-03b527178ec7
Nom complet du package défaillant : 
ID de l’application relative au package défaillant :


Up to now the only way to keep maximum users working is to add more vda.

But crashes still occur.



Link to comment

7 answers to this question

Recommended Posts

  • 0

Little update on our case :
We downgraded VDA to the 2203 LTSR CU4, unfortunatly for us, crashes still happen.

We will try another version (2206).

And I published secure desktop so we can compare either published app is making the fuss or globaly VDA.
Another option we haven't tried out yet is to dowgrade OS from 2019 to 2016.


If any encounter the same issue, please let me know.


Link to comment
  • 0

We are having exact same issue it appears - Server 2019 with LTSR 2203 CU3. Luckily the frequency isn't really high (about once/week) but we also don't have a massive server farm either. Was hoping CU4 would fix this but there's also unknown causes of BSOD issues with that version so holding off on that. Will likely open a case as well (*sigh).






Link to comment
  • 0

Hi all !
It seems  that Citrix took it seriously :



The N2 Citrix support replied to us that they experienced the issue on their test env, so ? .


In the meantime, to prevent end users bad experience, we check via powershell SDK the "faultsate" value :

Get-BrokerMachine -MachineName "*" -FaultState "Unregistered" | Select-Object MachineName,FaultState

If it returns an entry, we reboot the concerned entry.


Downgrade to 2203 - CU3 seems to do the job for us, but brings other issues.

We hope the quick fix will come shortly.

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...