Dazed and confused

[SaltyDog]

First of all I use both FSX/A and P3d V3.4, I have them on seperate HD so that I can have access to both.

Having said that, I recently installed P3d V3.4 and did a fresh install of the F4J using the latest installer I had: MilViz_F-4_Phantom_II_S_J_vA1.161120.exe

Then after I finished installing that, I installed: MilViz F-4 Phantom II SJ vA1.170323 Update.exe (don't know what that is all about) but it was installing only a few files and I don't have the foggest
Idea what that was supposed to do but it sure didn't take long to install the updater.

Now for the reason of this post, when I opened my P3d V 3.3 I could see the F4J/S to choose from and when I selected one the screen went on (so I thought) to load my selection only to crash.
It did this twice, so for now and until something can be resolved, I took it all out. I have AI Installer for P3d and I had to resort to using that program to uninstall what was installed. I did not see
an uninstaller so I resorted to my AI Installer for P3d. That did the trick.

Back last fall, I had lapsed in keeping the F4 up to date in FSX with all the subsequent updates thus I think the latest installed version (For FSX) is F-4SJ_vA1.151121.zip. (as far as I can tell.)
I would get updates and never did install the ones that followed for FSX. Now as far as P3D is concerned, I would think that I could of used MilViz_F-4_Phantom_II_S_J_vA1.161120.exe as a fresh
install and update over it with that MilViz F-4 Phantom II SJ vA1.170323 Update.exe. I would think that the latest full version released was complete and inclusive of all previous versions.

So I need to know why my P3D crashes....
Pls advise.

[Raptor]

The update has only 2 files I think, so a quick install is normal. As far as the CTD, can you please post your log from windows?

[SaltyDog]

What am I/you looking for in here?

[JonathanBleeker]

Need you to go to the Windows Logs\Application list. Should be an error there showing the crash involving P3D.

[SaltyDog]

Does this help?

XML View:
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Hang" />
<EventID Qualifiers="0">1002</EventID>
<Level>2</Level>
<Task>101</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-03-28T01:36:01.000000000Z" />
<EventRecordID>242354</EventRecordID>
<Channel>Application</Channel>
<Computer>ijdjr-PC</Computer>
<Security />
</System>
- <EventData>
<Data>Prepar3D.exe</Data>
<Data>3.4.22.19868</Data>
<Data>da8</Data>
<Data>01d2a755d565b735</Data>
<Data>289</Data>
<Data>P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe</Data>
<Data>e25c8966-1356-11e7-b448-6cf0497dce43</Data>
<Binary>430072006F00730073002D00700072006F00630065007300730000000000</Binary>
</EventData>
</Event>

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -- - - - - - - - - - - - - - - - - - - - - - - - -

Friendly VIew:

+ System

- Provider

[ Name] Application Hang

- EventID 1002

[ Qualifiers] 0

Level 2

Task 101

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2017-03-28T01:36:01.000000000Z

EventRecordID 242354

Channel Application

Computer ijdjr-PC

Security


- EventData

Prepar3D.exe
3.4.22.19868
da8
01d2a755d565b735
289
P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe
e25c8966-1356-11e7-b448-6cf0497dce43
430072006F00730073002D00700072006F00630065007300730000000000


--------------------------------------------------------------------------------

Binary data:


In Words

0000: 00720043 0073006F 002D0073 00720070
0008: 0063006F 00730065 00000073 0000


In Bytes

0000: 43 00 72 00 6F 00 73 00 C.r.o.s.
0008: 73 00 2D 00 70 00 72 00 s.-.p.r.
0010: 6F 00 63 00 65 00 73 00 o.c.e.s.
0018: 73 00 00 00 00 00 s.....



The program Prepar3D.exe version 3.4.22.19868 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: da8
Start Time: 01d2a755d565b735
Termination Time: 289
Application Path: P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe
Report Id: e25c8966-1356-11e7-b448-6cf0497dce43



Hope this helps and I hope this is what you are looking for. So what does this all mean?



I put red arrow next to data that shows contents above.

[JonathanBleeker]

That looks more like a momentary freeze which the user shut down. Will test this side but one suggestion I can make is to go in to your MVAMS directory\Configurations\F4E and delete all the config files there and then test.

[SaltyDog]

That looks more like a momentary freeze which the user shut down. Will test this side but one suggestion I can make is to go in to your MVAMS directory\Configurations\F4E and delete all the config files there and then test.

I can assure you that I did not shut it down, it quit on its own.
I don't know if I sent you the file that you were looking for all I know is that
this particular incident looked to be P3D related. As you can see on that screen shot there were other issue in the event logger maybe one of those events
would of been more helpful is solving the crash, I don't know, I just sent what looked to be P3D related.

I can tell you one thing. I have no issues with P3d crashing when installing/using a different version of the F4 (F4B) from another vendor and it didn't crash my system.
I also wish that there was an uninstaller provided so as to clear out all the related files from the install session. That would of been nice.


I would have to reinstall this program that I manually uninstalled, it is a pain as there is no auto uninstaller provided, I guess I could use Addit Pro for P3d to track/trace all files related to
this F4J program.

[Krazycolin]

If you run the installer, there's a check box for uninstalling.

[SaltyDog]

If you run the installer, there's a check box for uninstalling.

Thanks I will look for that.

[SaltyDog]

That looks more like a momentary freeze which the user shut down. Will test this side but one suggestion I can make is to go in to your MVAMS directory\Configurations\F4E and delete all the config files there and then test.

There was a MVAMS directory\Configurations\F4J and no config files.

[SaltyDog]

Okay, I just reinstalled the F4j with no other update, as soon as I select a model to fly the next thing P3d does is choke and die looking for a solution. I did not do any thing witht he MVAMS program, should I of?
I just clicked of save defaults. Anyway, P3d choked and puked again.
here is latest event view

Log Name: Application
Source: Application Error
Date: 3/31/2017 1:28:54 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: ijdjr-PC
Description:
Faulting application name: Prepar3D.exe, version: 3.4.22.19868, time stamp: 0x588f7cbf
Faulting module name: MSVCR90.dll, version: 9.0.30729.6161, time stamp: 0x4dace5b9
Exception code: 0xc0000417
Fault offset: 0x00031484
Faulting process id: 0xd14
Faulting application start time: 0x01d2aa4c80c4c73a
Faulting application path: P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe
Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll
Report Id: e481ec90-163f-11e7-a478-6cf0497dce43
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-03-31T18:28:54.000000000Z" />
<EventRecordID>242691</EventRecordID>
<Channel>Application</Channel>
<Computer>ijdjr-PC</Computer>
<Security />
</System>
<EventData>
<Data>Prepar3D.exe</Data>
<Data>3.4.22.19868</Data>
<Data>588f7cbf</Data>
<Data>MSVCR90.dll</Data>
<Data>9.0.30729.6161</Data>
<Data>4dace5b9</Data>
<Data>c0000417</Data>
<Data>00031484</Data>
<Data>d14</Data>
<Data>01d2aa4c80c4c73a</Data>
<Data>P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe</Data>
<Data>C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll</Data>
<Data>e481ec90-163f-11e7-a478-6cf0497dce43</Data>
</EventData>
</Event>


Faulting application name: Prepar3D.exe, version: 3.4.22.19868, time stamp: 0x588f7cbf
Faulting module name: MSVCR90.dll, version: 9.0.30729.6161, time stamp: 0x4dace5b9
Exception code: 0xc0000417
Fault offset: 0x00031484
Faulting process id: 0xd14
Faulting application start time: 0x01d2aa4c80c4c73a
Faulting application path: P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe
Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll
Report Id: e481ec90-163f-11e7-a478-6cf0497dce43




Log Name: Application
Source: Application Error
Date: 3/31/2017 1:28:54 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: ijdjr-PC
Description:
Faulting application name: Prepar3D.exe, version: 3.4.22.19868, time stamp: 0x588f7cbf
Faulting module name: MSVCR90.dll, version: 9.0.30729.6161, time stamp: 0x4dace5b9
Exception code: 0xc0000417
Fault offset: 0x00031484
Faulting process id: 0xd14
Faulting application start time: 0x01d2aa4c80c4c73a
Faulting application path: P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe
Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll
Report Id: e481ec90-163f-11e7-a478-6cf0497dce43
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-03-31T18:28:54.000000000Z" />
<EventRecordID>242691</EventRecordID>
<Channel>Application</Channel>
<Computer>ijdjr-PC</Computer>
<Security />
</System>
<EventData>
<Data>Prepar3D.exe</Data>
<Data>3.4.22.19868</Data>
<Data>588f7cbf</Data>
<Data>MSVCR90.dll</Data>
<Data>9.0.30729.6161</Data>
<Data>4dace5b9</Data>
<Data>c0000417</Data>
<Data>00031484</Data>
<Data>d14</Data>
<Data>01d2aa4c80c4c73a</Data>
<Data>P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe</Data>
<Data>C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll</Data>
<Data>e481ec90-163f-11e7-a478-6cf0497dce43</Data>
</EventData>
</Event>


Like as before, I can see the selection of F4J to choose, I select one and then P3D tries to do its thing and then crashes looking for a solution.

[SaltyDog]

Now I can load a plane and shortly there after it freezes and then crashes.
Here is the event viewer, looks like a Gauges\MV_F-4J_Sys.dll that my P3D is choking on here, see for yourself
Log Name: Application
Source: Application Error
Date: 3/31/2017 3:16:36 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: ijdjr-PC
Description:
Faulting application name: Prepar3D.exe, version: 3.4.22.19868, time stamp: 0x588f7cbf
Faulting module name: MV_F-4J_Sys.dll, version: 1.4.0.8, time stamp: 0x5831d5de
Exception code: 0xc0000005
Fault offset: 0x0002c64f
Faulting process id: 0x19e4
Faulting application start time: 0x01d2aa5b668533fe
Faulting application path: P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe
Faulting module path: P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Gauges\MV_F-4J_Sys.dll
Report Id: f079b480-164e-11e7-a478-6cf0497dce43
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-03-31T20:16:36.000000000Z" />
<EventRecordID>242712</EventRecordID>
<Channel>Application</Channel>
<Computer>ijdjr-PC</Computer>
<Security />
</System>
<EventData>
<Data>Prepar3D.exe</Data>
<Data>3.4.22.19868</Data>
<Data>588f7cbf</Data>
<Data>MV_F-4J_Sys.dll</Data>
<Data>1.4.0.8</Data>
<Data>5831d5de</Data>
<Data>c0000005</Data>
<Data>0002c64f</Data>
<Data>19e4</Data>
<Data>01d2aa5b668533fe</Data>
<Data>P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe</Data>
<Data>P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Gauges\MV_F-4J_Sys.dll</Data>
<Data>f079b480-164e-11e7-a478-6cf0497dce43</Data>
</EventData>
</Event>



Log Name: Application
Source: Application Error
Date: 3/31/2017 3:16:36 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: ijdjr-PC
Description:
Faulting application name: Prepar3D.exe, version: 3.4.22.19868, time stamp: 0x588f7cbf
Faulting module name: MV_F-4J_Sys.dll, version: 1.4.0.8, time stamp: 0x5831d5de
Exception code: 0xc0000005
Fault offset: 0x0002c64f
Faulting process id: 0x19e4
Faulting application start time: 0x01d2aa5b668533fe
Faulting application path: P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe
Faulting module path: P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Gauges\MV_F-4J_Sys.dll
Report Id: f079b480-164e-11e7-a478-6cf0497dce43
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-03-31T20:16:36.000000000Z" />
<EventRecordID>242712</EventRecordID>
<Channel>Application</Channel>
<Computer>ijdjr-PC</Computer>
<Security />
</System>
<EventData>
<Data>Prepar3D.exe</Data>
<Data>3.4.22.19868</Data>
<Data>588f7cbf</Data>
<Data>MV_F-4J_Sys.dll</Data>
<Data>1.4.0.8</Data>
<Data>5831d5de</Data>
<Data>c0000005</Data>
<Data>0002c64f</Data>
<Data>19e4</Data>
<Data>01d2aa5b668533fe</Data>
<Data>P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe</Data>
<Data>P:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Gauges\MV_F-4J_Sys.dll</Data> <<<<<<<< Houston, looks like we got a problem!!!
<Data>f079b480-164e-11e7-a478-6cf0497dce43</Data>
</EventData>
</Event>

[SaltyDog]

Every thing works Okay now that the update for MV_F-4S_Sys.dll was replaced. I think the older version must of been buggy.

[JonathanBleeker]

And the F-4E? Is it working now?

[SaltyDog]

And the F-4E? Is it working now?

It's the F4J series, yes it works now. I think when P3d updates they sometimes unintentionally kill the phantoms here but I guess that is progress. The update contained a couple files that allowed P3D to not crash.