Possible .NET Issue?

[DevOma]

@030 - wir können hier nachstellen, das wenn keine Tabs/Fenster offen sind und als erstes eine Chromium-Session aufgemacht wird, kommt es zum Crash - bisher haben wir aber keine Lösung für dieses Problem gefunden, ausser einfach einen Tab vorher aufzumachen...

[mrobinsn]

I have the exact same issue.  Windows 10 Pro, up to date on patches.

Application: ASGRD.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FF8744C19A4


Faulting application name: ASGRD.exe, version: 13.0.6625.1, time stamp: 0x5e4fbf8f
Faulting module name: nvumdshimx.dll, version: 21.21.13.6909, time stamp: 0x579f36b5
Exception code: 0xc0000005
Fault offset: 0x00000000000519a4
Faulting process id: 0x3f98
Faulting application start time: 0x01d5f7cb6ec0235e
Faulting application path: C:\Program Files\ASG-Remote Desktop 2020 (X64)\ASGRD.exe
Faulting module path: C:\WINDOWS\SYSTEM32\DriverStore\FileRepository\nvddwu.inf_amd64_22a22f778ced373c\nvumdshimx.dll
Report Id: ab47c068-626a-4426-9f31-65e5aabe24f2
Faulting package full name:
Faulting package-relative application ID:

[DevOma]

No - it's not the same - crash is in nvumdshimx.dll - it seems to be a driver installed on your local system - as I see it's a driver from NVIDIA - perhaps you can check if you can update your drivers?!?

[ScottMcCoy]

I'm having the same issue as SBooth. The 32-bit version of v2020 crashes on launch with the following two errors in the Windows Application Log:

Source: Application Error
Faulting application name: ASGRD.exe, version: 13.0.6625.1, time stamp: 0x5e4fc7c8
Faulting module name: KERNELBASE.dll, version: 10.0.17763.1098, time stamp: 0xe934af74
Exception code: 0xe0434352
Fault offset: 0x00121a62
Faulting process id: 0x2690
Faulting application start time: 0x01d601f65027a0a7
Faulting application path: C:\Program Files (x86)\ASG-Remote Desktop 2020\ASGRD.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 52d9504f-bf4f-48b9-a921-fbaffba3e699
Faulting package full name:
Faulting package-relative application ID:

===============

Source: .NET Runtime
Application: ASGRD.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Security.SecurityException
Exception Info: System.IO.FileLoadException

===============

And while I can get the 64-bit version to launch without crashing, I cannot authenticate to anything as the RSA client logon dialog box is triggered instead of the normal RDP client logon prompt.

[ScottMcCoy]

Follow-up regarding the 64-bit version, SBooth and I were able to fix the problem on a Windows 10 workstation with the RSA Authentication Agent installed.

Navigate to here in your registry:
HKEY_LOCAL_MACHINE\SOFTWARE\RSA\RSA Desktop Preferences\Local Authentication Settings\

In the "RDCFileName" string, add the full path to the 64-bit ASG executable after the initial value. For example:
C:\Windows\System32\CredentialUIBroker.exe, C:\Program Files\ASG-Remote Desktop 2020\ASGRD.exe

Example:     

No reboot required, the normal RDP authentication prompt will display. I'm not sure if we care about the 32-bit version crashing at this point with the 64-bit version working for us now.

[DevOma]

Great that you found a solution for the 64bit version - we still have no idea what is causing the crash in x86 - would need to evaluate dump files for that

[mrobinsn]

No - it's not the same - crash is in nvumdshimx.dll - it seems to be a driver installed on your local system - as I see it's a driver from NVIDIA - perhaps you can check if you can update your drivers?!?

---SEE UPDATE/EDIT BELOW ---

I've been battling this for a while myself.  I have 2 Windows 10 Pro systems, 1 laptop, 1 desktop.  Laptop haven't had any problems.  Desktop, it seems like ASG works "for a while" and then after a while it crashes after I connect to a server.  I noticed 2 things:

1) .net error:
Faulting application name: ASGRD.exe, version: 13.0.6625.1, time stamp: 0x5e4fbf8f
Faulting module name: nvumdshimx.dll, version: 21.21.13.6909, time stamp: 0x579f36b5
Exception code: 0xc0000005
Fault offset: 0x0000000000050590
Faulting process id: 0x451c
Faulting application start time: 0x01d606a37cbbff9a
Faulting application path: C:\Program Files\ASG-Remote Desktop 2020 (X64)\ASGRD.exe
Faulting module path: C:\WINDOWS\SYSTEM32\DriverStore\FileRepository\nvddwu.inf_amd64_22a22f778ced373c\nvumdshimx.dll
Report Id: 66baa01e-0018-43dd-b0e5-aa89eef40f2a
Faulting package full name:
Faulting package-relative application ID:

2) It *only* crashes when I RDP into a windows 2012 or newer system.  For better or worse we still have a few 2008 R2 systems floating around that we haven't been able to retire, and when I RDP into them I have no problems.  My config isn't any different for them, in fact its pretty much the standard.

I do have an nvidia GT 750M and I just updated the drivers now, so I'll reboot and see if that resolves it.


--- UPDATE/EDIT ---

I have updated my nvidia driver and everything is working fine.  I'll have to keep an eye on it, if its still working in a week I suspect that might have been it.

I'm wondering if there is something about RDP into a 2012+ server that uses some other feature in the video driver.  I don't have directx enabled for the RDP sessions.