Hi all,

After the recent SU 6.1 and Nvidia driver 616.64 update, I can no longer load the A350, the GPU hangs and then closes the sim.

I have tried clearing the WASM folder, where the plane will load initially, but then hangs and I cannot enter the cockpit or interact.

Same goes after a full re-install. Loads initially then hangs, any further attempts to load it results in the below message.

Happens at all airports.

No other aircraft I own is affected.

Edited Monday at 08:06 PM4 days by Liamr685

Appears other have had this issue in the last few days with other aircraft, but mostly solved with 616.64.

Just your A350 that isn’t playing ball at the moment.

Microsoft Flight Simulator Forums

ERROR Crash: msfs error: dxgi_error_device_hung (0x887a0006)

I keep getting the following CTDs MSFS DXGI_ERROR_DEVICE_HUNG (0x887a0006) In event viewer: “nvlddmkm Event ID 153” This happens just before the crash, though “The activation of the CLSID Windows.

Well, further edit @iniKyle

Issue isn't solved.

Same error comes back due to gpu hang and causes the sim to CTD.

Issue is only with the A350.

Fenix A32X, iFly 737Max, TFDi MD11, i have 0 issues

Might be worth you guy as developers logging an issue with Nvidia?

not sure just us FS users can create enough momentum for them to investigate?

Another thread in relation to this driver

https://forums.flightsimulator.com/t/nvidia-geforce-game-ready-driver-616-64/775593/3

Edited Monday at 08:17 PM4 days by Liamr685

20 minutes ago, Liamr685 said:

Well, further edit @iniKyle

Issue isn't solved.

Same error comes back due to gpu hang and causes the sim to CTD.

Issue is only with the A350.

Fenix A32X, iFly 737Max, TFDi MD11, i have 0 issues

Might be worth you guy as developers logging an issue with Nvidia?

not sure just us FS users can create enough momentum for them to investigate?

Another thread in relation to this driver

https://forums.flightsimulator.com/t/nvidia-geforce-game-ready-driver-616-64/775593/3

Interesting. I am currently on 610.88 and having no issues. I will update drivers and report back.

Thanks for your patience!

36 minutes ago, Liamr685 said:

Well, further edit @iniKyle

Issue isn't solved.

Same error comes back due to gpu hang and causes the sim to CTD.

Issue is only with the A350.

Fenix A32X, iFly 737Max, TFDi MD11, i have 0 issues

Might be worth you guy as developers logging an issue with Nvidia?

not sure just us FS users can create enough momentum for them to investigate?

Another thread in relation to this driver

https://forums.flightsimulator.com/t/nvidia-geforce-game-ready-driver-616-64/775593/3

Update: Just installed newest driver (616.64), restarted PC and loaded in perfectly fine. I'm not entirely sure what could be causing the issue. What GPU are you using?

Thanks!

43 minutes ago, iniKyle said:

Update: Just installed newest driver (616.64), restarted PC and loaded in perfectly fine. I'm not entirely sure what could be causing the issue. What GPU are you using?

Thanks!

RTX5070Ti

It’s an odd one as when I made this initial post I had got it working again, but after doing a couple of flights in the Fenix, I decided just to try and load up the 350 again as I was planned a flight in it tomorrow,, and I have the same issue as before, aircraft fails to load and GPU hangs.

I originally installed the driver on its release day on September 3rd.

I don’t think anything should have changed between then and you installing it now, to warrant me doing a driver reinstall.

Edited Monday at 09:30 PM3 days by Liamr685

1 minute ago, Liamr685 said:

RTX5070Ti

It’s an odd one as when I made this initial post I had got it working again, but after doing a couple of flights in the Fenix, I decided just to try and load up the 350 again as I was planned a flight in it tomorrow,, and I have the same issue as before, aircraft fails to load and GPU hangs.

If you're willing, I’d recommend giving this tool a try. I use it myself and can vouch for it. It’s helped tremendously in certain situations.

