DS4Windows Crashes a few seconds after opening with DualSense connected

[Raiders160]

When I try to open DS4Windows while my DualSense Edge or DualSense is connected it either will not open unless I run as administrator or open through the DS4Updater then open. Once open it will briefly show it is connected and then crash. If I disconnect the DualSense Edge or DualSense DS4Windows will open correctly until I connect the controller.

To Reproduce Steps to reproduce the behavior:

1. Have the latest version (3.2.8 x64) installed correctly from the step by step procedures.
2. Extract the files to the desktop.
3. Open DS4Windows
4. Connect any dualsense controller ( Edge or not)
5. No controllers detected.
6. Head to settings>Device options>Check DualSense controller support
7. Stop and start DS4Windows
8. DS4Windows closes and will only reopen for a few seconds before closing again.
9. Disconnect controller DS4Windows will open until the controller is reconnected.

Expected behavior I expect the controller should be detected without forcing the program to close.

Screenshots and Logs I was able to get a screenshot of the logs. I opened up DS4Windows without the controller connected>then went to the logs section>plugged in the controller>took Screenshot, then DS4Windows closed.

• Controller Make and Model: Sony DualSense Edge Wireless Controller CFI-ZCP1
• OS: [Windows 10 Home]
• DS4Windows Version [3.2.8]

[Raiders160]

ds4windows_log_20230213.87.txt

[Masamune3210]

Seems like the program crashed while trying to handle information relating to the gyroscope

[Raiders160]

Do you have an idea to fix this?

[phatsk]

I'm having the same issue. Not sure exactly when it started happening but noticed it last night. Here's my logs

• Windows 10
• Controller: Sony DualSense CFI-ZCT1W
• DS4Windows version 3.2.8

[phatsk]

I have some additional details now:

• I reinstalled any .NET framework stuff I could find in Add/Remove Programs, did not help
• Downloaded several older versions of DS4Windows.
  • Version 3.1.12 was the first one that stayed open, so I started going up version by version
  • 3.2.0 works
  • 3.2.6 works
  • I then tried 3.2.7 and the latest release and they work as well!

So, I think something about 3.1.12 kicked my system into working again. Not sure why, but I will keep an eye on things especially after a reboot and see what happens.

[Quixote1]

I have the same issue. As soon as I connect the controller, DS4Windows crashes, barely leaving me any time to see the log. I don't seem to be able to grab a screen capture. Everything was working fine last year until recently when I dusted off my controllers and did an update. I receive the message "Controller was removed or disconnected" right before DS4Windows crashes, the controller changes from "connected" to "paired" in Windows Bluetooth settings -- and this happens regardless of whether I connect the controller before or after starting DS4W. Using version 3.2.10 Windows 10, x64 EDIT: Found the log files in AppData:

