Hi All,

Another day, another CTD on V5. Must say at this point I'm tempted to move back to 4.5 with how unreliable this sim is for me now. In only a few weeks I've had multiple different CTDs.

I just attempted another Hong-Kong -> Anchorage flight (VHHX-PANC Specifically) in the PMDG 744. Both times I've had CTD at a specific position but this time it crashed without even a semblence of an error. Last time this was the error I got:

Faulting application name: Prepar3D.exe, version: 5.2.22.27615, time stamp: 0x60db69bf
Faulting module name: mso20win32client.dll, version: 0.0.0.0, time stamp: 0x6179dc15
Exception code: 0xc0000005
Fault offset: 0x0000000000071021
Faulting process ID: 0x35ac
Faulting application start time: 0x01d7cfc532c86d98
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: 56c08e1b-1ddf-4f9b-8b06-cf011574271f
Faulting package full name: 
Faulting package-relative application ID: 

I implemented a fix I saw on a forum (it seemed to be some corrupt office stuff being used by RAASPro); however now I've had the CTD again at the same location, this time with no message. Specifically I was just about to start my descent into PANC, and was crossing the AKGAS waypoint having arrived from SQA (and would then have gone on to fly the NEEL6 arrival). Can't give much more data atm and given this is the second time I've made the same 8 hour flight with a CTD right at the end I'm in no mood to repeat atm.

I'm aware Vram is still a constraint in 5.2 but I don't understand how this can happen in a not very dense area; particularly considering I'm not usually too ambitious in my settings as I tend to prioritise FPS.

While picking through my various CTDs I also came across one I hadn't noticed yet:

Faulting application name: Couatl64_P3D.exe, version: 4.0.0.4585, time stamp: 0x6138d0de
Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf
Exception code: 0xc0000409
Fault offset: 0x000000000007286e
Faulting process ID: 0x10b0
Faulting application start time: 0x01d7d08bd8d390a4
Faulting application path: E:\FSDT\Addon Manager\couatl64\Couatl64_P3D.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report ID: a67d856b-ad8d-45ed-81d2-8554ad5d2bbe
Faulting package full name: 
Faulting package-relative application ID: 

Not sure what I was doing when this happened but I've inserted AdaptiveSimGroupEnable=False into my P3D.cfg in hope that fixes some of my stability problems.

 

This is a relatively new install of V5, and though I will do a reinstall If I have to I am pretty baffled that a version of P3D out for over a year is causing me this much instability. I am currently regretting moving from V4.

If anyone has any advice or could help with any of this I would gladly appreciate it, this sim is currently driving me spare.

 

Many Thanks,

Martin

How do you get the error report?

I use Simstarter & if it is set for my Europe scenery/airfields, P3D v5.2 HF1 starts & runs ok, without CTD's during flights.

If Simstarter is set for South America or the UK, it loads to a '1/2 screen box'  in the middle of the PC screen & within a second or two of my hitting the Full Screen symbol, it CTD's.

I suspect a VRAM issue, but reading an Error Report might help me sort it out.

Thanks

T45

Footnote: I saw another post from you referencing EventViewer. Which option in the LHS menu is the one that gives the error report??

 

Edited November 14, 20214 yr by Treetops45

On 11/14/2021 at 4:28 PM, Treetops45 said:

How do you get the error report?

I use Simstarter & if it is set for my Europe scenery/airfields, P3D v5.2 HF1 starts & runs ok, without CTD's during flights.

If Simstarter is set for South America or the UK, it loads to a '1/2 screen box'  in the middle of the PC screen & within a second or two of my hitting the Full Screen symbol, it CTD's.

I suspect a VRAM issue, but reading an Error Report might help me sort it out.

Thanks

T45

Footnote: I saw another post from you referencing EventViewer. Which option in the LHS menu is the one that gives the error report??

 

Hi,

The Error reports I use are all from eventviewer. Regarding your footnote the acronym doesn't ring a bell unfortunately so I'll need my mind jogging in order to answer that.

I was suspecting it may be a Vram Issue but I'm not convinced here. This was an area without any custom scenery (too far away from PANC for that to have loaded in), and I've flown into EGLL after a 6hr flight before with no issues. That being said I have had an unrecoverable freeze/hang when flying the MaddogX into ORD on a return leg from SFO and my Chicago scenery is very dense, different symptoms to this though.

I've done multiple long-hauls since this CTD including one into quite dense scenery (FlyTampa OMBD, again at the end of a long session) without any CTDs so I'm very strongly suspecting this is area specific as it has happened twice at the same waypoint. I have yet to try the route again however, as after running a registry cleanup and updating my graphics drivers the other day some of the unrelated problems I've been having on my system have been solved, and hopefully this may also be one of them.

Edited November 16, 20214 yr by SimeonWilbury

3 hours ago, SimeonWilbury said:

Hi,

The Error reports I use are all from eventviewer. Regarding your footnote the acronym doesn't ring a bell unfortunately so I'll need my mind jogging in order to answer that.

I was suspecting it may be a Vram Issue but I'm not convinced here. This was an area without any custom scenery (too far away from PANC for that to have loaded in), and I've flown into EGLL after a 6hr flight before with no issues. That being said I have had an unrecoverable freeze/hang when flying the MaddogX into ORD on a return leg from SFO and my Chicago scenery is very dense, different symptoms to this though.

