Jump to content

CRJ 700/900 crashes FSX


Mateo

Recommended Posts

I bought and installed the CRJ 700/900 a week ago. As soon as I start FSX, the variants are also displayed to me. 
But if I select the planes and the airports after take-off, the FSX program crashes. 
Do you know the cause? Did you already have such messages?

 

I got this information from Aerosoft support, but unfortunately did not help:

There are several possible reasons that can cause the gauge files not to load. First, the best hint that they are not loading is that the yoke is deflected fully left. Now for the possible reasons:


1) If FSX or P3D has been installed to "C:\Program Files" or "C:\Program Files (x86)" (these are the default paths of the FSX/P3D installers but it's still a bad idea to put them there), running FSX/P3D as Administrator should solve the problem.

2) The CRJ relies on data from "Documents\Aerosoft\Digital Aviation CRJ", so if this folder doesn't exist, the gauge will terminate and unload. This seems to happen every from time to time and is an issue with the CRJ installer. As Mathijs said, probably the best cure is to reinstall the CRJ as Administrator

3) If the folder is not "C:\Program Files" or "C:\Program Files (x86)" and the "Documents\Aerosoft\Digital Aviation CRJ" folder exists, then it's likely that something else (C++ redistributable files or Simconnect) is missing. In this case I have no idea why that would happen, but I would recommend a reinstall as Administrator as well.

 

Link to comment
Share on other sites

  • Deputy Sheriffs

Please give us the detailed error message. Make a screenshot or have a look at the Windows Eventviewer, search for an entry at the the time the crash happens and post the complete content:
 

Please login to display this image.

Link to comment
Share on other sites

Ich habe das Ganze kopiert.

Hier sind die Angaben

 

 

 

Protokollname: Application
Quelle:        ESENT
Datum:         26.08.2019 18:53:45
Ereignis-ID:   455
Aufgabenkategorie:Protokollierung/Wiederherstellung
Ebene:         Fehler
Schlüsselwörter:Klassisch
Benutzer:      Nicht zutreffend
Computer:    
Beschreibung:
svchost (8596,R,98) TILEREPOSITORYS-1-5-18: Fehler -1023 (0xfffffc01) beim Öffnen von Protokolldatei C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log.
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="ESENT" />
    <EventID Qualifiers="0">455</EventID>
    <Level>2</Level>
    <Task>3</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-08-26T16:53:45.758840000Z" />
    <EventRecordID>4588</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Mateo-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>svchost</Data>
    <Data>8596,R,98</Data>
    <Data>TILEREPOSITORYS-1-5-18: </Data>
    <Data>C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log</Data>
    <Data>-1023 (0xfffffc01)</Data>
  </EventData>
</Event>

Link to comment
Share on other sites

  • Deputy Sheriffs

Die Meldung hat nichts mit FSX und der CRJ zu tun. Sorg nochmal für einen Crash, merk dir die genaue Uhrzeit und schau nochmal in der Ereignisanzeige nach. Oder mach einen Screenshot von der Fehlermeldung die beim Crash angezeigt wird.

Link to comment
Share on other sites

Im Prinzip will Windows etwas protokollieren, kann es aber nicht, da der Ordner fehlt.

Diese Meldung hatte ich ebenfalls und habe sie mit dem Hinweis im Link abgestellt:

 

https://www.deskmodder.de/blog/2019/05/27/esent-ereignis-id-455-windows-10-1903-fehlermeldung-beheben-die-loesung-ist-so-einfach/

 

Wolfgang

Link to comment
Share on other sites

vor 1 hour , Mateo sagte:


    <Data>8596,R,98</Data>
    <Data>TILEREPOSITORYS-1-5

Protokollname: Application
Quelle:        Windows Error Reporting
Datum:         26.08.2019 20:46:39
Ereignis-ID:   1001
Aufgabenkategorie:Keine
Ebene:         Informationen
Schlüsselwörter:Klassisch
Benutzer:      Nicht zutreffend
Computer:      Mateo-PC
Beschreibung:
Fehlerbucket 337148348, Typ 1
Ereignisname: APPCRASH
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: fsx.exe
P2: 10.0.60905.0
P3: 44fd0a92
P4: ai_player.dll
P5: 10.0.60905.0
P6: 44fd0f32
P7: c0000005
P8: 00031319
P9:
P10:

Angefügte Dateien:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA336.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA75E.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA77E.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA78B.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA7CB.tmp.txt

Diese Dateien befinden sich möglicherweise hier:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_5b250d1ee8289e2f255bb39f52efc8c5431ea5f_06199ce8_5a5def17-519f-491d-9be2-189f4c91119e

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 4e49f6c2-99fd-4db2-b5bc-67980bf2c4e1
Berichtstatus: 268566528
Bucket mit Hash: bb9a7d04a064e67ab2bd1e80326ec05e
CAB-Datei-Guid: 0
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Error Reporting" />
    <EventID Qualifiers="0">1001</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-08-26T18:46:39.515471100Z" />
    <EventRecordID>4611</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Mateo-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>337148348</Data>
    <Data>1</Data>
    <Data>APPCRASH</Data>
    <Data>Nicht verfügbar</Data>
    <Data>0</Data>
    <Data>fsx.exe</Data>
    <Data>10.0.60905.0</Data>
    <Data>44fd0a92</Data>
    <Data>ai_player.dll</Data>
    <Data>10.0.60905.0</Data>
    <Data>44fd0f32</Data>
    <Data>c0000005</Data>
    <Data>00031319</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA336.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA75E.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA77E.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA78B.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA7CB.tmp.txt</Data>
    <Data>\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_5b250d1ee8289e2f255bb39f52efc8c5431ea5f_06199ce8_5a5def17-519f-491d-9be2-189f4c91119e</Data>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>4e49f6c2-99fd-4db2-b5bc-67980bf2c4e1</Data>
    <Data>268566528</Data>
    <Data>bb9a7d04a064e67ab2bd1e80326ec05e</Data>
    <Data>0</Data>
  </EventData>
</Event>

Link to comment
Share on other sites

  • Deputy Sheriffs
1 minute ago, Hoffie3000 said:

Im Prinzip will Windows etwas protokollieren, kann es aber nicht, da der Ordner fehlt.

Diese Meldung hatte ich ebenfalls und habe sie mit dem Hinweis im Link abgestellt:

 

https://www.deskmodder.de/blog/2019/05/27/esent-ereignis-id-455-windows-10-1903-fehlermeldung-beheben-die-loesung-ist-so-einfach/

 

Wolfgang

Genau, und hat nicht mit FSX etc. zu tun.

Link to comment
Share on other sites

  • Deputy Sheriffs

Mateo,

 

you are on FSX RTM but the CRJ requires FSX Service Pack 2 to be installed!

 

Please login to display this image.

 

 

Please login to display this image.

 

Source: https://www.aerosoft.com/en/flight-simulation/flight-simulator-x-steam/aircraft/1638/crj-700/900-x?number=AS10195

 

 

Link to comment
Share on other sites

  • Deputy Sheriffs
4 minutes ago, Mateo said:

Problemsignatur:
P1: fsx.exe
P2: 10.0.60905.0

Das ist der Grund für dein Problem, dein FSX entspricht nicht den Systemanforderungen der Produkseite!

Please login to display this image.

 

Link to comment
Share on other sites

  • Deputy Sheriffs

Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use