Jump to content
The simFlight Network Forums

Recommended Posts

Posted

This is the first time I've had to come here in over 20 years. FSX kept crashing and I could not figure out why. It happened all of a sudden. I tried it narrowing it down. Installed and uninstalled FSX many times. Come to find out it was FSUIPC. I have Windows 7 64bit with FSX+Acceleration. What in the world is going on? It took me 2 days to figure out what it was so I'm aggravated. Is there a fix for this problem please?

Posted

Have you tried downloading the latest version of FSUIPC from this thread: http://forum.simflight.com/topic/66139-updated-modules/ ?

There was a "security" change made to Windows 7 a while ago that has caused a lot of problems with FSX add-ons including FSUIPC. Therefore installing the latest version with Pete's latest set of fixes may well help. Not guaranteed, but it's a good starting point.

Ian P.

Posted

Have you tried downloading the latest version of FSUIPC from this thread: http://forum.simflig...pdated-modules/ ?

There was a "security" change made to Windows 7 a while ago that has caused a lot of problems with FSX add-ons including FSUIPC. Therefore installing the latest version with Pete's latest set of fixes may well help. Not guaranteed, but it's a good starting point.

Ian P.

I used the latest version and it's still crashing and i'm getting aggravated. The screen just goes black randomly and the monitor turns orange. There's no errors or anything.

Posted

I used the latest version and it's still crashing and i'm getting aggravated. The screen just goes black randomly and the monitor turns orange. There's no errors or anything.

That is sounding very much like a corrupted installation or a bad video driver, or even hardware problems. Nothing in FSX or any of my software can make monitors turn orange!

I think you are looking at some serious problem which may require some amount of re-installation at minimum.

If you still think it must be FSUIPC (which is really impossible), show me the FSUIPC4.LOG file from the FSX modules folder -- one produced by the last time you attempted to run FSX. If there isn't one there, then it hasn't even been run yet asnd it is certainly an FSX or simConnect problem. If there is one, you can paste it into a message here.

Pete

Posted

That is sounding very much like a corrupted installation or a bad video driver, or even hardware problems. Nothing in FSX or any of my software can make monitors turn orange!

I think you are looking at some serious problem which may require some amount of re-installation at minimum.

If you still think it must be FSUIPC (which is really impossible), show me the FSUIPC4.LOG file from the FSX modules folder -- one produced by the last time you attempted to run FSX. If there isn't one there, then it hasn't even been run yet asnd it is certainly an FSX or simConnect problem. If there is one, you can paste it into a message here.

Pete

The weird thing is that I just reinstalled FSX. The minute I take FSUIPC out it runs fine. When put it in and starts all over again.

Posted

The weird thing is that I just reinstalled FSX. The minute I take FSUIPC out it runs fine. When put it in and starts all over again.

Yes, but without more information I can't help. One thing, though, why did you reinstall FSX? If it was after a complete windows install that's okay, but if you simply tried to uninstall and reinstall then it is actually quite likely that the Simconnect side-by-side system is in a mess. That seems to be the biggest cause of SimConnect problems with FSX. The uninstall just makes a complete hash of that side of things.

Did you find a log? The next step depends on the answers to my previous requests for information.

You might also look at my recommendations at the end of this thread, near yours:

FSUIPC causing CTD in FSX

Regards

Pete

Posted

Yes, but without more information I can't help. One thing, though, why did you reinstall FSX? If it was after a complete windows install that's okay, but if you simply tried to uninstall and reinstall then it is actually quite likely that the Simconnect side-by-side system is in a mess. That seems to be the biggest cause of SimConnect problems with FSX. The uninstall just makes a complete hash of that side of things.

Did you find a log? The next step depends on the answers to my previous requests for information.

You might also look at my recommendations at the end of this thread, near yours:

FSUIPC causing CTD in FSX

Regards

Pete

********* FSUIPC4, Version 4.726 by Pete Dowson *********

Reading options from "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini"

