Windows 10 Keeps Waking PC

[htpc_user]

I've had my main PC for several years now. This ECS motherboard has been the most stable motherboard I've ever used, and it's been the only computer I've ever had where "Sleep" functioned correctly. Now ever since installing Windows 10 if I put it in Sleep I'll come in the next morning and find it on. So then I said, "OK, I'll just put it in Hibernate." Now I come in, and I still find it turned on.

I searched for this problem, and it seems other people are having the same problem with Sleep. I'm not sure about Hibernate because I've just discovered it wakes from that too. Has any one here seen this problem and how to fix it? During my search, others have said looking at "lastwake" and other normal solutions for this don't work and that their PC is still waking.

 

[Nettwerk]

Under your ethernet properties, is "only allow magic packet to wake computer" checked?

 

[htpc_user]

Under your ethernet properties, is "only allow magic packet to wake computer" checked?

Went in yesterday and put a check mark on "Only allow magic packet to wake computer". Put it in Sleep mode last night after doing so. Come in this morning to find the computer on.

 

[mnewxcv]

try going to update settings, advanced, and change automatic to notify. the description for automatic is:

"Keep everything running smoothly. We'll restart your device automatically when you're not using it. Updates won't download over a metered connection (where charges may apply)."

That in itself wouldn't be a problem I wouldn't think, but do you have your computer to sleep automatically after a certain amount of time, or you just do it manually before bed? If it does not sleep automatically, it might be turning on to update, and then staying on.

 

[htpc_user]

It's already set to "Notify" instead of "Automatic". I put it to sleep manually. That's how I always did it on Windows 7.

 

[HeavensCloud]

I can't get my PC to sleep or even turn off the monitor since I upgraded to W10. I have turned every setting off in advanced settings and shut down every program running. Still wont go to sleep.

 

[htpc_user]

I went in my room this morning and found the computer on and some kind of error screen. I had put it in Hibernate yesterday. I've seen plenty of computers wake from Sleep or Standby over the years, so when mine did that after upgrading to 10 I wasn't that surprised. But I have never seen a computer wake up from Hibernate on it's own. I've always had to push the power button.

 

[Brian_B]

Mine has a similar issue - the monitors will go to sleep (10min setting), but wake up very frequently. I can't find the culprit. DId not occur on same hardware with 8.1.

