Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

New MSFS error in graphics

Featured Replies

Is anyone else getting this error? MSFS was working fine 24 hours ago. Nothing's changed and I still get the same error with nothing in the Community folder and after updating to the latest graphics driver. This error occurred before today's update (March 30).

I'm pretty certain it's not the graphics card or driver. Why? Because P3D and DCS flightsims and another graphics demanding game is still working. So it's got to be MSFS right?

spacer.png

Hardware: i7-8700k, GTX 1070-ti, 32GB ram, NVMe/SSD drives with lots of free space.
Software: latest Windows 10 Pro, P3Dv4.5+, FSX Steam, and lots of addons (100+ mostly Orbx stuff).

 Pilotfly.gif?raw=1

  • Replies 113
  • Views 22.2k
  • Created
  • Last Reply
  • Commercial Member

“ …. 

Hello everyone,

In talking with Asobo, they have informed us that this message is triggered when memory consumption is too high for your particular system. Before, you would just get a CTD or freeze with no error message. Suggested solutions if you are regularly getting this message are one or more of the following:

Reduce graphical quality settings (e.g. from High to Medium)

Reduce LOD sliders

Remove addons that could be causing this error

We agree that the message is a bit vague and unclear. We have submitted feedback to the devs to change the text of this error message so it better describes the cause.

Thanks,
MSFS Team


https://forums.flightsimulator.com/t/warning-your-graphics-device-has-encountered-a-problem/541301

Edited by polosim

I have those once in a moon time . Different times and with different builds. I don’t change anything . They happens randomly and go away randomly. I could fly 8 hours in PMDG without problems then fly default 172 in have this message within 5 minutes of first fly .

 

Asobo and Nvidia has to look deeper at that 

flight sim addict, airplane owner, CFI

And yet, my lowly 6GB GTX 980Ti has never thrown this error. I also don’t get CTD. I run a mix of High and Ultra settings, LOD 160. I must be stressing my old GPU (and overclocked  CPU) to the max. The sim runs locked at 30 FPS 95% of the time with mostly payware stuff. Up to 6 hour flights.

Something not adding up…. 

Even worse for those affected, a simple wording change to the message is the planned fix…

GregH

Intel Core i7 14700K / Palit RTX4070Ti Super OC / Corsair 32GB DDR5 6000 MHz / MSI Z790 M/board / Corsair NVMe 9500 read, 8500 write / Corsair PSU1200W / CH Products Yoke, Pedals & Quad; Airbus Side Stick, Airbus Quadrant / TrackIR, 32” 4K 144hz 1ms Monitor

5 minutes ago, RaptyrOne said:

And yet, my lowly 6GB GTX 980Ti has never thrown this error. I also don’t get CTD. I run a mix of High and Ultra settings, LOD 160. I must be stressing my old GPU (and overclocked  CPU) to the max. The sim runs locked at 30 FPS 95% of the time with mostly payware stuff. Up to 6 hour flights.

Something not adding up…. 

Even worse for those affected, a simple wording change to the message is the planned fix…

I have RTX 4090 and totally agree it’s not LOD it is something else 

flight sim addict, airplane owner, CFI

I went back to 531.29 and all is fine.

Menno 

i7-11700, 16GB, 1 TB SSD, 2 TB HDD, RTX 3070, Windows 11, MSFS 2020 DeLuxe, P3D 4.5

@polosim, are you from MFS / ASOBO?  

Just out of curiosity, and it would be Great if that's the case !!!

I believe someone from ASOBO might be tracking important forums, like AVSIM.

We are the best simmers in the whole World, after all... AVSIM simmers are TOP !!!

Flying gliders since 1980

Flightsimming since 1992

AMD Ryzen 5600x, 32GB RAM, GPU Nvidia RTX 3060 Ti 8 GB, 1 TB and 500 GB nvme2 SSD drives, HP 27" 60Hz LED monitor @ 1920x1080, T16000, Hotas from old X52 Pro, Saitek Combat Rudder Pro (2010 model)

3 hours ago, bofhlusr said:

Is anyone else getting this error? MSFS was working fine 24 hours ago. Nothing's changed and I still get the same error with nothing in the Community folder and after updating to the latest graphics driver. This error occurred before today's update (March 30).

I'm pretty certain it's not the graphics card or driver. Why? Because P3D and DCS flightsims and another graphics demanding game is still working. So it's got to be MSFS right?

spacer.png

Had this yesterday for the first time ever. 

Just like the bandwidth error first time ever it almost never went away.  

Let's hope this is not a new one. 

 

Edited by altenae

MSI Tomahawk Z790, I7-13700K, DDR5 6000mhz, MSI 4090, 3x SSD 980 PRO, Corsair 360 Liguid CPU cooler, Corsair H1200V2 power.

  • Author
4 hours ago, bofhlusr said:

Is anyone else getting this error? MSFS was working fine 24 hours ago. Nothing's changed and I still get the same error with nothing in the Community folder and after updating to the latest graphics driver. This error occurred before today's update (March 30).

