IGCIT / Intel-GPU-Community-Issue-Tracker-IGCIT

IGCIT is a Community-driven issue tracker for Intel GPUs.
GNU General Public License v3.0
113 stars 3 forks source link

Microsoft Flight Simulator (MSFS, FS2020) crashes PC #291

Closed derlade closed 1 year ago

derlade commented 1 year ago

Checklist [README]

Game / Application [Required]

Microsoft Flight Simulator

Game Platform [Required]

Other game platform

No response

Processor / Processor Number [Required]

Intel Core i3-12100

Graphic Card [Required]

Intel Arc A770 LE

GPU Driver Version [Required]

Rendering API [Required]

Windows Build Number [Required]

Other Windows build number

No response

Intel System Support Utility report

igcit_ssu.txt

Description and steps to reproduce [Required]

Microsoft Flight Simulator crashes in different stages of the game. Once during flight, twice in the main menu when loading a flight plan and twice in the initial loading screen. First, I encounter a black screen with audio still working for a few seconds, then the audio stops and my PC is on for about 10 seconds, then it reboots. Minidumps are created for every crash. They all have in common that dxgkrnl.sys seems to be the culprit for the crashes. Happens both in DX11 and DX12 mode. I will post ICGIT crash dumps after posting the issue. When I get back into the game, I can also post screenshots of the in-game graphics settings, if required.

Game graphic quality [Required]

Game resolution [Required]

1920x1080

Game VSync [Required]

Off

Game display mode [Required]

Detailed game settings [Required]

n/a

Device / Platform name

No response

Crash dumps [Required, if applicable]

igcit-dumps_8ec144f4.zip Repackaged as .zip, since Github didn't allow .7z upload

Save game

No response

Karen-Intel commented 1 year ago

Hey @derlade thank you for your submission!

We will perform some testing and get back to you in case we have questions

Talk to you soon

Karen

Karen-Intel commented 1 year ago

Hey @derlade a quick update. Have you tried our latest driver release? Please upgrade to latest driver v.4314 and DDU version and let us know if you see any improvement I have tried the game on my system and I have had no crashes so far. It is also recommended to follow these these steps when updating the game to ensure there's nothing else interfering with its performance

Please give it a try and let us know how it goes!

Karen

derlade commented 1 year ago

Hi @Karen-Intel , I've installed 4314 and also DDU'd and reinstalled the driver, unfortunately to no avail. The crash even occurs on other games now, i.e. in CS:GO after a few minutes of matchmaking. Initially, I suspected some kind of malconfiguration with third-party MSFS software, which seems to be unlikely now. Even if it is some kind of incompatibility though, the driver should never crash like this.

Karen-Intel commented 1 year ago

Hi @Karen-Intel , I've installed 4314 and also DDU'd and reinstalled the driver, unfortunately to no avail. The crash even occurs on other games now, i.e. in CS:GO after a few minutes of matchmaking. Initially, I suspected some kind of malconfiguration with third-party MSFS software, which seems to be unlikely now. Even if it is some kind of incompatibility though, the driver should never crash like this.

Hey @derlade that's definitely not expected. In the case of CSGO we did have a case that got fixed with DDU and latest driver, however we have not been able to reproduce the crash in that game anymore. In the case of MSFS it has been the same case so far. If you want we can keep on trying but we need consistent data to reproduce the issue. We are following the recommendations I shared with you before and no crash has happened so far. Please share with me if you already have performed the recommended steps and I will keep on trying to reproduce the crash, sounds good? Thanks

Karen

derlade commented 1 year ago

Unfortunately, I don't think the MSFS recommended steps would help me in any way, since the same type of crash occurs not only in MSFS, but also in CSGO and in Cities Skylines. Every time, the crash looks the same (sudden black screens, audio for a few seconds, then full reboot) and the minidumps all reference a VIDEO_TDR_FAILURE (116). Any application-specific fix is extremely unlikely to remedy the crash in other applications.

I am more than happy to provide any detail of debug information required by you or any other support technicians, because it seems to me like a driver bug. I have already tested my RAM with memtest86, checked CPU, GPU and chipset temperatures, monitored workloads and RAM/VRAM usage right before the crashes, and nothing seems out of the ordinary. Furthermore, I have tried limiting the GPU wattage to 120 W to exclude PSU issues, reproduced the crash with just one monitor plugged in via HDMI, AND confirmed that the bug also happens the same way in Linux when playing CS:GO.

Karen-Intel commented 1 year ago

@derlade Hi again

Well, the thing is that VIDEO_TDR_FAILURE are pretty difficult to track and reproduce. If there are dumps that you have already created and could share, that would be great. I can analyze it and get more details about the culprit with the help of the dev team. Question, have you tried an older driver version to see if there's any change? That way we could get to a regression but again, the repro % should be consistent in a machine different to yours.

Also, this forum is only for Windows support and we don't have technicians. Only engineers :)

Karen

derlade commented 1 year ago

Hi @Karen-Intel ,

I have uploaded some minidumps and other logs already in the initial Github posting (packaged with ICGIT, as detailed in the Wiki). If it is any help, I can also upload a Time Travel Debug trace which I have recorded in MSFS (weirdly enough, when attaching WinDbg to FlightSimulator.exe to record the trace, only the game crashes and the system is still operational after). Unfortunately, I don't know if it would even be useful for you guys.

Regarding older driver versions: I have tried DDU'ing to 4255 and 4146 to no avail; I can also try even older versions. Also was unaware of a difference between engineers and technicians. The more you learn...

derlade commented 1 year ago

Well, I've found the culprit. Parts of the 8-pin connector to the graphics card got loose, presumably by vibrations or something similar. The problems I've encountered all make sense now: MSFS crashed as soon as it demanded more than (probably) about 100 W of power (which is hard to debug by software, since in Arc Control one can only limit power usage to 95 W), Furmark crashed instantly, probably because it draws maximum power right from the start, CS:GO only crashed after a few rounds, since it is not too demanding of the graphics card most of the time, and so on. In hindsight, I should have expected a hardware malconfiguration much sooner, but it's the first time I've had to deal with cables that got loose over time, and not instantly after PC building.

Thanks for the swift support anyways!

Karen-Intel commented 1 year ago

Hey @derlade thank you for sharing!

This info is very useful and we will make sure to inform this situation internally, specially if we start seeing similar behavior.

@IGCIT can you please help to close this issue? Game crashes due to loose GPU power cables. Game requires high wattage consumption

Karen