I had another FSX freeze, where the animation totally stopped but with the sound running seemingly fine.I waited out the freeze and after about ten minutes, it SEEMINGLY corrected itself, but then I saw that Active Sky 6.5 was trying to update the weather depiction. You know..you get that slight texture flash from the sky in the upper quadrant of your screen, just before the update to graphics.Well...FSX froze again. I then went into the Task Manager and found that both FSX and Active Sky 6.5 were reporting as non-responding.Instead of just ending FSX, I ended Active Sky and as soon as I did that, FSX corrected itself and carried on as if nothing had happened in the first place. Ok..so what does this mean? Is it Active Sky that is causing the freeze up's with W7 as the O.S? Is it interaction/dependency on FSUIPC that is causing the freezes? Is it in fact Active Sky at all...but rather FSUIPC (the latest version) that is causing the freezes? There are so many relationships and layering of programs...Should there be a dedicated FSUIPC version written just for the Window 7 operating system? I do have Active Sky running in XP SP3 mode, as it was the operating system when this program was released. I had it running in W7 native as well as Vista SP2, but still had the freezes. I'm not saying that Active Sky (ALONE) is the culprit, but somewhere in the relationships of programs: Active Sky--->SimConnect--->FSUIPC that is causing FSX to freeze and AppHang. I proved that because as soon as I ended the Active Sky/SimConnect/FSUIPC interaction, I got back FSX with no aberrations or crashing of core program.So...what does this suggest? FSX is not freezing of itself. It is not in the core coding, other than perhaps if somehow SimConnect is what is crapping out. I don't know. But at least, I know that it is when I have a satellite program in play...is when this freeze up thing is happening. How would one be able to back track from FSX----SimConnect--->FSUIPC--->Active Sky 6.5 to find what EXACTLY is causing FSX to stop animation and merely sit there, locked up. Does anybody have a suggestion as to how this can be nailed down? It seemed that when Active Sky was trying to update/inject the new weather/graphic directive is when FSX hung up. So...to the guru's, what becomes involved in program interaction (what is being called into play) when Active Sky, or any weather program is TRYING to inject its directive to FSX? That could be a start to finally ridding ourselves of this PITA.Post Edit: One of my practises is to reduce all the satellite programs to the task bar. I wonder if when you reduce a program's window, can this have any effect on the subject?Mitch

I had another FSX freeze, where the animation totally stopped but with the sound running seemingly fine.I waited out the freeze and after about ten minutes, it SEEMINGLY corrected itself, but then I saw that Active Sky 6.5 was trying to update the weather depiction. You know..you get that slight texture flash from the sky in the upper quadrant of your screen, just before the update to graphics.Well...FSX froze again. I then went into the Task Manager and found that both FSX and Active Sky 6.5 were reporting as non-responding.Instead of just ending FSX, I ended Active Sky and as soon as I did that, FSX corrected itself and carried on as if nothing had happened in the first place. Ok..so what does this mean? Is it Active Sky that is causing the freeze up's with W7 as the O.S? Is it interaction/dependency on FSUIPC that is causing the freezes? Is it in fact Active Sky at all...but rather FSUIPC (the latest version) that is causing the freezes? There are so many relationships and layering of programs...Should there be a dedicated FSUIPC version written just for the Window 7 operating system? I do have Active Sky running in XP SP3 mode, as it was the operating system when this program was released. I had it running in W7 native as well as Vista SP2, but still had the freezes. I'm not saying that Active Sky (ALONE) is the culprit, but somewhere in the relationships of programs: Active Sky--->SimConnect--->FSUIPC that is causing FSX to freeze and AppHang. I proved that because as soon as I ended the Active Sky/SimConnect/FSUIPC interaction, I got back FSX with no aberrations or crashing of core program.So...what does this suggest? FSX is not freezing of itself. It is not in the core coding, other than perhaps if somehow SimConnect is what is crapping out. I don't know. But at least, I know that it is when I have a satellite program in play...is when this freeze up thing is happening. How would one be able to back track from FSX----SimConnect--->FSUIPC--->Active Sky 6.5 to find what EXACTLY is causing FSX to stop animation and merely sit there, locked up. Does anybody have a suggestion as to how this can be nailed down? It seemed that when Active Sky was trying to update/inject the new weather/graphic directive is when FSX hung up. So...to the guru's, what becomes involved in program interaction (what is being called into play) when Active Sky, or any weather program is TRYING to inject its directive to FSX? That could be a start to finally ridding ourselves of this PITA.Mitch

