Jump to content
The simFlight Network Forums
Sign in to follow this  
Beavis

FSUIPC P3D Crash on Startup

Recommended Posts

Hello Guys!

 

Ive got problems with my P3D since i installed FSUIPC.

After the installation P3D always crashes at this blue startup screen.

- "Prepar3d has stopped working.."

Would be greate if you guys got an idea, whats going wrong :c

Windows event error:

Name der fehlerhaften Anwendung: Prepar3D.exe, Version: 3.0.10.14945, Zeitstempel: 0x560b4abe
Name des fehlerhaften Moduls: FSUIPC4.dll_unloaded, Version: 0.0.0.0, Zeitstempel: 0x5715e438
Ausnahmecode: 0xc0000005
Fehleroffset: 0x52b38300
ID des fehlerhaften Prozesses: 0x7ac
Startzeit der fehlerhaften Anwendung: 0x01d1a2fee9f54baf
Pfad der fehlerhaften Anwendung: D:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe
Pfad des fehlerhaften Moduls: FSUIPC4.dll
Berichtskennung: 30b6dc83-0ef2-11e6-8693-448a5b846b2f
 
FSUIPC Installation log :
 
Installer for FSUIPC4.DLL version 4.949p
 
 
Looking in registry for FSX install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
     Parameter"SetupPath"
... >>>  OK! FOUND FSX!  <<< ...
     SetupPath=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\
 
Looking in registry for FSX-SE install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX
     Parameter"Install_Path"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\DovetailGames\FSX
     Parameter"AppPath"
Not there, so looking in:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0
     Parameter"AppPath"
... NOT found! ...
 
Looking in registry for Prepar3D v1 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"AppPath"
... NOT found! ...
 
Looking in registry for Prepar3D v2 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"AppPath"
... NOT found! ...
 
Looking in registry for Prepar3D v3 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v3
     Parameter"SetupPath"
... >>>  OK! FOUND Prepar3D v3!  <<< ...
     SetupPath=D:\Program Files (x86)\Lockheed Martin\Prepar3D v3\
===========================================================
 
INSTALLATION FOR FSX:
SetupPath="C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\"
Checking version of the FSX EXE:
Couldn't obtain Version Info! Asking user to find FSX.EXE ...
User aborted attempt to find FSX. Installation failed.
===========================================================
 
INSTALLATION FOR Prepar3D v3:
SetupPath="D:\Program Files (x86)\Lockheed Martin\Prepar3D v3\"
Checking version of the Prepar3D v3 EXE:
... Version 3.0.10.14945  (Need at least 1.0.677.0)
Checking compatibility with installed SimConnect:
Checking if there's already a version of FSUIPC4 installed in:
       D:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\FSUIPC4.DLL
... No previous valid version found.
Prepar3D v3 Modules folder already exists.
Okay -- installed FSUIPC4 into "D:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path: 
... found as "C:\Users\Tom\AppData\Roaming"
Now finding \Lockheed Martin\Prepar3D v3\Prepar3D.CFG for all users, including this one
Looking in "C:\Users\Tom\.android\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Tom\Anwendungsdaten\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Tom\AppData\Roaming"
Found Prepar3D.CFG in "C:\Users\Tom\AppData\Roaming\Lockheed Martin\Prepar3D v3\Prepar3D.CFG"
Now checking DLL.XML ...
... There is a previous DLL.XML, checking for FSUIPC4 section.
... FSUIPC4_Loader section already exists but will be replaced.
     (for FSUIPC4, without Loader)
... FSUIPC4 section of DLL.XML written okay
Now checking for a SimConnect.XML file ...
... No SimConnect.XML file found. This is okay.
Looking in "C:\Users\Tom\AVM_Driver\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Tom\Contacts\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Tom\Cookies\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Tom\Desktop\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Tom\Documents\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Tom\Downloads\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Tom\Druckumgebung\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Tom\Eigene Dateien\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Tom\Favorites\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Tom\Intel\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Tom\Links\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Tom\Lokale Einstellungen\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Tom\Music\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Tom\Netzwerkumgebung\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Tom\Pictures\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Tom\Recent\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Tom\Saved Games\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Tom\Searches\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Tom\SendTo\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Tom\Startmenü\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Tom\Tracing\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Tom\Videos\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Tom\Vorlagen\Roaming"
 ... No Prepar3D.CFG there
