Jump to content

CTD After Upgrade 2.5.0.2


tcvalley
 Share

Recommended Posts

Ever since upgrading my CRJ Pro to 2.5.0.2 I have about 15 mins before a CTD occurs sometime around loading the FMS, but not always. It does seem to be related to looking around the cabin. Are there error logs somewhere I can post? The aircraft was operating perfectly before I upgraded.

Help is greatly appreciated.

 

Thanks

 

Tom

 

Link to comment
Share on other sites

  • Deputy Sheriffs

In case of CTD you find error messages in the Windows Eventviewer. Under Windows Logs/ApplicationCheck for any entries at the time of the crash.

Link to comment
Share on other sites

Thanks Otto, I will check that.

Additional info I noticed that the CTD may occur when using GSX2.

Plan to test it a little more today.

Not sure how to attach this but I will try. I am not sure what all this means. I can usually find my way around the computer but this is a little over my head.

 

Log Name:      Application
Source:        Application Error
Date:          7/15/2021 9:15:57 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-4NGI79H
Description:
Faulting application name: Prepar3D.exe, version: 4.5.13.32097, time stamp: 0x5d8abf93
Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf
Exception code: 0xc0000409
Fault offset: 0x000000000007286e
Faulting process id: 0x2ce0
Faulting application start time: 0x01d7797957418459
Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: e7ef5084-a331-48f1-9c43-d8f56bb8c7d5
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2021-07-15T13:15:57.8013531Z" />
    <EventRecordID>12685</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-4NGI79H</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>4.5.13.32097</Data>
    <Data>5d8abf93</Data>
    <Data>ucrtbase.dll</Data>
    <Data>10.0.19041.789</Data>
    <Data>2bd748bf</Data>
    <Data>c0000409</Data>
    <Data>000000000007286e</Data>
    <Data>2ce0</Data>
    <Data>01d7797957418459</Data>
    <Data>C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe</Data>
    <Data>C:\WINDOWS\System32\ucrtbase.dll</Data>
    <Data>e7ef5084-a331-48f1-9c43-d8f56bb8c7d5</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

 

 

Thanks,

Tom

Link to comment
Share on other sites

I had to run my client install and I guess I forgot to add the HF that may solve my problems. Thanks for catching that Otto. Were you able to tell that by the event log?

 

 

 

Tom

Link to comment
Share on other sites

  • Deputy Sheriffs
8 hours ago, tcvalley said:

Were you able to tell that by the event log?

Yes, behind Prepar3D.exe you find the version number, which should be 4.5.14….. with HF3 installed.

 

16 hours ago, tcvalley said:

Faulting application name: Prepar3D.exe, version: 4.5.13.32097

 

Link to comment
Share on other sites

Thanks Otto,

 

Well I installed HF3 and the problem is still occurring this time as I was using the FMS.

 

Faulting application name: Prepar3D.exe, version: 4.5.13.32097, time stamp: 0x5d8abf93
Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf
Exception code: 0xc0000409
Fault offset: 0x000000000007286e
Faulting process id: 0x430c
Faulting application start time: 0x01d77a3f589031d4
Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: e0700e32-3444-4c30-95c5-1dc77806a6ca
Faulting package full name:
Faulting package-relative application ID:

 

What does this mean?

 

Regards

 

Link to comment
Share on other sites

  • Deputy Sheriffs
24 minutes ago, tcvalley said:

Faulting application name: Prepar3D.exe, version: 4.5.13.32097, time stamp: 0x5d8abf93
Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf
Exception code: 0xc0000409
Fault offset: 0x000000000007286e
Faulting process id: 0x430c
Faulting application start time: 0x01d77a3f589031d4
Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: e0700e32-3444-4c30-95c5-1dc77806a6ca
Faulting package full name:
Faulting package-relative application ID:

Is this for sure the latest error message? It still shows that P3Dv4.5 is not up to date:
It should show this version: Prepar3D v4.x (4.5.14.34698)

Link to comment
Share on other sites

Otto, I didn't install the hotfix properly but I did now and there is still the CTD.

Here is the latest event log

 

 
      Prepar3D.exe
      4.5.14.34698
      5e94b5c2
      ucrtbase.dll
      10.0.19041.789
      2bd748bf
      c0000409
      000000000007286e
      11f0
      01d77c0bd0c06ce3
      C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe
     

C:\WINDOWS\System32\ucrtbase.dll

c1a6860c-f175-4a4e-a109-5f66c7322821
     

 

 

It seems the

ucrtbase.dll file is the common denominator to my untrained eye anyway.

 

Best Regards,

Tom

       
       
Link to comment
Share on other sites

  • Deputy Sheriffs

Ok, so at least it git nothing to with the CRJ AND P3D not being updated. The problem is in combination with the ucrtbase.dll. A very weird one, hard to track down. In most cases it is due to systemdriver being broken or not upt-to-date or incompatibility with certain hardware add-ons. When you google this error in combination with P3Dr, you'll find tons of reports.

First step would be to run Windows Update multiple times to make sure that all Updates are installed. Also make sure that all drivers are up-o-date and your .NET and MS Visual C++ Redistributables are all installed and up-to-date.

If this doesnt help, serach google for P3D + ucrtbase.dll. Unfortunately there are many reports, because there are many reasons for this error. In some cases only a fresh install of Windows solved it.

Link to comment
Share on other sites

You hit it on the nose it was the .net. One of the guys at AIG advised me to run the .net repair tool and it works like a charm.

Hopefully anyone else with this problem can benefit from these posts.

Thanks again Otto.

 

Regards

 

Tom

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...