Hi Mitch,Sorry about your issues and you are not the only, as many have had similar and other problems with FSX. What I would do is load FSX alone without any of your 3rd party addons and see if she performs without lockups. I would also recommend that you do not try to run FSX in another compatibility mode as this just complicates the issue. It is one step at a time. As far as Active Sky is concerned, the best place to go is to their forum and see if any others are having problems like yours. 1st though, just narrow the playing field and run FSX only. After that, you can inject the other addons and see what happens. Remain Calm :( RegardsBob

I had another FSX freeze, where the animation totally stopped but with the sound running seemingly fine.I waited out the freeze and after about ten minutes, it SEEMINGLY corrected itself, but then I saw that Active Sky 6.5 was trying to update the weather depiction. You know..you get that slight texture flash from the sky in the upper quadrant of your screen, just before the update to graphics.Well...FSX froze again. I then went into the Task Manager and found that both FSX and Active Sky 6.5 were reporting as non-responding.Instead of just ending FSX, I ended Active Sky and as soon as I did that, FSX corrected itself and carried on as if nothing had happened in the first place. Ok..so what does this mean? Is it Active Sky that is causing the freeze up's with W7 as the O.S? Is it interaction/dependency on FSUIPC that is causing the freezes? Is it in fact Active Sky at all...but rather FSUIPC (the latest version) that is causing the freezes? There are so many relationships and layering of programs...Should there be a dedicated FSUIPC version written just for the Window 7 operating system? I do have Active Sky running in XP SP3 mode, as it was the operating system when this program was released. I had it running in W7 native as well as Vista SP2, but still had the freezes. I'm not saying that Active Sky (ALONE) is the culprit, but somewhere in the relationships of programs: Active Sky--->SimConnect--->FSUIPC that is causing FSX to freeze and AppHang. I proved that because as soon as I ended the Active Sky/SimConnect/FSUIPC interaction, I got back FSX with no aberrations or crashing of core program.So...what does this suggest? FSX is not freezing of itself. It is not in the core coding, other than perhaps if somehow SimConnect is what is crapping out. I don't know. But at least, I know that it is when I have a satellite program in play...is when this freeze up thing is happening. How would one be able to back track from FSX----SimConnect--->FSUIPC--->Active Sky 6.5 to find what EXACTLY is causing FSX to stop animation and merely sit there, locked up. Does anybody have a suggestion as to how this can be nailed down? It seemed that when Active Sky was trying to update/inject the new weather/graphic directive is when FSX hung up. So...to the guru's, what becomes involved in program interaction (what is being called into play) when Active Sky, or any weather program is TRYING to inject its directive to FSX? That could be a start to finally ridding ourselves of this PITA.Mitch

Hey Mitch,You could try disabling AS for a while and see how it goes, but then again it could just be the combination and last straw effect...Who knows.After so many attempts at stoping BlackScreens, Stuttering, dropped textures or half rendered 3d moderls ,I find that Win7 graphic memory mngr WMMD1.1 just cant handle certain situations of FSX maxed out.So last night I set up the system as a dual boot win764Ult/WinXP64P-SP2 and will move all the FSX stuff over to XP64 and looking forward to using my hardware as it was meant to be.

Hi Mitch,Sorry about your issues and you are not the only, as many have had similar and other problems with FSX. What I would do is load FSX alone without any of your 3rd party addons and see if she performs without lockups. I would also recommend that you do not try to run FSX in another compatibility mode as this just complicates the issue. It is one step at a time. As far as Active Sky is concerned, the best place to go is to their forum and see if any others are having problems like yours. 1st though, just narrow the playing field and run FSX only. After that, you can inject the other addons and see what happens. Remain Calm :( RegardsBob

Hello Bob,Bob, I have already run through elimination, and have only used weather gen within FSX. No hangs. Ok...but when you add on back into the mix...you can't truly cause and effect with total isolation anything that needs an interpreter such as FSUIPC. Now...FSUIPC connects to FSX through SimConnect, is that not right? So let's say that I found by NOT running Active Sky 6.5, I get no further freezes. But, is that truly the cause, or by not running it, does FUSIPC go dormant, and perhaps a finger should be pointing to FSUIPC working with W7? How can you not run FUSIPC, when you need to for any other associate program layered on? I guess that is the problem. Who knows if FUSIPC even has a part in this? Either you don't use anything that needs a shell entry....or perhaps we can figure this out. Perhaps it is also as another posted, that the memory manager of W7 just doesn't do the trick, and by my ending Active Sky, it off-loads so as to allow FSX to run once more. It's of course not about finger pointing...but in finding out exactly WHY this happens, and can there be a work around, or outright patch/fix?Mitch

Hey Mitch,You could try disabling AS for a while and see how it goes, but then again it could just be the combination and last straw effect...Who knows.After so many attempts at stoping BlackScreens, Stuttering, dropped textures or half rendered 3d moderls ,I find that Win7 graphic memory mngr WMMD1.1 just cant handle certain situations of FSX maxed out.So last night I set up the system as a dual boot win764Ult/WinXP64P-SP2 and will move all the FSX stuff over to XP64 and looking forward to using my hardware as it was meant to be.

What a pain, huh? I really like W7, but don't use all the features it has, honestly. My P.C. came shipped with Vista Ultimate, and I can't remember if I ever had a freeze with FSX running any background program or not. If I did, I can't remember. But if this keeps up, I just might revert back to Vista Ultimate and be done with it. I use my computer mostly for flight sim'ming, so I do at least have Vista Ult to fall back on if that is what needs to be done. The only thing though, and this is troubling...is that I believe that those that are still running Vista 32/64 bit whatever's ALSO have reported FSX freeze-ups. If that is so...then W7's memory manager is not the bad boy here.....and we're right back to what is happening in the chain-of-command between the add-on program, and FSX....Mitch

I had another FSX freeze, where the animation totally stopped but with the sound running seemingly fine.I waited out the freeze and after about ten minutes, it SEEMINGLY corrected itself, but then I saw that Active Sky 6.5 was trying to update the weather depiction. You know..you get that slight texture flash from the sky in the upper quadrant of your screen, just before the update to graphics.Well...FSX froze again. I then went into the Task Manager and found that both FSX and Active Sky 6.5 were reporting as non-responding.Instead of just ending FSX, I ended Active Sky and as soon as I did that, FSX corrected itself and carried on as if nothing had happened in the first place. Ok..so what does this mean? Is it Active Sky that is causing the freeze up's with W7 as the O.S? Is it interaction/dependency on FSUIPC that is causing the freezes? Is it in fact Active Sky at all...but rather FSUIPC (the latest version) that is causing the freezes? There are so many relationships and layering of programs...Should there be a dedicated FSUIPC version written just for the Window 7 operating system? I do have Active Sky running in XP SP3 mode, as it was the operating system when this program was released. I had it running in W7 native as well as Vista SP2, but still had the freezes. I'm not saying that Active Sky (ALONE) is the culprit, but somewhere in the relationships of programs: Active Sky--->SimConnect--->FSUIPC that is causing FSX to freeze and AppHang. I proved that because as soon as I ended the Active Sky/SimConnect/FSUIPC interaction, I got back FSX with no aberrations or crashing of core program.So...what does this suggest? FSX is not freezing of itself. It is not in the core coding, other than perhaps if somehow SimConnect is what is crapping out. I don't know. But at least, I know that it is when I have a satellite program in play...is when this freeze up thing is happening. How would one be able to back track from FSX----SimConnect--->FSUIPC--->Active Sky 6.5 to find what EXACTLY is causing FSX to stop animation and merely sit there, locked up. Does anybody have a suggestion as to how this can be nailed down? It seemed that when Active Sky was trying to update/inject the new weather/graphic directive is when FSX hung up. So...to the guru's, what becomes involved in program interaction (what is being called into play) when Active Sky, or any weather program is TRYING to inject its directive to FSX? That could be a start to finally ridding ourselves of this PITA.Mitch

Wow! An i7 975X Extreme biting the dust with FSX! You know, FSX was never made to have ALL the sliders turned to the max, especially with modern computer systems. FSX is an old program. You can get away with it some of the time but not all of the time. You still need to give it room to breathe to enjoy the eye-candy and excitement of the game. As to your questions, you are the best person to answer each as you have each of those programs and you can test them yourself. For instance, if you suffer no crashes with Active Sky turned off, then you could assume it was Active Sky and you need to turn down the weather systems. I have Active Sky Advanced and know that when I'm running it (or even the default weather system), I have to turn my sliders down a little and not fly the heavy metal, like the aircraft over at PMDG, LDS, or CS. Instead I'll usually fly one of the default aircraft and that gives me just as much joy. You might check the event viewer and see what exactly caused FSX to crash. There may be an entry in the log. I think you'll find the crash was not caused by Active Sky alone but a combination of things loaded at the time. The aircraft, the lighting, the scenery, the weather, the gauges working, and the number of AI work to bring down even the most powerful systems in the world. My suggestion is for you to bring your FSX back to the time when you were publishing so many rants about how great your new system works with FSX and that this is the "holy-grail". That probably was back when you first installed FSX on your system and you were getting FPS over 100 consistently before you started adding commercial addons (even I was getting over 90 FPS on my system with just the defaults). The more installed, the more that has to be rendered. You can still have a pleasant adventure on your system by turning a few things down. You can get this program called Process Monitor and run it while you are running FSX and see all the processes loaded and running during a flight. It will be a massive list but it might give you some insight into what it takes to run FSX and all of the eye-candy addons. Sorry to hear about your disasters and hope you can work out a fix soon and enjoy your nice new computer system!Best regards,Jim Young

Wow! An i7 975X Extreme biting the dust with FSX! You know, FSX was never made to have ALL the sliders turned to the max, especially with modern computer systems. FSX is an old program. You can get away with it some of the time but not all of the time. You still need to give it room to breathe to enjoy the eye-candy and excitement of the game. As to your questions, you are the best person to answer each as you have each of those programs and you can test them yourself. For instance, if you suffer no crashes with Active Sky turned off, then you could assume it was Active Sky and you need to turn down the weather systems. I have Active Sky Advanced and know that when I'm running it (or even the default weather system), I have to turn my sliders down a little and not fly the heavy metal, like the aircraft over at PMDG, LDS, or CS. Instead I'll usually fly one of the default aircraft and that gives me just as much joy. You might check the event viewer and see what exactly caused FSX to crash. There may be an entry in the log. I think you'll find the crash was not caused by Active Sky alone but a combination of things loaded at the time. The aircraft, the lighting, the scenery, the weather, the gauges working, and the number of AI work to bring down even the most powerful systems in the world. My suggestion is for you to bring your FSX back to the time when you were publishing so many rants about how great your new system works with FSX and that this is the "holy-grail". That probably was back when you first installed FSX on your system and you were getting FPS over 100 consistently before you started adding commercial addons (even I was getting over 90 FPS on my system with just the defaults). The more installed, the more that has to be rendered. You can still have a pleasant adventure on your system by turning a few things down. You can get this program called Process Monitor and run it while you are running FSX and see all the processes loaded and running during a flight. It will be a massive list but it might give you some insight into what it takes to run FSX and all of the eye-candy addons. Sorry to hear about your disasters and hope you can work out a fix soon and enjoy your nice new computer system!Best regards,Jim Young

Geez Jim...it's not about the hardware config of my system. Sorry, but your post sort of smacked of you-know-what envy.I clearly stated that my freeze up is occurring when Active Sky seems to want to update. My system's performance is quite stellar thank you! :) The FPS's are rock solid with everything that I have thrown at it. It is not about performance, given that everything runs at a steady 30 plus under lock-down and over 100 when not.... but about what particular set of circumstances is causing FSX to hang up. It is certainly not I7-975 HORSEPOWER! It could be that I am running an O.S. that was not created when FSX was coded. But the core system, thank you, is superb. Wow...that came out of you rather strong, LOL! Again, this is not a hard-ware 'can it run at full throttle', but a coding issue here between programs and perhaps the O.S.Cheers,Post Edit: I just had another freeze..and again, when I only ended Active Sky 6.5, I got back a properly functioning FSX. I know that Active Sky 6.5 was written for FS9. While it does work (sic) with FSX, could something in its coding, or when partnered with FSUIPC for FSX, be causing it to hang up, or....(many or's here) could W7 also have its share of the fault. Again folks, my system allows me to run everything at maximum with no performance hit. This is completely different. It is an app hang issue, and not a performance issue. Hopefully I will (sure I will, lol) get it sorted out and be freeze free once more. I did not have freezes of any kind when W7 was originally installed, so you can even suspect whatever Microsoft updates have been downloaded since the original W7 code was running. That's the problem with operating systems, they are not stagnant. They keep getting their coding modified by security and performance updates. That is why it is so hard to point a finger at the cause. You'd probably run out of fingers..... I'll work it out. :)Post Edit 2: I have been just running FS9 with AS 6.5 with no problems whatsoever. Same system, same hardware. Same drivers. I have a question, has anybody that has a weather program that was WRITTEN sole for FSX...had any issues with the use of it? By issues, I mean that it hung up on you since having owned and run it. If so, were you using any other O.S. than W7 (32/64 bit)?Mitch