"Modules\FSUIPC Documents" folder created okay!
Now installing the Prepar3D SimConnect interface for FSUIPC4 into the "Modules" folder:
   Installed "SimConnectP3D3.dll" okay
Now installing additional files into the "Modules\FSUIPC Documents" folder:
   Installed "FSUIPC4 User Guide.pdf" okay
   Installed "FSUIPC4 for Advanced Users.pdf" okay
   Installed "FSUIPC4 History.pdf" okay
   Installed "List of FSX and P3D controls.pdf" okay
   Installed "FSUIPC Lua Library.pdf" okay
   Installed "FSUIPC Lua Plug-Ins.pdf" okay
   Installed "Lua License.pdf" okay
   Installed "Lua Plugins for VRInsight Devices.pdf" okay
   Installed "LuaFileSystem.pdf" okay
   Installed "Example LUA plugins.zip" okay
   Installed "ASN WX Radar facilities in FSUIPC4.pdf" okay
   Installed "Offset Mapping for PMDG 737NGX.pdf" okay
   Installed "Offset Mapping for PMDG 777X.pdf" okay
   Installed "FSUIPC4 Offsets Status.pdf" okay
   Installed "Profiles in Separate Files.pdf" okay
===========================================================
 
All installer tasks completed.
Registration dialog 'not now' selected
*************** End of Install Log ***************
 
FSUIPClog:
********* FSUIPC4, Version 4.949p by Pete Dowson *********
Prepar3D.exe version = 3.0.10.14945
Reading options from "D:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\FSUIPC4.ini"
Running inside Prepar3D v3 on Windows 7
Module base=51F40000
User Name=""
User Addr=""
FSUIPC4 not user registered
WIDEFS7 not user registered, or expired
     1046 System time = 30/04/2016 18:40:02
     1046 FLT path = "C:\Users\Tom\Documents\Prepar3D v3 Files\"
     1061 ------ Module Version Check ------
     1061        acontain.dll: 3.0.10.14945
     1061             api.dll: 3.0.10.14945
     1061        controls.dll: 3.0.10.14945
     1061      fs-traffic.dll: 3.0.10.14945
     1061             G3D.dll: 3.0.10.14945
     1061        language.dll: 3.0.10.14945
     1061            sim1.dll: 3.0.10.14945
     1061        visualfx.dll: 3.0.10.14945
     1061         weather.dll: 3.0.10.14945
     1061          window.dll: 3.0.10.14945
     1061 ----------------------------------
     1061 Trying D:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D3.dll
     1077 Found it: trying to connect
     1077 FS path = "D:\Program Files (x86)\Lockheed Martin\Prepar3D v3\"
     1233 LogOptions=00000000 00000001
     1233 -------------------------------------------------------------------
     1233 ------ Setting the hooks and direct calls into the simulator ------
     1233 --- CONTROLS timer memory location obtained ok
     1233 --- SIM1 Frictions access gained
     1233 --- FS Controls Table located ok
     1233 --- Installed Mouse Macro hooks ok.
     1233 --- Wind smoothing fix is installed
     1233 --- All links okay (except older global weather setting method)
     1233 -------------------------------------------------------------------
     1233 SimConnect_Open succeeded: waiting to check version okay
     1233 Trying to use SimConnect Prepar3D
     3308 Exception 5 "VERSION_MISMATCH", Ref 1, Version 0.60905: Open: SimConnect Version incorrect!
     3308 Trying another version of SimConnect ...
     3401 Trying D:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D3.dll
     3417 Found it: trying to connect
     3417 SimConnect_Open succeeded: waiting to check version okay


I hope that are all information you need! Would be greate if you could help me!
Thanks in advance!

 

Share this post


Link to post
Share on other sites

ve got problems with my P3D since i installed FSUIPC.

