Windows 10: Windows 10 x64 directinput8 related device compatibility issue

Hello,

I'm trying to troubleshoot a error/crash effecting my system under Windows 10 x64. Reviewing crash dumps and event viewer points towards the use of directinput8 specifically dinput8.dll called by the Immersion Direct Input Effect dll in order to call force feedback effects under multiple applications. From what i gather this issue appears to effect a number of older devices by a number of manufacturers. This problem did not present in Windows 7 x64.


I did come across this information: https://cookieplmonster.github.io/2019/08/02/win10-dinput8-crash/ indicating a bug exists with dinput8.dll I grabbed my Windows 7 x64 dinput8.dll and ported it to Windows 10 x64 but nothing changes.


I note that 32bit programs which utilise the 32-bit dlls under Windows 10x64 work fine, as does both the 32 and 64 bit sample programs FFconst.exe bundled with the DirectX SDK. So the driver/device does work under Windows 10 x64. This video further confirms that the driver works/worked with Win 10x64 as of version 1709 https://www.youtube.com/watch?v=cxeaGz3s5aM


So it looks like something has changed in Windows 10 x64 that has broken software compatibility with a number of programs utilising directinput8. This thread https://gamedev.stackexchange.com/questions/68757/is-idirectinput8finddevice-totally-broken-on-windows-7 indicates that there have not been changes to dinput8.


Grateful for any assistance to understand what is going on here.


See below for crash data...


Event viewer crashlog:


Faulting application name: rundll32.exe_shell32.dll, version: 10.0.18362.1, time stamp: 0x8ceb427f
Faulting module name: SaiQFF04.dll, version: 6.0.4.1, time stamp: 0x46372b3b
Exception code: 0xc0000005
Fault offset: 0x0000000000005a80
Faulting process id: 0x10e0
Faulting application start time: 0x01d5d887c89645ee
Faulting application path: C:\Windows\system32\rundll32.exe
Faulting module path: C:\Windows\system32\SaiQFF04.dll
Report Id: d7b2ec6e-6d54-473c-8a17-cbc7d9f9d1eb
Faulting package full name:
Faulting package-relative application ID:


Application Crash log:


CRASH in:
OS-Version: 6.1.7600 0x300-0x1
DEBUG TIMER: Sim::Sim:16600.330500
LOADING MODEL content/objects3D/cubemap_model.kn5
VERSION=5
Loading 6 textures
TIME TO INIT: 16714.155600
SplashScreen removed from evOnEndFrame that has 0 listeners
ERROR: NO STAT FOR ks_vallelunga
ERROR: SymGetLineFromAddr64, GetLastError: 487 Address: 0000000010005A80
0000000010005A80 SaiQFF04: filename not available: DllGetClassObject
ERROR: SymGetSymFromAddr64, GetLastError: 487 Address: 00000000100013B6
ERROR: SymGetLineFromAddr64, GetLastError: 487 Address: 00000000100013B6
00000000100013B6 SaiQFF04: filename not available: function-name not available
ERROR: SymGetSymFromAddr64, GetLastError: 487 Address: 0000000010001697
ERROR: SymGetLineFromAddr64, GetLastError: 487 Address: 0000000010001697
0000000010001697 SaiQFF04: filename not available: function-name not available
ERROR: SymGetSymFromAddr64, GetLastError: 487 Address: 0000000010001D1D
ERROR: SymGetLineFromAddr64, GetLastError: 487 Address: 0000000010001D1D
0000000010001D1D SaiQFF04: filename not available: function-name not available
ERROR: SymGetSymFromAddr64, GetLastError: 487 Address: 0000000010003118
ERROR: SymGetLineFromAddr64, GetLastError: 487 Address: 0000000010003118
0000000010003118 SaiQFF04: filename not available: function-name not available
ERROR: SymGetLineFromAddr64, GetLastError: 487 Address: 00007FFED25C916F
00007FFED25C916F DINPUT8: filename not available: GetdfDIJoystick
ERROR: SymGetLineFromAddr64, GetLastError: 487 Address: 00007FFED25CDB67
00007FFED25CDB67 DINPUT8: filename not available: DllGetClassObject
ERROR: SymGetLineFromAddr64, GetLastError: 487 Address: 00007FFED25CD48D
00007FFED25CD48D DINPUT8: filename not available: DllGetClassObject
d:\dev\dev_pc_master_race\ksdi\inputdevice.cpp 248: InputDevice::sendFF
d:\dev\dev_pc_master_race\acs\dicarcontrol.cpp 535: DICarControl::sendFF
d:\dev\dev_pc_master_race\ksphysicsac\car.cpp 1818: Car:nTyresStepCompleted
d:\dev\dev_pc_master_race\ksphysicsac\tyre.cpp 345: Tyre::step
d:\dev\dev_pc_master_race\ksphysicsac\car.cpp 592: Car::stepComponents
d:\dev\dev_pc_master_race\ksphysicsac\car.cpp 564: Car::step
d:\dev\dev_pc_master_race\ksphysicsac\physicsengine.cpp 198: PhysicsEngine::step
d:\dev\dev_pc_master_race\acs\physicsdrivethread.cpp 200: PhysicsDriveThread::step
ERROR: SymGetLineFromAddr64, GetLastError: 487 Address: 00007FFEF5952851
00007FFEF5952851 WINMM: filename not available: PlaySoundW
ERROR: SymGetLineFromAddr64, GetLastError: 487 Address: 00007FFEFA657BD4
00007FFEFA657BD4 KERNEL32: filename not available: BaseThreadInitThunk
ERROR: SymGetLineFromAddr64, GetLastError: 487 Address: 00007FFEFA90CEE1
00007FFEFA90CEE1 ntdll: filename not available: RtlUserThreadStart