Note: If you do decide to use the tool, restart your PC afterwards, then try jumping into the A350.

https://flightsim.to/addon/92765/msfs2024-cache-removal-tool

4 minutes ago, iniKyle said:

If you're willing, I’d recommend giving this tool a try. I use it myself and can vouch for it. It’s helped tremendously in certain situations.

Note: If you do decide to use the tool, restart your PC afterwards, then try jumping into the A350.

https://flightsim.to/addon/92765/msfs2024-cache-removal-tool

Does the 350 use virtual displays?

There’s a hot fix (616.86) which fixes:

This hotfix addresses the following:

• Intermittent flicker may be observed in browsers when navigating to certain websites [6673430]

• Fixed an issue where virtual displays could not be created after updating to driver 616.56 [6674464]

• Remote Desktop Protocol (RDP) sessions may display a black screen after updating to driver 616.56 [6687328]

https://nvidia.custhelp.com/app/answers/detail/a_id/5906/~/geforce-hotfix-display-driver-version-616.86

Edited Monday at 09:39 PM3 days by Liamr685

4 hours ago, Liamr685 said:

Does the 350 use virtual displays?

There’s a hot fix (616.86) which fixes:

This hotfix addresses the following:

• Intermittent flicker may be observed in browsers when navigating to certain websites [6673430]

• Fixed an issue where virtual displays could not be created after updating to driver 616.56 [6674464]

• Remote Desktop Protocol (RDP) sessions may display a black screen after updating to driver 616.56 [6687328]

https://nvidia.custhelp.com/app/answers/detail/a_id/5906/~/geforce-hotfix-display-driver-version-616.86

I'm not entirely sure, it can't hurt to try the hotfix though!

7 hours ago, iniKyle said:

I'm not entirely sure, it can't hurt to try the hotfix though!

What graphics settings are you running?

Specifically DLSS or TAA? As I have TAA selected instead of DLSS which is currently to go to setting.

4 hours ago, Liamr685 said:

What graphics settings are you running?

Specifically DLSS or TAA? As I have TAA selected instead of DLSS which is currently to go to setting.

I am also using TAA. Just tested again after applying that hot fix and everything is working as intended.

On 9/8/2026 at 2:43 PM, iniKyle said:

I am also using TAA. Just tested again after applying that hot fix and everything is working as intended.

Still having the issue with todays driver update 616.92

Im stumped as to whats going on

14 minutes ago, Liamr685 said:

Still having the issue with todays driver update 616.92

Im stumped as to whats going on

I'm stumped as well. Was just testing something in the A350 and everything is working as intented.

If you're willing to try this troubleshooting step, I'll leave it below:

• Make sure the simulator is completely closed.

• Locate your Community Folder.

• Rename your Community Folder to Community1.

• Relaunch the simulator. This should create a new Community folder.

• Once you reach the main menu, close the simulator.

• Move the A350 from Community1 into the newly created Community folder.

• Launch the simulator again.

Let me know if that helps, thanks!

21 minutes ago, iniKyle said:

I'm stumped as well. Was just testing something in the A350 and everything is working as intented.

If you're willing to try this troubleshooting step, I'll leave it below:

• Make sure the simulator is completely closed.

• Locate your Community Folder.

• Rename your Community Folder to Community1.

• Relaunch the simulator. This should create a new Community folder.

• Once you reach the main menu, close the simulator.

• Move the A350 from Community1 into the newly created Community folder.

• Launch the simulator again.

Let me know if that helps, thanks!

Still doing the same.

It must be something to do with the way the A350 loads, and how much draw it puts on the GPU during the loading phase. The new 616.xx drivers really don't like it, but at least its not isolated to me, with other having issues with other aircraft, but in my case, with the 350

Edited Wednesday at 05:53 PM2 days by Liamr685

2 minutes ago, Liamr685 said:

Still doing the same.