After the installation P3D always crashes at this blue startup screen.

- "Prepar3d has stopped working.."

Would be greate if you guys got an idea, whats going wrong :c

 

The offset address given for the crash is very strange:

 

 Fehleroffset: 0x52b38300

 
This is actually going to be in a library I think, because it isn't within FSUIPC code.
 
The usual reason for a crash at this stage is a corrupt weather file -- either wxstationlist.bin in the same folder as your Prepar3D.cfg file, or the current default flight's .wx file. It happens when FSUIPC gets access to SimConnect and starts reading weather data. So the first step is to try deleting those. The station list will be rebuilt by P3D.
 
BTW why are you still using an old version of P3D? Best to keep up to date and bug fixes are on-going.
 
Prepar3D.exe version = 3.0.10.14945
 
Pete
 

 

Fehleroffset: 0x52b38300

Share this post


Link to post
Share on other sites

WOW! Thanks for this extrem fast response!

Yes, ive already searched in many other Topics, and atleast it seems as when im the only one with this specefic error..

Sadly deleting the wxstationlist.bin didnt fix it! - It seems like it just changed the problem?!
Here the new error :

 

Name der fehlerhaften Anwendung: Prepar3D.exe, Version: 3.0.10.14945, Zeitstempel: 0x560b4abe
Name des fehlerhaften Moduls: SimConnectP3D3.dll, Version: 3.2.2.16659, Zeitstempel: 0x5715ea8c
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00006860
ID des fehlerhaften Prozesses: 0x9a8
Startzeit der fehlerhaften Anwendung: 0x01d1a3074c2b0cb0
Pfad der fehlerhaften Anwendung: D:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe
Pfad des fehlerhaften Moduls: D:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D3.dll
Berichtskennung: 9376de2a-0efa-11e6-8693-448a5b846b2f

 

 

Share this post


Link to post
Share on other sites

 

WOW! Thanks for this extrem fast response!

Yes, ive already searched in many other Topics, and atleast it seems as when im the only one with this specefic error..

Sadly deleting the wxstationlist.bin didnt fix it! - It seems like it just changed the problem?!

Here the new error :

 

Name der fehlerhaften Anwendung: Prepar3D.exe, Version: 3.0.10.14945, Zeitstempel: 0x560b4abe
Name des fehlerhaften Moduls: SimConnectP3D3.dll, Version: 3.2.2.16659, Zeitstempel: 0x5715ea8c
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00006860
ID des fehlerhaften Prozesses: 0x9a8
Startzeit der fehlerhaften Anwendung: 0x01d1a3074c2b0cb0
Pfad der fehlerhaften Anwendung: D:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe
Pfad des fehlerhaften Moduls: D:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D3.dll
Berichtskennung: 9376de2a-0efa-11e6-8693-448a5b846b2f

 

 

 

Ah, that's better/ Yes, sorry. That version of SimConnectP3D3 is only compatible with P3D 3.2. I hadn't realised L-M had changed the SimConnect interface between 3.1 and 3,2. I've made a version which is compatible to 3.0 and 3.1 as well, but it's not due for Release till Monday, with 4.95 Just finishing updates to documentation.

 

However,here's a pre-release link to the changed version:

SimConnectP3D30.zip

 

Alternatively, if you installed (or already have installed) any of the FSX versions of SimConnect, from the Redist folder in P3D, then all you need to do is delete the SimConnectP3D3.DLL from the Modules folder. Then FSUIPC will use an FSX version quite happily.

 

Pete

Share this post


Link to post
Share on other sites

Ah, that's better/ Yes, sorry. That version of SimConnectP3D3 is only compatible with P3D 3.2. I hadn't realised L-M had changed the SimConnect interface between 3.1 and 3,2. I've made a version which is compatible to 3.0 and 3.1 as well, but it's not due for Release till Monday, with 4.95 Just finishing updates to documentation.

 

However,here's a pre-release link to the changed version:

SimConnectP3D30.zip

 

