14

Since I've upgraded from Windows 7 to Windows 10, the screensaver doesn't start anymore, and the screen never goes into standby when my gamepad is plugged (even idle) into the computer. "Allow this device to wake the computer" is unchecked in the gamepad's properties.

Disabling the gamepad from the Device Manager works as a workaround, but I would prefer a solution that doesn't involve disabling or unplugging.

harrymc
  • 480,290
Cutter
  • 352
  • 3
  • 8
  • 22
  • Have you found the screensaver settings panel, and what does it say? – harrymc Oct 21 '15 at 16:34
  • Does invoking the sceensaver manually work? – William Oct 22 '15 at 15:25
  • @harrymc : yes, I've set the screensaver to 1 minute, and it doesn't ever start. However, when I click on "Preview" it starts and doesn't stop as long as I don't touch the mouse. – Cutter Oct 22 '15 at 18:01
  • @William: yes, invoking the screensaver manually works, and the screensaver doesn't stop unless I touch the mouse. However, I've set Windows to put the monitor in standby when I press the computer case's power button, and when I press it, the screen turns black but turns back on after one second, as if something triggered it immediately out of standby. – Cutter Oct 22 '15 at 18:11
  • It wouldn't hurt to post a screenshot of the screensaver settings panel as described above. Please also run powercfg -energy and post the report - this will take 60 seconds and the result is in the file energy-report.html in the current folder (not all the signaled "errors" need fixing). – harrymc Oct 22 '15 at 18:40
  • Bonjour. My take on the problem is in my answer below. – harrymc Oct 23 '15 at 07:49
  • Which gamepad are you using? Maybe this has something to do with the analogue sticks/triggers sending a signal? I've confirmed that my 360 pad on Windows 10 does not have this issue, it also doesn't cancel the screensaver when using it (only mouse/keyboard works). – Quietus Oct 27 '15 at 23:56
  • EDIT: Read below that it's a Madrics adapter. My first guess would still be that either the controller or adapter is constantly sending a signal... Is the issue resolved by (1) unplugging the controller from the adapter, or (2) removing the adapter itself? (Cannot edit after 5 minutes unfortunately) – Quietus Oct 28 '15 at 00:09
  • I've unplugged the controller from the adapter (the adapter is still plugged to the computer), and the problem persists. Removing the adapter lets the screensaver start, (same as disabling it from the device manager). – Cutter Oct 28 '15 at 21:09
  • I also have this problem with a clean install of Windows 10 and an xbox 360 controller. – Tristan Nov 04 '15 at 15:31

7 Answers7

2

This is old but still an issue, so if you come here with this issue and the stuff above doesn't help, I fixed my issue by turning off GeForce Experience In-game Overlay. For some reason this is the problem.

2

Update: It appears the information below, while helpful, do not actually resolve the issue. The best resolution at this time, at least for me, is still just to unplug any USB controller when not in use.

My guess is the analog drift, while not relayed in controller movement, is still recognized by the OS as activity. However, the steps below are still helpful for resolving other issues related to drift, so I will leave them here.


I recently dug out one of my old game controllers (Saitek P880) and started experiencing this problem. It took a while just to get to this level of troubleshooting, so I appreciate all the hard work everyone did to get us to this point.

In my case, the issue was caused by an erratic analog axis sensor, causing the analog axis to drift (actually, more like swap between two different values rapidly). Sometimes rebooting or disconnecting the controller will cause the issue to temporarily go away, but eventually the drift will return. The Windows USB Game Controllers control panel does not have a built-in capability to adjust dead zones.

However, at least in the case of Saitek, their website still includes 32-bit and 64-bit drivers that work in Windows 10, including for my P880. Once the drivers are installed (reboot required), the control panel is updated with a much better representation of the buttons and functions, as well as a new tab to manually set the deadzone.

Bear in mind the files must be retrieved using the FTP protocol, and since this functionality is slowly being removed from the latest browsers, you may need to consider using an alternative utility (such as WinSCP) to retrieve them.

Here are two images showing the updated control panel with deadzone modified. You can right click any of the axes controls and uncheck "Link Deadzones" to more granularly control the deadzone range.

Images

Test tab Deadzones tab

D.N.
  • 171
2

Updating Windows 10 to version 1511 (build 10586.3) solved the problem.

Cutter
  • 352
  • 3
  • 8
  • 22
  • 5
    Maybe it did once, but the problem is definitely back. I've had it 1709 and 1803. – Zan Lynx Jun 18 '18 at 18:14
  • Bob Phrapples had an answer on the bottom that worked for me, and it will probably work for others too, if you have GeForce Experience installed. – diynevala Jul 07 '20 at 18:57
  • Un-accepting this because I get the issue again after updating Windows 10 to version 2004. – Cutter Dec 08 '20 at 17:21
1

The Nvidia Geforce Experience overlay may also be causing the problem. Read https://details-of-note.blogspot.com/2020/12/nvidia-3-year-old-bug.html

Disabling the overlay will allow it to sleep. Or hope Nvidia fixes this.

Zan Lynx
  • 2,178
0

A couple posts on this page suggest the following:

Windows 10 don't turn off monitor neither screen saver turns on

  1. In Power Settings, enable "When sharing media: Allow the computer to sleep."

  2. In Device Manager, disable "HID-compliant game controller" and "Virtual XInput device" under "Human Interface Devices."

Steven
  • 27,892
  • I don't have that setting. Maybe because I have uninstalled Windows Media Player.

  • Disabling "HID-compliant game controller" disables my gamepad. I'm looking for a solution that avoids that. I don't have a "Virtual XInput device".

  • – Cutter Sep 29 '15 at 23:22