I randomly get this error. How can i fix this please?

 

It happens when I'm at the gate doing pre-flight startup on the PMDg 737.

 

Description:
Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b8f
Exception code: 0xc0000374
Fault offset: 0x000ce6c3
Faulting process id: 0x43b0
Faulting application start time: 0x01cdfefa08b398b1
Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 6beca4d9-6af0-11e2-a4cb-a56b3cc5ef10

Exception code 0xc0000374 means Status_Heap_Corruption. NTDLL is a system dll related to memory. I think something in your fsx setup is corrupted, maybe a recent addon. Does it happen with the default 737? Perhaps there was a problem installing the PMDG 737. You might uninstall/reinstall this aircraft. Do you have GSX installed and does it occur when you enable this program? You might download and run the latest Standalone Addon Manager. Heap corruptions are difficult to find the offending program as it could be a printer driver or something wrong with the print spool. Others have had the problem with Microsoft Office programs. You can try restoring your system to a date before this crash began to happen and see if that fixes the problem. Also, make sure you have your Microsoft Visual 2005 w/SP1 and the files as described in the following link installed - http://support.microsoft.com/kb/2538242. This version of the 2005 MSV can only be updated through a Windows Update. Just be aware there is no magic/silver bullet to fix this problem.

 

Best regards,

Jim

Thanks Ill have a look.

 

Got another error today:

 

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

Faulting module name: API.DLL, version: 10.0.61637.0, time stamp: 0x46fadb58

Exception code: 0xc0000005

Fault offset: 0x000230b3

Faulting process id: 0x5dc0

Faulting application start time: 0x01cdff9a4d61bf50

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\API.DLL

Report Id: 631ae945-6bb6-11e2-a4cb-a56b3cc5ef10

i recently have the ntdll.dll error, when using the pmdg 747. after a thousand searches, and a thousand things done, i discovered that the error was because the fspassengers dll. So i made a reinstall (of fspassengers), and it's all fine since then! i suggest a reinstall of your 737, or another addon you use with 737

I use REX, EFB and FS2Crew. i was looking at Task manager as saw the RAM being used at around 7GB out of 9GB. FSX uses 1.5Gb itself. Maybe I need more RAM?

Who overclocked your video card? This could be your problem. Is there a setting where you can bring the OC back to the default? Overclocking a video card is difficult.

 

I use REX, EFB and FS2Crew. i was looking at Task manager as saw the RAM being used at around 7GB out of 9GB. FSX uses 1.5Gb itself. Maybe I need more RAM?

 

FSX can only 'see' up to 4GB. That's it. No more. The rest of your memory is used for Windows functions and things to keep your computer running. You might want to check what's running in the background by looking at the processes. You may have a memory leak somewhere with one of your applications.

 

After reading the OP and the rest of the post, I would say you have your sliders in FSX set too high and/or your display driver settings. The API.dll error has also been known to be caused by overclocking, overheating, or bad memory configurations.

 

Best regards,

Jim

Thanks for the tips Jim the card was factory oced by Sapphire. I will reduce the FSX sliders when I get home and have a test this weekend.

Who overclocked your video card? This could be your problem. Is there a setting where you can bring the OC back to the default? Overclocking a video card is difficult.

 

 

 

FSX can only 'see' up to 4GB. That's it. No more. The rest of your memory is used for Windows functions and things to keep your computer running. You might want to check what's running in the background by looking at the processes. You may have a memory leak somewhere with one of your applications.

 

After reading the OP and the rest of the post, I would say you have your sliders in FSX set too high and/or your display driver settings. The API.dll error has also been known to be caused by overclocking, overheating, or bad memory configurations.

 

Best regards,

Jim

would having the latest fsuipc fix the ndtl errors since it fixes some of the ctds that users seem to be having but not to sure about the ndtll which are difficult to track down, and i noticed the op has fsx in the prog(86) folder which some people say causes more problems that having it in it own root drive eg C: fsx etc?

would having the latest fsuipc fix the ndtl errors since it fixes some of the ctds that users seem to be having but not to sure about the ndtll which are difficult to track down, and i noticed the op has fsx in the prog(86) folder which some people say causes more problems that having it in it own root drive eg C: fsx etc?

 

No. The FSUIPC only fixes certain instances (not all) of the g3d.dll error. I have my installation setup in the default fsx folder (C:\Program Files (x86)) and have never had a problem so I can't comment on whether this would be a fix or not. The OP is having issues relating to memory and think those would occur no matter what folder FSX is located in. There are a lot of members posting here who are receiving crashes even though FSX is installed in an outside folder like C:\FSX. Like the uiautomationcore.dll fix many people use, it works for some but not for others. I think that if the OP decides to uninstall/reinstall FSX, he should maybe think about installing it in C:\FSX or another non-default folder. May work. Thanks for your comments and help.

 

Best regards,

Jim