Software Center Crashes after approx 30 Minutes - Certain HP Models

Question

Software Center Crashes after approx 30 Minutes - Certain HP Models

Richard Ward 0

Hi All,

We have started to buy in new models of laptop (HP EliteBook 640 G9) and desktop (HP Elite Mini 600 G9) and have used the standard Gold Build we use for all other devices (deployed via OSD TS) on the device. For information, this error is not happening on any of our other models after a new build or even during current operation.

After the build, we then log in to the device to start configuring and allowing the software / updates to deploy to the device via Software Center. When Software Center has been left open for approximately 30 minutes (sometimes a little longer), it will suddenly stop working and display this message:

Annotation 2023-11-07 074850

I have checked the SCClient log and the main messages I can see before it happens is as follows:

Exception caught in OnGetException, line 193, file C:__w\1\s\src\SoftwareCenterApplication\App.cs - Type System.Runtime.InteropServices.COMException: UCEERR_RENDERTHREADFAILURE (Exception from HRESULT: 0x88980406) (Microsoft.SoftwareCenter.Client.SingleInstanceApplication at OnGetException)

StackTrace: at System.Windows.Media.Composition.DUCE.Channel.SyncFlush()
at System.Windows.Interop.HwndTarget.UpdateWindowSettings(Boolean enableRenderTarget, Nullable`1 channelSet)
at System.Windows.Interop.HwndTarget.UpdateWindowPos(IntPtr lParam)
at System.Windows.Interop.HwndTarget.HandleMessage(WindowMessage msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

I have completed the following based on information I have found when searching the error:

Rebuilt WMI
Reinstalled SCCM Client
Repaired SCCM Client
Updated Graphic Drivers
Checked version of .NET is up to date (latest version of 4.8 installed)

I am now unsure what next to try and would appreciate any help you may be able to give.

Many Thanks,

Richard

1 answer

Your answer

Answer 1

AllenLiu-MSFT 49,316 Microsoft External Staff

Hi, @Richard Ward

Thank you for posting in Microsoft Q&A forum.

The error message "UCEERR_RENDERTHREADFAILURE" in Software Center on HP EliteBook 640 G9 and HP Elite Mini 600 G9 models may be caused by a graphics rendering hardware acceleration issue.

As a workaround, you can disable graphics rendering hardware acceleration by modifying the registry subkey "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems\Windows" and adding 512 to the "SharedSection" value.

For more information on modifying the registry, see the "Workaround" section in the article：

https://learn.microsoft.com/en-us/troubleshoot/windows-server/application-management/error-8008005-when-start-complus-applications#workaround

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Add comment".

Richard Ward 0 Reputation points

2023-11-23T08:24:38.5133333+00:00

Hi @AllenLiu-MSFT

Thank you for the information and I will give the workaround a go to see if it resolves my issue.

On our devices, the default for that registry entry was this:

%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,20480,768 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=sxssrv,4 ProfileControl=Off MaxRequestThreads=16

I have added ",512" at the end of the SharedSection entry, and just waiting to see if it makes a difference.

If it turns out that this resolves the issue, would you see this as a permanent fix or what should I be looking at next?

Many Thanks,

Richard Ward
AllenLiu-MSFT 49,316 Reputation points Microsoft External Staff

2023-12-04T02:28:59.5733333+00:00

Just checking if there's any progress or updates? Is the "workaround" helpful?
Richard Ward 0 Reputation points

2023-12-04T07:01:31.0433333+00:00

Unfortunately not, Software Center still crashes as before with the same error.

Any other ideas?
Garth Jones 1,666 Reputation points MVP

2023-12-04T14:53:45.68+00:00

It sounds like a SU issue, are you deploying HP SU? If so I would block them for a test and see if only the MS SU cause a problem or not.

Once you determine which SU is causing the problem, open a support case with that team.
Richard Ward 0 Reputation points

2023-12-04T15:14:33.4366667+00:00

Hi Garth,

We do not deploy HP SUs automatically, only when required. I am not sure it is update related, as it is only affecting certain model of laptops and our client estate has the same updates applied.

I think it is related to the Graphics chip / driver within the device, but I am unable currently to find a resolution for this.

There was another driver released recently by HP / Intel, so I have installed that on a machine today and I'm in testing at the moment.
Garth Jones 1,666 Reputation points MVP

2023-12-04T17:27:10.2866667+00:00

The way I look at it, if it works for 30 minutes and stop working after than, it would suggest that a SU is being applied and breaks the SW center. I'm thinking it is a HP SU/driver as it only affect particular models, otherwise it would affect everyone.
Richard Ward 0 Reputation points

2023-12-05T12:46:23.6033333+00:00

Hi Garth,

I appreciate the feedback, but as I advised we do not apply HP SU/Drivers through our MECM system. All devices have the same level of SU applied and it is only a few models that are having the issue.

If with the latest Graphic driver installed, we are still seeing the same issue, and how I believe it is related is we recently purchased some ZBook Power G10 laptops that have both integrated graphics (Intel(R) Iris(R) Xe Graphics) and a separate Graphics chip (NVIDIA RTX 2000 Ada Generation Laptop GPU). When the system is set to prioritise the Intel graphics, we are seeing the Software Center crashing issue, however when set to use the NVIDIA graphics as a priority, Software Center does not crash and continues to run with no issues.

This for me points to an issue with the Intel Graphics (possibly compatibility with our build), but I am not sure why or what is actually causing it. Some of our other laptops are using the Iris Xe Graphics driver (although older iterations) with out this issue occurring.

Any further help would be much appreciated.
Garth Jones 1,666 Reputation points MVP

2023-12-05T13:34:10.91+00:00

If you think it is the Driver, then look for a newer or older driver and see if that fixes the problem.

At the end of the day, there isn't much anyone here can do, you will need to contact either Microsoft or Intel for support, particularly once you confirm it is the driver.
Richard Ward 0 Reputation points

2023-12-06T07:38:07.22+00:00

Hi Garth,

I have tried 3 different versions of the driver, and all have the same issue. I am not specifically saying it is a driver issue, but something has changed in these models of device that is causing an incompatibility with Software Center on our current gold build.

I was hoping that someone may have had or is having a similar issue (error code) and could of helped me decipher what is going wrong and why it is only affecting Software Center (that we know of).

If you think that no one else on here is likely to have any other ideas for us to try, or anything for us to check, I will look to investigate elsewhere.

Thanks for all of the assistance so far.
Olivier POUSSIN 0 Reputation points

2024-02-08T11:01:06.87+00:00

Hello Richard, I'm facing the same issue, on Intel Iris Xe and Intel UHD770 graphic chipsets. Did you find a solution or are you still searching ?
Thank you regards
Richard Ward 0 Reputation points

2024-02-08T11:41:13.24+00:00

Hi Oliver,
I have unfortunately not found anything so far, and it has now started to affect another one of our applications as well that uses a similar technology. Is there anything you have tried so far? Many Thanks, Richard Ward
Olivier POUSSIN 0 Reputation points

2024-02-08T12:44:46.42+00:00

Hi Richard, that's sad..
We tried few driver versions and high graphic performances in windows parameters, without success.
Still searching. I'll keep you in touch.
Regards
Olivier POUSSIN 0 Reputation points

2024-03-13T15:42:42.8633333+00:00

Hi Richard, on our side, we can easily make our app, while using DisplayPort screen instead of an HDMI screen.
If you are using DisplayPort screen, you can try an HDMI one and see if it's more stable

Regards
Richard Ward 0 Reputation points

2024-03-13T16:12:51.8533333+00:00

Hi Olivier,

Thank you for letting us know and we will have to look into this. I have also found another workaround that seems to stop the issue from occurring at all, but I do not believe we should have to do this and I have a ticket logged with Intel to investigate a better solution.

However try the below against an affected user on an affected device and let me know if this works for you as well.

Many Thanks

Registry key Value type Value

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Avalon.Graphics\DisableHWAcceleration DWORD 1
Olivier POUSSIN 0 Reputation points

2024-03-13T16:37:13.3466667+00:00

Hello Richard, we already tried this registy key, and unfortunately it didnt resolve completely the problem, we had much less crashes but it kept crashing.
Instead of deactivating the HWA through this registery key, we deactivated it only for our app, by coding an update. It seems the best workaroud found for the DisplayPort screens users.

Regards
Richard Ward 0 Reputation points

2024-03-13T16:47:35.6066667+00:00

Hi Olivier,

No problem, I thought I would share as it seems to be working for us so far. We have devices where more than one user may be needed, and we found it had to be added to all users to be effective.

I think for now I will continue asking Intel support to investigate and will let you know what I hear back. I will also let them know your findings as it may help them further.

Many Thanks,

Richard

Share via

Software Center Crashes after approx 30 Minutes - Certain HP Models

1 answer

Your answer