Trying to connect to SimConnect Acc/SP2 Oct07 ...

User Name=""

User Addr=""

FSUIPC4 not user registered

WIDEFS7 not user registered, or expired

Running inside FSX on Windows 7 (using SimConnect Acc/SP2 Oct07)

Module base=61000000

Wind smoothing fix is fully installed

DebugStatus=0

140 System time = 29/08/2011 06:18:20

140 FLT path = "C:\Users\Timster\Documents\Flight Simulator X Files\"

140 FS path = "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\"

406 LogOptions=00000000 00000001

406 SimConnect_Open succeeded: waiting to check version okay

6287 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)

6287 Initialising SimConnect data requests now

6287 FSUIPC Menu entry added

6318 C:\Users\Timster\Documents\Flight Simulator X Files\Atlanta.FLT

6318 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\b747_400\Boeing747-400.AIR

6770 Weather Mode now = Custom

18330 ASE with WX requester detected

Posted

********* FSUIPC4, Version 4.726 by Pete Dowson *********

Reading options from "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini"

Trying to connect to SimConnect Acc/SP2 Oct07 ...

User Name=""

User Addr=""

FSUIPC4 not user registered

WIDEFS7 not user registered, or expired

Running inside FSX on Windows 7 (using SimConnect Acc/SP2 Oct07)

Module base=61000000

Wind smoothing fix is fully installed

DebugStatus=0

140 System time = 29/08/2011 06:18:20

140 FLT path = "C:\Users\Timster\Documents\Flight Simulator X Files\"

140 FS path = "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\"

406 LogOptions=00000000 00000001

406 SimConnect_Open succeeded: waiting to check version okay

6287 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)

6287 Initialising SimConnect data requests now

6287 FSUIPC Menu entry added

6318 C:\Users\Timster\Documents\Flight Simulator X Files\Atlanta.FLT

6318 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\b747_400\Boeing747-400.AIR

6770 Weather Mode now = Custom

18330 ASE with WX requester detected

I did a clean install of FSX taking everything out of the registry. Is there a way to clean simconnect? Can you please give me give me some instructions? I just want to fix the problem. I was on the phone with Dell and it's not a hardware problem. I'm just trying to avoid having to do a clean install of windows starting all over again.

Posted

I did a clean install of FSX taking everything out of the registry. Is there a way to clean simconnect? Can you please give me give me some instructions? I just want to fix the problem. I was on the phone with Dell and it's not a hardware problem. I'm just trying to avoid having to do a clean install of windows starting all over again.

Here's the information form the install

Installer for FSUIPC4.DLL version 4.703

Looking in registry for FSX install path:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0

Parameter"AppPath"

... >>> OK! FOUND FSX! <<< ...

Looking in registry for ESP install path:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft ESP\1.0

Parameter"AppPath"

Not there, so looking in:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft ESP\1.0

Parameter"SetupPath"

... NOT found! ...

Looking in registry for Prepar3D install path:

HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D

Parameter"AppPath"

Not there, so looking in:

HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D

Parameter"SetupPath"

... NOT found! ...

===========================================================

INSTALLATION FOR FSX:

AppPath="C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\"

Checking version of FSX.EXE:

... Version 10.0.61637.0 (Need at least 10.0.60905.0)

Checking compatibility with installed SimConnect:

Found SimConnect build 60905 (Original)

Found SimConnect build 61242 (SP1 May07)

Found SimConnect build 61259 (Acc/SP2 Oct07)

Checking if there's already a version of FSUIPC4 installed in:

C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL

... No previous valid version found.

FSX Modules folder already exists.

Okay -- installed FSUIPC4 into "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL"

Looking for the current user's Application Data path:

... found as "C:\Users\Timster\AppData\Roaming"

Now finding \Microsoft\FSX\FSX.CFG for all users, including this one

Looking in "C:\Users\All Users\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Default\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Default User\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\DefaultAppPool\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Public\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Timster\AppData\Roaming"

