Nilpo's Ultimate Windows Troubleshooting and Security Guide

The Window's Guru's original Windows Troubleshooting and Security Guide!

PC problems can be a huge nightmare. Finding the answers that you need can be even harder. I've put together some simple guides that can get you headed in the right direction. If these guides don't get you up and running feel free to post a thread in one of our forums.

Although this thread is being written as thoroughly as possible, please don't let that deter you from starting a thread of your own. Even if a solution here solves your problem, we'd still like for you to share your experience for the benefit of the group.

Things to Remember When Posting a Thread

1. Before posting, use the search box at the top of the page to see if we have had a thread dealing with your specific problem in the past. Replying to the same specific problems over and over again can become a tedious task. If you can't find a thread, or it doesn't fit your specific situation, feel free to start a new one in an appropriate forum. We're not here to send anyone away.
2. Please be as specific as possible when asking questions. Clear concise questions will get the the fastest most effective responses.
3. Describe your problem in detail. Please provide as much background information as possible to indicate when the problem started, what events led up to it, and how frequently the problem occurs. All of these details can be extemely helpful in properly diagnosing a problem. Always remember other members can't see what you see so you need to be as thorough and descriptive as possible.
4. List the hardware involved. Every PC is different and there are literally thousands of hardware combinations available. Whenever possible please provide both brand and model numbers for the hardware in your system. If you have a system from a large company like Dell or Gateway providing information such as Service Tag numbers can allow members to find specific information about your configuration.
5. Never post information that could reveal your personal identity unless your are comfortable with that risk. If a serial number or service tag number can reveal your identity, DO NOT POST IT. If you post screenshots of your problem, keep in mind that screenshots can reveal information such as user account names and IP addresses. You can edit or blur this information out before posting them. Several freeware image editing tools can be found in the Useful Freeware Database thread.
6. Post any errors or error information in their entirety including any text messages and error numbers (if any). If possible, indicate what program generated the error.
7. Post any related log files and information about what programs were running when the problems occurred. Information on how to export system event logs are provided in the posts below. You may be asked to run programs like HijackThis whose log files can be extremely helpful in diagnosing some problems.
8. Please be patient! It sometimes takes time to receive a response. This doesn't mean that we don't care.

And above all, please post back when you have found a solution that works. Not only do we like to know things worked out for you, but it may also be helpful for anyone else who comes along your thread with a similar issue.

For help on how to ask the right questions, check out this link provided by Quantum Skyline.

Good luck, and thanks for choosing DevH!

Contents:

Windows Troubleshooting Guide

• Troubleshooting BSOD's (Blue Screen Of Death)
• Troubleshooting a Non-Booting PC or Boot Errors
• Troubleshooting Random Reboots During Startup
• Troubleshooting Resource Conflicts
• Diagnosing a Sluggish or Slow PC
• Diagnosing a PC that Frequently Hangs or Freezes
• Dealing With Spyware, Adware, Viruses, and Other Malware
• Using Device Manager to Troubleshoot Hardware
• Using Dr. Watson for System Troubleshooting
• Using Windows Event Logs
• Using Windows Boot Logging
• Troubleshooting Windows Errors
• Other Miscellaneous or Program Specific Errors
• Troubleshooting Windows Installer Problems
• Using the Network Troubleshooter for Internet and Connectivity Problems
• Repairing Internet Explorer and Windows Explorer
• Troubleshooting Shutdown Issues
• Dealing With Random Problems and Glitches
• Additional Resources: Finding the Answers You Need
• Recovery Suggestions and Disaster Planning
• An Overview of Windows Troubleshooting and Recovery Tools
• What To Do When All Else Fails

Virus Removal Primer

• Updated Virus Removal Guide
• Sysclean Script
• Common Executable File Types
• Living In The Aftermath
• Online AV and Security Tools

Windows Security

• The Complete EFS (Encrypted File System) Tutorial

Other Contributions by Nilpo

• Index of Articles published by Developer Shed Network
• Index of topics for future articles.

Note:

The bulk of this guide is written for Windows XP, most of the steps outlined in this guide will work in other versions as well. It would be a tedious task to customize this guide for every version of Windows available. Some links for other Windows distributions have been provided. If this guide doesn't fit your particular setup, please open a thread with your issue and someone will be happy to give you a customized response.

Have you found this guide helpful?

Please take a moment and show your appreciation for the work involved in writing and maintaining this guide.

• If you believe this guide was helpful, please add to my reputation by clicking the button above one of the posts.
• Please take a moment to rate this thread. You can rate it by clicking the button in the blue bar above this thread.

  

Thanks for your support. I hope to bring more great guides as well.

If you like this guide, don't miss any of my articles on the Developer Shed network. Subscribe to the Live Feed

Need to link to this guide?

Don't try to remember the long URL. Just point your links to http://guide.nilpo.com!

When a Windows machine randomly reboots during the boot process, Windows will generally tell you what the problem is. Please complete the following steps before posting a thread. This will save time in diagnosing your problem.

What Is A Blue Screen of Death (BSOD)?

Most of the time when Windows reboots during the boot sequence, it will display an elusive BSOD (Blue Screen of Death) that contains the error information. Typically, this will flash too quickly for you to read before the computer restarts. Here is how to stop the system from restarting so that you can collect the error information.

Click here for an example blue screen from Windows XP.

1. Boot into Safe Mode by pressing F8 repeatedly during boot and selecting Start Windows in Safe Mode from the Advanced Boot Menu.
2. Right-click My Computer and choose Properties to open the System Properties dialog.
3. On the Advanced tab, click the Settings button under Startup and Recovery.
4. In the System failure section, remove the checkmark next to Automatically Restart.
5. Click OK twice to close all dialog boxes and restart normally.

