Basic Computer Troubleshooting: Computer is Slow

How to troubleshoot a computer that is performing or running slowly?

Follow this procedure to troubleshoot a computer that is performing or running slowly in the Windows Vista® operating system.


NOTE: When troubleshooting slow performance using the steps below, some steps may take an extended time to complete. Move on to the next step and complete the unused steps at a later time.

1. Close any programs that are not being used.

2. Software loading when the computer starts may be causing the computer to slow down. Remove unused applications from startup.

3. If this is a notebook computer, the power settings may have an overall effect on system performance.

WARNING: There is a risk of data loss. Before closing an application or process using the task manager, be sure to save all open files because the application may not prompt you to save data before closing. Also,
closing critical processes may cause system instability.

4. Use the Task Manager to close any unused applications or processes without an icon on the task bar or in the system tray, or which are listed as (not responding).

5. Stop any instances of host svcs that may be running.

6. Delete any unnecessary files using the Disk Cleanup utility.

7. Adjust visual effects.

8. Perform a System Restore to return the configuration to a time when the computer was not performing as slowly.

9. Detect and repair possible errors on the hard drive using the Check Disk utility.

10. For computers upgraded to the Windows Vista® operating system, check the Windows Experience Index rating to determine expected performance.

11. Defragment the hard drive.

12. Remove any recently added hardware.

NOTE: For assistance with any third-party hardware or software, please contact the hardware or software manufacturer.

13. Setup the Windows Readyboost™ feature on a removable disk or flash memory drive.

14. The presence of viruses, spyware, and adware can cause the operating system to perform slowly. Use a spyware or adware removal utility and anti-virus application to clean the system of malware.

NOTE: The presence of two or more anti-virus programs may decrease computer performance.


15. Documents waiting to be printed may affect performance. Let the print jobs finish and performance should increase.

NOTES:

• Upgrading the system memory is likely to improve performance.
• A full recovery of the system may be required if the above steps did not resolve the issue.
  
  

WARNING: There is a risk of data loss. Ensure to back up any important data before running a full recovery of the system.

Basic Computer Troubleshooting: Networking and Internet Connections in XP

Even though my split as computer technician is hardware, about 30% of the calls I received is about networking problem. Issues like cannot connect to the internet, local access only and no available networks are some of the common problems with networking. Because of this, I requested a special training for networking and internet from our operations manager which she granted. The training is just about basic networking troubleshooting that is why I am still doing research online for advanced troubleshooting of networking and internet.

Here are the links to the most popular Microsoft Knowledge Base troubleshooting articles for troubleshooting networking issues, cable modems and internet connection sharing (ICS). Also includes home networking, connectivity, TCP/IP, TRACERT, file sharing, permissions, wireless network connections, internet connection problems, VPN, cable modems, XP firewall, routers and print servers



GENERAL NETWORKING

• Troubleshooting Home Networking in Windows XP
• How to Troubleshoot Network Connectivity Problems
• Network Problems with a Router in Windows XP
• You May Be Unable to Browse the Network
• Network Adapter Not Working no Compatible Driver
• Cannot Create a Network Connection After XP Restore

TCP/IP

• How to Troubleshoot TCP/IP Connectivity with Windows XP
• How to Use TRACERT to Troubleshoot TCP/IP Problems
• How to Reset Internet Protocol (TCP/IP)
• Syntax and Options of Ipconfig Diagnostic Utility

WIRELESS CONNECTIVITY

• How to Troubleshoot Wireless Network Connections
• How to Make 802.11b Wireless Network More Secure
• Wireless Network Adapters May Lose Connectivity
• How to Enable Automatic Wireless Network Configuration

INTERNET CONNECTIONS

• How to Troubleshoot Internet Connection Problems
• WebCast: Troubleshooting Internet Connectivity
• Using Internet Connection Sharing with User Profiles
• Troubleshooting Internet Connection Sharing in Windows XP
• Resources for Troubleshooting Internet Connection Sharing
• Setting up Internet Connection Sharing
• Description of Repair Option LAN or Internet Connection
• Check Your Internet Connection Speed

FILE SHARING

• Description of File Sharing and Permissions in Windows XP
• Connect to Network Resources Without Mapping a Drive or Port
• XP Firewall Can Prevent Browsing and File Sharing

NETWORK PRINTING

• Cannot Print from the Network to a Windows XP Print Server
• How to Print to Network Printer from an MS-DOS Program
• How to Troubleshoot Network Printing Problems
• "Access Denied" When Printing to a Network Printer

OTHER

• How to Configure a Virtual Private Network (VPN)
• Troubleshooting Cable Modems
• IEEE 1394 Network Connectivity Lost on Resume
• Resources for Troubleshooting Modem Problems

Basic Computer Troubleshooting: Hardware