Found FSX.CFG in "C:\Users\Timster\AppData\Roaming\Microsoft\FSX\FSX.CFG"

Now checking DLL.XML ...

... There is a previous DLL.XML, checking for FSUIPC4 section.

... FSUIPC4 section already exists but will be replaced.

... 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\UpdatusUser\AppData\Roaming"

... No FSX.CFG there

"Modules\FSUIPC Documents" folder created 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 controls.pdf" okay

Installed "GlobalSign Root.exe" 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 "Example LUA plugins.zip" okay

FSUIPC4.DLL installed and signature checked out okay!

Deleted GlobalSign Root fix program ... no longer relevant

===========================================================

All installer tasks completed okay!

*************** End of Install Log ***************

Then I put in the FSUIPC4726 patch.

Posted

Here's the information form the install

Installer for FSUIPC4.DLL version 4.703

Looking in registry for FSX install path:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0

Parameter"AppPath"

... >>> OK! FOUND FSX! <<< ...

Looking in registry for ESP install path:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft ESP\1.0

Parameter"AppPath"

Not there, so looking in:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft ESP\1.0

Parameter"SetupPath"

... NOT found! ...

Looking in registry for Prepar3D install path:

HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D

Parameter"AppPath"

Not there, so looking in:

HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D

Parameter"SetupPath"

... NOT found! ...

===========================================================

INSTALLATION FOR FSX:

AppPath="C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\"

Checking version of FSX.EXE:

... Version 10.0.61637.0 (Need at least 10.0.60905.0)

Checking compatibility with installed SimConnect:

Found SimConnect build 60905 (Original)

Found SimConnect build 61242 (SP1 May07)

Found SimConnect build 61259 (Acc/SP2 Oct07)

Checking if there's already a version of FSUIPC4 installed in:

C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL

... No previous valid version found.

FSX Modules folder already exists.

Okay -- installed FSUIPC4 into "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL"

Looking for the current user's Application Data path:

... found as "C:\Users\Timster\AppData\Roaming"

Now finding \Microsoft\FSX\FSX.CFG for all users, including this one

Looking in "C:\Users\All Users\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Default\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Default User\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\DefaultAppPool\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Public\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Timster\AppData\Roaming"

Found FSX.CFG in "C:\Users\Timster\AppData\Roaming\Microsoft\FSX\FSX.CFG"

Now checking DLL.XML ...

... There is a previous DLL.XML, checking for FSUIPC4 section.

... FSUIPC4 section already exists but will be replaced.

... 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\UpdatusUser\AppData\Roaming"

... No FSX.CFG there

"Modules\FSUIPC Documents" folder created 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 controls.pdf" okay

Installed "GlobalSign Root.exe" 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 "Example LUA plugins.zip" okay

FSUIPC4.DLL installed and signature checked out okay!

Deleted GlobalSign Root fix program ... no longer relevant

===========================================================

All installer tasks completed okay!

*************** End of Install Log ***************

Then I put in the FSUIPC4726 patch.

So it's not a hardware problem as Dell did a rigorous test and turned up nothing. That leaves software. I'm having no other problems. I'm going to try doing a flight and see what happens.

Posted

I did a clean install of FSX taking everything out of the registry. Is there a way to clean simconnect? Can you please give me give me some instructions?

I've no idea how yto "clean SuimConnect" -- when i deliberately messed mine up in order to work out how to sort it out (I had in mind to write a program to do it0, I ended up having to reformat and reinstall Windows and everything else from scratch. The whole side-by-side system of libraries in Vista and Win7 is totally horrendously involved and complex.

Anyway, on the good side the crash you are getting seems to be well beyond the SimConnect loading and linking part, so that may not be the problem. Additionally, since you asren't a registered FSUIPC user, in fact FSUIPC is doing very little indeed until you start up some FSUIPC-using applications (you hadn't, had you?).

The last thing which happened in FSUIPC was

6770 Weather Mode now = Custom