I've done multiple long-hauls since this CTD including one into quite dense scenery (FlyTampa OMBD, again at the end of a long session) without any CTDs so I'm very strongly suspecting this is area specific as it has happened twice at the same waypoint. I have yet to try the route again however, as after running a registry cleanup and updating my graphics drivers the other day some of the unrelated problems I've been having on my system have been solved, and hopefully this may also be one of them.

LHS= Left Hand Side.

I have been through updating SimStarter & other programs & am now at the point that I can load via Simstarter, specific sceneries for Europe, North America, NZ & the UK & have P3D v5.2 HF1 run satisfactorily.

South America is the hold out.

95% of the Scenery is Orbx & South America just has Open LC & Mesh. I've run verify on that, but each time I choose the Simstarter South America 'set' & pick  South American Depart/Arrive airports, P3D opens up, then after about 5 seconds goes 'non responsive', then crashes.

Bit of a head scratcher.

T45

1 hour ago, Treetops45 said:

LHS= Left Hand Side.

I have been through updating SimStarter & other programs & am now at the point that I can load via Simstarter, specific sceneries for Europe, North America, NZ & the UK & have P3D v5.2 HF1 run satisfactorily.

South America is the hold out.

95% of the Scenery is Orbx & South America just has Open LC & Mesh. I've run verify on that, but each time I choose the Simstarter South America 'set' & pick  South American Depart/Arrive airports, P3D opens up, then after about 5 seconds goes 'non responsive', then crashes.

Bit of a head scratcher.

T45

Should have realised what that acronym was! My mind obviously went a bit blank.

If you're looking for your errors on eventviewer it should be under the "administrative events" section (under the "custom views" dropdown), that should compile all relevent events on your PC including Application errors. You can also check "Windows Logs" -> "Application" which will also list them, but a lot more minor stuff to scroll through. Unfortunately with some of these CTDs they don't log anything, which is why the error that is the subject of this post annoys me somewhat.

I haven't tried SimStarter myself, but may have a look at it if it does a good job limiting vram usage. That said my settings are already fairly modest on the graphical side so I'm still in doubt whether that's the issue here.

Yes the Orbx South America issue is rather a puzzling one, not sure what would be causing that, I'm assuming they work if you install them and run them through P3D Normally? If not I'm guessing there's something wrong with your other software there.

Insofar as my own issue, I'm going to run a flight from PANC and try to retrace the arrival I was taking when the issue occured to see if I can reproduce it. If I get through it with no CTD I'll try another long-haul, and if I CTD again It might hopefully be solvablethen.

3 hours ago, SimeonWilbury said:

ANC and try to retrace the arrival I was taking when the issue occured to see if I can reproduce it. If I get through it with no CTD I'll try another long-haul, and if I CTD again It might hopefully be solvablethen.

Good luck with your CTD research.

SimStarter manages Scenery load up via a table. Down the left are all your scenery products & airfields, 1 per row.

Across the columns are the headings for the Combo's you want. eg, Europe, UK, N. America. 

You then tick a box for EGLC in the UK column, if you want EGLC in UK only, & don't tick it under Europe, & so on.

I tried ticking all the S.America rows into the North America column.

I was then able to get a flight in Mexico, & Panama, but Argentina to Chile was a CTD straight after load up.

B. elusive thing😀

T45

Edited November 16, 20214 yr by Treetops45

As an update to this thread, yesterday I flew the Anchorage route again and... no problems. Worked smoothly as can be. Now I did the next leg to KLAX and once again, a freeze and then CTD with no error when lining up for approach. Frustrating

I now have a clean install of 5.3, and one of the culprits for CTDs on my 5.2 install (FS2Crew RAAS, which would cause a mso20win32client.dll CTD via MS Office on occasion) is no longer present. I hadn't flown into LAX in v5 yet so scenery could be a culprit, but the airport loads in fine when I load a scenario. Can hardly be shaders considering the install is less than a week old. I really am scratching my head, and very little to work with other than trial and error repeating the flights to try and nail down a cause. I'm wondering if the PMDG itself may be a cause, though I also used to get freezes with the Maddog on 5.2.

Am currently rather demoralised, particularly when moments before this CTD I was marvelling at how good my sim was looking after the latest update, shame.

Edited December 8, 20214 yr by SimeonWilbury

Had a brainwave - the last change I made to my sim was activating Navigraph Simlink - In the logs I am constantly getting lines like this:

[2021-12-08 03:27:36] Status: 0; Last error: 183

Will try the flight tomorrow and see if it CTDs with Simlink deactivated

Another Day another no error CTD...

PANC-VHHX this time

No Simlink Running this time around so think I can rule that out. This is becoming increasingly difficult to pin down.

This time the CTD happened at 8-9 hours flight time. Checked the log for the PMDG 744 and these were the last entries that suggest something may be up

2021/12/15 20:03:00  readPrecipData: Previous cycle not finished.
2021/12/15 20:03:03  readPrecipData: Previous cycle not finished.
2021/12/15 20:03:06  readPrecipData: Previous cycle not finished.

Other than that nothing to go on. Hardly possible to run Process monitor given that 60 mins of runtime generates an 8gb file.

This is like trying to investigate an air accident with no wreckage and all data suddenly going dead with no indication of anything unusual.

Edited December 15, 20214 yr by SimeonWilbury