CTDs in FSX - PMDG 737NGX & Win 7 system files

[richjb2 195]

I would like to request assistance from the Forum in resolving CTDs events that I have been experiencing with FSX and PMDG’s B737NGX SP1. I have filed a support ticket with PMDG (Ticket Number 19F-16516662-9243) and they assisting me with the issue.Most recently, I have experienced numerous CTDs that were reported as follows:Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3Faulting module name: PMDG_737NGX.DLL, version: 1.0.0.0, time stamp: 0x4eaa4addException code: 0xc0000005Fault offset: 0x0005ad70Faulting process id: 0x2710Faulting application start time: 0x01cca0d967a0be8aFaulting application path: D:\FSX\fsx.exeFaulting module path: D:\FSX\GAUGES\PMDG_737NGX.DLLReport Id: f02e61f1-0ccc-11e1-89ea-f46d0457f6d1In the FSX\GAUGES folder, I have three related to PMDG:PMDG_737NGX.DLL - 92.5 MBPMDG_737NGX.DLL_2 - 4.3 MBPMDG_737NGX.DLL_3 - 524 KB - kilobytesThe huge size of this file compared to all the other .DLL files in the GAUGES Folder leads to me to believe that this file is corrupt. There is no other file in the GAUGES folder that even approaches this size. The closes is the PMDG_747400_Overhead, which is 9.34 MB.Question #1: Does the size of PMDG_737NGX.DLL indicate a possible corrupted file?MS Event View reported several other CTD events resulting from these Win 7 system files:C:\Windows\syswow64\USER32.dll -- 3 EventsC:\Windows\SysWOW64\ntdll.dll -- 3 EventsC:\Windows\system32\dinput.DLL -- 6 EventsHere are the Event Viewer Reports:Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3Faulting module name: USER32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba59Exception code: 0xc0000005Fault offset: 0x00020d26Faulting process id: 0x2a78Faulting application start time: 0x01cca0e242a063b2Faulting application path: D:\FSX\fsx.exeFaulting module path: C:\Windows\syswow64\USER32.dllReport Id: 17c963d6-0cd8-11e1-89ea-f46d0457f6d1Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3Faulting module name: dinput.DLL, version: 6.1.7600.16385, time stamp: 0x4a5bd9c0Exception code: 0xc0000005Fault offset: 0x00016570Faulting process id: 0xc30Faulting application start time: 0x01cc9bd0422c03e5Faulting application path: D:\FSX\fsx.exeFaulting module path: C:\Windows\system32\dinput.DLLReport Id: 645298fc-07c4-11e1-8472-f46d0457f6d1Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3Faulting module name: ntdll.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba58Exception code: 0xc0000005Fault offset: 0x00033a93Faulting process id: 0x1d6cFaulting application start time: 0x01cc9a867e87ee6fFaulting application path: D:\FSX\fsx.exeFaulting module path: C:\Windows\SysWOW64\ntdll.dllReport Id: 0ab2c352-067a-11e1-b58f-f46d0457f6d1PMDG Product Support reported that these crashes were the result of Windows 7 system files that are unrelated to NGX. A search of this forum did not return anything for the dinput.DLL or the USER32.DLL CTDs. However, the ntdll.dll CTDs were well documented.Concerning the ntdll.dll CTDs, a driver issue was cited as possible cause. Recently, I have been experiencing numerous NVIDA driver failures on my GTX-460 card. An update to driver ver 285.62 did not fix this problem. I wonder if these two are related? Or, is the file size of the PMDG_737NGX.DLL file resulting in FSX memory issues that cause a failure on the ntdll.dll file?Any thoughts on the other two listed CTDs, the USER32.DLL & dinput.DLL?Thank you for your assistance!Best regards,Rich BollWichita, KSSystem Info:Intel I7 2600K 3.4G - No OverclockingASUS P8Z68 Deluxe, Rev 1.xxBIOS: AMI 5/9/2011 ver. 05012 x GSkill F-1700CL9-4GBXLD 4096 MB 800 MHzGeForce GTX 4600 - Driver 285.62Cool Master CaseNoctura Monster CPU cooler (the big one!)

[Guest jahman]

If you suspect a file is corrupted, you can always re-download from PMDG and compare the two installers.In any case you would improve your chances for assitance by re-posting in the PMDG 737-NGX forum here.Cheers,- jahman.

[Guest firehawk44]

The Exception Code 0xc0000005 indicates you had Memory Access Violation while the faulting .dll. I would run Windows Memory Diagnostic that comes with Windows 7 first and make sure there are no problems with the installed memory. You can always repair PMDG installations by double-clicking on the program and then selecting the repair option. Most of your crashes were caused by system files not belonging to FSX, including NTDLL.dll. Your installation of the PMDG product may be corrupted too. For instance, you installed FSX on D drive and not the default (x86). Perhaps FSX is calling a file and the system registry has the file located in another location on your hard drive. If it cannot find it, crash! I realize that PMDG gives you the option to show where FSX is located but maybe that got somehow corrupted. Make sure any anti-virus and UAC is disabled when reinstalling/repairing.Best regards,Jim