18330 ASE with WX requester detected

which implies you were starting ASE. Could you test without ASE just in case there's some interaction? Possibly it's related to corrupted cloud graphics being inserted. With the screen blanking and going green it has to be something with some graphic operations -- nothing in FSUIPC involves any such things. It could also possibly be a corrupt weather file being loaded initially -- try (temporarily) removing all the .WX files from the Flight simulator X Files folder in your Documents folder.

If none of this helps, I need yet more information. Maybe a SimConnect log, the DLL.XML and EXE.XML files, and details from the Windows error log. Please see my recommendations at the end of this thread, near yours:

FSUIPC causing CTD in FSX

Regards

Pete

Posted

I've no idea how yto "clean SuimConnect" -- when i deliberately messed mine up in order to work out how to sort it out (I had in mind to write a program to do it0, I ended up having to reformat and reinstall Windows and everything else from scratch. The whole side-by-side system of libraries in Vista and Win7 is totally horrendously involved and complex.

Anyway, on the good side the crash you are getting seems to be well beyond the SimConnect loading and linking part, so that may not be the problem. Additionally, since you asren't a registered FSUIPC user, in fact FSUIPC is doing very little indeed until you start up some FSUIPC-using applications (you hadn't, had you?).

The last thing which happened in FSUIPC was

which implies you were starting ASE. Could you test without ASE just in case there's some interaction? Possibly it's related to corrupted cloud graphics being inserted. With the screen blanking and going green it has to be something with some graphic operations -- nothing in FSUIPC involves any such things. It could also possibly be a corrupt weather file being loaded initially -- try (temporarily) removing all the .WX files from the Flight simulator X Files folder in your Documents folder.

If none of this helps, I need yet more information. Maybe a SimConnect log, the DLL.XML and EXE.XML files, and details from the Windows error log. Please see my recommendations at the end of this thread, near yours:

FSUIPC causing CTD in FSX

Regards

Pete

I really appreciate helping me out. Yes. I'm using Delta Acars, AI Smooth, and FS RealTime that all use FSIUPC but it is unregistered. Could that be a problem? I just don't have the money right now as the long exhaust pipe that going to the muffler resonated through and dragged on the road last week and by the time I got all that fixed up it was $500. Before that was the garage door opener, sprinklers, and the kitchen faucet. On top of it I'm having surgery 9/28 both my parents are having health problems.

Life has been dealing me a blow.

Posted

I really appreciate helping me out. Yes. I'm using Delta Acars, AI Smooth, and FS RealTime that all use FSIUPC but it is unregistered.

Being unregistered isn't a problem, but the point is I'd need to know whether any of those (and ASE) are running at the time you get the problems. There's precious little information at present, and none pointing to FSUIPC specifically other than it doesn't happen when FSUIPC isn't there. Since an unregistered FSUIPC does almost nothing, only responding to requests from applications, you need to test first with no such applications.

Then we can take the next step and determine which application and then what exactly it is doing causing the crash.

One thing even an unregistered FSUIPC is doing is getting the weather. If FS is loading with a corrupt weather file, that could be a problem not associated with an application. That's why I suggested moving the WX files out of the way too, as a test.

Please re-read my previous message and see that it is information that is needed, not money!

Regards

Pete

Posted

Being unregistered isn't a problem, but the point is I'd need to know whether any of those (and ASE) are running at the time you get the problems. There's precious little information at present, and none pointing to FSUIPC specifically other than it doesn't happen when FSUIPC isn't there. Since an unregistered FSUIPC does almost nothing, only responding to requests from applications, you need to test first with no such applications.

Then we can take the next step and determine which application and then what exactly it is doing causing the crash.

One thing even an unregistered FSUIPC is doing is getting the weather. If FS is loading with a corrupt weather file, that could be a problem not associated with an application. That's why I suggested moving the WX files out of the way too, as a test.

Please re-read my previous message and see that it is information that is needed, not money!

Regards

Pete

