I use an Xbox One controller to play the Division on PC. Once I have exited the game, as soon as the power to the controller is turned off, my computer will crash. I have uplay friends that have also experienced this consistently. I can exit the game and take the batteries out of the controller to instantly cause the issue. Once the controller is powered off, the mouse "beeps" when you click anywhere although the click is not registered. At that point I am unable to interact with anything without using the keyboard (which works fine). The computer is also unable to shutdown or restart using windows, (it will just hang). I need to physically power off the computer to restart. This happens every time I exit the division. This issue never occurred until I started playing the division. This has not happened with other uplay games either. I am launching through steam if that makes a difference.
Same except I'm using an ATI card. This also did not occur during beta. It can also happen in the middle of the game.Originally Posted by Slangwell Go to original post
Yep, I'm having this exact issue as well, and you did a great job at describing it. The issue is 100% with uplay itself and nothing to do with any game. I am able to reproduce this every time by launching uplay and simply unplugging my controller, after that pretty much all USB functions stop working.
I'm running Windows 10 64bit on skylake 6700k and msi z170a motherboard
Agree that this is a Uplay issue. Has been happening since last week with FC Primal. Now I'm getting it with this game too. Desktop Window Manager is using +25% of my CPU when I exit. Mouse beeps, left and right clicking does nothing. Hard reboot is only solution.
Using the Wireless Adapter for Windows synced to an Xbox One Controller.
I just got this same problem again in a different game on Steam that I was using an Xbox One Controller to play. So I think it is a problem with Windows 10 & Xbox One Controllers. Game and Game Provider seem irrelevant since I had the problem in The Division through Uplay only (no Steam), and a different game through Steam.
I have the same issue but it happens after a few minutes of playtime. (Just built my PC and kinda glad I am not alone with this problem). I would like to follow this thread and hope someone knows soon how to fix it.
Win10 pro
GTX 960
I7-6700
MSI Z170A
16 GB RAM
XBOX ONE controller with Ear Force Xo Four