FSX Has Detected a Problem - Error

[cfelix]

I had to do a DVD repair on my FSX.  After re-installing 4.931 I started getting this error when starting FSX:

 

 

If I click yes I get a fatal crash with the details pointing to FSUIPC.  If I click no FSX starts normally but with no FSUIPC.  I've tried going back to a previous version but still got the error message.  I've also tried removing my INI file. Please help - I need my FSUIPC.

 

Charlie

 

[Pete Dowson]

I had to do a DVD repair on my FSX.  After re-installing 4.931 I started getting this error when starting FSX:

 

Is an FSUIPC4.LOG file produced in the Modules folder? Are there any crash details mentioning FSUIPC4 in the Windows event viewer? If either, or both, I need to see them please -- paste into a reply here. And where are these "the details pointing to FSUIPC" -- obviously I need to see those, so why keep them to yourself?

 

One of the most likely problems is a corrupt Weather file (.WX file) being loaded by default, or a corrupt WXStationList.bin file (same folder as your FSX.CFG file). You could try deleting both.

 

Otherwise, if no log is being produced and there is no crash reported in Windows, then it is the usual SimConnect timing bug. Please see the FAQ subforum. There's a thread relating to such problems.

 

Regards

Pete

[cfelix]

Thanks for getting back to me so quickly.

 

I went to the FAQ and tried the Loader file. I see that it added "FSUIPC4_Loader.dll" to my "dll.xml" file.  It seemed to help and I was able to run FSX.  However FSUIPC does not appear in the addon drop-down.  Here is the FSUIPC.fsx.log:

 

********* FSUIPC4, Version 4.931 by Pete Dowson *********

Reading options from "K:\FSX\Modules\FSUIPC4.ini"

Running inside Prepar3D v2 on Windows 7

... Prepar3D has been renamed as "fsx"

Module base=59650000

User Name=""

User Addr=""

FSUIPC4 not user registered

WIDEFS7 not user registered, or expired

       16 System time = 21/04/2014 13:49:50

       16 FLT path = "C:\Users\Charlie\Documents\Flight Simulator X Files\"

       16 Trying K:\FSX\Modules\SimConnectP3D2.dll

       32 Trying to connect to SimConnect ESP Orig ...

       32 FS path = "K:\FSX\"

      234 LogOptions=00000000 00000001

      234 ### Failed to obtain SIM1 Frictions access: no frictions facilities available!

      234     Reason 7: SIM1 base=20B10000

      234     FrictionAddr=20C14F38 contains FEEC85D9

      234     BrakingAddr=20C161F8 contains DDE0D910

      234 Hook Error: no DOS signature for SIM1.dll

    55193 System time = 21/04/2014 13:50:46

    55193 *** FSUIPC log file being closed

Memory managed: 4 Allocs, 4 Freed

********* FSUIPC Log file closed *** *******

 

 I see that is says "not user registered" but I am a register user.  I hope we're getting closer.

 

Charlie

[Pete Dowson]

Running inside Prepar3D v2 on Windows 7

... Prepar3D has been renamed as "fsx"

 

There's your problem. If you rename the EXE then FSUIPC will most certainly not be using it's normal files and can go very wrong. It depends on the EXE name.

 

Update your P3D with the Hotfix to build 10438, and make sure you are running Prepar3D.exe.

 

Pete

[cfelix]

Hi Pete,

I'm not sure what to do. I'm running FSX not P3D. I do have P3D installed but my problem is with running "FSX.exe".

Charlie

[Pete Dowson]

I'm not sure what to do. I'm running FSX not P3D. I do have P3D installed but my problem is with running "FSX.exe".

 

 

Well, FSUIPC certainly thinks it is P3D for some reason. Most odd. Please show me the FSUIPC4 Install log file (paste in in a reply). Also check the FSX folder "K:\FSX", as I think that FSUIPC might be seeing a Prepar3D.exe there too.

 

Unfortunately FSUIPC cannot trust just the name of the EXE in which it finds itself because folks appear to be renaming these to try to get around installers not yet updated to deal with P3D. Therefore FSUIPC does additional checks. It assumes it won't find a Prepar3D.EXE inside an FSX folder (why should it?), but because of installer faking it has to be able to recognise a P3D folder with an FSX.EXE inside it.

 

Pete

[cfelix]

Thank You !!! 

 

:oops: The problem was that a copy of the Prepar3D.exe got into my FSX folder.  I have no Idea how it happened but when I removed it things worked fine.  I've had problems with missing or corrupted files before but I never would have thought that an extra file would cause this much trouble.  Thanks again for your dedication to not only creating and constantly updating this fantastic product, but also for providing top notch customer service.

 

Charlie