OK took out Activesky. Then the whole thing became a mess. Had to reinstall a clean version of windows and then start all over. Interesting though. Installed FSUIPC only and onlne with a Dell representative. Sure enough FSX crashed while flying in Honolulu. Then the computer kept restarting and getting blue screens. Took out FSX and now no problems at all. I give up at this point. I just don't think FSX is compatible with windows 7. It doesn't matter what I do but windows 7 doesn't like FSX. I hardly have anything installed. Did the uiautomationcore.dll fix and still the same problem. What was interesting is right after I installed FSUIPC everything went downhill. Oh well any suggestions would be appreciated. All other issues were fixed. So for right now I don't have FSX installed.

Posted

`

OK took out Activesky. Then the whole thing became a mess. Had to reinstall a clean version of windows and then start all over. Interesting though. Installed FSUIPC only and onlne with a Dell representative. Sure enough FSX crashed while flying in Honolulu. Then the computer kept restarting and getting blue screens. Took out FSX and now no problems at all. I give up at this point. I just don't think FSX is compatible with windows 7. It doesn't matter what I do but windows 7 doesn't like FSX. I hardly have anything installed. Did the uiautomationcore.dll fix and still the same problem. What was interesting is right after I installed FSUIPC everything went downhill. Oh well any suggestions would be appreciated. All other issues were fixed. So for right now I don't have FSX installed.

It's not really your fault. I think what has happened is the Microsoft Game Studios went out and so now that Windows 7 is out, it's not as compatible because it wasn't made for windows 7. From what I see is a lot of people are having problems running FSX on Windows 64 bit. I'm not the only person by a long shot.

Posted

OK took out Activesky. Then the whole thing became a mess. Had to reinstall a clean version of windows and then start all over.

??? I think Pete just asked that you not start ActiveSky, not to remove it.

Sure enough FSX crashed while flying in Honolulu. Then the computer kept restarting and getting blue screens. Took out FSX and now no problems at all.

If you're getting blue screens, you're having hardware issues, or a bad video driver. Most software won't tax a modern PC enough to trigger an issue, but FSX certainly can.

I just don't think FSX is compatible with windows 7.

Both FSX and FS9 work quite nicely with Win7. I think there's something specific to your PC that's causing your issues.

Cheers!

Luke

Posted

??? I think Pete just asked that you not start ActiveSky, not to remove it.

If you're getting blue screens, you're having hardware issues, or a bad video driver. Most software won't tax a modern PC enough to trigger an issue, but FSX certainly can.

Both FSX and FS9 work quite nicely with Win7. I think there's something specific to your PC that's causing your issues.

Cheers!

Luke

Ever since I installed acceleration there seems to be a problem. FSX never really worked well with Windows 7 64bit. It wasn't made for it. There are no more patches after sp2. I'm not going to do another clean boot of windows for FSX. It seems just a waste of time.

Posted

Ever since I installed acceleration there seems to be a problem. FSX never really worked well with Windows 7 64bit. It wasn't made for it. There are no more patches after sp2. I'm not going to do another clean boot of windows for FSX. It seems just a waste of time.

As others have pointed out, there's something seriously wrong with your PC, that's pretty much a certainty. Windows 7 64-bit and FSX work excellently together, as if they were made for each other. Since updating from XP and the awful Vista I've had no problems whatsoever with FSX + Acceleration and many many add-ons, and that goes for 4 PCs all running Win7-64. The only times I've seen a blue screen with Win7 was when I overclocked a little too much!

Think of FSX as a benchmark test for your PC. Nothing else you're likely to run, other than specifically designed stress tests and benchmarks will stress it anywhere near the same. PC restarts and blue screens can only be caused by faults in drivers or hardware. Nothing else has enough privilege to cause them. It may even be as simple as a faulty memory module, or a badly seated one, or some BIOS setting wrong, or overheating. There are ways to nail it down reasonably accurately, but it takes patience and forethought.

Regards

Pete

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • 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.