Recommended Posts

So I installed the 747-8 and the first time I attempt a takeoff I get a CTD. So is there any fix to that? My laptop meets the recommended specs

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Will be needing a lot more of information than I got a CTD.

I suggest to open a support ticket from support.precisionmanuals.com portal.

Share this post


Link to post
Share on other sites

What information are you getting in eventvwr ?

Run eventvwr -> "Windows Logs" -> Click "Application" 

Any reference to the crash will have a red  "Error".  It should provide us with useful information. 

PS: Add your name as a signature to save manually typing it in every reply. 

 

Edited by Jude Bradley

Share this post


Link to post
Share on other sites

I opened a support ticket and they said to wait the the next patch coming up next week. Is this the first patch? Also is anyone else having a 748 CTD?

Share this post


Link to post
Share on other sites
On 12/22/2018 at 11:32 PM, lukejw20 said:

I opened a support ticket and they said to wait the the next patch coming up next week. Is this the first patch? Also is anyone else having a 748 CTD?

Yep me, just today after about 5 hours of flight.

CTD with ntdll. error in the Eventviewer and some strange entry in the ContentError Log file:

[error.0]
error=Gauge/Script Error
Type: Unknown
Name: Unknown
Error: PANELS lookup_var : SimVarGet Failed - Module_Var ID: "280".

[error.1]
error=Gauge/Script Error
Type: Unknown
Name: Unknown
Error: PANELS lookup_var : SimVarGet Failed - Module_Var ID: "280".

[error.2]
error=Gauge/Script Error
Type: Unknown
Name: Unknown
Error: PANELS lookup_var : SimVarGet Failed - Module_Var ID: "280".

[error.3]
error=Gauge/Script Error
Type: Unknown
Name: Unknown
Error: PANELS lookup_var : SimVarGet Failed - Module_Var ID: "280".

Looking forward to the patch, hope that solved the issue.

It was my first flight in 4.4 after a fresh reinstallation so I am afraid to say that the 747-8 is the reason for the CTD.

Will do another long flight with another airplane again to check if its only with the 747-8.

I activated Autosave and continued my flight. Lets see if I can finish it without another CTD 🙂

Edited by Flyinggok

Share this post


Link to post
Share on other sites

I'm having no problems with the other PMDG aircraft, not even the -400. -400 runs great. Do you know when the patch is coming out? Btw Merry Christmas 🙂

  • Upvote 1

Share this post


Link to post
Share on other sites

Oddly I started getting a CTD when selecting any 747-8 variant.  It's repeatable gets to about 8% loading of a flight and will CTD with the following event log error message:

Faulting application name: Prepar3D.exe, version: 4.4.16.27077, time stamp: 0x5bfdbb35
Faulting module name: util.dll, version: 4.4.16.27077, time stamp: 0x5bfdbbf2
Exception code: 0xc0000005
Fault offset: 0x000000000002fa33
Faulting process id: 0x2da8
Faulting application start time: 0x01d4a167c363d295
Faulting application path: D:\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: D:\Lockheed Martin\Prepar3D v4\util.dll
Report Id: 495939c2-7cd2-4273-865f-21880ef41eff
Faulting package full name: 
Faulting package-relative application ID: 

I tried to use the Operations Center Support portal to submit a ticket but I just get a spinning wheel when I attempt to login and never get to the ticket section to be able to enter my issue.  Unfortunately since I can't get into the 747-8 and Deactivate my license, I'm reluctant to re-install unless the license key/process will remain intact local so it will not trigger any DRM issues?

NOTE: the 747-400 and 777 and 737 all working very well, in fact exceptionally well on the performance and stability front.

Cheers, Rob.

 

 

Share this post


Link to post
Share on other sites
48 minutes ago, Rob Ainscough said:

Oddly I started getting a CTD when selecting any 747-8 variant. 

Rob,

I wish I could help, my last flight for the -8 was 9 days ago for 8.6 and no problems.  I did just go load it and it loaded fine.  I'm running W10-64 Pro/1803 and 17.35 driver.  

Grace and Peace, 

Share this post


Link to post
Share on other sites
3 hours ago, Rob Ainscough said:

I tried to use the Operations Center Support portal to submit a ticket but I just get a spinning wheel when I attempt to login and never get to the ticket section to be able to enter my issue.  Unfortunately since I can't get into the 747-8 and Deactivate my license, I'm reluctant to re-install unless the license key/process will remain intact local so it will not trigger any DRM issues?

Operations Center Support? Never heard of this.

Support.Precisionmanuals.com is always the place to go.

Util.dll doesn’t sound like us. Is your sim’s connection okay? If it can’t get to Navigraph to authenticate, you may see a crash (fixed in the next update).

Share this post


Link to post
Share on other sites
2 hours ago, Rob Ainscough said:

I tried to use the Operations Center Support portal to submit a ticket but I just get a spinning wheel when I attempt to login and never get to the ticket section to be able to enter my issue.  Unfortunately since I can't get into the 747-8 and Deactivate my license, I'm reluctant to re-install unless the license key/process will remain intact local so it will not trigger any DRM issues?

Hi Rob, I just logged into PMDG Support Portal (support.precisionmanuals.com) without problem... well that's not true I first tried to use my email as a user name and it didn't like that but it logged me in when I got the correct user name entered.  I am using Firefox.  If you cannot get past login then try creating new support account.  Ah, Kyle beat me.

Yeah, util.dll is a new one.  I've not seen that one myself or reported by anyone else.  Even the navigraph bug shouldn't effect you if you are not on a very slow internet so I don't think it is the QOTSII.  However, you can uninstall with control panel and install anew without affecting your license.  We do it dozens of times during every beta test.

Share this post


Link to post
Share on other sites
6 hours ago, Rob Ainscough said:

Oddly I started getting a CTD when selecting any 747-8 variant.  It's repeatable gets to about 8% loading of a flight and will CTD with the following event log error message:

Faulting application name: Prepar3D.exe, version: 4.4.16.27077, time stamp: 0x5bfdbb35
Faulting module name: util.dll, version: 4.4.16.27077, time stamp: 0x5bfdbbf2
Exception code: 0xc0000005
Fault offset: 0x000000000002fa33
Faulting process id: 0x2da8
Faulting application start time: 0x01d4a167c363d295
Faulting application path: D:\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: D:\Lockheed Martin\Prepar3D v4\util.dll
Report Id: 495939c2-7cd2-4273-865f-21880ef41eff
Faulting package full name: 
Faulting package-relative application ID: 

I tried to use the Operations Center Support portal to submit a ticket but I just get a spinning wheel when I attempt to login and never get to the ticket section to be able to enter my issue.  Unfortunately since I can't get into the 747-8 and Deactivate my license, I'm reluctant to re-install unless the license key/process will remain intact local so it will not trigger any DRM issues?

NOTE: the 747-400 and 777 and 737 all working very well, in fact exceptionally well on the performance and stability front.

Cheers, Rob.

 

 

Also have you made any recent changes?

Regards

Share this post


Link to post
Share on other sites
12 hours ago, scandinavian13 said:

Operations Center Support? Never heard of this.