Breaking The Code:

The Blue Screen contains very important information that should be included when you post your thread.

• The first is a textual error code. This will be located near the top of the screen and will appear in CAPS. Words will be separated with underscores (_) rather than spaces. Here is the text code from our example:
  Code:

  PAGE_DEFAULT_IN_NONPAGE_AREA

• The second is a hex code. This is the first line in the Technical information section and will generally be a Stop code. You should include the entire line. The error from our example is:
  Code:

  STOP: 0x000000050 (0xFD3094C2, 0x00000001, 0xFBFE7617, 0x00000000)

• The third is optional since it will not appear for every error. This is located at the bottom of the blue screen and indicates the file that caused the error and, typically, the memory address where the error occurred. Our example shows:
  Code:

  SPCMDCON.SYS - Address FBE7617 base at FBFE5000, DateStamp 3d6dd67c

All three pieces of information (or as many as possible) should be included when opening a thread or posting your problem.

If your computer randomly reboots without displaying a BSOD, this indicates a hardware failure. While this is typically a failing PSU (Power Supply Unit) it can often be other hardware as well. When posting in this instance, be sure to include as much information about your hardware and system configuration as possible. Wherever possible you should indicate brands and model numbers for all of the system components.

It also helps to know if this problem has occurred before and with what kind of frequency. Typically, these problems will begin intermittently and progressively become worse.

Additional information may also be found in the system Event Logs or in the Boot Log if enabled. The following posts will describe how to enable these logs and use the information they contain.

Armed with this information we can better help you diagnose your problem and get you up and running more quickly.

Thanks for choosing DevH and remember to stop by often.

Click here for a description of the BSOD and it's purpose.

Additional Resources:

