July 1, 20169 yr Hi Folks, I am experiencing a similar situiation. Computer hardware: Alienware X51, brand-new, 4790K overclock This CTD occurred while using PMDG 777 in cruise at 4x acceleration (I don't use time acceleration frequently) Also has occurred yesterday while using the 737NG Log Name: Application Source: Application Error Date: 7/1/2016 5:53:09 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: baffroom Description: Faulting application name: Prepar3D.exe, version: 3.3.5.17625, time stamp: 0x5758bb31 Faulting module name: ntdll.dll, version: 10.0.10586.306, time stamp: 0x571afb7f Exception code: 0xc0000374 Fault offset: 0x000dc7c9 Faulting process id: 0x820 Faulting application start time: 0x01d1d3dbfab63628 Faulting application path: C:\Prepar3d v3\Prepar3D.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: 54e14ac6-9c61-4d39-8899-57543d4a8fd9 Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2016-07-01T21:53:09.287759300Z" /> <EventRecordID>43084</EventRecordID> <Channel>Application</Channel> <Computer>baffroom</Computer> <Security /> </System> <EventData> <Data>Prepar3D.exe</Data> <Data>3.3.5.17625</Data> <Data>5758bb31</Data> <Data>ntdll.dll</Data> <Data>10.0.10586.306</Data> <Data>571afb7f</Data> <Data>c0000374</Data> <Data>000dc7c9</Data> <Data>820</Data> <Data>01d1d3dbfab63628</Data> <Data>C:\Prepar3d v3\Prepar3D.exe</Data> <Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data> <Data>54e14ac6-9c61-4d39-8899-57543d4a8fd9</Data> <Data> </Data> <Data> </Data> </EventData> </Event> Thanks, George
July 2, 20169 yr Also has occurred yesterday while using the 737NG I split your post from the other topic as it is difficult to figure out who's who and systems and things done to try to fix it. The OP of that topic had a module that was unknown. Your faulting module is known. I suspect you have checked out the AVSIM CTD Guide (link in my signature) and looked at the probable fixes for an ntdll.dll error. One other possibility that has fixed the ntdll.dll error for many is to rename the MyTrafficmil.bgl as this causes crashes for some (so far it has not for me). Just rename it to MyTrafficmil.bgl.off or .orig. If you do not own MyTraffic Professional 6a, then disregard. If you do own MyTraffic Pro, I would disable MyTraffic in the scenery.cfg. You will not have AI but you want to see if the crashes continue without it loading. If the crashes continue, then it is something else. The ntdll.dll is a system file and does not belong to the P3D or FSX installations. The exception code 0xc0000374 indicates a "heap corruption". It is a common crash and it usually involves high settings or a bad overclock. If your cpu voltages are off just one point, a crash will occur with the ntdll.dll shown as the faulting module. Hope this helps. Best regards, Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
Create an account or sign in to comment