What a pain, huh? I really like W7, but don't use all the features it has, honestly. My P.C. came shipped with Vista Ultimate, and I can't remember if I ever had a freeze with FSX running any background program or not. If I did, I can't remember. But if this keeps up, I just might revert back to Vista Ultimate and be done with it. I use my computer mostly for flight sim'ming, so I do at least have Vista Ult to fall back on if that is what needs to be done. The only thing though, and this is troubling...is that I believe that those that are still running Vista 32/64 bit whatever's ALSO have reported FSX freeze-ups. If that is so...then W7's memory manager is not the bad boy here.....and we're right back to what is happening in the chain-of-command between the add-on program, and FSX....Mitch

Well fun isnt the word for it...but FYI It is related to both the WMMD of Vista and Win7, thats why the strong suggestions of Nick and others to go back to XP64Pro-SP2 as it all works there. Give me a week or two to get everything loaded and I'll report, FSX side by side in Win7-64 vs XP-64I even have the I7 cranked up to 4.4+ using the Nochtua D14 with 3 P14 fans cooling it along with 12 GB of 2000 speed ram with a highly overclocked 285GTX...will see.BTW not too many copies of XP-64 pro SP2 left out there...

Well fun isnt the word for it...but FYI It is related to both the WMMD of Vista and Win7, thats why the strong suggestions of Nick and others to go back to XP64Pro-SP2 as it all works there. Give me a week or two to get everything loaded and I'll report, FSX side by side in Win7-64 vs XP-64I even have the I7 cranked up to 4.4+ using the Nochtua D14 with 3 P14 fans cooling it along with 12 GB of 2000 speed ram with a highly overclocked 285GTX...will see.BTW not too many copies of XP-64 pro SP2 left out there...