Troubleshooting Windows Stop Messages (Author's Choice )
Windows XP Professional Resource Kit: Understanding the Startup Process
Windows XP Events and Errors Database
Interpreting Bug Check Codes

Direct Link: http://guide.nilpo.com/bsod

Windows keeps event logs that can be useful in identifying problems. You can view these event logs using the Event Viewer. The following example will show you how to troubleshoot an example event (failing hard drive).

1. Open Administrative Tools in the Control Panel. This will differ slightly depending on your Start Menu settings. Typically, you will click the Start Button, choose Control Panel, click Performance and Maintenance, click Administrative Tools, then double-click Event Viewer. (You can also open the Event Viewer by eventvwr.msc in the Run dialog.)
2. In the left-hand pane of the Event Viewer, select the Event Log you wish to investigate. (In our example, we'll be using the System log.) screenshot
3. Double-click the event in question to view the Event Properties. screenshot
4. Click the link in the Description box to open the event's details in the Help and Support Center. You may see a security dialog box warning you that information is being sent over the internet, if so, click OK to continue. screenshot
5. The Error Details that are displayed by the Help and Support Center can be used to further research the error. Resource links will be provided below. For now, scroll down to the User Action section to see the recommended fix. In our example, we had a IO_ERR_BAD_BLOCK error. The recommended action was to replace a failing hard drive. screenshot

The event logs can be extremely useful in diagnosing and troubleshooting problems. They will also contain warnings that can help indicates problems before they happen.

How to Export the Event Log Contents:

With the Event Viewer open, select the log you would like to export in the left pane. Select Export List... from the Action menu to save a tab-delimited text file of your event log. screenshot

Additional Resources:

Windows Events and Error Messages Center Search
Event Search at EventID.net
Deciphering Windows Error Messages
EventLogScan.com - Scan your security event log online!

Direct Link: http://guide.nilpo.com/eventlogs

Windows Boot Logging can be an effective way to diagnost startup issues. Boot with any of the Windows Safe Mode options will enable boot logging automatically, however, it can also be enable in Normal mode as well.

Enabling Boot Logging - Method 1:

1. Click the Start button and enter msconfig in the Run dialog to start the System Configuration Utility.
2. Click the Boot.ini tab and select your Windows installation. An example has been provided. screenshot
3. Put a checkmark next to /bootlog.
4. Press Apply and OK and restart your computer for changes to take affect.

Enabling Boot Logging - Method 2:

1. Restart the computer and press F8 when prompted.
2. On the Windows Advanced Options Menu, select Enable Boot Logging.

Enabling boot logging will cause Windows to create a log file of the boot process. The default location for the log file is:

C:\Windows\Ntbtlog.txt Click here for an example log file.

The log file will specify the time of startup and the location of all drivers that were loaded. It will also note any drivers that were not successfully loaded. This log file can be used with other tools such as the System Event Viewer to locate problems.

Programs like Boot Log Analyzer can help you use your boot log more effectively.

Additional Resources:

Available Switch Options for the Windows XP Boot.ini File
Ntbtlog.txt File Not Written When Boot Logging Is Enabled

Direct Link: http://guide.nilpo.com/bootlog

So what do you do when you're not having a Windows specific problem? Perhaps, you're receiving an error from another program. The following links will guide you to some other common troublespots.

Additional Resources:

Windows Installer Error Reference
Program: Error Messages For Windows
Error code information for Windows Media Player 9 Series
File Download: Windows XP Device Manager Error Code Help File (free membership required)
Program: WinErrs
Microsoft Outlook and Outlook Express Error Codes
InstallShield Error Codes

Direct Link: http://guide.nilpo.com/programerrors

The Device Manager can be a very useful tool in diagnosing hardware related problems such as hardware failures, resource conflicts, and firmware or driver conflicts. Learning to make use of the Device Manager can greatly reduce diagnostic times and increase overall system performance. Here are some common uses of the Device Manager.

Troubleshooting Hardware:
The Device Manager's primary function is to provide an interface for diagnosing and troubleshooting your system's hardware. Right-clicking any device and choosing Properties will open the devices Properties dialog. From here, you can access many of the Device Manager's tools.

On the General tab, the Device Status box will indicate any problems with your device. The links below can be used to identify the specific error code. Beneath the Device Status box you will also find a Troublehoot button. Clicking this button will start Windows' Hardware Device Troubleshooter which can be very useful in identifying configuration problems and failing hardware.

Working With Device Drivers:
In order for your system to use installed hardware, it must have a valid device driver for it. Drivers are generally provided by your hardware manufacturer when you purchase your hardware, but they are often updated frequently. You should always be sure to use the latest driver available for the best performance. The Device Manager makes working with drivers very easy. After downloading the latest driver release from your hardware manufacturer's website, follow the following steps to install your updated driver.

1. Right-click My Computer and choose Properties (or press the Windows key and Pause/Break at the same time) to open the System Properties dialog box.
2. Select the Hardware tab and click the Device Manager button to open the Device Manager.
3. Expand the category for the device you wish to update by clicking the + sign, and select the device you wish to update.
4. Right-click the device and choose Properties to open the device's Properties dialog box.
5. Select the driver tab.
6. In this view, you can see the currently installed driver version and provider information. Click the Update Driver button to begin the Hardware Update Wizard.

It is also a good idea to ensure that any software or hardware was designed to work with your Windows version. Microsoft provides a constant database of certified software and hardware components that meet its standards.

Windows Catalog and Hardware Compatibility List

Verifying Unsigned Drivers:
Digital signing is an added security feature used to ensure that you are using an original device driver. This helps ensure that your driver comes from a credible source and that it is not corrupt. You should always use signed drivers whenever possible. The following link will guide you through verifying a driver's signature.

How to Use Driver Verifier to Troubleshoot Windows Drivers

Rolling Back Drivers:
Whenever you use the Hardware Update Wizard to install or update device drivers, a backup of any existing driver is created in the event that the new driver is corrupt or incompatible. Windows makes it very simple to roll back to a previous driver in case of a problem.

How To Roll Back A Device Driver
Using Windows XP Device Driver Rollback Beats BSOD

Identifying System Resource Usage:
In order for hardware components to function they must make use of system resources such as memory. Each device is assigned certain resources that it is allowed to use. Sometimes incompatible devices are assigned the same resources causing a resource conflict. The Device Manager provides an easy way to identify the resources in use by a specific device. Power users can also use this information to customize how resources are used and use the information to increase hardware and system performance and also to increase system stability.

In a device's properties dialog, you can click the Resources tab to view the resource information for that device. This view not only shows what specific resources are reserved for that device but also any conflicts there may be.

Printing a Device Manger Report:
The Device Manager also has the ability to print reports about your hardware configuration. This can be useful for documenting a system configuration, identifying problems, and for submitting when requesting help with device issues.

How To Print a Device Manager Report in Windows XP

Other Resources:

Troubleshooting Device Manager Issues in Win XP
HOW TO: Manage Devices in Windows XP
Troubleshooting Device Conflicts With Device Manager
Explanation of error codes generated by Device Manager in Microsoft Windows XP Professional
A downloadable error code database can be found here
How to Identify Unknown Devices Listed In Device Manager

Direct Link: http://guide.nilpo.com/devicemanager

A broken internet connection or lost network connection can make for a bad day. With so many different possibilities ranging from confguration problems to hardware failures it can often be difficult and time consuming trying to resolve the problem. Windows provides a tool called the Network Troubleshooter that can help identify potential trouble spots.

How to troubleshoot home networking in Windows XP

Additional Resources:

Windowx XP and Windows 2003 Network Problem Solver (Requires IE6+)
Troubleshooting Internet Connection Problems
Troubleshooting Network and Internet Connections
Troubleshooting Internet Connection Sharing in Windows XP

For help installing a network, check out the excellent Home Networking with Windows XP guide by moistmule.
Also, check out my guide How To Diagnose a Slow or Broken Connection.

Direct Link: http://guide.nilpo.com/nettroubleshooter

Dr. Watson for Windows is a program debugger that ships with all Windows versions. This tool can be a very effective way to troubleshoot program errors.

Anytime a program error occurs, for instance when a program terminates or becomes unresponsive, Dr. Watson is started automatically and a log of the problem is created. This log can be a great aide in resolving the problem. The links below will help you use the Dr. Watson and the Dr. Watson log more effectively.

The default location of the Dr. Watson log is:
C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\drwtsn32.log
Click here for an example log file

An error dump called user.dmp may also be created. This is a binary memory dump file.

Additional Resources:

Dr. Watson Overview
Description of the Dr. Watson for Windows Tool (Windows NT+)
Description of the Dr. Watson Tool (Windows 9x)
Using the Dr. Watson Log File
How to Troubleshoot Program Faults with Dr. Watson
Dr. Watson Does Not Collect Program Fault Information
Dr. Watson May Not Create a User.dmp File for an Application Error

Direct Link: http://guide.nilpo.com/drwatson

Many Internet Explorer and Windows Explorer problems already have fixes available. Run Windows Update to ensure that you have the latest patches and hotfixes installed.

Internet Explorer and Windows Explorer errors can stem from a variety of different places. Incorrect system configurations, spyware/adware, viruses, and failing hardware can all cause unexpected behavior.

Various tools are availabe below for fixing general problems. Specific problems can be googled. I'll touch on some of the more common ones below.

Internet Explorer Opens Blank Pages:
This issue is generally caused when system files used by Internet Explorer become corrupt or changed. Replacing and re-registering these files will generally fix the problem.

Internet Explorer opens blank pages

Windows Explorer Causes an "Invalid Page Fault" When Using Thumbnail View:
This problem can occur when the Thumbs.db file in a particular folder becomes corrupt. A fix can be found in this Knowledgebase Article.

Windows Explorer Needs to Close When Viewing My Network Places:
This problem can occur when using printers that do not support printer sharing on a home network. One resolution can be found here.

Explorer.exe Repeatedly Quits Unexpectedly:
There can be a number of causes for this problem. Cleaning your system of spyware/adware and running a full AV scan can relieve this problem. Other issues can be found here.

Additional Resources:

Description of the Internet Explorer Repair Tool
IEFix - General Purpose Fix for Internet Explorer
Troubleshooting Windows Explorer Errors
How to reinstall or repair Internet Explorer and Outlook Express in Windows XP

Direct Link: http://guide.nilpo.com/explorer

Errors that occur during software installations can be difficult to figure out. They can range from insufficient resources, locked memory, and hardware problems. The errors generated by Windows Installer and the system event logs can prove useful in determining the problem.

Many issues with Windows Installer arise when trying to reinstall a program that has been removed. In this case, part of the previous install process may still remain in the registry. Microsoft provides a tool for removing these old traces.

Windows Installer CleanUp Utility

When having problems installing software, it's usually good to run Windows Update and update device drivers prior to the installation.

Don't forget, you should always create a restore point or backup before new software or making hardware changes.

Windows Installer Error Messages
Windows Installer Error Codes
Windows Installer Error Reference

NOTE:
The information in the above links only applies to installations based on the Windows Installer.

Direct Link: http://guide.nilpo.com/windowsinstaller

Troubleshooting shutdown issues can be a very tedious task. There are hundreds of possibilities that can cause your computer to shutdown slowly. Hanging or unresponsive programs are the most common cause, however, failing hardware is also very common.

Some Typical Causes of Slow Shutdown:

• If you have an nVidia graphics card installed...
  Type Services.msc in the Run... dialog and disable Nvidia Driver Helper service.
  
• Disable Terminal Services
  Type Services.msc in the Run... dialog and disable Terminal Services. Note that Terminal Services is required by Remote Assistance, Fast User Switching, and (in XP Pro) Remote Desktop.
  
• Windows is set to clear the Pagefile
  Type gpedit.msc in the Run... dialog and drill down to Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options and check if Shutdown: Clear virtual memory pagefile is enabled. This is rare since the Windows default is disabled, but some programs like Privacy Eraser enable this automatically.
  
• iTunes for Windows
  The GEARSEC.exe service that is used by iTunes has been known to prolong system shutdown. The only fix is to end the service (net stop gearsecurity from the Run... dialog) prior to shutting down. A shutdown script for this could come in handy.
  
• Hardware Issues
  You can narrow your search down to hardware related issues by disabling Event Logging (from services.msc) and seeing if shutdown speeds improve. If they do, start diagnosing your hardware and/or updating hardware drivers. Your event log can help point you toward the culprit. The speed improvement is gained because Windows does not stop to log every error. The event log should be reenabled after this test.
  
• Hanging or Nonresponsive Programs
  Some programs or services may hang at shutdown. You can tell Windows to automatically end these tasks and set the default time to wait before ending them. Type regedit in the Run... dialog box to open the Registry Editor. Navigate to HKEY_CURRENT_USER\Control Panel\Desktop. Set the value for AutoEndTasks to 1. (1 is enabled, 0 is disabled.) Set the value for WaitToKillAppTimeout to the number of milliseconds to wait before ending the program. The default is 20000 (20 seconds). This is the most common problem when slow shutdowns only affect one user on a machine.
  
• Roxio CD Creator 5
  A known problem bug in Roxio Easy CD Creator 5 has been known to cause shutdown problems. This bug also effects the Platinum version of the popular software. A patch can be download from the Roxio website to fix the problem.
  
• ACPI Support
  Windows XP has never support ACPI technology very well. Motherboard manufacturers have become aware of these limitations so updating your motherboard BIOS to the latest available version can resolve these issues. Check your board manufacturers website for a download and instructions.
  
• Updated Hardware Drivers
  If you had hardware installed with "unsigned" drivers and recently updated to "signed" drivers or vice versa you may experience shutdown issues. Try removing the device and only installing the new driver. Avoid installing signed or unsigned drivers over top of their counterpart when using the update feature.
  
• Window's CD Burning Feature
  Explorer.exe can become nonresponsive at shutdown during sessions when Windows built in CD burning features were used. Follow the step above for ending nonresponsive programs.
  
• Resource Conflicts
  Two or more hardware devices sharing the same IRQ, Ram, or DMA resource can cause a conflict. Use msinfo32 from the Run... dialog to start the System Information Tool. Navigate to Hardware Resources > Conflict/Sharing and look for red X's. A specific example of this is documented in this Microsoft Knowledgebase Article.
  
• Fast User Switching
  Some shutdown issues have been documented on machines that have Fast User Switching Enabled when more than one user logs on and then log off in a different order. Disabling Fast User Switching will eliminate this problem. Microsoft has noted this bug.

DevH Thread: WinXP needs 15min to shut down

Windows Restarts Instead of Shutting Down:

Sometimes Windows may restart instead of shutting down. This typically happens when your system has a STOP 0x0000000a error while the "Automatically Restart [on System Failure]" option is set in your system properties. You can see this to disable that option. However, you need to resolve the STOP error to fix the problem. This happens on system that have Roxio Easy CD Creator installed. The resolution can be found in this Microsoft Knowledgebase Article.

Shutdown Hangs or Your System Stops Responding During Shutdown:

Sometimes your system will just refuse to shut down. This can happen when Windows doesn't properly unload from memory or when it cannot end certain running processes. Various hardware failures or corrupt drivers can also cause these symptoms.

Try uninstalling any newly installed hardware or software or returning to a previous restore point before the problem occured. Make sure that your are running the latest available drivers for your hardware. The items below can help you pinpoint an actual problem.

Other Ways to Identify Problems:

• Enable the Shutdown Event Tracker in Windows XP Professional and higher. This logs the reason for every shutdown. This tool is used to monitor shutdowns by requiring a reason to be given. More information on how to use it in this Knowledgebase Article.
• In Windows 2000 you can configure Windows so that you receive verbose startup, shutdown, logon, and logoff status messages. This makes it possible to tell exactly at what point problems occur. Learn more in this Knowledgebase Article.

Additional Resources:

Windows XP Shutdown Troubleshooter
Windows Shutdown Troubleshooter (Windows 95/98/ME)
Computer Hangs During Shutdown or Displays a "Cannot Find Enough Free Resources" Error Message
Windows XP restarts when you try to shut down your computer
Windows stops responding during Windows XP shut down

Direct Link: http://guide.nilpo.com/shutdown

A resource conflict occurs when two or more devices try to use the same system resources, such as IRQ or Memory Address, at the same time. Modern Windows versions are generally very good at handling resource requests and configurations for you. However, it's not always that easy. Resource conflicts have taken on seemingly legendary status. In the old days, they were difficult to diagnose, but today that is no longer a problem. They are both quick and relatively easy to fix.

How To Identify Possible Resource Conflicts:

Typical symptoms of a resource conflict can include a popping or cracking sound from your computer's speakers, unresponsive or non-working hardware, and extremely slow system performance when accessing specific hardware. Frequent system crashes when accessing specific hardware is also a good indicator of a conflict.

Locating the Conflict:

If you suspect a certain hardware device as being the culprit, viwiing it's status in Device Manager will reveal any conflicts. However, if you do not know where to begin, the System Information tool can be quite useful.

1. Click the Start button and choose Run...
2. Type msinfo32 in the Run dialog and press enter to open the System Information tool.
3. In the left-hand pane, expand Hardware Resources and then select Conflicts/Sharing.
4. Any conflicts will be noted in the shared resources information.

Resolving the Conflict:

If the trouble device is Plug-N-Play compatible, uninstalling and reinstalling the device is the simplest way to resolve conflicts. If that does not work you will have to manually set the resource settings for one or more devices. You might also try removing the device in Device Manager and letting Windows auto-detect it again.

Additional Resources:

Resolving Hardware Conflicts
Troubleshooting Device Conflicts With Device Manager
A General Description of IRQ Sharing in Windows XP
Unable to change resource settings in Windows XP Device Manager

Direct Link: http://guide.nilpo.com/resourceconflicts

A PC that will not boot can be the beginning of a very bad day. There can be many causes from hardware failures to software conflicts that can cause your PC to become useless. Here are some commonly occurring problems and how to troubleshoot and fix them.

Troubleshooting A PC That Won't Turn On:

You press the power button and nothing happens. Now what? First, begin with the basics.

1. Your computer needs electricity to operate. Check your PC's connectivity. Make sure that all necessary power cords are securely plugged in to a working power outlet. If you don't have a receptacle tester you can use a lamp or other small electrical device to make sure that the outlet is working properly. If a plug does not fit snugly into an outlet or if the outlet is loose in the wall, DISCONTINUE USE IMMEDIATELY. Faulty wiring can cause fires, electric shock and even death. You should also avoid using outlets that are not properly grounded.
   
2. If your electrical outlet is working properly, check the power cord. Examine the power cord for any nicks or cuts in the insulation. You should also check the cord for loose contacts and severe bends or crimps. If the cord is in good condition, try it in another device such as a monitor or use the cord from another working device in your PC. If you are plugging into a power strip or UPS unit, try plugging directly into the wall. Mark any bad equipment or cords and properly dispose of them immediately. Faulty equipment or cords are a very dangerous electrical hazard.
   Editor's Note - Cutting the plug off of faulty power cords, power strips, and unserviceable equipment is a good way to prevent someone else from trying to use unsafe items
   
3. If all electrical sources are in good working order, carefully remove the side panel from your PC tower. (Removing the side panel may void some manufacturer's warranties.) It is typically secured by a couple small screws or plastic latches. Some panels may fit very tightly, but you should never try forcing or prying them off. With the side panel off, press the power button to see if any fans begin moving, most importantly the ones in the PSU (Power Supply Unit). Many newer motherboards also have a small green LED to indicate power connection. Some systems also have safety switches (interlocks) that the side panel would hold closed. These need to be held in in order for the power to turn on. Hold them with your hand or a wooden clothes pin.
   
4. If your PC has a built in system speaker or buzzer (most do), listen for beeps. If you don't hear anything this indicates a bad power supply or a bad power switch. Try switching the power switch with the reset switch by changing their positions on the motherboard. Check your motherboard's documentation for the proper connections. Always remove the power cord from the back of your computer and make sure you are free of static before touching any components inside your PC. Use of an anti-static wrist strap is highly recommended.
   
5. Test your power supply. You can get a decent power supply tester for around $10 that will tell you if your power supply is working or not. You can also switch your power supply for a known good one and see if your system will turn on. Also be sure that your power supply's 12V connector is firmly attached to the motherboard. Loose or broken connectors should be replaced immediately to prevent further damage.
   
6. If your computer still will not turn on, the problem is most likely a failed motherboard. Visually check your motherboard for any burnt or dark areas, cracks, or loose or broken components. A faulty motherboard should be replaced immediately. If you are still unable to determine a cause, have your system evaluated by a trained professional with the proper testing equipment.

Using BIOS Beep Codes and POST Results:

Every system BIOS performs a POST, or Power On Self Test, when the computer is turned on. The intial hardware test will return audible beeps to indicate the results. While most are fairly similar, each company has their own beep codes. Check your BIOS manufacturer's website for those codes. Links to the most common companies are provided below. Beep codes will generally indicate hardware failures. If you suspect that hardware is failing, double check to make sure that it is properly installed. If the hardware connects in a slot such as a PCI or AGP slot, be sure that it is properly seated. This also applies to RAM modules and processors. Be sure any required cables are firmly plugged into the appropriate connections. If all seems wel, then the hardware is most likely bad and should be replaced.

The POST sequence continues with other tests that will display on-screen errors. These errors should be noted. You can typically find the meaning of these errors in your motherboard documentation or on your motherboard manufacturer's website.

BIOS Beep Code References:

http://www.pchell.com/hardware/beepcodes.shtml
http://www.bioscentral.com/
http://www.pcguide.com/ts/x/sys/beep/index.htm
http://networking.ringofsaturn.com/PC/beep.php

Common Boot Errors:

• Non-system disk or disk error
  Replace and press any key when ready
  Typically, this means that you are trying to boot your computer with a non-bootable floppy disk in the floppy disk drive. Remove the disk and reboot. If you do not have a floppy disk in the drive, be sure that your BIOS boot priority options are set correctly and then try the resolutions under Invalid System Disk to repair the MBR on your boot device. If you are trying to boot from a bootable floppy, be sure the floppy is the correct format for your system and/or recreate the floppy. If the floppy is bootable this indicates an incorrect file system format or a corrupt floppy boot sector. Reformatting the disk from Windows should resolve the problem.
  
• Invalid System Disk
  The Invalid System Disk error is a BIOS error, not a Windows error. This error indicates that the BIOS could not locate a valid boot device. In other words, it could not find an MBR (Master Boot Record) on any of your storage devices. Repairing or replacing the MBR will fix this problem. On a Win9x/ME machine, you can simply boot to a DOS Floppy and use the fdisk /mbr command. Windows 2000 and higher will require the use of the Recovery Console.
  
• UNMOUNTABLE_BOOT_VOLUME
  This error commonly has two causes. If your computer is configured to uses UDMA, be sure that your hard drive is connected with an 80-pin UDMA connector, and reset your BIOS to Fail-Safe options. Otherwise, this error indicates a damaged filesystem. Use your XP cd to boot into the Recovery Console and run chkdsk /r to repair the filesystem. If that does not work, load the Recovery Console again and run fixboot.
  
• Operating System Not Found
  After POST, the BIOS attempts to pass control to the operating system. This error occurs when the BIOS cannot find the operating system kernel in the active partition. Possible causes can be a filesystem error, invalid MBR, an incorrectly configured boot.ini file, or you are attempting to boot from a partition that is not set as bootable. If this is a new drive, make sure that the ctive partition is set to bootable. If this is an existing installation, it could be indicative of hard drive failure. Running fixmbr from the Recovery Console and verifying the boot.ini file can resolve this issue. In older versions of Windows, use a Windows 98 boot disk and run fdisk /mbr.
  
• Memory Size Mismatch
  This error is generated by the CMOS. It indicates that there is a problem with the system RAM. If you have recently added or removed RAM from your machine, be sure that it is compatible with your board and installed properly. If it is, double check your CMOS settings. If you have not added or removed memory from your system, this usually indicated a failing RAM module or mortherboard.
  
• No Boot Device or Boot Device Missing
  This happens when the BIOS cannot find a bootable device in your system. Make sure that the BIOS boot order is set correctly and that your bootable devices are installed correctly. This can also indicate a problem with the Master Boot Record on your primary drive.
  
• Checksum Errors
  A BIOS checksum error will generally indicate a failed BIOS chip on your motherboard. A CMOS checksum error generally indicated incorrect CMOS settings. Using the jumper on your motherboard to clear settings or removing the CMOS battery for a few minutes will usually resolve this issue.
  
• Windows could not start because the following file is missing or corrupt.
  Windows root\system32\hal.dll.
  Please re-install a copy of the above file.
  This error occurs when Windows attempts to load a Hardware Abstract Layer is that is incorrect, corrupt, or missing. Replacing the correct HAL from the Windows CD can resolve the issue. However, choosing the proper one can sometims be tricky. Seek outside help if needed. This can also be cause by an incorrect boot.ini file. Try running the following from the Recovery Console:

  Attrib -H -R -S C:\Boot.ini
  DEL C:\Boot.ini
  BootCfg /Rebuild
  Fixboot

  If that is unsuccessful (and you have installed either SP1 or SP2) you can recover using a backup that was created when the service pack was installed. You will need to boot with a standalone CD or mount the drive as a slave in another machine to do this. A working copy of the hal.dll file can be found in WINDOWS\ServicePackFiles\i386 on the drive. If you do not have this backup you will need to replace it with the appropriate HAL from your Windows CD renaming it to Hal.dll if necessary.
  
• Windows XP could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM
  This error occurs when the SYSTEM hive in your local registry becomes corrupt. You can replace the registry files with backups by following the instructions in MSKB: Q307545.
  
• Windows NT could not start because the following file is missing or corrupt:
  Winnt_root\System32\Ntoskrnl.exe
  Please re-install a copy of the above file.
  In Windows XP, you should first attept to boot using the Last Known Good Configuration option. This will usually work. Otherwise this error indicates a problem with the boot.ini file, a missing kernel file, or a corrupt filesystem. You can rebuild the boot.ini file from the recovery console or expand the required file from your Windows CD.
  
• NTLDR is missing
  This indicates a problem with the boot.ini file or that the NTLDR or ntdetect.com file(s) are corrupt. Repairing the boot.ini file or replacing the appropriate files from you Windows CD will resolve this issue.
  
• Boot stops at a black screen with a blinking white cursor in the upper left corner
  This happens when the BIOS attempts to load an MBR that it cannot recognize. Reset your BIOS default and make sure that the drive is properly bootable.

Additional Boot Errors can be found here.

Your PC Freezes or Hangs During Boot:

When a PC hangs or freezes during boot this usually indicates either corrupt startup files or corrupt device drivers. Try booting into Safe Mode and see if boot completes successfully. If it does, disable any uneeded startup items.

Typically, the PC does not actually hang. It will usually load eventually. Try walking away from the computer and seeing if the boot finishes. In some cases this has taken up to a couple of hours. The bootlog or event log can lead to the culprit. Update device drivers and run sfc /scannow from the Command Prompt. If this does not work check for failing hardware and reintall Windows as a last resort.

Additional Resources:

Real World Technologies' Boot-Up Troubleshooting Cookbook

Direct Link: http://guide.nilpo.com/startup

Diagnosing a sluggish or slow PC can be a drag. Anything from installed software to failing hardware can affect your PC's performance drastically. Here are some tips for bring that PC back to life.

Eliminating Unnecessary Services:

You have to understand that your computer only has so many resources available. Your CPU is only so fast, there is only so much RAM, and your paging file is only so big. With these limitations, you have to make wise use of them. System services are programs that run in the background anytime your PC is turned on. Many of these support the operating system and are required, but many are not. Microsoft doesn't always know what is best for us. You can disable any services you don't need and free up some of those wasted resources. A complete list of all the Windows XP services can be found here. Another great guide can be found here.

Windows XP Services that can be disabled (PDF by TechRepublic)

Ugrade You Hardware:

Computer programs today are much more intensive than they were months or even years ago. From time to time you will need to upgrade your hardware in order to maintain decent performance. The most common, and probably cheapest, upgrade is your system RAM. RAM, often referred to as memory, is key to proper system performance. Every active program is running on your PC is loaded into memory. The more available, the better. And don't cheap out. Name brand memory modules will perform much better than "value" modules. Upgrading your CPU and motherboard periodically is also recommended. While you're inside your case adding your new hardware, don't forget to periodically replace any ribbon cables. A failing power supply may also affect system performance.

Update Windows:

Windows Update will ensure that you are always running the latest, most stable copies of your system files. It will also plug known security holes. You can run the Windows Update tool from the All Programs group on your Start Menu or use Internet Explorer and visit the Microsoft Windows Update website.

Free Up Disk Space:

The more junk you have on your hard drive, the longer it takes to find and load programs and files. Uninstall any unused applications, and delete any uneeded files. Storing lots of photos, mp3's, or other files? Try compressing them so that they take up less space. Periodically reintalling your OS can have dramatic results as well. This will remove any old and unneeded system files as well as rebuilding a clean registry. Consider using a second hard drive for storage to keep the size of your working hard drive as small as possible.

Remove Spyware, Malware, and Viruses:

These types of processes can be very hard to find in your system. Having spyware, adware, or viruses on your system will result in very poor performance. Regularly run a full AV scan and spyware scan to keep your system clean and healthy. The links below will provide several options for doing this. For more detailed information check out Nilpo's Updated! Virus Removal Primer. Another great resource is A Windows XP Optimization Guide.

• Spyware Removers
  Lavasoft Ad-Aware SE {free/commercial)
  Spybot Search & Destroy (free)
  Webroot's SpySweeper (commercial)
  Windows Defender (Beta 2) (free)
  Microsoft's Malicious Software Removal Tool (free)
• Popular Antivirus Packages
  Grisoft AVG Anti Virus (free/commercial)
  Symantec (Norton) Antivirus (commercial)
  McAfee VirusScan (commercial)
  Trend Micro's PC-Cillin (commercial)
  eTrust ezAntivirus (commercial)
  F-Secure Anti-Virus (commercial)
  Panda Antivirus (commercial)
• Online Tools
  Microsoft's Malicious Software Removal Tool Online
  Windows Live Safety Center
  A full list of online tools can be found here

Defragment Your Hard Drives:

Over time your hard drive can become fragmented. This happens as files are deleted and overwritten. If fragmentation is severe enough this can cause serious performance issues. Programs will open slower, the paging file will take longer to access, and overall transfer speeds will seem to crawl. You can use Windows' own built in defragmenter or download a third-party one at your own discretion.

Enable Disk Caching:

Most modern hard disk have an internal cache. This cache is a small bit of RAM on the hard drive used to index recent or often accessed information. Enabling this features can dramatically improve drive search times when performing common tasks. This Knowledgebase Article describes how to enable the disk caching feature. You should note that enabling disk caching can post a risk for possible data loss if the the drive loses power. This risks are further explained here.

Control Your Startup Tasks:

The programs that start when your computer boots are known as tasks. As you install more and more programs on your computer, often your task list can become quite large. Many of these programs are not needed at Windows startup and can be safely disable. Several freeware programs are available to aid in this task. Stop by The Useful Freeware Database for several suggestions. For help identifying startup tasks try Startup Programs and Executables Listings or Task List Programs.

Update the BIOS:

The BIOS is a memory chip located on your motherboard. It contains all of the basic input/output instructions that make your hardware work. The BIOS version on your motherboard may not always support the latest capabilities of your hardware, and in some cases, may not be compatible at all. Updating the BIOS regularly will keep your hardware working together more smoothly. Visit your motherboard manufacturer's website for the latest stable BIOS release. For a list of hardware manufacturer's websites, try your favorite search engine or check out Nilpo's "Abridged" Bookmarks.

Enable DMA or UDMA:

Most modern hard drives and optical drives support DMA, or Direct Memory Access. DMA is a feature that allows your drive to transfer data into memory without involving your CPU. This means it's both faster and less intensive on your system. Making sure this feature is enabled on all drives that support it can take a tremendous load off of your computer's processor. In Windows XP, DMA is enabled automatically on drives that support it, but it can sometimes become disabled. You can re-enable it in the Device Manager from the Properites dialog of your drive's controller.

Optimize the System Registry:

The registry is a central location for storing system settings. It spans across several files, but appears as one storage unit. Applications add settings to the registry all of the time. However, these settings aren't always removed when programs are uninstalled. Use a program like Tweaknow's RegCleaner Standard or Jouni Vuoro's RegCleaner (last freeware edition) to keep your registry as slim as possible.

Another thing to keep in mind is that the registry is a combination of files. As information is added and deleted from these files they will often become fragmented resulting in slower system performance due to the fact that it takes longer for Windows to locate the information it needs. Using a program like NTREGOPT will keep your registry files degragmented for the best system performance.

Optimize Video Settings:

Your video display is probably the intensive part of your overall system performance. Always use the latest drivers available from your graphics card manufacturer to ensure that your video hardware is running at it's peak performance level. You should also configure Windows to make the most of your hardware's capabiltiies to take some stress off of other areas of your system. One way to do that is too make sure that Windows is making full use of the hardware's acceleration.

1. Right-click the Desktop and choose Properties to open the Display Properties dialog.
2. Click the Settings tab and then the Advanced button to open the Advanced Properties dialog for your video hardware.
3. Click the Troubleshoot tab and make sure that the Hardware Acceleration slider is moved all the way over to Full.
4. Click OK to close all dialog boxes.

If this settings is too high for your hardware is can cause system instability. If this happens, move the slider down one position at a time until the problem is solved.

Disable GUI Effects:

Windows XP comes with all kinds of nice pretty effects and animations for the various menus. Disabling these will take some toll off of your system.

1. Right-click My Computer and choose Properties to open ths System Properties dialog.
2. Select the Advanced tab and click the Settings button in the Performance section to open the Performance Options dialog.
3. On the Visual Effects tab, select Custom and remove all of the checkmarks from the checkboxes.
4. Click OK to close all dialog boxes.

You should also consider using the Classic Start Menu instead of the Windows XP Start Menu because it uses less graphics. You can change this in the Taskbar and Start Menu Properties dialog by right-clicking the Taskbar and choosing Properties.

Uninstall Unused Fonts:

When Windows loads it loads every font installed on your system into memory regardless of whether or not they are being used. Deleting or moving unused or uneeded fonts from the Fonts folder in your Windows directory will increase system performance. You can double-click most fonts for a preview or try a third-party font manager such as FontFinder 32.

Clean Your Desk!:

Just like having a messy desk makes any office less productive, having a cluttered Desktop will make Windows perform slower. Group desktop items into meaningful folders or use the Desktop Cleanup Wizard to remove some old or unused icons.

1. Right-click the Desktop and choose Properties to launch the Display Properties dialog.
2. Select the Desktop tab and click the Customize Desktop... button to open the Desktop items dialog.
3. Click the button labelled Clean Desktop Now to start the wizard.

Additional Resources:

PC Pitstop: Free PC Diagnostics, computer help, and Tuneups
Ten ways to troubleshoot a slow PC
OptimizeXP

Over time, every computer begins to perform slower. Wearing hardware, system changes, and installed programs are just a few of the culprits. Using these tips will help you get maximum performance and maximum life out of your investment.

Direct Link: http://guide.nilpo.com/slowpc

A PC that frequently hangs or freezes is unreliable and relatively useless. When a PC hangs, it's usually because it is waiting for system resources to become available or because and unrecoverable program error has occured.

After a crash, first end any uneeded programs running on your computer to eliminate the possibility of a subsequent crash. So, first things first, let's determine exactly what's running on your PC. The Windows Task Manager isn't always enough. It's relatively easy to hide processes from the Task Manager, and it won't show you anything running as a system service. Try using a program like Sysinternal's Process Explorer instead. End any uneeded or unwanted processes. For help identifying processes, try one of the following links:

Windows Process Library
ProcessLibrary.com

In addition, you should follow the steps outlined in Diagnosing a Sluggish or Slow PC to determine if adware or viruses are to blame.

Try uninstalling any recently installed programs that may be causing your computer to crash.

You should also check the Event Logs for any pertinent information.

You may also use Microsoft's Online Crash Analysis to determine the cause and cure for your troubles.

Take the time to stop by PC Pitstop and perform a full tune-up.

Direct Link: http://guide.nilpo.com/frozenpc