On 10/23/2017 at 11:01 PM, alanmetcalf said:

The heads up is too late for me Ryan, I tried the work round molleh and it made no difference.

The odd thing is my areosoft aircraft works fine and the rest of my PC is good.

No-one can explain what the technical truth is about the issue. 

Regards

Alan Metcalf

 

These are what I've been able to find so far.

Apparently this issue tend to occur when PMDG products tries to create windows or other UI objects, like the banner on top that says "initializing".

In FSX: SE, my 747V3 crashes almost immediately when spawns, DC6 crashed once during flight, maybe that's when it tried to generate a banner.

NGX and 777 works as of now, but I was able to find system logs saying PMDG dlls crashed when exiting FSX normally.

All crashes have application name fsx.exe (of course), however the faulty module of child window error is actually ntdll.dll. Exception are all "0xc0000005" which is access violation.

 

I'm not a Windows platform core engineer and don't have the knowledge or resources to check further, but based on what I know, the below causes are possible.

1: Someone broke certain Windows APIs that handle UI objects in 1709 and new fixes are coming.

2: FSX or PMDG frameworks have been using the APIs improperly, In 1709 the APIs were updated and will crash when they are called the old way. In this case 3rd party software developers have to update their software, or if the issue is "breaking" a lot of software although it is not MS's fault, MS may actually "unfix" the API just to make everything work again.

Tom Chai

 Thanks Tom, very clearly explained.

You can disable/ postpone updates on w10 home by a regedit changing your internet connection to metered.

So far MS is not actually taking the money out of your wallet without permission. So far.

Hi my system Specs are 

Windows 10 X64 pro 1709 with all updates installed, FSX SE, REX Essentials plus Overdrive for environment textures, ORBX GLOBAL,VECTOR, EUROPE, various Airports, EFASS

I have the same problems. PMDG 737 NGX and Aerosoft  A32X. My add-ons RAAS, AS16, GSX work perfectly in flight, but

1) You cannot access the FSX menus while in flight, FSX will Crash.

2) Exiting FSX will throw various error messages and will try to Restart

3) Very interesting is the % of CPU that windows defender uses (Anti malware Service)

 

The conclusion is that you can fly as long as you don't mess with FSX menus after you have loaded PMDG or Aerosoft planes. It is very annoying but this works for me.

Regards

PS

Some say it's Microsoft's OneCore Project that cause it.

Hello all

For those that fully understand this stuff, me not being one of them.

 One of many examples I have when I click on any panel on the 737. 

 Problem signature
Problem Event Name:    APPCRASH
Application Name:    fsx.exe
Application Version:    10.0.62615.0
Application Timestamp:    559f9a9a
Fault Module Name:    PMDG_737NGX_2.dll
Fault Module Version:    11.14.0.0
Fault Module Timestamp:    572b6e57
Exception Code:    c0000005
Exception Offset:    00002689
OS Version:    10.0.16299.2.0.0.256.48
Locale ID:    2057
Additional Information 1:    2beb
Additional Information 2:    2beba6fb4680d73a8c78ca7c24ccdb46
Additional Information 3:    3ad0
Additional Information 4:    3ad0e9f4486e91d86927e4a71227ee49

Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: PMDG_737NGX_2.dll, version: 11.14.0.0, time stamp: 0x572b6e57
Exception code: 0xc0000005
Fault offset: 0x00002689
Faulting process ID: 0xf84
Faulting application start time: 0x01d34fc05dd558cf
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\FSX\Gauges\PMDG_737NGX_2.dll
Report ID: c852a2ce-02ae-477e-a972-8cf8f9ecd81b
Faulting package full name: 
Faulting package-relative application ID: 
 

Does anyone have any estimate on the OS fix date.

My sincere thanks to all the PMDG support team who have been working on this problem.

20 minutes ago, alanmetcalf said:

Does anyone have any estimate on the OS fix date.

Wasn't it scheduled for sometime mid-november?

Hi Alan, have you tried other airplanes? Aerosoft, FSX airplanes? Have you Check any updates regarding the Graphics Card? UAC settings? Set all simulation Software as trusted in windows defender Menu?

Regards.

Hello Dio

 

Thanks for asking, and yes done all of the above checks. 

 

My PMDG shipment all went to the maintenance hangar since the last Windows 10 update (kb4041676) except for the JS4100 and the DC6.   That includes the 747, the 777 and the NGX.  I uninstalled the "culprit" update and switched on the option to prohibit updates for at least a month.  So far it worked like a charm.  I tested all three of the affected aircraft and they all loaded.  Tested the NGX on a trip from FAPE to FALE with no problems at all.

Hermann Kühne 

Dear Hermann

I am glad you have a  solution that's good for you.

I am fully aware that rolling back is the temp cure. But sooner or later users will want to move forward.

Because I have never had a need to roll back, be it on a temp basis,  I have been used to deleting the old windows files to save space on my SSD.

Also my backup strategy has not included saving a system image. If I have major problems I do a rebuild. 

So, my personal options are to rebuild windows 10, using my pre update usb  media, or wait for the os fix.

I choose to wait at this time.

15 hours ago, alanmetcalf said:

Dear Hermann

I am glad you have a  solution that's good for you.

I am fully aware that rolling back is the temp cure. But sooner or later users will want to move forward.

Because I have never had a need to roll back, be it on a temp basis,  I have been used to deleting the old windows files to save space on my SSD.

Also my backup strategy has not included saving a system image. If I have major problems I do a rebuild. 

So, my personal options are to rebuild windows 10, using my pre update usb  media, or wait for the os fix.

I choose to wait at this time.

I do hope, and sincerely believe, PMDG will eventually give us a thumbs up when the Windows problem is solved.  I agree that this is also a temporary solution.  Eventually Windows updates will have to be switched on again.

Sorry but I didn't followed the complete posts.
Is the issue in overall for everyone or does it work for someone?

I did the update but I didn't checked if the products are working or not.

As far as I am aware, it only affects 32bit Flightsim products. It has not affected me with P3D v4 so far. 

 

7 minutes ago, Jude Bradley said:

As far as I am aware, it only affects 32bit Flightsim products. It has not affected me with P3D v4 so far. 

 

That's not true. V4 has been affected as well, not necessary the win update but mostly the October KB updates MS released

Hi to all of you, Has any one tried PMDG without any add-ons? Just FSX and the PMDG 737 NGX for example?