If I put the system to sleep, it will stay asleep, but my nVidia driver has issues waking from sleep for some reason and always crashes and then produces strange artifacts until I reboot (also didn't occur with 8.1)

I've wrote it off to "Random Windows 10 Errata" that I keep hoping will get fixed with one of those automatic updates.

 

[HeavensCloud]

I think it has to do with the Nvidia drivers. I'm getting completely random driver crash/recovers wince upgrading to 10. Sometimes with nothing pushing the card.

 

[ob1]

I was having little hitches and glitches here and there, nothing I could really narrow down, but I used that Windows reset function and essentially reinstalled (wiped disk option too), and things have worked great since then. The reset functions are great, although I think they take longer than just a plain wipe/install, but man, so easy.

 

[Spidey329]

I've had issues like this all the way back to Windows 7. There are utilities built in to track it down.

When it wakes up, open an admin cmd prompt and type ' powercfg -lastwake ' without quotes. See what it says.

Other helpful commands:
Powercfg -energy (generates a report, http://www.howtogeek.com/howto/7638/use-powercfg-in-windows-7-to-evaluate-power-efficiency/ )


Once you track down the culprit, you can start blacklisting them with ' powercfg -requestsoverride ' ( http://forums.steampowered.com/forums/archive/index.php/t-1819902.html ).

I had to do quite a few different apps to get the SOB to stay asleep (Chrome, Audio Drivers).

 

[Gopher1]

I had issues with Windows 7 Home Premium turning on every 15 minutes with my new build until someone helped me resolve the problem by advising me to turn off the Intel Smart Technology feature.

 

[Brian_B]

I've had issues like this all the way back to Windows 7. There are utilities built in to track it down.

When it wakes up, open an admin cmd prompt and type ' powercfg -lastwake ' without quotes. See what it says.

Other helpful commands:
Powercfg -energy (generates a report, http://www.howtogeek.com/howto/7638/use-powercfg-in-windows-7-to-evaluate-power-efficiency/ )


Once you track down the culprit, you can start blacklisting them with ' powercfg -requestsoverride ' ( http://forums.steampowered.com/forums/archive/index.php/t-1819902.html ).

I had to do quite a few different apps to get the SOB to stay asleep (Chrome, Audio Drivers).

This was a helpful post - thank you

 

[YeuEmMaiMai]

are you sure your mouse isn't doing it? f mine moves even in the slightest, the PC will wake up

 

[Canon]

Spidey329 has your answer.

To add to this if you run powercfg -lastwake from an elevated command prompt, you should see why it woke up last. By default windows has a scheduled maintenance task that can wake your PC to check for AV defs, Windows updates etc. This could quite likely be why your PC has woken if you already set your NYC to only respond to magic packets.

Running powercfg -requests from an elevated command prompt will tell you why your PC is being kept awake. I have found frequently it's an active audio stream doing it. Sometimes you can just close the app that is keeping an open audio stream and be good but you can optionally use the requestoverride switch as described by Spidey329 to ignore this and sleep any way.

 

[schizrade]

My gaming rig at home magically turns itself on even though every feature to wake it is disabled. I have to keep the power switch off.

Fucking ghosts.

 

[HeavensCloud]

Running powercfg -requests from an elevated command prompt will tell you why your PC is being kept awake. I have found frequently it's an active audio stream doing it. Sometimes you can just close the app that is keeping an open audio stream and be good but you can optionally use the requestoverride switch as described by Spidey329 to ignore this and sleep any way.

Genius!

[DRIVER] USB Audio Class 1.0 and 2.0 DAC Device Driver (USB\VID_0D8C&PID_0005&MI_00\6&28e4d788&0&0000)
An audio stream is currently in use.

The only usb sound device I have hooked up is a Blue Snowball, and it only has generic windows drivers. Is that what's causing my issues?

 

[MikeTrike]

https://youtu.be/7qnd-hdmgfk

 

[Nettwerk]

Cortana wants to hear you sleep

 

[jyi786]

My gaming rig at home magically turns itself on even though every feature to wake it is disabled. I have to keep the power switch off.

Fucking ghosts.

I've actually had this happen with older Intel NIC drivers.

There's nothing magical about your computer turning on itself; there's always a cause (although I'm sure you already knew that). Just make sure you disable the options to auto-wake in your BIOS AND in Windows, and that should do the trick.

The powercfg switch mentioned above will also help. In my case, it was some Network Sharing thing that was continuously running in the background (never figured out what was holding it open), so I used the powercfg switch and disabled it from holding a "wakelock" (as they say in the Android world). Problem solved.

 

[Tawnos]

Genius!

[DRIVER] USB Audio Class 1.0 and 2.0 DAC Device Driver (USB\VID_0D8C&PID_0005&MI_00\6&28e4d788&0&0000)
An audio stream is currently in use.

The only usb sound device I have hooked up is a Blue Snowball, and it only has generic windows drivers. Is that what's causing my issues?

Blue Snowball matches that usb device's hardware ID. In Device Manager, find the device and go to properties, make sure "allow this device to wake the computer" is unchecked.

 

[schizrade]

I've actually had this happen with older Intel NIC drivers.

There's nothing magical about your computer turning on itself; there's always a cause (although I'm sure you already knew that). Just make sure you disable the options to auto-wake in your BIOS AND in Windows, and that should do the trick.

The powercfg switch mentioned above will also help. In my case, it was some Network Sharing thing that was continuously running in the background (never figured out what was holding it open), so I used the powercfg switch and disabled it from holding a "wakelock" (as they say in the Android world). Problem solved.

Yeah its all disabled, just keeps turning on. I just hit the switch when I am done, cause fuck it, plus it keeps the kids from messing with it that way.

 

[HeavensCloud]

Blue Snowball matches that usb device's hardware ID. In Device Manager, find the device and go to properties, make sure "allow this device to wake the computer" is unchecked.

There isn't a power management tab under it. Any other way around it?

 

[Spidey329]

Genius!

[DRIVER] USB Audio Class 1.0 and 2.0 DAC Device Driver (USB\VID_0D8C&PID_0005&MI_00\6&28e4d788&0&0000)
An audio stream is currently in use.

The only usb sound device I have hooked up is a Blue Snowball, and it only has generic windows drivers. Is that what's causing my issues?

My SBZ caused this issue. Because it was digital out, it'd never close an audio stream thus preventing wake. I've seen it with other soundcards as well.

You could try doing an elevated command prompt and then typing this command:

Powercfg -requestsoverride DRIVER "USB Audio Class 1.0 and 2.0 DAC Device Driver" System

The next time you type powercfg -requestsoverride, it should be listed there. The name has to be exact though, so make sure that's the name it uses in device manager. I use the same exact command except with "Sound Blaster Z" for my system.

This will tell the sleep manager to ignore the audio stream and sleep anyways.

 

[HeavensCloud]

Thanks man. I put it in, let's see if it works.

 

[htpc_user]

I've had issues like this all the way back to Windows 7. There are utilities built in to track it down.

When it wakes up, open an admin cmd prompt and type ' powercfg -lastwake ' without quotes. See what it says.

Other helpful commands:
Powercfg -energy (generates a report, http://www.howtogeek.com/howto/7638/use-powercfg-in-windows-7-to-evaluate-power-efficiency/ )


Once you track down the culprit, you can start blacklisting them with ' powercfg -requestsoverride ' ( http://forums.steampowered.com/forums/archive/index.php/t-1819902.html ).

I had to do quite a few different apps to get the SOB to stay asleep (Chrome, Audio Drivers).

powercfg -lastwake on mine is not very helpful; here's what it says

Wake History Count - 1
Wake History [0]
Wake Source Count - 0

 

[H-street]

Oh wow. Mine is doing the some thing.

Sleep. Powers back on after 30 seconds
Shutdown. Powers back on after 30 seconds

Any fix for this yet?

Windows 7 I didn't see anything like this

 

[htpc_user]

OK, so my previous post above was not helpful. That was from putting it in Hibernate the night before.

Last night I put it in Sleep mode, and this morning I come in to find it on. Here's what it says:

Wake History Count -1
Wake History [0]
Wake Source Count - 1
Wake Source [0]
Type: Device
Instance Path: pci\ven_1022&dev_9606&subsys_1b611019&rev_00\3&267a616a&0&30
Friendly Name:
Description: PCI-to-PCI Bridge
Manufacturer: <Standard system devices>

 

[Killahurtz]

it is Bill Gates and the Microsoft legion watching you sleep!!!...hahahaha

...Windows 10 is crap...pretty soon you will not have a PC at all , in order to use "Windows" you will log in to a cloud based operating system with your home "terminal" , you will not "own" squat....isn't it cool?

 

[Spidey329]

Figured I'd post this, since the most recent Windows 10 update (threshold2) made my computer not go to sleep (and when it did, it'd wake back up).

Because powercfg -lastwake is often useless. I used powercfg -requests to check what was holding the PC awake and found the lovely "A computer has recently made a request..." (or whatever). It lists srvnet as the service.


I had to add this:

powercfg -requestsoverride DRIVER srvnet System


Now I don't have anymore issues. I don't recommend this if you share files from your PC, as it can cause it to interrupt an actual transfer. But if you're like me and don't share (only connect to a central server), it's fine to roll with it.

Any powercfg can be removed by simply typing it again and omitting the last part, e.g.: powercfg -requestsoverride driver srvnet

OK, so my previous post above was not helpful. That was from putting it in Hibernate the night before.

Last night I put it in Sleep mode, and this morning I come in to find it on. Here's what it says:

Wake History Count -1
Wake History [0]
Wake Source Count - 1
Wake Source [0]
Type: Device
Instance Path: pci\ven_1022&dev_9606&subsys_1b611019&rev_00\3&267a616a&0&30
Friendly Name:
Description: PCI-to-PCI Bridge
Manufacturer: <Standard system devices>

The Vendor is 1022, a quick look up of that is that it's an AMD device.
The Device is 9606, a quick check is that it's a PCI-to-PCI Bridge, that matches the description (AMD Motherboard?) --> http://pcidatabase.com/search.php?device_search_str=9606&device_search=Search

Go to Device Manager > System Devices > Select the PCI-to-PCI Bridge, open properties, click "Details", and then on the property dropdown, select "Device Instance Path". See if it matches. Find the one that does.

At that point, you can choose a few options:
- Is there something plugged into this? If no, then you may just want to disable it in Device Manager and see if it stops waking.

Otherwise, find the one in the list that corresponds to that Instance Path and then count them. If it's the third one down, type this:

powercfg -requestsoverride DRIVER "PCI-to-PCI Bridge (003)" System

^^ The device is the "friendly name" listed in Device Manager, the (###) is the list number from top to bottom. You could trying just doing them all, as well.

powercfg -requestsoverride DRIVER "PCI-to-PCI Bridge" System



You can also try typing:

powercfg -devicequery wake_armed

That'll output a list of devices that are allowed to wake your PC. Usually a mouse/kb and network are listed.

 

[Oldie]

Mine turns on when I power it off. Pretty annoying.

 

[HeavensCloud]

I still can't get mine to sleep, before or after the latest update. I'm pretty angry about it.

 

[HeavensCloud]

Ok update for me. I switched monitors last night, still using the same DVI cable, same resolution, same DVI port on the graphics card. After I did the monitor would finally turn off, but the PC still wouldn't sleep. I turned it off for the night, now today it will go to sleep as it should. Anyone have any idea why this would happen?

 

[B00nie]

I don't get it. Why fight with it? Just shut the computer down when you don't use it. It boots fast enough.

 

[HeavensCloud]

I don't get it. Why fight with it? Just shut the computer down when you don't use it. It boots fast enough.

Three people use this computer so it is a pain in the ass to shut it down 15 times a day. I would rather it sleep after 10 minutes like it is supposed to.

 

[B00nie]

Three people use this computer so it is a pain in the ass to shut it down 15 times a day. I would rather it sleep after 10 minutes like it is supposed to.

In that case why not leave it on for the day? You're overcomplicating things. The computer is going to use only a few watts of power when idling. It's going to cost you way more in lost time compared to the potential loss of electricity. When I open my Windows PC I keep it on the whole day until it's time to sleep, I don't bother putting it to sleep or shutting down between sessions. That would be pointless especially considering the flaky stability record with Windows sleep.

On my Macbook it's another story though. It sleeps 100% reliably and wakes up in a second or two (although the latest updates made waking slower, it used to be sub-second).

 

[flu!d]

The only PC I use sleep on is the HTPC and that's only so I can wake it via IR remote.

For what it's worth, it's a Windows 7 box and it's always woken itself up and shut itself down at least three times a day like clockwork on every install I've ever done.

Like B00nie, I can't see the point of sleep in any other scenario with the PC's booting so fast these days. It's not like the days of mechanical drives and Windows 98 where I could make a coffee while the PC booted up.

 

[HeavensCloud]

Holy shit guys, I said it's working perfect now. I just wanted to know why changing a monitor would effect Windows sleep actions. I'm not looking for a debate on how I should use my own computer.

 

[jyi786]

Holy shit guys, I said it's working perfect now. I just wanted to know why changing a monitor would effect Windows sleep actions. I'm not looking for a debate on how I should use my own computer.

Maybe the driver of the other monitor was incompatible with Windows 10?

And by you installing the new one and turning the computer off (if you turned it off 100% all the way and not one of those hybrid powerdowns), maybe that was enough of a restart the computer needed to start functioning properly.

All I can think of.

 

[Tawnos]

Holy shit guys, I said it's working perfect now. I just wanted to know why changing a monitor would effect Windows sleep actions. I'm not looking for a debate on how I should use my own computer.

You sure it was DVI and not HDMI or DisplayPort? The latter two support CEC, which means that devices like monitors, televisions, etc can trigger a power transition state.