--------------------------------------------------------------------------------------I'd be most interested on your findings... :( Mitch

Mitch, dumb question, and perhaps Jim Skorna should be asking this - but why would you be running ASv6???We have ASX - written specifically for FSX: it was followed by ASA - MUCH better - and now ASE... The suggestion of the (long-named).dll file fixed my freezes, and I've never had a freeze that I could say definitively was caused by AS.

Hi Mitch,I had that happen to me a couple of times, once being a windows update, another time being a REX weather update. Each time I did not wait it out but stopped the FSX program. Jim,The FSX sliders are far right on my computer and the FPS are fantastic everywhere as is the smoothness. The fight between FSX and machinery to run it past its maximum design limits is over, and the machinery finally won. That is not the cause of these various spooky challenges, for they are software and operating systems related.FSX tweaks and mods are like a pretty woman putting on makeup and arranging her clothes just so. That is not the way it once was before the enormous advances in sceneries (ORBX), environment (REX) and great payware aircraft. Without all that stuff, tweaking FSX was like putting lipstick on a pig.The machinery is up to just about any task, however keeping the lady happy and healthy can be another matter. Stephen

Mitch, dumb question, and perhaps Jim Skorna should be asking this - but why would you be running ASv6???We have ASX - written specifically for FSX: it was followed by ASA - MUCH better - and now ASE... The suggestion of the (long-named).dll file fixed my freezes, and I've never had a freeze that I could say definitively was caused by AS.

