Hello all,

 

I hope there is a guru amongst you that can shed some light on my recent FSX crashes.

 

I have read the CTD guide here and it would appear the ntdll.dll is the cause of my issues.

 

One of the causes mentions MyTraffic 5.4C, which I'm running but I'm keen to find out how I can roll back to version 5.4b without a complete MyTraffic uninstall.

 

So far I have removed the UIAutomationCore.dll and it made no difference.

I've updated FSUIPC to 4.297a as I also had a g3d.dll error right on the back of an earlier ntdll.dll error. No difference there, either.

I've checked the dll.xml but cannot find any old or duplicate entries.

 

Short of a complete re install, or a maybe a roll back to MyTraffic 5.4b (if someone could explain how to do that) I'm out of ideas.

 

Here's the event viewer log:

 

Log Name:      Application
Source:        Application Error
Date:          08/01/2014 11:59:52
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Stu-PC
Description:
Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3
Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521ea8e7
Exception code: 0xc0000005
Fault offset: 0x0002e41b
Faulting process id: 0x1b5c
Faulting application start time: 0x01cf0c62b0d86412
Faulting application path: D:\AAA_FSX\fsx.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 616cdb4b-785c-11e3-8977-10bf4888f551
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="2014-01-08T11:59:52.000000000Z" />
    <EventRecordID>14478</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Stu-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>fsx.exe</Data>
    <Data>10.0.61472.0</Data>
    <Data>475e17d3</Data>
    <Data>ntdll.dll</Data>
    <Data>6.1.7601.18247</Data>
    <Data>521ea8e7</Data>
    <Data>c0000005</Data>
    <Data>0002e41b</Data>
    <Data>1b5c</Data>
    <Data>01cf0c62b0d86412</Data>
    <Data>D:\AAA_FSX\fsx.exe</Data>
    <Data>C:\Windows\SysWOW64\ntdll.dll</Data>
    <Data>616cdb4b-785c-11e3-8977-10bf4888f551</Data>
  </EventData>
</Event>

 

I look forward to your answers.

 

Thanks

 

Stu

 

 

 

Short of a complete re install, or a maybe a roll back to MyTraffic 5.4b

 

The problem with MyTrafficX crashing all the time with the latest version has been fixed.  A fix is on the MyTrafficX website.  As I recall it was one of the schedules that was causing the ntdll.dll errors.  When I rolled MyTrafficX back I simply clicked on uninstall 5.4c in the Add/Remove programs.  If you did not employ this fix though, then this is probably your problem.  I recently had several ntdll.dll CTD's and I reset my OC back to Optimized Defaults and so far no CTD's.  I think it was one of the CPU C States settings.  C States are normally disabled for overclocking but I followed the advice of NickN (we have the same Haswell setup) and the periodic ntdll.dll crashes started. 

 

Best regards,

Thanks for your input, Jim.

 

I ended up doing a full re-install of MyTraffic to 5.4b.

 

The ntdll.dll crash seems to be fixed now.

 

I will look for the fix that you mention and get 5.4c back up and running.

 

I feel happy I now know the cause and do something about it.

 

Cheers

 

Stu

Well, I reinstalled 5.4C and the patches Burkhard had done to fix the ntdll.dll crash.

 

It didn't work for me, and, as it seems, didn't work for a few other folks on the forums.

 

A guy with similar issues to mine had adjusted the MyTraffic schedules back to 2012 and this had cured it.

 

I have to say it worked for me, too.

 

So, anyone else with this MyTraffic issue, the patches may or may not work, but adjusting the schedules certainly works.

 

Hope this info is of use.

 

Thanks

 

Stu

Thanks Stu for posting your solution.  It's amazing how some "fixes" work for some and not for others.

 

Best regards,