General discussion


Does restarting desktop each day have any adverse impact?

By onbliss ·
For a long long time, I have the habit of restarting my machine before I leave work, at the end of the day. Before this habit I used to shut the desktop off.

My coworker said that sometimes "restarting" everyday could adversely affect the computer. He talked about variances in temperature and what not. To put it simply I did not understand :-(

So here is my question: Does restarting the desktop each day reduce its life compared to restarting it less often? Or does it in anyway have a negative impact on the desktop?

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

I have all

by Old Guy In reply to Does restarting desktop e ...

of our users Restart every day. Reasons are, even with XP, the programs will run better with less sluggishness by restarting each day. In what you friend says is true if you do a Shut down. I do agree with that. However, every time one of the docs calls me and says one of the PCs in the patient rooms is running real slow I go to check it and it has not been logged off for several days. I restart it and, wow, just like magic, it works great. I also have several programs that update and run every night so they have to be on. In my book the computers, at least in the work place, should be restarted each day.

Edited to add: we keep our computers until they die a terrible death. We have had these with XP for three years and have not seen any adverse effect of Restarting.

Collapse -

Sluggishness ?

by onbliss In reply to I have all

Is there any sluggishness due to just hardware issues?

Collapse -

When I have checked the

by Old Guy In reply to Sluggishness ?

Memory usage after the PC has been logged for several days it is almost maxed with the amount of RAM. Restarting the workstation dumps everything out and helps it to run better. Even closing out the programs doesn't clear the memory usuage all the way.

Collapse -


by onbliss In reply to When I have checked the

...this is software related, right?

Collapse -

In my mind,

by Old Guy In reply to But...

which has a lot of room to get lost, the software is using the RAM for working. Sometimes the software doesn't turn loose of its portion of the RAM even when you close it out. What I have experienced is that doing the restart each day the users have a lot less issues with sluggishness.
Edited to add: I think it is both but one could argue it's software. Just a thought.

Collapse -

A question for you

by TechExec2 In reply to In my mind,


A question for you...

"Sometimes the software doesn't turn loose of its portion of the RAM even when you close it out."

Are you saying that you have observed something that indicates when a Windows XP process (program) is shut down, that its memory is not released? Can you describe how you determined this?

In Windows XP, each program runs in its own virtual memory address space. Shutting down the program removes the address space and the memory pages (paged in or out) are made available for reuse.

Now, there are persistent common SYSTEM memory areas that running applications can cause to become enlarged. These persist beyond the life of an individual address space. If you're experiencing problems with this, more physical RAM should completely solve it.

My experience: With Windows XP workstations running 1.5 or 2.0 GB of RAM, they can stay up indefinitely without ever slowing down -- weeks or months.

Thanks in advance.

edit: grammar

Collapse -

My Answer for you, Yes.

by Old Guy In reply to A question for you

Yes, I have seen where you can close out a program and it does not release all it's memory allocation. This article is regarding User Hive issues but in the overview it states the same .
All of our workstations in the patient areas are running 2GB of RAM. The longer (days) they stay open the slower it gets. Just closing the programs will release some of the RAM but a complete restart will let it start off, usually >250MB. It could be a direct correlation to the software but I couldn't show that. My statement is it is better, at least for our systems, to restart each day. Even the users can tell a dramatic difference.

BTW, TechExec2, on a personal note, I have noticed a tremendous change from the time you first started posting in TR and now. Good change. :)

Collapse -


by w2ktechman In reply to A question for you

Windows is supposed to work as you say, but often it does not. I have 3 work systems, and for the most part they do not need to be rebooted during the work week. However, sometimes they do.
Windows does not release the memory address if a thread of the program is still running, especially if the program called a file (like a dll) and there was no proper close to it. This memory is 'in use' even when nothing is actually running or using it.
Also, Windows does not always release temp files properly either, nor does it release page file memory properly (often). Unless using 3rd party tools, or altering some registry entries. there are many places that Windows fails to free up memory and/or clean the page file.
Shutting down in the eve is a good practice, leaving them on as I do is not. But with the network problems recently, I fear that I will not be able to log back in if I shut down (happens often) for a few hours. And I hate being down completely.

Collapse -

Old Guy: Memory leaks

by onbliss In reply to A question for you

Maybe the software applications are leaking memory. It is not uncommon for the code to release its memory cleanly. If it is not the software application itself, then it could be an issue at framework/platform/OS level.

Collapse -

OldGuy: Thanks for your reply

by TechExec2 In reply to A question for you

My read of the MS "User Profile Hive" article is that it is only talking about incomplete termination of user sessions when a user logs off and not being able to log in. The article doesn't mention memory allocation problems, although one could assume some memory was not freed also.


In w2ktechman's post (link below), he mentions things that are about system memory allocations (memory shared between processes) that are sometimes not properly released when an application (process) is shut down, and some other problems.

So, this still looks like system memory allocation issues (and Windows bugs in handling them), not the process' virtual memory address space per-se. And, a good way to resolve that is to reboot.

But, it still leaves unexplained how I can get away with rebooting only after weeks or months, and never to resolve slow-downs or instability (always for some other reason like a software install or testing an aberrant pre-release program).


I think onbliss (link below) is right (VERY presumptive of me since it is YOUR shop! :0 ). It is likely your applications are leaking memory in their own address space. And, merely restarting them should produce an great result. But, having done all that, going one step further and rebooting too makes a LOT of good sense.


w2ktechman's post

onbliss' post

edit: spelling

Related Discussions

Related Forums