Hi Paul,Not a dumb question at all! Well..I like AS 6.5. Until now, it worked perfectly..and I haven't nailed it as the culprit actually. I have noted that if I end its session, I can get FSX back to running. Could this also be FSUIPC, though? Paul, I have read of some who actually preferred AS 6.5 over ASX. Since I already had it...just thought to use it. Like I said, it works perfectly until the freeze happens. You mean the UIAuto one, right? I have that in my root folder as well. I would hate to buy ASX and find out it was not the root cause. Also, AS 6.5 works like a bear with FS9 of which is was written for, so that cancels out my system as a low-level fault. No, it's something around the coding with FSX OR...and a large 'or'..it could be something that was downloaded from the M.S. Update bound for W7. Needle in the haystack sort of thing. I know that I am not alone with this particular FSX PITA. Too bad they didn't have the iron-clad written efund policy that Flight1 Ltd has. It would help in a situation like this.Thanks for the input.Mitch

Mitch,Ask Pete if he thinks about your problem is related to FSUIPC.http://forums.simflight.com/viewforum.php?f=54Pete is always helpful in resolving problems related to his product.Rod

Mitch,Ask Pete if he thinks about your problem is related to FSUIPC.http://forums.simflight.com/viewforum.php?f=54Pete is always helpful in resolving problems related to his product.Rod

