• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Windows 7 minimize power draw without Standby/Hibernate

Connoisseur

Connoisseur

Platinum Member
I have a Win 7 pro desktop at home which i have tied to DynDNS. While i don't use it a ton, i still occasionally access it via Remote Desktop from work in order to setup some downloads, update apps, install apps etc. etc. Currently, I have it going to sleep after an hour to save on the energy but this obviously precludes me from accessing it. Are there any power optimization tricks i can use on a desktop system to save on power without putting the system on sleep/hibernate mode so I can still access the system via RDP? I'm thinking something like CPU/GPU throttling. i haven't tried it in a while so i'm out of the loop with the options available for this. My system is in my signature.
 
I guess you could underclock and/or undervolt your CPU, but do you want it to be full performance when you get back and use it?

If that's the case then make sure the obvious things are enabled in BIOS, like Enhanced Speedstep, power states like C-states. On Windows you can set the hard drives to power down after certain time. Make sure the minimum processor state in power management settings is really low(like 5%), so speedstep can do its job.

You could try undervolting without underclock, experiment to see how low you can go before it sacrifices stability.
 
Most Routers have a menu that can be configured to keep DYNDNS updated.

Hibernation works better than sleep. Make sure that the NIC Configuration Advanced tab is check to Powersave and allow the computer to wakeup on LAN.

*Note. It has to be a wired NIC. At the moment Wireless NICs will not work. Future NICs are suppose to provide Wake for Wireless. When? even the old mighty does not know).

It takes about 20 - 30 sec. to brink up an Hibernated computer to be ready.
---------

As an example I have a computer that is configured with UVNC server running as a service using a port of my choice (more secure than the common default).

It is configured with UVNC internal encryption (which is AES). The UVNC server's port is forwarded through the Router to the Hibernating computer (set for this purpose with Static IP)

The computer goes to Hibernation and takes about 1-2 watt to keep the NIC alive.

Using a VNC viewer (on a flash drive) I can plug the flash drive to any Windows computer in the world that has Internet connection.

Type to the VNC myaccount.dyndns:xxxxx

xxxxx being the remote VNC port number.

Press Connect enter the password, and Voila. If it takes more than 20 second to boot the remote computer, the VNC might not fully connect at the first trial. Then starting the VNC again, it will connect because the computer meantime finished its boot up.

While UVNC provides better control than any other remote application. Once the computer is up and running you can use other methods to connect to it too.

The nice thing about the above, it is all free.

UVNC, http://www.uvnc.com/download/

----------------------
VNC Viewer portable here, http://portableapps.com/node/2031


😎
 
Last edited:
You must log in or register to reply here.

TRENDING THREADS

Back
Top