CTD ntdll.dll exception code 0xc0000374

[Daniel]

Hello! I am new to the forum so thanks in advance to the volunteers that put time solving this issues. I appreciate it.

I am having a crash to desktop occurring with one particular application called Prepar 3d v2.5. This is a flight simulator software developed by Lockhead Martin.
After being using the simulator for some time, if I try to open a pop up window (like going to file...save, or file...load, or any other menu option) I get a crash. This does not happen always, but it tend to happen after having it in use for a while. It would not fail if you do not try to open a pop up windows, and when it fails it will do it with any window, not one in particular.

This only happens with Prepar3D, I do not have crashed with any other app.

This is the description of the crash in event viewer:

Faulting application name: Prepar3D.exe, version: 2.5.12944.0, time stamp: 0x54ee1a39
Faulting module name: ntdll.dll, version: 6.3.9600.17668, time stamp: 0x54c846bb
Exception code: 0xc0000374
Fault offset: 0x000e5934
Faulting process id: 0x32ec
Faulting application start time: 0x01d06e251a5af967
Faulting application path: C:\Prepar3Dv2\Prepar3D.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 5c4256a4-da22-11e4-8256-8c89a502bf7b
Faulting package full name:
Faulting package-relative application ID:

The only hint I have is that this is occurring less often since I configured prepar3d.exe to run as administrator.
I monitor the process with sysinternal's process explorer and I have discarded relations to VAS issues.
I am in a Win8.1 x64 system, MSI GE70 gaming laptop, core i7, 8Gb RAM.

Do you think that taking a dump of this process when failing will give us an insight of what is going on?
Let me know what other info will be needed to further clarify this issue.

Thanks
Dan.

 

[Jared]

I've got hardly any experience with user mode crashes, so now might be the time to see if I can be of help.

First, try to get the process dump, that should be of help.
Although I'm not sure there's much we can do if it's an issue with the application itself, you might need to contact the developers and request a fix, as it's most likely poor programmign techniques on the application's behalf.

The exception code, 0xc0000374, indicates heap corruption, which is why the application crashes. Now what is being corrupted exactly, I'm not sure, maybe we can find out.

 

[Daniel]

Thanks for your reply, Jared.

I suppose yes, this is a problem with app dev. This app was designed for win7 and it works great in it, but is not the case in my 8.1

Will a full dump from process explorer at the time it crashes work? or should I use other method?

Would using compatibility mode or a modified DEP setting help prevent this crashes due to heap corruption?

Thanks,
Dan

 

[x BlueRobot]

Use the dump feature in Process Explorer, and try and get a stack trace leading up to the crash if possible.

 

[Daniel]

Ok. How do I get the stack trace?

 

[Patrick]

Will a full dump from process explorer at the time it crashes work?

About the only way we can tell you what's going on without taking random and likely incorrect guesses.

 

[Daniel]

I have been trying to make the app fail over the weekend without luck. This could be good news, but I do not call it victory yet.
The last modification I did before CTD's stopped was to follow app compatibility instructions in the message center, which enables compatibility mode to windows 8.0 (i have 8.1).
I will probably disable that to try few cycles and make it fail so we can have a clue on what is going on with this app.

thanks all!
Dan