Unhandled exception: UCEERR_RENDERTHREADFAILURE

[tmac16]

Hi, everyday I experience the issue where 1000's of error messages popup and in the log is Unhandled exception: UCEERR_RENDERTHREADFAILURE (Exception from HRESULT: 0x88980406). I did see older posts on this but they are from 4 years ago, so not sure if OS from then is my issue. I am running the following:


Edition Windows Server 2022 Datacenter
Version 21H2
Installed on 4/1/2022
OS build 20348.2461

[NinjaTrader_ChristopherJ]

Hello tmac16,

Thank you for posting.

So I may look into this further please send an email to platformsupport [AT] ninjatrader [DOT] com with "ATTN: Chris Jameson" in the subject line.

In the message, please include the following:
1.) A link to this forum thread.
2.) A copy of your log and trace files.

Please follow the steps below to manually attach your log and trace files to your email.

• Open your NinjaTrader folder under, "Documents" (sometimes called, "My Documents")
• Right click on the 'log' and 'trace' folders and select Send To> Compressed (zipped) Folder.
• Send the 2 compressed folders as an attachment in your email
• Once complete, you can delete these compressed folders.

[Playdc]

It work, Thank you, Christopher.

[tmac16]

Should there be some more information here? I only see the "It work, Thank you, Christopher." from someone else.

[gustavobp]

Hi Playdc!
i have the same error in Ninja8, Can you say me what did you do for to resolve it? Thank you!!! Gus

[NinjaTrader_Jesse]

Hello gustavobp,

That may be related to something you are using on the chart. I would suggest making a new chart and apply 1 item that you use at a time to see when you get the error. The RENDERTHREADFAILURE part leads me to believe something rendering on the chart failed. That could be an indicator, strategy or drawing object.

[gustavobp]

Hi Jesse, This error appears hundreds of times in the loop log, I'm desperate, I can't use my ninja, do you know what that error refers to?

this is the error appear in the log in documentos/NinjaTrader 8/Trace/ :

2025-03-27 08:59:36:100 UCEERR_RENDERTHREADFAILURE (Excepción de HRESULT: 0x88980406)
2025-03-27 08:59:36:101 System.Runtime.InteropServices.COMException (0x88980406): UCEERR_RENDERTHREADFAILURE (Excepción de HRESULT: 0x88980406)
en System.Windows.Media.MediaContext.CompleteRender()
en System.Windows.Interop.HwndTarget.OnResize()
en System.Windows.Interop.HwndTarget.HandleMessage(Wi ndowMessage msg, IntPtr wparam, IntPtr lparam)
en System.Windows.Interop.HwndSource.HwndTargetFilter Message(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
en MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
en MS.Win32.HwndSubclass.DispatcherCallbackOperation( Object o)
en System.Windows.Threading.ExceptionWrapper.Internal RealCall(Delegate callback, Object args, Int32 numArgs)
en System.Windows.Threading.ExceptionWrapper.TryCatch When(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
2025-03-27 08:59:36:162 *************** unhandled exception trapped ***************

[NinjaTrader_Jesse]

Hello gustavobp,

Unfortunately the error does not list a specific item. Have you tried to troubleshoot by closing your workspaces and then opening a single chart to test what item may be causing that? Because the error does not list a specific item that would be a necessary step to find out what item is causing that.

[gustavobp]

Hello Jesse,

I have tried removing all the indicators and opening several graphs in limoios at the same time and I have verified that Ninja now works perfectly. I think that by chance I discovered the possible problem, and that is that by having Ninja open and opening OBS Studio or Goggle remote desktop, that automatically causes Ninja to start opening hundreds and thousands of messages of these errors blocking Ni ha, it occurs to me that it could be a port problem, that both are using the same port at some point and so Ninja is blocked. Does Ninja use any of the remote connection ports 443, or some port that could also be used by these other applications? If that could be the problem, you could modify those ports in these applications.

[NinjaTrader_Jesse]

Hello gustavobp,

The error you are seeing does not seem to be network related, it's a rendering failure. If you are opening other applications that use advanced rendering like obs or remote desktop its possible that your video card is having a problem while executing both applications.

[gustavobp]

Hello everyone
First of all I want to thank the users who have sent me their answers to my query. Tell them, in case it helps someone now or in the future someone who may experience the same thing. I have solved the problem and my solution was the following:
I have stopped using OBS Studio and installed StreamLab, since I remember that my NinjaTrader 8 would freeze, opening hundreds and thousands of error windows that would block ninja almost instantly. Solution:
1) I have uninstalled OBS Studio and installed another similar and Open Source application of equal or better quality, and I assure you that the difference in system resource consumption has been brutal, StreamLab consumes almost 80% of PC resources, and I use a latest generation PC with a 9th Generation chip with 8 GB, it is not that it is an old PC.
2) My PC had .NET Framework installed BUT it did NOT have .NET Framework 4.8 installed in its latest version.
After making these 2 modifications, the NinjaTradwr 8 runs like a rocket, and it has been used for 24 hours with StreamLab and with more than 10 screens and graphics open, and Ninja has not frozen ONCE, and not only that, but it runs very smoothly.

Conclusion: The problem with Base was that the .NET Framework and OBS needed to be installed without this Framework 4.8 update crashing Ninja every time it was opened. And yet WITHOUT OPENING OBS Studio EVEN, the Ninja crashed and blocked after a few minutes of use, now with StreamLab and the .NET Framework everything works perfectly and excellently.
I hope my solution helps many people, and thank you all again.