It must be something to do with the way the A350 loads, and how much draw it puts on the GPU during the loading phase. The new 616.xx drivers really don't like it, but at least its not isolated to me, with other having issues with other aircraft, but in my case, with the 350

I'm very sorry to hear that this didn't help resolve the issue. I'll keep an eye out for any further information and will update you here if I receive anything that may help.

Thanks again for your patience!

5 minutes ago, iniKyle said:

I'm very sorry to hear that this didn't help resolve the issue. I'll keep an eye out for any further information and will update you here if I receive anything that may help.

Thanks again for your patience!

Ive raised it on the nvidia driver post.

https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/590373/geforce-grd-61692-feedback-thread-released-9926/3624691/

@iniKyle

When you installed the new driver, did you do express or custom via the Nvidia app?

If custom, did you do clean install?

Edited yesterday at 05:10 PM1 day by Liamr685

41 minutes ago, Liamr685 said:

@iniKyle

When you installed the new driver, did you do express or custom via the Nvidia app?

If custom, did you do clean install?

I use express!

15 hours ago, iniKyle said:

I use express!

hmm.

I've done a fresh install of the driver, A350, and deleted directx shaders.

First load of the aircraft after the long load time while the folders build, it works...however if I come out of the aircraft and try loading inn for a second time...bam, the error is back, and its just with the A350.

Something in the A350 is taking a bit longer to load with the new drivers than previously, which is triggering the GPU TDR

Edited 11 hours ago11 hr by Liamr685

5 hours ago, Liamr685 said:

hmm.

I've done a fresh install of the driver, A350, and deleted directx shaders.

First load of the aircraft after the long load time while the folders build, it works...however if I come out of the aircraft and try loading inn for a second time...bam, the error is back, and its just with the A350.

Something in the A350 is taking a bit longer to load with the new drivers than previously, which is triggering the GPU TDR

Very very weird. I've noted this with the team, but none of us have been able to reproduce this error.

I'll keep looking around. Thanks for your patience!

49 minutes ago, iniKyle said:

Very very weird. I've noted this with the team, but none of us have been able to reproduce this error.

I'll keep looking around. Thanks for your patience!

No one in the team has edited the GPU TDR time in the registry have they?

By default it’s 2 seconds.

7 minutes ago, Liamr685 said:

No one in the team has edited the GPU TDR time in the registry have they?

By default it’s 2 seconds.

Not that I'm aware of.

25 minutes ago, iniKyle said:

Not that I'm aware of.

Hmmm,

Apart from doing a full driver rollback to pre 616.xx, I don’t know what else to try.

Don’t really want to do a driver rollback for one add-on unless I really have to.

Might have to just wait and see if you guys find anything, or what comes out from Nvidia drivers wise between now, and when I get the itch to take the A350 for a spin (or between when the A380 releases to when it comes on the ini store instead of marketplace)

The only thing I don’t know how to check is how the GPU / Driver interacts with the A350 compiling the WASM every time it loads

As mentioned, after a fresh install and the initial compiling of files…it loads.

Thereafter I get the gpu hang and Ctd.

Edited 5 hours ago5 hr by Liamr685

1 hour ago, Liamr685 said:

Hmmm,

Apart from doing a full driver rollback to pre 616.xx, I don’t know what else to try.

Don’t really want to do a driver rollback for one add-on unless I really have to.

Might have to just wait and see if you guys find anything, or what comes out from Nvidia drivers wise between now, and when I get the itch to take the A350 for a spin (or between when the A380 releases to when it comes on the ini store instead of marketplace)

The only thing I don’t know how to check is how the GPU / Driver interacts with the A350 compiling the WASM every time it loads

As mentioned, after a fresh install and the initial compiling of files…it loads.

Thereafter I get the gpu hang and Ctd.

Yeah, that’s definitely a strange one. It’s odd that it loads correctly on the initial load, but doesn’t work afterward.

We’ll keep testing on our end, but so far, unfortunately, everyone who has tried has been unable to reproduce the issue.

Thanks again for your patience!