Hi All,

First CTD since I came back from my sim hiatus, I have done a google and can't seem to find many instances of this particular error code, so I thought I would post in case it rings a bell to anyone:

Faulting application name: Prepar3D.exe, version: 5.4.9.28482, time stamp: 0x6463925f
Faulting module name: mso20win32client.dll, version: 16.0.5023.1000, time stamp: 0x69e51f53
Exception code: 0x01483052
Fault offset: 0x000000000043a82d
Faulting process id: 0x5078
Faulting application start time: 0x1DCDBA6930D324B
Faulting application path: E:\Lockheed Martin\Prepar3D v5\Prepar3D.exe
Faulting module path: C:\Program Files\Common Files\Microsoft Shared\Office16\mso20win32client.dll
Report Id: efabe954-9310-407a-bbff-d903111c75d7
Faulting package full name: 
Faulting package-relative application ID: 

Happened when I was around 20nm from MIA and the scenery was loading in - it may well be a VRAM issue given the LVFR scenery is rather intensive, though previously I did not get any error message at all when I had VRAM-related CTDs. Also that the fauling module is connected to MS Office makes me wonder if it is connected to something else (I previously had a series of CTDs caused by this module that traced back to a demo-module of FS2Crew). Previously my sim has been rock-solid aside from previous VRAM issues, but I wouldn't put it past Microsoft managing to break something again...

Unfortunately I did not have FSUIPC autosave turned on, so I will need to repeat the entire flight to reproduce (which I don't have much free time for these days).

Give a shout if any ideas!

Can confirm this was just a VRAM exhaustion issue - managed the landing this time though!

@SimeonWilbury, only saw this post today. If you have the LatinVFR Miami it's one of the most demanding airports I have. But a 4090 card ensures I have sufficient VRAM. I've had many successful flights into Miami.

What card do you have?

1 hour ago, Ray Proudfoot said:

@SimeonWilbury, only saw this post today. If you have the LatinVFR Miami it's one of the most demanding airports I have. But a 4090 card ensures I have sufficient VRAM. I've had many successful flights into Miami.

What card do you have?

I switched to a second hand Radeon RX6700XT recently - 12gb VRAM but as it turns out, LVFR KMIA is still rather demanding!

Turns out my settings were not particularly optimal however - dropping my texture resolution to Medium seems to have resolved the issue (seemingly without too much lost in graphical fidelity). So I think as long as I keep it there I won't have any VRAM issues going forward.

I did however then get a Terrain.dll CTD today on hitting the acceleration point out of IAD on the return leg to London - may be that I've been fiddling with my settings too much and will need to rebuild my p3d.cfg, but thankfully having turned on FSUIPC autosave I was able to reload to a few minutes earlier and carry on the flight without any further issues (so far).

Edited May 10May 10 by SimeonWilbury

From memory KMIA consumes around 12Gb of VRAM with textures set to High. I was getting some CTDs with it set higher. Medium will be fine.

I wouldn’t touch your settings as terrain.dll crashes are unlikely to be related to a particular point in the sim. I was getting it over Lincolnshire enroute to Schiphol from Manchester. Don’t get them now but the scenery is unchanged. Something else is responsible.

 

The terrain.dll CTD is probably one of the only non-VRAM related CTDs I've had for some time, so for now I will leave things as they are for now and hopefully will just have been an intermittent issue.

Another terrain.dll CTD this evening. This time over the Atlantic near Halifax.

This has been happening since I raised the amount of autogen in my settings, so perhaps I need to knock that down again - that is all I can really think of at present, as it appears to be completely unrelated to where the aircraft actually is

What setting do you have for the three autogen entries? Mine are Medium, Normal and Sparse. No terrain.dll CTDs.

1 hour ago, Ray Proudfoot said:

What setting do you have for the three autogen entries? Mine are Medium, Normal and Sparse. No terrain.dll CTDs.

I knocked them up to high & extremely dense when I was experimenting with my settings - kept it as I was still getting pretty decent FPS (at 1080p), in retrospect that was probably a mistake. From what I read it is one of more more common causes of the terrain.dll CTDs so it is possible I was flying too close to the sun with my current settings.

For the current fight I have knocked them down to high & very dense. If still a CTD then I'll go back to Medium & Very Dense, which is roughly what I had before - if I still have crashes after that then it may not be an autogen issue.

1 hour ago, Ray Proudfoot said:

What setting do you have for the three autogen entries? Mine are Medium, Normal and Sparse. No terrain.dll CTDs.

Even with mine (1080, 8gb), I can fly into Miami with autogen on Medium, sparse and sparse. Texture medium and shadows minimised as far as possible.

I do suspect I overestimated what my current card can do (albeit it can definitely do more than the old one). Hopefully it will just be a case of gradually adjusting over time until I get a good balance between graphical fidelity and performance/ stability.

1 hour ago, SimeonWilbury said:

For the current fight I have knocked them down to high & very dense

Without knowing your system it's hard to judge. But given the huge system demands Concorde places on it I keep my Autogen settings well down as I prefer to have more AIG aircraft at airports. And I'm running in 4K.

50 minutes ago, IanHarrison said:

Even with mine (1080, 8gb), I can fly into Miami with autogen on Medium, sparse and sparse. Texture medium and shadows minimised as far as possible.

Autogen places demands on the CPU and with Concorde it's a huge eater of resources. I'm happy to sacrifice buildings for higher fps even with a 4090 and a 13900K CPU. Lossless Generation is a huge asset doubling my fps too.

14 minutes ago, Ray Proudfoot said:

Without knowing your system it's hard to judge. But given the huge system demands Concorde places on it I keep my Autogen settings well down as I prefer to have more AIG aircraft at airports. And I'm running in 4K.

I don't use AI traffic (less queuing!), so I may have a bit more wriggle-room in that respect hopefully. I do like autogen to be as high as I can get away with - I did turn it down a lot with my old GPU to try and keep my framerate up around Heathrow. On my current card FPS is less of an issue - but it seems it does seem to need some more balancing for stability potentially.

@SimeonWilbury, it’s all about balancing those sliders to get what’s best for you. Are you using Steam’s Lossless Generation app?

10 minutes ago, Ray Proudfoot said:

Are you using Steam’s Lossless Generation app?

Not currently, I might give a try possibly, although again FPS isn't much of a concern for me currently. I may possibly try FSR which I understand has a similar overall effect.

Unfortunately I have now had another CTD at what seems to be exactly the same position (near Halifax), which is worrying - this time the faulting module is VCRUNTIME140.dll.

Edited May 12May 12 by SimeonWilbury