Narrator Posted October 17, 2015 Report Share Posted October 17, 2015 Hi, Phenom100, FSX Crashes after 15-20min every time I fly I bought a new laptop with specifications chosen to help FSX work more smoothly, especially with the Phenom. With my old laptop the Phenom was virtually unflyable. So after getting this laptop a week ago, I have a mixed response. Beautifully smooth to fly, but the it crashes FSX every single flight, 15 to 20 min into the flight. Toshiba Satellite Windows 10 Home ed Intel i7 5500 at 2.4GHz 8GB RAM NVidia GeForce 930M with 2048mb Laptop is just 1 week old FSX Gold with Accelleration pack installed (hence SP2 level) No other add-ons installed yet. I wanted to see the Phenom flying before adding anything else. Settings as follows: 1920 x 1080 x 32 with target frame rate of 24 Global texture res about 75% Antistropic and anti-aliasing Most tick-boxes ticked Scenery and terrain sliders all 50 to 60% Cloud to 100mi (80%) with high detail (70%) Traffic sliders, all 40 to 50% Flight conditions: I start cold and dark, follow the procedures and checklists and end up departing nicely. I either reach my cruise altitude or close to it, before FSX crashes. If I reach alt, then I set cruise speed. There is usually not a lot happening when it crashes. I have tried it in daylight and dark night. I bought this Phenom package 3 years ago. Have there been any patches? I wanted to buy one of the other feelThere Embraers back then, but I worried my old system wouldn't cope with those either. Now that I have a better computer, I want to get this problem sorted then look at the other Embraers. Thank you Link to comment Share on other sites More sharing options...
scoobflight Posted October 17, 2015 Report Share Posted October 17, 2015 Are you flying the same route each time? Link to comment Share on other sites More sharing options...
Narrator Posted October 17, 2015 Author Report Share Posted October 17, 2015 (edited) No.. the first few times I flew the training route from the manual. The next few times I flew VFR, no flight plan, setting direct-to on the GPS, from Melbourne Australia to Adelaide, a couple of times at night, a couple of times in daylight. Same thing happened over both routes. Edit: I just flew the same route (Melb-Adel) with the default 747, without a hitch. Cheers, Andrew Edited October 18, 2015 by Narrator Link to comment Share on other sites More sharing options...
scoobflight Posted October 18, 2015 Report Share Posted October 18, 2015 Are you running FX and/or the female in a compatibility mode? Link to comment Share on other sites More sharing options...
Narrator Posted October 18, 2015 Author Report Share Posted October 18, 2015 Are you running FX and/or the female in a compatibility mode? FX or FSX? Not running FSX in compatibility mode. If I did, which o/s would be best to select? The female? Not sure what you mean. Link to comment Share on other sites More sharing options...
scoobflight Posted October 19, 2015 Report Share Posted October 19, 2015 FX or FSX? Not running FSX in compatibility mode. If I did, which o/s would be best to select? try WinXP as that was what FSX was design to run on. Link to comment Share on other sites More sharing options...
scoobflight Posted October 19, 2015 Report Share Posted October 19, 2015 The female? Not sure what you mean. lol ... the wonders of autocorrect on a 'smart' phone. was suppose to state Phenom. Link to comment Share on other sites More sharing options...
Narrator Posted October 21, 2015 Author Report Share Posted October 21, 2015 Ok, so I did a bit of experimenting. First I ran it under compatibility for XP/SP3. I flew the Phenom for an hour and exited normally. The big problem was the frame rate dropped dramatically. So I tried it under Win 7 compatibility and only flew long enough to see that the frame rate was almost equally bad. Frame rates: Win 10: 23 fps Win XP: 1.4 fps (at worst it was 0.8 and at best it was 2.2) Win 7: 2.4 fps With those frame rates, compatibility is unworkable. :/ Link to comment Share on other sites More sharing options...
scoobflight Posted October 21, 2015 Report Share Posted October 21, 2015 uninstall the Phenom. set the Phenom's install to WinXP, or Win7, mode(s). keep FS in Win10 'mode'. Link to comment Share on other sites More sharing options...
Narrator Posted October 22, 2015 Author Report Share Posted October 22, 2015 I would think that if the package needed compatibility to install, it would fail almost immediately. It flies smoothly and perfectly for quite a while. I will try your advice, just to rule it out. Link to comment Share on other sites More sharing options...
Narrator Posted October 23, 2015 Author Report Share Posted October 23, 2015 Ok... I did as suggested. I uninstalled the Phenom, set the compatibility of the Phenom install package for Win XP/SP3 and then ran the install. It still crashes FSX, but with one small difference - it now flies for 45 min before crashing. I've flown it 3 times, with the same result each time - once in calm weather, and twice with live weather. After the first flight, I restarted the laptop to see if that would help, but it made no difference. Link to comment Share on other sites More sharing options...
Narrator Posted October 24, 2015 Author Report Share Posted October 24, 2015 Thinking back, it may not be that big a difference after all. For testing this time, I started at the duty runway. I still started from cold and dark, but I did not talk with ATC and did not need to taxi. Link to comment Share on other sites More sharing options...
Narrator Posted October 24, 2015 Author Report Share Posted October 24, 2015 I tried a different route today, twice. Same departure airport, different destination. 1st attempt. Cold and dark start at duty runway. Went through procedures and got into the air. Lasted 15 min. 2nd attempt. Stopped antivirus and Malwarebytes. Went into services. Stopped AV related services. Stopped any update service (e.g. Adobe Acrobat update service). Stopped Windows Defender. Then, cold and dark start at duty runway. Went through procedures and got into the air. Lasted 15 min... again. Link to comment Share on other sites More sharing options...
andrea1974 Posted November 9, 2015 Report Share Posted November 9, 2015 Guys.. I have the same problem .. the FS crash after at least 15 min . I read the post above .. but I did not understand if the problem has been solve or not .. Pease can y reply ? Tks andrea Link to comment Share on other sites More sharing options...
Narrator Posted November 10, 2015 Author Report Share Posted November 10, 2015 After identifying other performance issues, I am reinstalling my laptop. (Yes, my new laptop - sigh.) According to Toshiba support, I may not have upgraded from Win8.1 to Win10 correctly. I'll post here and let you know how it goes. Link to comment Share on other sites More sharing options...
Narrator Posted November 10, 2015 Author Report Share Posted November 10, 2015 It's working now! I just flew a perfect flight and logged 1.6 hrs from YMEN to YPAD. The fresh install of Win10 seems to have helped a lot, but I haven't installed Office, Trend AV and other programs that I use, yet. Here are my specs with the previous install, before running FSX: RAM usually around 2.7GB used, peaking to about 4GB (of a total 8GB). Hard drive in use, 90-100% a lot of the time. Here are my specs with the current install, before running FSX, no Office or Trend AV or other programs installed: RAM usually around 1.6GB used, peaking to 3.2GB, but usually remaining low. Hard drive in use, 5 to 20% most of the time. Several suspects for why it didn't work with the original Win10 install: - Win10 not installed properly - Trend AV may have a heavy footprint - Office 2016?? Does it have background things going on? - Other legacy programs even though I run FSX with no other progs running - Something else Last point....... Yay! I have a working Phenom 100!! ;) Link to comment Share on other sites More sharing options...
Narrator Posted November 11, 2015 Author Report Share Posted November 11, 2015 And another perfect flight. 2.7 hrs from YMML to YBBN. I should try somewhere busy next... maybe KORD to KJFK. All considered, I think I'm done here. If it misbehaves in the future, I'll be back. ;) Cheers Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now