Jump to content

GhiomKL

Members
  • Content Count

    37
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    IVAO
  1. thank you all for your suggestions. Uninstalled all FS Dream team sceneries and working again. pffwew...
  2. My FS9.1 under Win 7 has been working for ... years. Today, wanted to fire it, and I got the "Microsoft has stopped working" with the following details: Problem signature: Problem Event Name: APPCRASH Application Name: fs9.exe Application Version: 9.1.0.40901 Application Timestamp: 4135a208 Fault Module Name: StackHash_402a Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Code: c0000005 Exception Offset: 00000000 OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Additional Information 1: 402a Additional Information 2: 402ae66697f3c7c252f2b62e81016a2c Additional Information 3: 6a56 Additional Information 4: 6a564d47c9d9dc4d34a2666d02875f6d I close the program and I get the same message with these details: Problem signature: Problem Event Name: APPCRASH Application Name: fs9.exe Application Version: 9.1.0.40901 Application Timestamp: 4135a208 Fault Module Name: StackHash_ef1f Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Code: c0000005 Exception Offset: 74facb49 OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Additional Information 1: ef1f Additional Information 2: ef1f787c5664fac2bff7e410e1cf4f40 Additional Information 3: 8f9f Additional Information 4: 8f9f202d6061339f3526e904f0df3676 then it's closed for good. I tried to let it redo the fs9.cfg, use the default scenery.cfg but no success. also turn on DEP except fs9.exe. Process Monitor gives that just before the crash happens: 5:48:10.4706509 PM fs9.exe 7060 Thread Exit SUCCESS Thread ID: 5000, User Time: 0.0000000, Kernel Time: 0.0156001 5:48:10.4708263 PM fs9.exe 7060 Thread Exit SUCCESS Thread ID: 1144, User Time: 0.0000000, Kernel Time: 0.0000000 5:48:11.1030648 PM fs9.exe 7060 Thread Create SUCCESS Thread ID: 7080 5:48:11.1043235 PM fs9.exe 7060 Load Image C:\ProgramData\eSellerate\eSellerateEngine.dll SUCCESS Image Base: 0xa270000, Image Size: 0x5b000 5:48:11.1054777 PM fs9.exe 7060 Load Image C:\ProgramData\eSellerate\eSellerateEngine.dll SUCCESS Image Base: 0xa270000, Image Size: 0x5b000 5:48:11.1645238 PM fs9.exe 7060 Load Image C:\ProgramData\eSellerate\eSellerateEngine.dll SUCCESS Image Base: 0xa270000, Image Size: 0x5b000 5:48:11.1725238 PM fs9.exe 7060 Load Image C:\ProgramData\eSellerate\eSellerateEngine.dll SUCCESS Image Base: 0xa270000, Image Size: 0x5b000 5:48:11.1756290 PM fs9.exe 7060 Load Image C:\ProgramData\eSellerate\eSellerateEngine.dll SUCCESS Image Base: 0xa270000, Image Size: 0x5b000 5:48:11.1834642 PM fs9.exe 7060 Load Image C:\ProgramData\eSellerate\eSellerateEngine.dll SUCCESS Image Base: 0xa270000, Image Size: 0x5b000 5:48:11.1860630 PM fs9.exe 7060 Load Image C:\ProgramData\eSellerate\eSellerateEngine.dll SUCCESS Image Base: 0xa270000, Image Size: 0x5b000 5:48:11.1941273 PM fs9.exe 7060 Load Image C:\ProgramData\eSellerate\eSellerateEngine.dll SUCCESS Image Base: 0xa270000, Image Size: 0x5b000 5:48:11.1967293 PM fs9.exe 7060 Load Image C:\ProgramData\eSellerate\eSellerateEngine.dll SUCCESS Image Base: 0xa270000, Image Size: 0x5b000 5:48:11.2046276 PM fs9.exe 7060 Load Image C:\ProgramData\eSellerate\eSellerateEngine.dll SUCCESS Image Base: 0xa270000, Image Size: 0x5b000 5:48:11.2079294 PM fs9.exe 7060 Load Image C:\ProgramData\eSellerate\eSellerateEngine.dll SUCCESS Image Base: 0xa270000, Image Size: 0x5b000 5:48:11.2163431 PM fs9.exe 7060 Load Image C:\ProgramData\eSellerate\eSellerateEngine.dll SUCCESS Image Base: 0xa270000, Image Size: 0x5b000 5:48:11.2190886 PM fs9.exe 7060 Load Image C:\ProgramData\eSellerate\eSellerateEngine.dll SUCCESS Image Base: 0xa270000, Image Size: 0x5b000 5:48:11.2285077 PM fs9.exe 7060 Load Image C:\ProgramData\eSellerate\eSellerateEngine.dll SUCCESS Image Base: 0xa270000, Image Size: 0x5b000 5:48:11.2312847 PM fs9.exe 7060 Load Image C:\ProgramData\eSellerate\eSellerateEngine.dll SUCCESS Image Base: 0xa270000, Image Size: 0x5b000 5:48:11.2391106 PM fs9.exe 7060 Load Image C:\ProgramData\eSellerate\eSellerateEngine.dll SUCCESS Image Base: 0xa270000, Image Size: 0x5b000 Tried to delete esellerateengine.dll but it says that the dll is missing and then crashes the same way. how can I dismiss that it's not a hardware issue? the only thing I can remember is that the day before I experienced an unusual inflight crash with the iFly 737 on downwind to Cloud9 Klax. The faulty dll was unfamiliar (I cleaned the event log so I can't know what it was. It probably had an "8" in it or at least a number. anyone PLEASE !n HELP HELP! Ghiom
  3. You still need to be at 40NM at a set altitude. And after declaring a deviation for turbulence you need to announce that you cleared the area and are back on track. The messages exchanged are also not very realistic when there is obviously no turbulence. my best best is to turn off the volume of RCv4 or if available within the addon (eqv to Q in the sim). ghiom
  4. Does not work. I am thinking I can indeed quiet the controller. Can I do it with a shortcut from RCv4 or I need to use the Windows sound controller? ghiom
  5. Thank you i will try that. What about the hard constraint at 40nm. Is it overriden as well? ghiom
  6. Thanks I guess if the 40mm is a hard constraint there is nothing to be done... I hate to have to be at FL110 at 50nm coming from the South when having to land North and coming off a STAR. i just have to quiet the controller that isn't happy. I certainly do the IAP as soon as I can which is almost always too late.
  7. Having used RCv4 for ever, with the development of RNAV STARs in the US, I am now struggling to fly my STAR respecting the constraints while adhering to unlinked (if not contradictory) RC's instructions. I'd like to know how you guys manage that? too bad there is no option to fly our own STAR like there is to fly the SID. Ghiom
  8. In fact, just tried it, did not like it, deleted it. back to RCv4. thanks for the feedback.
  9. Thanks a lot for this. i am interested in PFE3 because it looks like it lets you fly SiD and STAR while RCv4 only SID. i still fly STARs with RCV4 but I don't comply (exactly) to the ATC constraints which makes it unrealistic. how is PFE3 from that standpoint?
  10. I have been a user of RCv4 for ages. I am considering a switch to PFE3. Any one can chime in to give their opinions of the pros and cons of each (excluding voices). Thank you Ghiom
  11. Was the administrator thing. thanks for your help
  12. Yes. I installed it on a distinct drive. Not C:, not FS9's. Maybe the reason. Won't work for me then since I have no room on my C: drive (win7)... If this is indeed the reason, why would you impose that this huge software (all the wavs) reside on C:???
  13. Installed it yesterday and couldn't connect to FS9. Got a "IPC timed out..." suggesting that FS9 isn't started and therefore FSUIPC can't connect. no help from the PF3 forum or FAQ. any idea? thanks ghiom
×
×
  • Create New...