Hi Rossia Luca,
How is your issue going? Has it been resolved yet? If it has, please consider accepting the answer as it helps others sharing the same problem benefit too. Thank you :)
VP
Investigating 0xc0000005 Access Violations and Memory Crashes in RDS Sessions on Windows Server
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(243.2, 70%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERL%3C/text%3E%3C/svg%3E)
Rossia Luca
0
Reputation points
We've got a few people runing GeoMedia Professional over an RDS farm, but whenever they start crunching heavy datasets and the memory usage spikes, the whole app just tanks. The Event Viewer keeps spitting out that 0xc0000005 access violation code, usualy pointing at ntdll.dll or sometimes KERNELBASE.dll, but its totally random. My users are geting pretty fed up because they lose all there unsaved work every time the session crashes during a big render. Does anyone know if this is a known memory leak with how RDS handles high-demand apps, or is there a specific patch for the Windows NT layer that I'm missing?
Windows for business | Windows Server | Devices and deployment | Configure application groups
2 answers
Sort by: Most helpful
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 16%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EV%3C/text%3E%3C/svg%3E)
VPHAN 34,230 Reputation points Independent Advisor2026-04-24T06:43:33.1833333+00:00 -
VPHAN 34,230 Reputation points Independent Advisor
2026-04-22T13:33:04.28+00:00 Hi Rossia Luca,
The recurring
0xc0000005with GeoMedia Professional in your RDS farm is a symptom of resource exhaustion within the session's isolated memory workspace. To stabilize the environment, you must increase the Desktop Heap size on your RDS hosts. This is controlled via the Windows Registry. Navigate to:HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystemsOpen the
Windowsstring value and locate theSharedSectionparameter. It usually looks likeSharedSection=1024,20480,768. The second value (20480) defines the heap size for interactive sessions in kilobytes. I recommend increasing this value to40960or higher to give your GIS application the necessary headroom for complex data processing. Also, you should check theSessionViewSizeto ensure there is enough address space for the graphical mapping data itself. This is located at:HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory ManagementIf this DWORD value is missing or low, create or set it to
64(Decimal, representing Megabytes). You will need to reboot the RDS hosts for the changes to take effect.Hope this answer brought you some useful information. If it did, please hit “accept answer”. Should you have any questions, feel free to leave a comment.
VP