I'm pretty certain it's not the graphics card or driver. Why? Because P3D and DCS flightsims and another graphics demanding game is still working. So it's got to be MSFS right?

spacer.png

I have 32 GB of RAM. Nothing is overclocked. The PC is problem free. I have about 1TB of NVMe free space in C:_drive where MSFS Steam version is installed.  I've been using the same GTX1070ti graphic card for almost 5 years without problems.

I also did a Windows system file integrity check: "SFC /scannow". No problems. I don't use an anti-virus.

This is the first error since I started using MSFS in 2021. 

This might be unrelated, but I'll mention it anyway.  I was testing a new joystick (Turtle Beach's Velocity One Flightstick) the day before and couldn't get the touchpad on the joystick to work. Is anyone using this joystick and getting the same error? Doing a restore to a restore point before testing the joystick did not fix the issue.

The question is what I should do now. I'd hate having to re-install MSFS since there's no guarantee it'll fix the error. Since I get a CTD now, I don't have access to MSFS, Options. Any suggestion most welcome.

@Altenae, did you recover from the error?

Edited by bofhlusr
Correct a typo.

Hardware: i7-8700k, GTX 1070-ti, 32GB ram, NVMe/SSD drives with lots of free space.
Software: latest Windows 10 Pro, P3Dv4.5+, FSX Steam, and lots of addons (100+ mostly Orbx stuff).

 Pilotfly.gif?raw=1

29 minutes ago, altenae said:

Had this yesterday for the first time ever. 

Just like the bandwidth error first time ever it almost never went away.  

Let's hope this is not a new one. 

 

Same error, msg and crash this morning. I never have this error before.

Nvidia 531.41 installed this week.

My system  I7 12700S 32G RTX 3070

Intel(R) Core(TM) i7-12700F - RAM 32 - RTX 3070 - SSD Blue 1T -  Thrustmaster Hotas Warthog - Track IR - Optical fiber

MSFS 2020/2024 Premium Deluxe

I had this error coming  up last Fall and after some trials and errors, I found it was easily reproducible. 

It came up like a clockwork after a short while approaching and flying around two landmarks buildings on the shores of the Lake  Como in Italy. Flying the Guimbal Cabri. It looks like a memory leak building up around them. I have flown before and after the world over without any problem... And my hardware is on the low side.

So before doing any change, check you don’t have a similar problem where you fly.

Edited by Dominique_K

Dominique

Simming since 1981 -  [email protected] GHz with 16 GB of RAM and a 1080 with 8 GB VRAM running a 27" @ 2560*1440 - Windows 10 - Warthog HOTAS - MFG pedals - MSFS Standard version with Steam

 

  • Commercial Member
1 hour ago, jcomm said:

polosim, are you from MFS / ASOBO?  

Just out of curiosity, and it would be Great if that's the case !!!

I believe someone from ASOBO might be tracking important forums, like AVSIM

Hi @jcomm , I don’t but for sure MSFS/ASOBO monitor multiple flight simulator forums including AVSIM.

Greetings.

Alway strange that for some reason more users have this error for the first time yesterday.  
It makes me think.....

MSI Tomahawk Z790, I7-13700K, DDR5 6000mhz, MSI 4090, 3x SSD 980 PRO, Corsair 360 Liguid CPU cooler, Corsair H1200V2 power.

Count me in. 2 or 3 days ago I have got this first time ever, just again. GPU temp 61C cannot be the issue. RAM? My VRAM is not even fully used

Screenshot-1983.png

 

Phil Leaven

i5 10600KF, 32 GB 3200 RAM, ASUS 4070 12GB EVO, Asus ROG Z490-H, 2 WD Black NVME for each Win11 (500GB) and MSFS (1TB), Rolling Cache 16GB, Photogrammetry always OFF, Live Weather and Live Traffic always ON, Res 2560x1440 on 27"

5 hours ago, polosim said:

“ …. 

Hello everyone,

In talking with Asobo, they have informed us that this message is triggered when memory consumption is too high for your particular system. Before, you would just get a CTD or freeze with no error message.

Is that system RAM or VRAM that is too high?
Both are unlikely in my case. I have 32GB of RAM and 24GB of Vram. I received this message only once, on my first flight after updating to the latest Nvidia drivers. I quickly reverted back to my old drivers and haven't seen the message since.

Flightsim rig:
CPU: AMD 5900x  | Mobo: MSI X570 MEG Unify | RAM: 32GB G.Skill Trident Z Neo | GPU: Gigabyte RTX 3090 | Storage: M.2 (2 & 4 TB) | PSU: Corsair RM850x | Case: Fractal Define 7 XL
Display: Acer Predator x34 3440x1440 | Speakers: Logitech Z906 
Controllers: Fulcrum One Yoke | MFG Crosswind v2 pedals | Honeycomb Bravo Quadrant |Thrustmaster TCA Quadrant | Stream Deck XL & Plus | TrackIR 5 Tobii eye tracking

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.