I recently started to have FSX (boxed) CTDs -  usually DINTUP8.dll but also BEX/Stackhash - and after consulting the excellent Asim CTD guide I isolated the problem to fsuipc and my Saitek USB throttle quadrant.  If I disable fsuipc the crashes stop. Alternatively if I just disconnect the the USB Saitek throttle quadrant the crashes stop.  If I have both the USB throttle quadrant and fsuipc connected I get a crash from 5 min to 30 mins after starting FSX.  No errors when I run dxdiag and nothing useful in the fsuipc logs just a "sim stopped" entry.  As I have two Saitek throttle quadrants (including the one that came with my Saitek yoke) set up for twin engine operations I could just live with the one quadrant but would rather not and alternatively being without fsuipc is a hassle. I have tried different usb ports for the quadrant with no joy.  I also ran tests with an FSX backup install that I hadn't used for some months but got the same CTDs. I could just purchase another Saitek throttle as the one I have was working fine for the 14 months I have had it but I'm not sure this would fix the problem.  Grateful for any other suggestions.  Thank you.

 

Bruceb

 

 

Hi Bruce,

 

Did you use any Driver Updater to update the sys bus, the USB ports, etc., as suggested in the AVSIM CTD Guide, page 15?  Also, making sure you checked your system for corrupted files as suggestion on Page 14.  And fsuipc.dll is up-to-date for FSX.

 

I doubt there is a problem with your Saitek throttle.  I have never heard of BEX/StackHash crashes caused by throttles.  BEX/StackHashes crashes involves memory  (not OOM's or lack of VAS).  Usually the ntdll.dll error gets involved.  You could try fixing any issues with Windows by running this freeware program called Windows Repair located at http://www.tweaking.com/content/page/windows_repair_all_in_one.html.  It was developed by Microsoft techs and one of the best tools I have seen for a long time.  It will not do anything to mess up fsx but it is basically a reset of your Windows (without using system restore or reinstalling Windows).  It backs everything up first.  It's amazing how much systems can get corrupted because of Windows and the system registry.  As you stated, it use to work great for 14 months and then something went amiss. 

 

As far as the dinput8.dll error, the following topic might help as it sounds familiar with your issue - http://www.avsim.com/topic/436185-dinput8dll-crash-fsx/.

 

Best regards,

Jim

Thanks Jim

 

I am pleased to report that the windows repair utility seems to have done the trick.  Having put this tweaking software through it paces FSX with fsuipc and the Saitek quadrant enbabled has been running for over 4 hours with no crashes.  So hopefully this is a long term fix.  Thanks again.

 

Bruceb

Glad you got it working again.  That tweaking.com repair utility is a slick program!

 

Best regards,

Jim

An update on this.  Unfortunately after returning from a month away the error as per my OP returned.  I redid the windows tweaking repair but this time no joy. Then after re reading some of the linked threads I deleted Gigabyte OC Guru II which I no longer use and this seems to have done the trick.  I have had a week now with no dinput8.dll error errors.  This utility has been on my system since it was built 3 years ago so why it should start causing problems now is a mystery - but possibly because I recently replaced my Gigabyte 770 GPU for an AUSUS 980ti STRIX.  However it did work fine for a couple of months after I made the change.

 

Bruceb

I was having a similar issue which I seemed to have fixed by Removing all of my Nvidia Drivers and doing a clean install of them.  I spent four days chasing the issue.  Hopes this helps/