WinDbg x64 stack trace:





WinDbg x64 dissassembly:




:)

 

related to no device problem of micromax mmx353g net setter with windows 10

Hi Vishal,

Thank you for posting your query in Microsoft Community.

I understand your concern and will assist you to resolve this issue.



I suggest you to follow the steps below and check if it helps.

Method 1: Troubleshoot

Windows 10 has a built-in troubleshooter to check and fix issues with hardware and devices. I would suggest you to run this troubleshooter to check if the issue is with device. Refer these steps:

• 
  Press Windows key +X, select Control panel.
  
• 
  Change the view by option on the top right to Large icons.
  
• 
  Click on troubleshooting and click on the view all option on the left panel.
  
• 
  Run the Hardware and devices troubleshooter.
  

I suggest you to update drivers from the manufacturer's website and check if the issue persists.

Install the latest drivers in compatibility mode and check if it helps.

Method 2: Compatibility mode

I would suggest you to install the latest available drivers on manufacturer's website in compatibility mode.

Follow the steps below on how to install driver in compatibility mode:

1. Download the driver from the manufacturer’s website and save it on your local disk.

2. Right click on the setup file of the driver and select “Properties”.

3. Select “Compatibility” Tab.

4. Place a check mark next to “Run this program in Compatibility mode” and select operating system from the drop down list.

5. Let the driver install and then check the functionality.

Hope this helps. If the issue remains unresolved, please get back to us and we would be happy to help

 

XCom TexMod Issues On Windows 10 x64 Help?

So, i use the mod called TexMod to mod XCom, I mainly use it to get better visual cues like brighter text, symbols so i don't need to strain my eyes looking for stuff on screen since i am visually impaired, and its really difficult for me to do so and uncomfortable.

I have used it previously, a few years ago when XCom was still new and had no problems and i was using windows 10 X64 Version 1511 at that time.

Now i just cant seem to make it work, i mean when i launch it, it just stays there with a blank screen and nothing happens and it just stays like this forever.

Tried running it in compatible mode for Win 7, XP SP2, XP SP1 and running as admin and no luck, am at my wits end here and have no idea what else should i do.

The thing is i still have an old i3 Laptop that's running the older windows 10 X64 Version 1511 which I have managed to keep it that way for experimenting, and Texmod seems to work just fine on that one.

Am currently running the latest version of windows 10 X64 on my main system.

My system specs are as follows -

• i7 8700
• GTX 1080 Ti
• 32 GB (2x16) Ram
• Z370 Motherboard
• 250 GB Samsung SSD
• 500 GB Samsung SSD
• 2 TB Toshiba HDD (7200 RPM, 64 MB Catch)

Any help regarding the issue is greatly appreciated. The game is not the same for me without that Mod.

 

Windows 10 issues!

I had a similar issue but it only happen on older hardware, Windows would install the stock drivers which would make it nearly impossible to access the internet. Luckily I had newest Intel and Realtek NIC drivers that ran perfectly on Win 10 x64 1607 version, installing those fixed my that problem.

This also can happen on a non-fresh install of WIn 10, when you try to boot from a different computer/motherboard, after a single failed boot, Windows will try to re-detect and re-install all of the drivers, which definitely won't be the most stable or newest.

I tried everything, flushing cache, resetting router, uninstalling the device completely from the list, removing the LAN connection entirely, none of those helped.