CTDs After Upgrading to Windows 10!

[Flaps30]

Hi,

Please help!

FSX has been working fine for me for years with Win 7-64 bit.  After all the popups encouraging me to upgrade to Win 10 I finally took the bait and installed Windows 10.  While going through the walkaround with A2As Cessna 172 which was never a problem before, I had 2 CTDs and a  "Flight Sim has stopped working" freeze. I have several ORBX sceneries along with Global, Vector, and Open LC Canada.   Again I have not had a problem before.  Also, I have plenty of Ram and HD space available.   Any ideas?  Thanks.    Tom

[Bobsk8]

I downloaded GWX control panel awhile back and got rid of those ** Windows popups. My Windows 7 works fine, and I am  not going to fix what isn't broken. 

 

http://www.majorgeeks.com/files/details/gwx_control_panel.html

[Jude Bradley]

Any event viewer clues? (start ->Run -> eventvwr

[VeryBumpy]

Welcome to the club. Windows10 is proving to be much more unstable for me also. Many various FSX errors on exiting, total CTD once and a while, and not as addon friendly. These never occurred in my Vista64 install.

 

Here's hoping Windows updates will improve on these.

[Cat_Dad]

This problem is similar to what I am currently experiencing.

 

I currently only have FSX Deluxe Edition which ran perfectly in Windows 7 Pro 64 bit.  update to Win 10 on Leap day last month and since I cannot move the aircraft from one location to another without halting the program and forcing back to the desk top. This was not a "Clean" install.

 

I have tried the following steps to try and trouble shoot what might be causing the halts. They are the following:

 

Removed and reinstalled FSX.

 

Moved FSX from it's own SSD to the C drive SSD where Win 10 is. No Change

 

Removed the current NVIDA drivers 362.0 and rolled back to 361.45 (last known Win 7 driver prior to Win 10)

 

Completely removed all NVIDA drivers to see if they were the problem. Answer was still no good

 

Turned off just about every Window 10 setting i.e talking computer, send M/S info on what you are doing, etc

 

Turned off/turn down FSX settings in program and on the NVIDA Inspector to conserve computer memory/resource.

 

My system is a Intel i7 4790 with 16Gb DDR3 and NVIDA GTX 980. Two Samsung 250 Gb SSDs

 

Reset the FSX config back to default.  Still no good

 

Installed the standard FSX cong updates i.e. highmemfix=1, widescreen=true etc. Nothing radical

 

Supposedly, DX9.0Cc which was current when FSX came out is supposed to be part of the current DX 12 in Windows 10. I wonder if that has any bearing on this problem?

 

Still cannot move the aircraft from one airport to another.  (ABQ to PHX or ORD or etc)I can however "FLY" as much as I would like and go anywhere that way with "Zero" problems even at my normal or higher program settings. Can load the "Canned flights/mission OK but lost audio/ATC/cockpit voice instructions

 

Every thing seems to lead to "WINDOW 10" and what is is doing to the FSX program.

 

​You would think that two Microsoft programs would work with each other.

 

Hopefully this will help others out there to try and figure out what is causing our FSX programs to come to a grinding halt.

 

Terry

[Jim Young]

The problem with upgrading to a new OS is that there are several bugs in much of the hardware.  Hardware manufacturers haven't updated all of their products to the new OS yet so many will suffer crashes until the products are updated.  So, what you are experiencing are timeouts from a USB connection or a throttle or a mouse or any other HID device.  It could also be a problem with other hardware connected to your system.  A USB port.  Your SSD or your HDD.  Nothing wrong with FSX as many have successfully upgraded and have no problems.  I would recommend running a driver updater.  I use driver booster which is freeware but has nags for you to buy the product.  It will still scan your system and download and install updated device drivers though.  Windows Update mostly updates the OS when bugs are discovered.  Your problem is likely your hardware.

 

Best regards,

[vc10man]

Spot-on, Jim. I've lost count the number of times I have had to re-install the driver for my USB MSFF2 joystick. Apparently that is one of the current bugs with Windows 10 and nobody from MS has fixed it as yet. They are more interested in pushing out adverts to garner revenues for their 'free offer' ala Google with their Androids, Facebook, etc., or removing software like CPU-Z they don't like.

[Cat_Dad]

Thanks Jim for the info on the driver updates. Yes my drivers (12 of them) needed updates as the computer is only 3 months old and local shop built. Sad to say they did absolutely nothing to  correct my problem of not being able to go to a different airport without flying to it.

 

I would think that should rule out input/output devices such as keyboard/mouse/stick as they are all in use when flying and do not seem to have any problems then  The problem is when FSX sends the aircraft to the new destination. All is OK for about 5 to 10 seconds and then it freezes up and only way to clear it is to stop the program back to the desktop.

 

This never happened up XP and 7 pro, only under win 10.z

 

Sure is sad when Microsoft sends out bug laden products. The old saying that you get what you paid for is definitively true here. The only thing worse would paying for it.

 

Terry

 

PS:

So far knock on wood, none of other programs on the computer are acting up over the window 10 update.

PPS:

 

The aircraft arrives at the new destination airport and all of the scenery appears to load just fine. Then after a few seconds, I get the message that the program is not working correctly and windows will close.

 

Almost sounds like maybe it is a virus but nothing is detected thru my antivirus program (Kaspersky) which was on the computer prior to the window 10 upgrade.

[vc10man]

Cat_Dad

 

Is it FSX closing or Windows itself closing  error you get?  If it is just FSX, then that's where the issue lays, not with Windows 10. If it is Windows 10, then if you can get the data from EventVwr, look for what Faulting Module is causing the crash. Post that image here and maybe we can delve deeper.

 

As regards you local shop that built your system, I think it is a tad unfair slating them for a simulation software they have no direct control over. They only built your hardware and maybe installed the OS.

[rlgoodson]

Does it still crash after a clean boot?  I had a similar problem after upgrading to Windows 7 64 bit and found that if I open it with a clean boot it works fine.  Not sure about Windows 10.  Also, kudos to the people who put together the Avsim CTD guide.  Helpful ideas.

[VeryBumpy]

Does it still crash after a clean boot? 

 

What do you mean by this?

[rlgoodson]

If you go into msconfig and have the system do a Selective Startup and have it start without the startup items loading.  Helped a lot for me.

[fppilot]

What do you mean by this?

 

https://www.google.com/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=what%20is%20a%20clean%20boot%20in%20windows

 

If the link does not work then just Google Clean Boot into Windows.  I had issues with my previous Windows 7 computer after I purchased it in 2011 until I swapped out the Radeon vid card that came in it for an Nvidia card.  The way I got around the issue before upgrading the card was to establish a new Windows User, and configure the settings for that User so that a bare minimum of background programs/utilities loaded on startup.  Then to fly I would reboot into that User account.

 

I have a fresh new system with Windows 10 from day one and the only issues I have had were waiting for Saitek to update its Pro Flight drivers.

[Guest Raven9000]

Welcome to the club. Windows10 is proving to be much more unstable for me also. Many various FSX errors on exiting, total CTD once and a while, and not as addon friendly. These never occurred in my Vista64 install.

 

Here's hoping Windows updates will improve on these.

Are you seriously comparing windows 10 to Vista (one of the agreed WORST operating systems of all time, ever?) okay buddy...

[VeryBumpy]

Are you seriously comparing windows 10 to Vista (one of the agreed WORST operating systems of all time, ever?) okay buddy...

 

Absolutely. My experience so far is Win10 is a worse experience than Vista64 in regards to stability and compatibility with games.

 

Working with the OS itself, I like Win10 better.