Who is this article for?

Users who encounter client crashes on launch.

Local Admin permissions are required for some steps.

Internal Audit may crash due to memory-related problems, displaying one of several behaviours. This article helps you determine whether this is the issue you're experiencing and how to resolve it.

1. Issue
   • Crashes with errors
   • Crashes without errors
2. Solutions
3. Further reading

1. Issue

Crashes with errors

After a crash, you may see a:

• Blank error message box.

• Error message:
  Fatal Error: A critical error has occurred which will require the application to close.  Please refer to the error log for full details. Insufficient memory to continue the execution of the program.
• Error message:
  Insufficient memory to continue the execution of the program

Crashes without errors

In some instances, the application shuts down and vanishes from the screen without displaying an error message.

In addition, the client error log at %localappdata%\Vision\[instance]\LogFiles\ may contain the following message:

• Exception of type: OutOfMemoryException -
  Message: Exception of type 'System.OutOfMemoryException' was thrown.

Or:

• Exception of type: COMException - Message: UCEERR_RENDERTHREADFAILURE (Exception from HRESULT: 0x88980406)
  System.Object:
  at System.Windows.Media.Composition.DUCE.Channel.SyncFlush()

Known causes for these crashes are Windows updates and graphics drivers, or attempting to display "too much" data on the screen.

2. Solutions

If the crashing is not frequent and only happens on a screen with a data grid, the cause is normally that the user is attempting to display a lot of data on screen, and there is not enough available memory.

You can mitigate issues when working with data grids to avoid this problem in the future.

If crashing is frequent and is not limited to specific screens, and particularly if it affects many users and seems to start suddenly, then it is likely caused by an interaction with a Windows update or graphics drivers.

You can resolve the issue by disabling hardware acceleration for WPF applications.

To disable this:

1. Log in as the user experiencing the problem.
2. Run Regedit.
3. Go to Computer\HKEY_CURRENT_USER\Software\Microsoft\Avalon.Graphics.
4. Add a new DWORD value, called DisableHWAcceleration.
5. Set it to 1.
   This is how the new line should appear in Regedit:

6. Reboot the PC.

After the change, use the application as normal for a while to make sure the issue doesn't reoccur. If the application continues to crash, contact our Support Team.

3. Further reading

• Graphics Rendering Registry Settings - WPF .NET Framework | Microsoft Learn