PC turns on by itself?

[yusoffb01]

OK, after manually disconnecting the PWR SW and shorting the pins when I boot up, I've been monitoring the past 3 days and the shutdown/startup issue has not happened since.

Does this means that I may have a faulty, or overly sensitive power switch (perhaps thermal expansion/contraction causes a short in the contacts?) or something else?

Wait 1 week and see

 

[drawistwl]

couldnt explain y it shutdown suddenly. probably is some window setting.

i got the same problem with my rig, it turn on by itself when it connecting to internet. seem like whenever there is some packet signal, it will tigger my com to turn on.
so i turn off the "wake on lan" and "ac back" and some other setting under the power management in the BIOS. and it fixed.
now is tht my comupter LAN light on the back of the cpu, wont light up after i shutdown.

u can try test with
1. shutdown ur com, don off the main plug
2. switch on and off the power of ur router tht connected directly to ur com with ethernet cable
3. montior if it turn on ur com.

hopefully it help.

 

[hlots123]

Something else strange happened which I think is linked to the startup issue. Was surfing the new when my PC suddenly shutdown on me, like as though I pressed the power button.. it displayed the blue shut down screen. First time it happened it stayed shut down till I pressed the button to turn on, second time it happened, it started up by itself again... could it be a short in the cable or PSU problem?

oic, u had power up shutdown issue too? guessing from ur follow up tat
1. mysterious turn on - combi of power button or PWR SW cable faulty, and EuP/ErP Ready bios setting
2. mysterious shutdown - power button or PWR SW cable faulty

and 1. happened more often since it was combi of 2 factors

 

[Gymrat76]

couldnt explain y it shutdown suddenly. probably is some window setting.

i got the same problem with my rig, it turn on by itself when it connecting to internet. seem like whenever there is some packet signal, it will tigger my com to turn on.
so i turn off the "wake on lan" and "ac back" and some other setting under the power management in the BIOS. and it fixed.
now is tht my comupter LAN light on the back of the cpu, wont light up after i shutdown.

u can try test with
1. shutdown ur com, don off the main plug
2. switch on and off the power of ur router tht connected directly to ur com with ethernet cable
3. montior if it turn on ur com.

hopefully it help.

Thanks, wake on LAN has always been off in BIOS on my rig

 

[Gymrat76]

oic, u had power up issue too? guessing from ur follow up tat
1. mysterious turn on - combi of power button or PWR SW cable faulty, and EuP/ErP Ready bios setting
2. mysterious shutdown - power button or PWR SW cable faulty

and 1. happened more often since it was combi of 2 factors

I guess so. Hope the distro is able to replace the cable and power button on my Fractal R4

 

[Gymrat76]

Update:

Got a replacement Power Button and PWR SW cable today (thanks Convergent!).

So far so good. Will monitor and see if the issue recurrs.

 

[precise]

Try this (run command prompt with admin rights)
powercfg -waketimers

You will find probably the task scheduler which wakes up your computer. For mine, it is the media center update which I have no clue how it got into task scheduler. Anyway, fixed mine just now and hopefully no more waking up my PC in the middle of the night. Quite scary especially when I wake up at night to go loo and find the monitor screen light up.

If you want more details to disable the task in the scheduler, if there is any, google for it. For me:
http://www.howtogeek.com/122954/how-to-prevent-your-computer-from-waking-up-accidentally/


Lastly, you can try to see what was the last event that wakes up your computer.

powercfg -lastwake

 

[Gymrat76]

Try this (run command prompt with admin rights)
powercfg -waketimers

You will find probably the task scheduler which wakes up your computer. For mine, it is the media center update which I have no clue how it got into task scheduler. Anyway, fixed mine just now and hopefully no more waking up my PC in the middle of the night. Quite scary especially when I wake up at night to go loo and find the monitor screen light up.

If you want more details to disable the task in the scheduler, if there is any, google for it. For me:
http://www.howtogeek.com/122954/how-to-prevent-your-computer-from-waking-up-accidentally/


Lastly, you can try to see what was the last event that wakes up your computer.

powercfg -lastwake

Thank you! Very helpful!

I got a similar one as you:

Timer set by [SERVICE] \Device\HarddiskVolume2\Windows\System32\svchost.exe (SystemEventsBroker) expires at 3:26:14 AM on 2/3/2016. Reason: Windows will execute 'NT TASK\Microsoft\Windows\Media Center\mcupdate_scheduled' scheduled task that requested waking the computer.



But the /lastwake showed '0'.

I think in my case it's a combination of faulty button + wake timers.

While the waketimers may explain the middle of the night startup, it doesn't explain the shutting down suddenly when I'm on the PC. So perhaps a combination of factors.

I've set waketimers to disabled, so will monitor and see. Thanks !

 

[hlots123]

Try this (run command prompt with admin rights)
powercfg -waketimers

You will find probably the task scheduler which wakes up your computer. For mine, it is the media center update which I have no clue how it got into task scheduler. Anyway, fixed mine just now and hopefully no more waking up my PC in the middle of the night. Quite scary especially when I wake up at night to go loo and find the monitor screen light up.

If you want more details to disable the task in the scheduler, if there is any, google for it. For me:
http://www.howtogeek.com/122954/how-to-prevent-your-computer-from-waking-up-accidentally/


Lastly, you can try to see what was the last event that wakes up your computer.

powercfg -lastwake

curios, in the article the pic shows the wake timers setting as a subset under "sleep". if u shutdown properly, windows not running, wonder how does a windows scheduled task trigger mb to power on?

believe this was mentioned in the previous link i posted. btw i hav not encountered any mysterious power ons. i only set the eup bios setting since day 1 when looking thru the bios...

 

[Gymrat76]

curios, in the article the pic shows the wake timers setting as a subset under "sleep". if u shutdown properly, windows not running, wonder how does a windows scheduled task trigger mb to power on?

believe this was mentioned in the previous link i posted. btw i hav not encountered any mysterious power ons. i only set the eup bios setting since day 1 when looking thru the bios...

That's why I think it was due to the faulty power button/PWR SW cable. Seems like a short cos the light flickers on and off a few times before it powers on fully, from the previous encounter.

 

[hlots123]

That's why I think it was due to the faulty power button/PWR SW cable. Seems like a short cos the light flickers on and off a few times before it powers on fully, from the previous encounter.

hi, hopefully its fixed .
but after u dbl cfm no more power ons/power downs, can u change back eup 2013 to original setting - to check if its partly to blame for some power ons

 

[Gymrat76]

hi, hopefully its fixed .
but after u dbl cfm no more power ons/power downs, can u change back eup 2013 to original setting - to check if its partly to blame for some power ons

Sure, I'll give it a week then disable the EuP2013 (original setting) and see.

 

[precise]

Mine is the first gen i5-750 running on very old motherboard. I have enabled s1 or s3.. can't remember to allow scheduled tv recording. Somehow, the issue of self power up happen during last year seventh month of the lunar calendar. Occasionally it will powered up on its own. Didn't bother about it until recently when I have time. Tried a few methods and apparently the one on the scheduled tasks solved my problem.

Almost went to buy a new psu as mine is already 8 years old.

 

[Gymrat76]

Update: After more than a week, the problem has not recurred.

Hence, my conclusion is that the problem was with the power switch.