Can someone please tell me why I'm getting the following Steam error after my second reinstall to Prepar3d.4. I thought maybe

I had installed Prepar3d into Steam, but I didn't My Steam install is working great

Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: PMDG_747QOTSII_2.dll, version: 11.14.0.0, time stamp: 0x572b6e57
Exception code: 0xc0000005
Fault offset: 0x00002689
Faulting process id: 0x16e0
Faulting application start time: 0x01d2f469db1e28ba
Faulting application path: C:\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: C:\Steam\steamapps\common\FSX\Gauges\PMDG_747QOTSII_2.dll
Report Id: adf5fdd8-6060-11e7-ba67-382c4aba4c8d

 fsx.exe 
   10.0.62615.0 
   559f9a9a 
   PMDG_747QOTSII_2.dll 
   11.14.0.0 
   572b6e57 
   c0000005 
   00002689 
   16e0 
   01d2f469db1e28ba 
   C:\Steam\steamapps\common\FSX\fsx.exe 
   C:\Steam\steamapps\common\FSX\Gauges\PMDG_747QOTSII_2.dll 
   adf5fdd8-6060-11e7-ba67-382c4aba4c8d 

Dan McLain
 

13 minutes ago, DanM said:

Can someone please tell me why I'm getting the following Steam error after my second reinstall to Prepar3d.4. I thought maybe

I had installed Prepar3d into Steam, but I didn't My Steam install is working great

Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: PMDG_747QOTSII_2.dll, version: 11.14.0.0, time stamp: 0x572b6e57
Exception code: 0xc0000005
Fault offset: 0x00002689
Faulting process id: 0x16e0
Faulting application start time: 0x01d2f469db1e28ba
Faulting application path: C:\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: C:\Steam\steamapps\common\FSX\Gauges\PMDG_747QOTSII_2.dll
Report Id: adf5fdd8-6060-11e7-ba67-382c4aba4c8d

 fsx.exe 
   10.0.62615.0 
   559f9a9a 
   PMDG_747QOTSII_2.dll 
   11.14.0.0 
   572b6e57 
   c0000005 
   00002689 
   16e0 
   01d2f469db1e28ba 
   C:\Steam\steamapps\common\FSX\fsx.exe 
   C:\Steam\steamapps\common\FSX\Gauges\PMDG_747QOTSII_2.dll 
   adf5fdd8-6060-11e7-ba67-382c4aba4c8d 

Dan McLain
 

Hi Dan,

What's changed on your system recently?

Hi, nothing that I am aware of except the updates. However I don't think it should 

effect the install. I did make a entry into the exe.xml to start Saitek Panels. Also

my Prepar3d core directory is in the C: drive. But that didn't effect the first install.

Thanks for your assistance,

Dan McLain

12 minutes ago, DanM said:

Hi, nothing that I am aware of except the updates. However I don't think it should 

effect the install. I did make a entry into the exe.xml to start Saitek Panels. Also

my Prepar3d core directory is in the C: drive. But that didn't effect the first install.

Thanks for your assistance,

Dan McLain

Try disabling the entry in the exe.xml

Ouch.. I am having a hard time building a sequence of events in my mind.  "after my second reinstall to Prepar3d.4,"  implies all was working well at one time, what was installed the second time to P3D? Did you install QOTSII to both FSXSE and P3D?  Did authentication work okay?

Also, "My Steam install is working great" but you are getting the crash report from FSXSE?

Your right, OUCH, I removed the entry from the exe.xml file and reinstalled and 

I can tell that the installation went different because I do not have any orphan liveries.

Something interesting even though I selected only the Prepar3dv4 installation in both

the 747 and 777 in the ops center I have installations in both version 3 and 4..

FSX Steam is working great Prepar3dv4 now just crashes to the desktop with no error 

message.

Thanks for the response,

Dan McLain

Sorry, just reread your post, when I say second install, I'm talking about the second install I tried after the update. I did two installs before I posted in the forum. I did install into FSX Steam and it is working great. Hope I cleared things up.

Thanks,

Dan McLain

-

45 minutes ago, DanM said:

Sorry, just reread your post, when I say second install, I'm talking about the second install I tried after the update. I did two installs before I posted in the forum. I did install into FSX Steam and it is working great. Hope I cleared things up.

Thanks,

Dan McLain

-

Dan,

Just to confirm:

You had FSX Steam edition + 747 installed and working well

You installed P3Dv4 + 747

After this your FSX Steam edition + 747 crashes with that error message?

Edit: Then you reinstalled the 747 to where P3Dv4? FSX?

Now after that steam is fine but P3D crashes?

HI Chris, 

No FSX Steam never crashed, it has always worked great. My Prepar3dv4 

was crashing with that error message. I have the 747 installed in Prepar3d and Steam.

Thanks,

Dan McLain

 

24 minutes ago, DanM said:

HI Chris, 

No FSX Steam never crashed, it has always worked great. My Prepar3dv4 

was crashing with that error message. I have the 747 installed in Prepar3d and Steam.

Thanks,

Dan McLain

 

But that crash log you posted is from FSX Steam?

HI Chris,

I know confused me too!!, the only crash I have experienced is with Prepar3d.

Dan mcLain

16 minutes ago, DanM said:

HI Chris,

I know confused me too!!, the only crash I have experienced is with Prepar3d.

Dan mcLain

Have you ever used the Estonia Migration Tool?

Hi Chris,

Yes one time, to my understanding it just creates a virtual FSX folder. So I stupidly

tried to install SPAD, long story short I did a complete repair on Prepard3

including Deleting the generated files. After that all was well untill the PMDG update.

Even though I only select version 4 in the install and it still installs both 3&4 could 

that cause a problem.

Thanks again,

Dan McLain

I still have no idea of what a description of the problem might be.  I would help if I could look over your shoulder but being unable to do that I have to rely on your problem description.  Only P3D is crashing but you are getting FSXSE error messages?

 

EDIT:  Just saw your post... You did use the EMT? Well then welcome to the club of unfortunates. It has by now corrupted your windows registry and even when uninstalled it will not restore things.  It doesn't create virtual folders, it used directory links and false registry entries to try to spoof installers.  In other words, it is a virus.  The only thing that makes it legal is that is doesn't include the installers it is spoofing.  Your best bet is to take your computer to a Geek and get the registry cleaned up.

HI Dan,

That is correct. I lived in Corpus Christi from 1976 to 1983.

Thanks, for your response,

Dan Mclain