2023-05-25 23:07:54.4987|INFO|DS4Windows version 3.2.10
2023-05-25 23:07:54.4987|INFO|DS4Windows exe file: DS4Windows.exe
2023-05-25 23:07:54.4987|INFO|DS4Windows Assembly Architecture: x64
2023-05-25 23:07:54.4987|INFO|OS Version: Microsoft Windows NT 10.0.19045.0
2023-05-25 23:07:54.4987|INFO|OS Product Name: Windows 10 Home
2023-05-25 23:07:54.4987|INFO|OS Release ID: 2009
2023-05-25 23:07:54.4987|INFO|System Architecture: x64
2023-05-25 23:07:54.4987|INFO|Logger created
2023-05-25 23:07:55.5395|INFO|Running as User
2023-05-25 23:07:55.5395|INFO|HidHide control device found
2023-05-25 23:07:56.5648|INFO|Starting...
2023-05-25 23:07:58.5659|INFO|Some applications may block controller inputs. (Windows UAC Conflictions). Please go to https://docs.ds4windows.app/troubleshooting/kb-mouse-issues/#windows-not-responding-to-ds4ws-kb-m-commands-in-some-situations for more information and workarounds.
2023-05-25 23:07:58.5659|INFO|Using output KB+M handler: SendInput
2023-05-25 23:07:58.5659|INFO|Connection to ViGEmBus 1.21.442.0 established
2023-05-25 23:07:58.5659|INFO|Searching for controllers...
2023-05-25 23:07:58.5659|INFO|Using Shared Mode
2023-05-25 23:07:58.7718|INFO|Found Controller: 1C:A0:B8:5D:9A:B4 (BT) (DS4 v.2).
2023-05-25 23:07:59.1470|INFO|Plugging in virtual X360 controller (XInput slot #1) in output slot #1
2023-05-25 23:07:59.1470|INFO|Associated input controller #1 (DS4 v.2) to virtual X360 Controller in output slot #1
2023-05-25 23:07:59.1665|ERROR|Thread App Crashed with message Object reference not set to an instance of an object.
2023-05-25 23:07:59.1759|ERROR|System.NullReferenceException: Object reference not set to an instance of an object.
   at DS4Windows.Mouse.sixaxisMoved(DS4SixAxis sender, SixAxisEventArgs arg)
   at DS4Windows.DS4SixAxis.handleSixaxis(Byte* gyro, Byte* accel, DS4State state, Double elapsedDelta)
   at DS4Windows.DS4Device.performDs4Input()
   at System.Threading.Thread.StartHelper.Callback(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.Thread.StartCallback()
2023-05-25 23:07:59.2108|INFO|Stopping Virtual Output Controllers
2023-05-25 23:07:59.2108|INFO|Closing connection to ViGEmBus
2023-05-25 23:07:59.2188|INFO|Disassociated virtual X360 Controller in output slot #1 from input controller #1 (DS4 v.2)
2023-05-25 23:07:59.2188|INFO|Unplugging virtual X360 Controller from output slot #1
2023-05-25 23:07:59.2188|INFO|Controller 1 was removed or lost connection
2023-05-25 23:07:59.2188|INFO|Stopping DS4 Input Controllers
2023-05-25 23:07:59.2188|INFO|Stopped DS4Windows
2023-05-25 23:07:59.2188|INFO|Closing connection to output handler SendInput

[Quixote1]

Ok, an update: Apparently the files in AppData were creating some sort of conflict since they were created by an older version. Deleting the DS4Windows directory there with all of my settings, etc. seems to have solved the crashing issue. Sorry for the false alarm!

[Ryochan7]

The initial transition to XmlSerializer with DS4Windows version 3.2.0 was fairly rocky. It took a few versions to fix some serialization problems in the DTO classes; there were also some model problems outside of DTO classes that had to be fixed. I am still glad that I changed settings and profile saving as the current system is a lot easier to read and maintainable than editing from the DOM directly. XmlSerializer still does not have some of the magic that Newtonsoft Json.NET offers though.

Also, you should not be using DS4Windows and Steam Input at the same time. That will cause many problems especially for some controllers. Although not related to DS4Windows, Steam Input will constantly cause Wiimote disconnects which makes Touchmote useless while Steam Input can see any Wiimote. HidHide is necessary to hide the Wiimote from Steam but I really wish I could distribute my custom changes as vanilla HidHide does not do what I want.

[AbdelrahmanSadat]

Ok, an update: Apparently the files in AppData were creating some sort of conflict since they were created by an older version. Deleting the DS4Windows directory there with all of my settings, etc. seems to have solved the crashing issue. Sorry for the false alarm!

Can you mention the path to those files, please?

[Quixote1]

Can you mention the path to those files, please?

Sure, So if you're using Windows 10 and it's on your C drive, it would be C:\Users*******\AppData\Roaming\DS4Windows where the blanked out field is your username.

[CarrionB]

Didn't work for me, and it kept creating new controllers

[Taschia]

Can confirm! I was experiencing the same issue, but deleting the DS4Windows folder inside AppData and reopening the program seems to have fixed it right up 👍

[Ryochan7]

Going to assume it is a profile issue somewhere down the line. Really would need the profile in question to have an idea about why this is happening. Found a couple bigger profile migration problems while working on DS4Windows 3.3.

[Ryochan7]

Again, making me shoot in the dark. Like I mentioned in the other issue, there was no way to know without the bugged profile in question. It worked for me but I was using recent profiles.

The triggers string was set to null and that is why the routines would error out.