There's a Login via the Ops Center for support ... it doesn't appear to work (I think it's a browser control within the app that might be running into security context issues).  I went to the URL directly and was able to submit a support ticket.

I was able to resolve my issue with the 747-8 doing an uninstall/reinstall.  However, now another odd problem (not a show stopper) ... whenever I add a new livery to any 747-8 series and try a flight, I get a DRM trigger (no wheels, no gauges, etc.).  If I exit and reboot my PC, try the very same livery I just added, it works the second time around?  Again this is ONLY for the 8 series, the 747-4's, 777's, 737's all work fine (new livery or existing).

I've downloaded the 8 series expansion a couple of times now from my account page to verify.  Installing with the usual "Run As Admin".  This is on Win10 1809.

I was aware that each purchase must be installed and registered one at a time (including expansions) and I did follow that process which worked well for everything except the 8 series expansion.  Anyway, I can live with this issue it's not major, just have to remind myself to reboot whenever I add a new livery for the 8 series.

Cheers, Rob.

Share this post


Link to post
Share on other sites
3 hours ago, Rob Ainscough said:

I was aware that each purchase must be installed and registered one at a time (including expansions) and I did follow that process which worked well for everything except the 8 series expansion.  Anyway, I can live with this issue it's not major, just have to remind myself to reboot whenever I add a new livery for the 8 series.

Embarrassing... I'm a beta tester and I never tried the product support link in the OC Need Help page, which by the way does work on my machine.  Are you using 3d party antivirus software other then the Windows Defender?

You should not have problems launching a new livery for the first time, unless you have a PMDG product set up as a default aircraft.  We cannot do that, only default aircraft should be used for default.  I use the BE58 at my home base as default but the F22 at Langley is fine.  When you select an aircraft/livery and start a scenario and it loads with no wheels or trigger that usually points to a load of one PMDG aircraft on top of another.  During testing, I routinely remove and add liveries all the time and I've never loaded with the situation you described.  Just have to observe the one scenario per session rule.

 

Share this post


Link to post
Share on other sites
4 hours ago, downscc said:

Are you using 3d party antivirus software other then the Windows Defender?

Windows Defender and it's disabled when I do my flights. 

I'm using default F22 and default P3D location for start.

Now the issue seems more "random" ... at first I thought it was related to adding a new livery to the 747-8.  But I'm now getting the DRM protection trigger about every 4th time I try to fly with the 747-8 ... it'll work for 3 starts, then 4th start I get the DRM trigger.  Really puzzled ... not sure how to proceed.  Uninstall/re-installed didn't solve it ... thought perhaps "Run As Admin" on the Ops Center was the cause, but tried with and without that setting and still same issue.

Disabled other add-ons just to see if there was some conflict ... but once again on the 4th or 5th flight attempt got the DRM trigger, so it doesn't appear to be related to any other add-ons.

Beyond SimConnect logging, is there any other PMDG specific diagnostics that might help ID the problem?

Cheers, Rob.

Share this post


Link to post
Share on other sites
4 hours ago, downscc said:

I use the BE58 at my home base as default but the F22 at Langley is fine.

Dan,

It is probably better to stick with the F22 as the default aircraft (and preferably with an airfield in your own local time zone).  Apparently the reason is if you use any of thedefault Beech aircraft (the Baron, King Air, or Carenado A36 Bonanza) or the gauge files from any of them (the G1000 is commonly used in third-party freeware acft, for example)--all of these aicraft have been intentionally removed fromP3Dv4.4

Share this post


Link to post
Share on other sites
7 hours ago, Rob Ainscough said:

There's a Login via the Ops Center for support ... it doesn't appear to work (I think it's a browser control within the app that might be running into security context issues).  I went to the URL directly and was able to submit a support ticket.

I suspect there may be a problem today with their OC/Server because I don't think it is working properly (maybe a New Year's day issue?).

Share this post


Link to post
Share on other sites
35 minutes ago, Rob Ainscough said:

is there any other PMDG specific diagnostics that might help ID the problem?

There are debug logs created in the PMDG 747 folder, but unless it is something obvious they are intended to help PMDG Product Support sort the issue out.  You've got a support ticket in, I'm confident you'll hear from them 2Jan.

Share this post


Link to post
Share on other sites
38 minutes ago, berts said:

Dan,

It is probably better to stick with the F22 as the default aircraft (and preferably with an airfield in your own local time zone).  Apparently the reason is if you use any of thedefault Beech aircraft (the Baron, King Air, or Carenado A36 Bonanza) or the gauge files from any of them (the G1000 is commonly used in third-party freeware acft, for example)--all of these aicraft have been intentionally removed fromP3Dv4.4

Perhaps, but I didn't install the v4.4 content specifically so I could keep my twin Beech.  I don't even like to look at the VC of the F-22, reminds me a lot of an arcade game that came out in the 90s with the F-16.  Very cartoonish.  The issue is one of grievance between LM and Textron, one of which I have little interest.

The importance of creating a default scenario in your own time zone cannot be over stressed.  This simulator has an inconsistent and game like approach to how it treats time, and it gets complicated when the user does not observe this.

Share this post


Link to post
Share on other sites

I'm also having util.dll crash when exiting P3D with 747. Solved this issue by temporarily disabling FSLabs both modules. 

Share this post


Link to post
Share on other sites
18 hours ago, downscc said:

The importance of creating a default scenario in your own time zone cannot be over stressed.  This simulator has an inconsistent and game like approach to how it treats time, and it gets complicated when the user does not observe this.

Do you know if this could lead to NTDLL.dll crashes? I‘m sitting in Germany but my default flight is the P3D default F22 in the USA..

Share this post


Link to post
Share on other sites
23 minutes ago, Ephedrin said:

Do you know if this could lead to NTDLL.dll crashes? I‘m sitting in Germany but my default flight is the P3D default F22 in the USA..

I doubt it, but setting your default flight in your current time zone (by locating the aircraft at an airport there) is a good practice, simply to help make sure your flight is on the correct time.

Share this post


Link to post
Share on other sites
30 minutes ago, scandinavian13 said:

I doubt it, but setting your default flight in your current time zone (by locating the aircraft at an airport there) is a good practice, simply to help make sure your flight is on the correct time.

Worth a try for no cost I guess

Share this post


Link to post
Share on other sites
Posted (edited)
35 minutes ago, scandinavian13 said:

I doubt it, but setting your default flight in your current time zone (by locating the aircraft at an airport there) is a good practice, simply to help make sure your flight is on the correct time.

I do what you are talking about and I don't have any ntdll.dll issues (so far). 🤣

I use the Carenado C152 at 6TE6 and use SAVED SCENARIO to save my PMDG flights. The SAVED SCENARIO flights load just like I left them except the time has updated to the current UTC time.

Grace and Peace, 

Edited by Bluestar
clarification

Share this post


Link to post
Share on other sites
On 1/2/2019 at 12:46 AM, downscc said:

Perhaps, but I didn't install the v4.4 content specifically so I could keep my twin Beech.

I went ahead and installed the 4,4 content and I have had no issues.  I already have the Milviz Baron, but if you want to keep the default Beech aircaft just make a backup of the relevant default aircraft files and put them back into the program's SimObject folder when you have finished the content update (someone else has posted more detailed information about this in the P3D Forum). 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now