Log why MP gets started/waked up (2 Viewers)

[chrisonline]

It seems the problem is fixed. Thanks for the great help!!

For all those who have the same problem here the solution:
In the device manager check your network card settings.
The important settings are "Wake on Magic Packet" and "Wake on pattern match".

The setting "Wake on pattern match" have to be of because every "Ping" or simple folder access from another PC wakes up the PC.

Attached there is a screenshot of the setting on a Realtek Device.

 

[mbuzina]

You found it - that was what I started to write before I've seen your post.

 

[TheBatfink]

Ahh I cant wait to try this out. I've been battling keeping my machine asleep. Hope this is the answer!

 

[Paranoid Delusion]

This would be great information to add to the wiki, especially as this setting seems to be enabled as default (checked mine and it was).

@TheBatfink please let us know if that resolves your problems, just as a form of confirmation, thanks.

 

[TheBatfink]

I have had the issue for a while where it wouldn't sleep or when it did it would wake up 15 minutes later, sometimes later. Rarely did it stay asleep (I have a server which monitors uptime of the networked machines).

I disabled this value and the first time it slept, it stayed there for over an hour so only one test so far but it looks promising. Will see when its left over night and how it works over the coming days. I also did some googling and came across this which details the same thing here. I'm also wondering why I never tried to test with the network cable unplugged and just concentrated on services running on the problem machine.
My Intel NUC is also doing the whole sleep wake sleep wake thing sometimes too, think I'll see if that adapter has the setting but that's an intel nic I believe (but which has suddenly started behaving the last day or too which doesn't help finding the issue).

I would like to try and get to the bottom of what was being sent that was waking the machine and where it was coming from though. I have a laptop which is usually off, a second PC which is also usually off, a MePo client and a WHS2011 server with lightsout installed (which has the uptime monitor). I'm wondering if that monitor was pinging the machine to see what it was doing and causing it to wake when asleep.

But thanks again for the idea @chrisonline really hope it works long term

 

[RonD]

looks like Batfink is running Win7, so he can try using Win7 Event Viewer to see what is waking his system. You need use

Control Panel > System and Security, Under Admin Tools click on Open Event Logs
On left side select Windows Logs > System
On right hand side, click on Filter Current Log, in that window select Event Sources and Enable "Power-Troubleshooter"

this will show wakeup events, on my Win7 system I see things like the following

The system has resumed from sleep.
Sleep Time: ‎2013‎-‎03‎-‎28T15:50:12.645489800Z, Wake Time: ‎2013‎-‎03‎-‎28T16:06:32.777015900Z
Wake Source: Timer - Task Scheduler will execute '\EPG Collector' task.

The system has resumed from sleep.
Sleep Time: ‎2013‎-‎03‎-‎28T15:14:43.804365000Z, Wake Time: ‎2013‎-‎03‎-‎28T15:25:14.071776300Z
Wake Source: Device -Realtek PCIe GBE Family Controller

The system has resumed from sleep.
Sleep Time: ‎2013‎-‎03‎-‎26T15:47:06.941379100Z, Wake Time: ‎2013‎-‎03‎-‎26T15:47:31.936025000Z
Wake Source: Device -USB Root Hub

I also see a few cases with "Wake Source: Unknown", where Win7 does not have info on wake soruce

 

[TheBatfink]

Hi, good tip for debugging. I had looked at that a little while ago before I lost the patience to troubleshoot it, in all instances that it woke (and it wasn't me waking it) the event source was unknown. It was at that point I just gave up while my hair was intact! - so if it wasn't this dodgy NIC wake up.. I may cry.

 

[RonD]

one quick test is unplug ethernet cable and all USB mouse/keyboards. If the system has a "unknown" wakeup, you know what is NOT causing it.

 

[TheBatfink]

Well my machine is definitely behaving itself now! One more issue off the snagging list