*3080 RTX, typo.
thats intresstingā¦ There is an update in that lib , the former one was 2.11 ( in my backupof 31.07.2022 ), now it is 2.18 .
What this lib do:
NVIDIA Nsight Aftermath SDK is a simple library you can integrate into your graphics applicationsās crash reporter to gather additional information or generate GPU āmini-dumpsā when a TDR or exception occurs.
soā¦ it points still that somewhat determine an issue with your GPU.
BUT:
R470 : Fixed misreporting of any GPU exception as a page fault.
sounds near by " Error_DMA_PageFault " , but of course rerported for R470 cardsā¦ but who knows.
Maybe someone is brave enough and tries the previous version of the dll 
PS: biggest guess I ever had and I also never seen that error popup
3 Likes
at last a proper crash dump , now will any Asobo dev please step up.
2 Likes
PS: dont forget to add all that infos at the ZenDesk ticket ( json + dump ).
1 Like
one wierd issue i noticed while updating to SU10 is that there was a particular packeges that were not updated, the installer just skipped them (their size Approximately 4.5 GB out of 16 GB), so if these files are not related to the update, why to include them in the update installer in the first place. so if thats an error and not a regular installation proccess in the SU10 update, maybe it has to do with this gpu error, by being files are missing or corrupt or something. thats just an idea.
1 Like
the problem is, that sometimes I can fly several hours without message or CTD but than suddenly , again this error/CTD. So it is hard to find the reason. Pse give a message if your problem was healed threw this driver version in long term testing.
With the last drivers of NVIDIA (DDU first) and HAGS desactivated i donĀ“t have now CTDs.
So is there any solution to this?
yesā¦ see one post above yoursā¦
PS. kind of useless such questions
Iāve done exactly what is above and still get same error and CTDā¦
PS. kind of useless to talk down to people when the solution doesnāt work for everyoneā¦
Thats just one users case. I wouldnt ask if it solved the problem for meā¦brb
Is there any way we can bump this up to āBug-Loggedā status. I think itās gone beyond āfeedbackā.
This severely impacts the reliability and playability of this sim
(I hope everyone posting here has voted at the top of this thread)
1 Like
Asoboās response is nonsense. This needs to be escalated and fixed. It happens very regularly on the new nvidia drivers and SU10, and has never happened before on any prior update. Nothing changed about my hardware or software setup except SU10 and the nvidia drivers we were officially recommended to install along with it.
Not to mention that it happens even before the flight has finished loading, a point at which you should never, ever have run out of GPU memory on my RTX 3060. Yet it doesnāt do it every time with the same setup, only intermittently. With the exact same settings it will regularly and happily work fine for a 6-8 hour long flight with a consistent 50+ fps and basically no stuttering. But every handful of attempts, it will fall on its face before it even starts the flight.
Either Asobo has a problem, nvidia has a problem, or you both do. This is clearly affecting many users and is a new bug; fix it.
9 Likes
Absolutely 100% correct. The problem occurs even before flights have started and on machines which are regularly able to run for many hours at high, stable frame rates with the exact same settings. There is a 0% chance that it is caused by VRAM running out, @SeedyL3205 . @FlyingNautiker 's screenshot proves this, as VRAM canāt ārun outā in the main menu of a properly-functioning program before it has even started to load a flight.
Nor are we talking about marginal machines here; mine happily runs for 6-8 hour flights at 50+ stable fps with these exact same settings most of the time, and yet you expect me to believe my card doesnāt even have sufficient memory to start the game with those settings because it randomly falls on its face before it even loads a flight at all? Nonsense!
Instead of dismissing this out of hand as a user issue, please acknowledge that literally hundreds of Asobo customers have actively gone out of their way to report this problem (which means that tens or perhaps hundreds of thousands will be silently experiencing it too). And that those same customers unanimously agree that we had NO such problems on the exact same hardware and settings prior to SU10 and the latest nvidia driver update that Asobo told us we should be using.
Please listen and help fix the problem.
7 Likes
I do not know, the same as most contributors , but I suspect that if Asobo knew the reason for the issue that they would tell use all. Any criticism therefore is totally useless because they have no reason to hold back a solution that would give them more credibility.
Unfortunately this started happening on the penultimate beta build when using the previous drivers.
This isnāt a new / post-release problem, and Asoboās proposed cause and fix (via Mods/Community Managers in this forum) is just plain incorrect. As Iāve said repeatedly based on my own experience, this is nothing to do with VRAM, it is nothing to do with RAM, itās nothing to do with graphics settings, nothing to do with drivers (at least not in any way we can control) and it is not adding a message to previously unidentified crashes.
Thankfully, Iāve only experienced this crash 3 times (which is enough frankly), but I really feel for those for whom this is making the game unusable.
Just be aware that relentlessly installing / uninstalling drivers, changing bios settings, fiddling with Windows etc WILL NOT fix this crash, doing so is wasting your time. There is a problem in the game and only Asobo can fix this.
4 Likes
Download DDU here and use the file in Safe mode. DDU will uninstall the old driver. Then restart and install a new or older graphic driver.
And it will only get fixed if it is brought to the attention of the dev team via the Zendesk or flagging this thread as a Bug and adding it to the Bug_Log with some degree of priority.
2 Likes
Ordinarily yes, but it was repeatedly reported during the beta and supposedly logged as a problem.
Dunno about anyone else, but Iām not sending Zendesk tickets for a problem that I and many others flagged repeatedly during the SU10 beta. Iāve got better things to do!
1 Like
because you are seemingly sure, have you checked that and how ( e.g disabled xmp mode ) ?