DirectX DX_Hung Error

Hey, folks

I know it has been a minute on this one, so I apologise for that. FC kicked in, and I got really sidetracked.

So, for this, I asked around, and the last update or conversation I had about this was that it was an Nvidia driver issue. At the time, the workaround was to do a rollback.

If you still run into this issue, can you please perform the following for me (even if tried before) and reply to this message so it tags me?

Uninstall the game
DirectX error update
Run the System File Checker tool
Check for Windows Updates
Install/Repair your VC++ files for the game (Microsoft VC++ Link)
Download NVIDIA PhysX System Software

Check for GPU updates - for this - only check the new version, don't install yet!

If you have the time or bandwidth, install a random EA game from the EA app. This will check and install anything missing from the above and should resolve it. If not, reinstall your GPU drivers, but choose a fresh install.

Because there has been multiple Nvidia updates, i need these tested before i send it ovn over as they will ask is this has been performed yet. Gotta test it out and see what happens.

Cheers

I completed all of those steps and even did a full DDU uninstall of drivers, no matter which rollback driver I have tried they all exhibit the same behavior. 

This is exclusive to the RTX 5000 series and shouldn't crash. PhysX was removed for RTX 5000 series as it is no longer supported. It still installs with the Nvidia drivers and Nvidia app but it is no longer a thing. C++ was already installed, but I uninstalled and reinstalled it just to be thorough. 

Regardless, after all of the prescribed steps the crash still occurred within moments after the opening kick off in a franchise game. This is with all settings maxed at 4k with Ray Tracing Ambient Occlusion enabled, and most importantly no limit on FPS. NOTE: this is not required to trigger the crash, but it is what accelerates the crash behavior to save time for testing. Otherwise with lesser settings it takes time for the crash to occur and it occurs at random making it hard to test.

Please fix this issue as it has been an ongoing problem for more than two months now.

EA_Shepard​ What is the Driver version we should roll-back to? Just rolling back would put me at a driver version that also has the crash. I'm not exact here but there are about four updates for the GeForce driver since Madden 26 has released.

 The error is pointing at a C++ file from EA code "SwapChainPcDX12.cpp".
This appears to me as having an issue with the buffers for V-Sync. But I'm looking in from the outside of a windowless building.

PS: I run the driver in Debug mode, this may explain why I get more details in my error message.

5080, 9800x3D owner here

I was unable to play a game for about a month after launch. Since then I turned off ray tracing, limited to 120fps, and dropped the  and resolution down to 1440p and have completed 100+ games without a crash. There are rare times, mainly after a TD or cutscene, where it pauses for a second and then catches up, seems like this would be when it crashed before. 

at least it works now 

EA_Shepard​ 

I set Ambient Occlusion to "Ground Truth". Not sure if related to this settings change; I received different error message on crash:

No, 120 fps works for a bit but then will still randomly crash. Uncapped FPS accelerates this process and causes it to pop even quicker which is great for troubleshooting. Not a fix though, especially for those of us at 4k.

It doesn't matter what it is set to. Ray tracing just really accelerates the crash when its set to uncapped FPS. Uncapped FPS is the trigger though as I can play at 60 FPS cap with RT enabled no problem.

Uncapped FPS needs to be addressed as a 4090 or 3090 can run it no problem without crashing. 5000 series can not.

EA_Shepard​ has my communication been passed on?

Today Nvidia released a stability fix for Madden 26 in the lastest drivers released

 today's driver 581.57 fixes madden 26. FIXED Madden 26: Stability issues after updating to R580 drivers [5446236]

slapstick22​ Saw that on the notes. Let us know if it makes a difference, or those error(s) still happen, so we can pass that along to the right folks!

Cheers.