Hello Rod,I think I might have stumbled onto something before I ask him: I went into the A.S. 6.5 Root folder and took inventory. I found that in there , is a copy of FSUIPC that I assume the A.S. 6.5 install program places there for when you fire up the A.S. 6.5 GUI without first running FS9 and/or FSX. It was a 3.xx dll file. I then read A.S.'s FSX help file, and it says that A.S. 6.5 can be used with FSX, but only with an FSUIPC file starting at 4.xx I just replaced the ROOT FSUIPC FS9 file with the latest FSX version. I think that what might have been happening all along, is that I had fired up the GUI, and it was reading in and using the FS9 FSUIPC file for the entire FSX session. I have not yet tried this 'fix' experiment, but if it does the trick...then that is what it was..and I will publish the results. If it screws up my using A.S. 6.5 with FS9...because the FSX dedicated FSUIPC.dll is now resident in the A.S. 6.5 root folder...than the find will have been a bust. I'll get back after a successful FSX freeze-free flight at length.Mitch

Hi Paul,Not a dumb question at all! Well..I like AS 6.5. Until now, it worked perfectly..and I haven't nailed it as the culprit actually. I have noted that if I end its session, I can get FSX back to running. Could this also be FSUIPC, though? Paul, I have read of some who actually preferred AS 6.5 over ASX. Since I already had it...just thought to use it. Like I said, it works perfectly until the freeze happens. You mean the UIAuto one, right? I have that in my root folder as well. I would hate to buy ASX and find out it was not the root cause. Also, AS 6.5 works like a bear with FS9 of which is was written for, so that cancels out my system as a low-level fault. No, it's something around the coding with FSX OR...and a large 'or'..it could be something that was downloaded from the M.S. Update bound for W7. Needle in the haystack sort of thing. I know that I am not alone with this particular FSX PITA. Too bad they didn't have the iron-clad written efund policy that Flight1 Ltd has. It would help in a situation like this.Thanks for the input.Mitch

Mitch, after briefly reading thru this post I had been wondering the same thing as Paul, why were you on AS 6.5? Although I dont have as new a system as you and I am still on Win XP 32bit, I started using ASA (ActiveSkyAdvanced) and now am running ASE (ActiveSkyEvolution). I had never tried AS 6.5 on my FSX system or ASX, however running ASA and now ASE I have never had these freezes when the weather engine updates. I am running ASE on another computer and have it networked to my flight sim computer so that maybe one reason. Typically when using ASE or previously ASA, I am flying the LDS 767 or CaptSim 727, with AI at 100% and most of my scenery settings at or near max, and have never had any freeze issues or performance issues like you mention, and I have antique hardware.I agree that its too bad you cant buy ASE/ASA thru Flight1 with the refund policy, but considering how much you have already spent, maybe another few dollars to try ASE might not be a bad idea. I cant see how with all its new features and improvements you wouldn't like it more than AS 6.5 anyway.Edit: Didn't see your last post while I was writting mine. Hope that in your latest post you got it figured out.