Alternatively, if you installed (or already have installed) any of the FSX versions of SimConnect, from the Redist folder in P3D, then all you need to do is delete the SimConnectP3D3.DLL from the Modules folder. Then FSUIPC will use an FSX version quite happily.

 

Pete

WOW!!! Thank you soo much!

Ive probably never experienced such an amazing support, you are doing a great job!

 

Share this post


Link to post
Share on other sites

Well.. 
Now i am able to Start Up P3D and edit my Free Flight.
As i loaded my flight, it crashed due to weather.dll 

 

Name der fehlerhaften Anwendung: Prepar3D.exe, Version: 3.0.10.14945, Zeitstempel: 0x560b4abe
Name des fehlerhaften Moduls: weather.dll, Version: 3.0.10.14945, Zeitstempel: 0x560b49cc
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0003498a
ID des fehlerhaften Prozesses: 0x1038
Startzeit der fehlerhaften Anwendung: 0x01d1a318bdb3179c
Pfad der fehlerhaften Anwendung: D:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe
Pfad des fehlerhaften Moduls: D:\Program Files (x86)\Lockheed Martin\Prepar3D v3\weather.dll
Berichtskennung: 74a58e39-0f0f-11e6-8693-448a5b846b2f
 
When i choose "Clear Skies" i can start the Flight, and get a random crash whilst flying.
 
Any other tipps? :(

Share this post


Link to post
Share on other sites

Any other tipps? :(

 

Well, the Weather crash one is the more usual symptom of corrupt weather files, as I said -- your previous crashes probably would be responsible for that. But as you omitted to show the FSUIPC4.LOG file I could not swear to it. With the log I can identify if it is at the exact position for the weather reading to commence.

 

Did you delete or rename the .WX files in your P3D Files folder in your Documents? Did you delete the wxstationlist.bin file again after your previous crash?

 

As for your random crash whilst flying, that could be due to almost anything, maybe even one of the bugs corrected inP3D since version 3.0.

 

You never said why you were not keeping your P3D up to date. I think that's a mistake. It would also make it a bit pointless reporting your crashes on the L-M Forums, which is otherwise where I'd suggest you "ask for tipps".

 

Pete

 

 

Pete

Share this post


Link to post
Share on other sites

BTW why are you still using an old version of P3D? Best to keep up to date and bug fixes are on-going.

 

Prepar3D.exe version = 3.0.10.14945

 

Pete

 

 

Fehleroffset: 0x52b38300

 

 

I'm having a similar problem on the first launch of P3D with the freshly installed FSUIPC after each reboot of my PC as posted in this thread:  http://forum.simflight.com/topic/81463-fsuipc495-crashes-p3dv32/

 

Pete, please note the latest version of Prepar3D.exe version = 3.2.3.16769    not     "Prepar3D.exe version = 3.0.10.14945" 

 

And it's been there since 16-03-07. Can that be the key to my problem posted in my thread?

 

Thanks,

Dirk.

Share this post


Link to post
Share on other sites

 

BTW why are you still using an old version of P3D? Best to keep up to date and bug fixes are on-going.
 
Prepar3D.exe version = 3.0.10.14945
 
Pete

 

Sorry Pete, I think I misinterpeted your post, you rather pointed to the old version of Prepar3D.exe that you found in Beavis's log, didn't you?

 

Dirk.

Share this post


Link to post
Share on other sites

I'm having a similar problem on the first launch of P3D with the freshly installed FSUIPC after each reboot of my PC as posted in this thread:  http://forum.simflight.com/topic/81463-fsuipc495-crashes-p3dv32/

 

Pete, please note the latest version of Prepar3D.exe version = 3.2.3.16769    not     "Prepar3D.exe version = 3.0.10.14945" 

 

The 3.0.10.1945 is from the crash log posted just above by "Beavis". Why are you referring to that? I was replying to Beavis.

 

Pete, please note the latest version of Prepar3D.exe version = 3.2.3.16769

 

Of course, and that is the main version supported in FSUIPC.

 

You seem to have tagged onto a thread of some one else using a different version of P3D. If you have a problem, why not post your own details, not make assumptions ... please?

 

Pete

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy 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.