Dear all,

 

I am fighting with the CTDP and only one least problem still apears. I recently found that I better run without any overlocking (at least till I install brand new AC power supply). so after cancel the overlock everything now runs smooth and fine (i5, 8GB RAM, GTX660Ti), but form time to time I get CTDP with error of DINPUT8.dll. I search over internet but I didn´t find any solution. At first I thought it is caused by one of my saitek throttle quadrants, so I pluged it off. But wasn´t the right solution. I am using Saitek Yoke and peddals and no other devices are connected via USB except the kaybord and mouse :-)

 

I would really like to fly one evening without this f****** crashes :-(

 

To complete the information, my FSX consists of:

 

EZDOK

REX (only textures)

Active Sky NEXT

FSUIPC registered

 

this happens no matter the plane I am using (I have majestic Dash q400, Coolsky Dc-9 and SibWings An-2).

 

Is there anybody experienced with this problem? Here is the "system error message":

 

 

Version=1

EventType=APPCRASH

EventTime=130379269913214419

ReportType=2

Consent=1

UploadTime=130379269914024465

ReportIdentifier=92ea3221-9f34-11e3-8d7c-94de80a6f5d5

WOW64=1

Response.type=4

Sig[0].Name=Application Name

Sig[0].Value=fsx.exe

Sig[1].Name=Application Version

Sig[1].Value=10.0.61637.0

Sig[2].Name=Application Timestamp

Sig[2].Value=46fadb14

Sig[3].Name=Fault Module Name

Sig[3].Value=DINPUT8.dll

Sig[4].Name=Fault Module Version

Sig[4].Value=6.1.7600.16385

Sig[5].Name=Fault Module Timestamp

Sig[5].Value=4a5bd9c1

Sig[6].Name=Exception Code

Sig[6].Value=c0000005

Sig[7].Name=Exception Offset

Sig[7].Value=000069e0

 

last time when it happens the sim runs and the error message dialog apears over it but the sim remains running until I hit "ok" or what it was there on that dialog...

Try searching again using "fsx DINPUT8.dll error".

Many of the topics seem to refer to a problem with

EZDOK and at least two were cured by unplugging

a USB device.

This is a system file connected to DirectX.  Did you recently reinstall your video card drivers?  You might try reinstalling them or going back to a previous version.  Do not try downloading and running the latest version of DirectX.  It probably won't let you anyway.  You can check your DirectX installation by going to the Run command and type dxdiag.  Check each page for errors.  If no problems good.

 

Make sure the installation of EZDok is not the cause.  I believe you can disable this program via the dll.xml.  Just open up the dll.xml with notepad and change the disabled line from False to True, save and see if that fixes the problem.  If so, then you know what the problem is and you can uninstall/reinstall EZdok. 

 

Make sure you have Windows Update has run recently and checked for updates.

 

You should run a scan of your system for corrupted drivers.  Run sfc /scannow - http://pcsupport.about.com/od/toolsofthetrade/ht/sfc-scannow.htm.  It will scan your system for corrupted files and restore them.  If no problems good.

 

You can try a system restore to the time when this error did not occur.

 

If this does not fix your problem, then download and run AppCrashView - http://www.nirsoft.net/utils/app_crash_view.html as it provides more information.  Copy and paste the results of the latest CTD here.

 

Hope this helps.

 

Best regards,

Thank you all for your thoughts! I didn´t noticed that the installation is in fact very fresh. I don´t have it installed longer than a week. 

Previously I have another throttle quadrant installed and I am using USB hub with shutable ports. I think I will start the testing by pluging the Yoke and peddals directly to the PC (which was something I want to avoid :-)) because beside this I have X-52, Logitech G-25, Club Sport pedalls...and till now all of these were unpluged.

I think I ve got the culprit :-)

Yesterday I tried the DC-9 without any USB devices - only slew and then hours of autopilot flying with all the weather, max. graphic settings, etc. and it was fine, no problem! I also installed last nVidia drivers and I uninstall madcatz saitek programing software. Then i tried again with Yoke, thorttles and peddals turned on. Everything runs OK, until I change settings on one axis in FSUIPC - if I use option "Sednt o FS as normal axis" it gaves me that DINPUT8 error imediately...

I then set all axises to run over FSUIPC "Send direct to FSUIPC calibration"...and from that point I didn´t get any errors! 

Looks like a little mistery for me...I didn´t have much time to test it in and out...I hope I will be able to try during the weekend...

One problem solved..another arise:

 

Název protokolu:Application

Zdroj:         Application Error

Datum:         1.3.2014 23:52:20

ID události:   1000

Kategorie úlohy:(100)

Úroveň:        Chyba

Klíčová slova: Klasické nastavení

Uživatel:      Není k dispozici

Počítač:       Charlee-PC

Popis:

Název chybující aplikace: fsx.exe, verze: 10.0.61637.0, časové razítko: 0x46fadb14

Název chybujícího modulu: unknown, verze: 0.0.0.0, časové razítko: 0x00000000

Kód výjimky: 0xc0000005

Posun chyby: 0x5d001810

ID chybujícího procesu: 0x1af0

Čas spuštění chybující aplikace: 0x01cf359ebb46a28e

Cesta k chybující aplikaci: D:\FSX\fsx.exe

Cesta k chybujícímu modulu: unknown

ID zprávy: 248f95d3-a194-11e3-8b8d-94de80a6f5d5

Kód XML události:

<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-03-01T22:52:20.000000000Z" />

    <EventRecordID>127278</EventRecordID>

    <Channel>Application</Channel>

    <Computer>Charlee-PC</Computer>

    <Security />

  </System>

  <EventData>

    <Data>fsx.exe</Data>

    <Data>10.0.61637.0</Data>

    <Data>46fadb14</Data>

    <Data>unknown</Data>

    <Data>0.0.0.0</Data>

    <Data>00000000</Data>

    <Data>c0000005</Data>

    <Data>5d001810</Data>

    <Data>1af0</Data>

    <Data>01cf359ebb46a28e</Data>

    <Data>D:\FSX\fsx.exe</Data>

    <Data>unknown</Data>

    <Data>248f95d3-a194-11e3-8b8d-94de80a6f5d5</Data>

  </EventData>

</Event>

That looks much like your last error except it did not indicate the faulting module.  You need to look in the AVSIM CTD Guide (see link under Hot Spots to the right of this forum) and take those steps beginning on page 2 (Actions to take after a crash has been encountered).

 

Best regards,

so...now I am 99% sure..I tested in and out with plugin off and on again all devices...and the DINPUT8 error is caused by standalone USB Saitek throttle quadrant...

How about changing the USB port the Saitek throttle is plugged into?  You should also make sure the USB port drivers are up-to-date.

 

Best regards,

I tried it in number of ports including that hub with 7 switchable ports. I am afraid it has some HW problem as sometimes the crash of the sim was in connection with extincioni the LED indicatior on the quadrant.

Make sure your USB drivers are up-to-date.  Mine have been updated several times and I have a new MB.  I use one of those driver update programs as Windows update does not update these drivers.

 

Best regards,

Hi,

 

I bought a new graphiccard yesterday (Gigabyte GTX 780 OC Windforce) and installed the software "Gigabyte OC Guru II" from the support CD.... And get in trouble with exactly the same!!! DINPUT8.dll every time I started FSX or after 2 minutes...

 

Hours of searching, reboots, reinstalling of DX9c, USB driver, and so on...

 

Finally it was just to deinstall this OC Guru program...!!

 

Now everthing is OK again...

 

Cheers Stephan

Thanks for sharing your solution. Hopefully it will help the OP.

 

Best regards,