Discussion Locked

Desktop Won't stay turned off!

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
A client has purchased a Gateway 500S. From day one we have a strange problem where the computer powers up on its own after being totalling shut down. I worked with Gateway support,even replacing the power supply. Stuck around 2 hours and thoughtit was fixed. Then received a call that it powered up again 5 separate times that day. Any ideas how to fix this?

5 replies

by niggiebro

Depending on the OS, there could be a few reasons why this problem exist. Do you know if the PC has a network card installed? If yes, check the BIOS and make sure the, (wake-up LAN), is disabled. Another suggestion is to search Microsoft's archives,I remember ready up on some of the same problems your client is having. Make sure you search for the info. on the OS that is installed on the PC.

by thechas

Make sure ALL Wake-On events are disabled. If they can be physically disabled, and not just disabled in BIOS settings, so much the better.

I have seen PCs with a wake on keyboard feature. Touching a key, or wiggleing the mouse will cause the PC to boot.

Next, try having the PC set for a few days without any phone or network lines connected. Noise, spikes, or commands from either could cause the PC to boot.

You could also disconnect the front panel power switch and see if the PC does not boot. The wires could be picking up noise, or the switch may be connecting once and awhile.

Finally, try an isolated AC supply. The simple system is a line conditioner.
Since an ATX power supply is always part way on, all it would take is the right power spike to start up the power supply.

Chas

by techviper

I recently had the same problem with a white box PC we had built and sold to one of our clients. Wake on LAN or Wake on Modem in the BIOS was the culprit. I disabled both since neither were desired features in this situation. Problem solved.

by mkrystinak

Thanks to TechViper, I was finally able to solve this problem. It was a Wake Up setting in bios that apparently was on. Thanks again

This discussion is closed to new replies.