Troubleshooting is a form of problem solving most often applied to repair of failed products or processes. It is a logical, systematic search for the source of a problem so that it can be solved, and so the product or process can be made operational again. Troubleshooting is needed to develop and maintain complex systems where the symptoms of a problem can have many possible causes. Troubleshooting is used in many fields such as engineering, system administration, electronics, automotive repair, and diagnostic medicine. Troubleshooting requires identification of the malfunction(s) or symptoms within a system. Then, experience is commonly used to generate possible causes of the symptoms. Determining which cause is most likely is often a process of elimination - eliminating potential causes of a problem. Finally, troubleshooting requires confirmation that the solution restores the product or process to its working state.

In general, troubleshooting is the identification of, or diagnosis of "trouble" in a system caused by a failure of some kind. The problem is initially described as symptoms of malfunction, and troubleshooting is the process of determining the causes of these symptoms.

A system can be described in terms of its expected, desired or intended behavior (usually, for artificial systems, its purpose). Events or inputs to the system are expected to generate specific results or outputs. (For example selecting the "print" option from various computer applications is intended to result in a hardcopy emerging from some specific device). Any unexpected or undesirable behavior is a symptom. Troubleshooting is the process of isolating the specific cause or causes of the symptom. Frequently the symptom is a failure of the product or process to produce any results. (Nothing was printed, for example).
Troubleshooting is a process. The process for troubleshooting is to isolate the area of the system that the problem has occurred and attempt to take steps toward resolving the problem.

It is important to note any changes to the system prior to the problem as well as immediate symptoms. Troubleshooting is a process. The process for troubleshooting is to isolate the area of the system that the problem has occurred and attempt to take steps toward resolving the problem. It is important to note any changes to the system prior to the problem as well as immediate symptoms. For instance, if a system performs well until you open an unexpected mail attachment from a co-worker. It is possible the system was affected by the act of opening the attachment (possible virus/worm).


COMPUTER TROUBLESHOOTING

Trying to track down and resolve technical problems on your computer is, undeniably, one of life's most frustrating experiences. To help you through the process, I've written some articles that explain the critical issues you need to understand to do effective troubleshooting on personal computers. This section will tackle mainly on the basic troubleshooting of computer's hardware problems.


1. The computer does not display, beep, clear POST or boot.

NOTES:
* Because each of these steps represents a possible solution to this issue, check the computer status after completing each step.

1. Restart the computer by pressing and holding the power button until all power indicator lights are off, waiting 30 seconds, and then pressing the power button again.
2. Remove or disconnect all removable media.
3. Restart the computer to Safe Mode.
4. Reset the computers BIOS to the default values.
5. Restart the computer to the Last Known Good Configuration.
6. Disconnect all peripheral devices connected to the computer.
7. Remove any additional third-party cards that were installed in the computer.
8. Remove any additional RAM memory modules that have been added to the computer.
9. Remove and replace (reseat) the original RAM memory modules that came installed in the computer.
   

NOTE: Refer to the operating instructions supplied with the computer for specific information on how to install, remove or replace RAM memory modules.

The troubleshooting steps listed above should resolve your issue. If you have completed all of the steps and the issue is not resolved, service may be required.

2. The Windows freezes or stops responding frequently.

Cause:

This issue could be caused by any of the below possibilities.

1. Software related issue.
2. Driver related issue.
3. Operating system related issue.
4. Heat related issue.
5. Hardware issue.
6. Serious issue with Windows
7. Hardware failure.

Answer:

This article contains recommendations on what to do if the computer frequently freezes or completely halts. An easy way to determine if your computer is in this situation is by pressing the Num Lock button on the keyboard and watching the Num Lock led to see if it turns off and/or on.

If you're able to get the light to turn off an on, press CTRL + ALT + DEL and attempt to end task the program. Additional information about this can be found on document CHTSR. Otherwise continue reading this document.
Software related issue

A computer locking up or freezing is often is caused by a software related issue. If you're encountering lockups when the computer is opening a particular program, make sure you have all the latest updates for that program. You can find the latest updates for your software through the software developer or publisher.

Driver related issue

A computer lock up can also be caused by drivers. For example, if there is an issue that exists with your video drivers a computer could lock up while playing a game or displaying any other type of video. Make sure you have the latest drivers for all major devices in your computer (video, sound, modem, and network). A listing of driver related pages as well as driver related help can be found on our drivers page.

Operating system related issue

Make sure your operating system has all of the latest updates installed on it. Additional information about updating Windows can be found on document CH000545.

Heat related issue

If the computer processor is getting too hot it can cause the computer to freeze. If you have heard any abnormal noises coming from your computer recently such as a high squealing, this could indicate a fan may be failing in your computer.

You can first start by verifying the fan on the power supply is working by examining the back of the computer and seeing if the fan is moving and moving smoothly. For all other fans in the computer you will need to either open the computer and make sure the fan are working (processor fan and case fan) and/or if your BIOS monitors the RPM of the fans, enter BIOS and make sure the BIOS does not report any errors.

Users may also be able to determine how hot their computer is by onboard thermal sensors. If your computer comes equipped with these sensors, make sure your CPU is not running too hot.

Hardware issue

In addition to software, hardware can also cause a computer to lock. If you have recently added any new hardware into the computer, try temporarily removing it to make sure it is not the cause of your issue.

Before attempting to remove any hardware, make sure you are not encountering this issue because of hardware conflicts by viewing Device Manager for errors. Additional information about Device Manager can be found on our Device Manager page.

If you have not recently installed any new hardware into the computer, the next best solution to determining if this is a hardware issue would be remove any hardware on the computer that is not needed. For example, remove your modem, network card, sound card, and any other expansion cards that are not needed for the computer to operate. Run the computer without these cards to see if they are the cause of your issue.

Serious issue with Windows

If you have tried all the above recommendations and the computer continues to frequently lock up, its possible that Windows may be seriously corrupt. Try running through the basic troubleshooting steps for your version of Windows on our basic troubleshooting page. If these additional steps do not resolve your issue, we suggest you backup all information and erase and reinstall Windows on your computer.

Hardware failure

If after reinstalling your operating system, or during the installation of your operating system, your computer turns off abnormally, it is very likely that other hardware is failing in the computer. Often this is RAM, CPU, Motherboard, and/or Power Supply (in that order).

If you have extra available parts or have a friend or co-worker with a similar configuration that is willing to allow you to test their hardware in your computer, try swapping these parts to determine if they are at fault. Otherwise, you will need to have the computer serviced.

On Being a Computer Technician

Although I love computers, it never occurred in my mind that I will be troubleshooting computer as a job. Computer troubleshooting needs a lot of patience and I easily get bored. I don't even know the basic troubleshooting steps and I usually go to a computer shop if my laptop is not working properly. I don't have much background in the computer aside from using it to social networking ans doing my research papers. I only learned how to operate computer when I was in fourth year high school, just the basic operations of turning it on/off and creating a word document. Hahaha!

Well, we don't have computer at home and I go to computer shops when I have to research about my assignments and check my email. I bought my notebook when I was in my last year in college. The primary reason is obvious, I intend to use my laptop while doing my thesis. It is more convenient to write your ideas in a computer than using a bulks of paper.

My cousins Kuya Benj and Robert, who are siblings, are the one who taught me many things about computers. Kuya Benj is into website business while Robert took up computer course in college. They are different in approach, though. I learned basic hardware troubleshooting from Robert because it was his forte. On the other hand, Kuya Benj taught me how to explore networking and computer programs (softwares). He even showed me how to make money online in numerous ways.

I was doing my thesis and was running out of budget. I decided to look for a part-time job to support my schooling. Working in a call center is my best option because of its schedule. Most of my classes are during afternoon especially the major subjects and I can use my vacant morning time to sleep while working at night. But it was never easy to get a job in the so called "sunrise industry". I applied as customer service representatives in many call centers but I was never offered the job. It took me more than six months until I decided to change focus, I applied as a technical support representatives.

My first application is with Teleperformance since my older brother is working there. I went to its hiring office at EDSA Central, along the corners of Shaw Boulevard and EDSA. It was not meant for me. Next day, that was Friday, I went to Sitel in Ortigas and on that day, I was hired! I was overwhelmed yet nervous because I am not a techie person. Sitel offered me first a networking account, a dial-up internet, and was scheduled for final interview the next day. I arrived home almost midnight and while taking dinner, Sitel called me and asked me to come to their office for final interview in a computer troubleshooting account. I really need a job and I want to start as soon as possible. Aside from that, it is a Sony account. I did not think twice and hurriedly went back to Sitel even I'm not yet finished taking my dinner. It was a panel interview and it came out to be fun and inspiring. On that day, I officially joined the product training which lasted for five weeks.

After training we spent two weeks on A-bay where we spend four hours further training while taking calls for the rest of our shifts. I learned many new things during the training but taking calls exposed me to the actual working environment which taught me things I never learned during the training. More so when we finally transferred to the floor which they called production. Experience is still the best teacher. I learned also by observing my fellow agents how they handle the calls.

At first, I was like lost in the middle of the forest. We, the newbies, have been distributed to different teams. New faces, and I have to make effort again in going along well with my teammates. All of us (newbies) has a hardware split that's why most of our calls ended up for service or repair. My first month is really a disaster and I received hundred percent bad returns or NO RESOLVED surveys. I have resolved calls but I only received bad surveys. How unlucky, right?

It's been almost four months since I'm taking calls and I noticed that most of the hardware problems customers encountered is about the operating system and the hard drive. These includes not able to log in to windows, having a blank or black screen, and freezing computer.
We also often received networking and internet problems and maybe customers also view them as hardware related. Because of this, I requested a basic networking training from the operations manager.

Right now, I am more confident than before in troubleshooting the computer over the phone. On my next posts, I will write about some basic troubleshooting of the most common hardware problem.