Windows XP Troubleshooting Tools


Not every problem encountered within Windows XP will bring the entire system to a crashing halt. There are a number of minor problems that can occur that range from the inability to use a peripheral device such as a printer or a gamepad, to a software program that is unable to run without crashing, to a malfunctioning system device such as a modem or an audio card.

Windows XP includes a number of built-in tools and resources for troubleshooting minor errors that occur within the operating system. Some of these troubleshooting tools and resources are

  • CHKDSK (also referred to as CheckDisk)

  • DirectX Diagnostic Tool

  • Dr. Watson (debugging program)

  • Program Compatibility Wizard

  • System Configuration Utility

  • Windows Troubleshooters

CHKDSK

CHKDSK is a tool you can use to check the integrity of a Windows XP file system, and possibly repair any errors that the tool finds. CHKDSK can be used as a command-line tool, or is available through the Windows GUI (although the GUI version doesn't include all of the functionality of the command-line version).

There are a number of switches you can use to determine how CHKDSK will function. If you just type CHKDSK at the command prompt and press Enter without any switches, the program will run as a read-only diagnostic. It will report any errors it finds, but it will not attempt to repair them.

Here is a list of the switches you can use with CHKDSK:

/f

CHKDSK attempts to fix any errors that it finds.

/v

On a FAT or FAT32 file system volume, CHKDSK will display the name and full path of every file on the disk. On an NTFS volume, this switch displays relevant information on any actions CHKDSK performs .

/r

CHKDSK attempts to locate bad sectors and recover any readable data from them.

/x

Attempts to dismount the volume you want CHKDSK to scan. This switch will not work on the boot volume (the volume that contains the Windows operating files).

/i

Forces CHKDSK to use a less complex scan of index entries, which reduces the amount of time CHKDSK takes to run. This switch is relevant for NTFS volumes only.

/c

Similar to the /i switch; it forces CHKDSK to skip over verifying the cycles in the folder structure of the volume being scanned.


Before you use CHKDSK to try to correct a problem with a Windows file system volume, you should make an attempt to back up the data on the volume. Also, if the volume you are scanning is fairly large and contains a lot of data, you may want to have a cup of coffee and a magazine handy; CHKDSK can take a very long time to complete when dealing with large volumes. Using the /i and /c switches can help to reduce the time it takes for CHKDSK to complete its scan of NTFS-based volumes.

There is a version of CHKDSK you can run from within the Windows GUI. Double-click My Computer or select it from the Start Menu, and right-click on the volume you want to scan. Click Properties, select the Tools tab, and click Check Now (see Figure 12.7).

Figure 12.7. Running the GUI version of CHKDSK while Windows is running.


From here, you can select three options:

1.
Run CHKDSK in read-only mode (finds errors but doesn't repair them) by clicking Start.

2.
Run CHKDSK with the Automatically Fix File System Errors check box selected. This is the equivalent of running CHKDSK with the /f switch.

3.
Run CHKDSK with the Scan For And Attempt Recovery Of Bad Sectors check box selected. This is the equivalent of running CHKDSK with the /r switch.

For more information on CHKDSK and other disk utilities, see "File System Utilities," p. 513.



Interestingly enough, the CHKDSK utility dates all the way back to the days of MS-DOS. CHKDSK was introduced with the release of MS-DOS 2.0back in 1983! Imagine thata utility that's been around for over 20 years that still exists in today's most popular desktop operating system.

DirectX Diagnostic Tool ( DXDIAG.EXE )

DirectX is a suite of multimedia- related application programming interfaces (APIs) built into the Windows operating system. Microsoft first created DirectX for the release of Windows 95. DirectX provides software developers with a standardized platform for multimedia application development, which enables them to create software that can access specialized hardware features, without having to write hardware-specific code. DirectX provides improved communication between software and hardware devices, and interacts with practically everything on a Windows PC that involves video, audio, and input devices. As of this writing, the most current version of DirectX is 9.0c, which was released in August 2004. DirectX 9.0c is compatible with Windows 9x/Me/2000/XP.

Windows XP includes a diagnostic tool that you can use to troubleshoot issues related to DirectX (see Figure 12.8). The DirectX Diagnostic Tool tells you which version of DirectX is installed on your system. It also displays information regarding the various DirectX-related drivers, and provides a series of user -initiated diagnostic tests you can use to determine if DirectX and the hardware devices it interacts with are functioning normally. This can be a valuable tool for troubleshooting Windows problems related to audio and video problems, and input devices such as gamepads.

Figure 12.8. Testing DirectSound with the DirectX Diagnostic Tool.

The DirectX Diagnostic Tool does not appear in the Start menu. To launch it, go to the Start menu, select Run, and type DXDIAG.EXE .

You can navigate through the DirectX Diagnostic Tool using the tabs at the top of the screen, or by using the Next Page button at the bottom of the screen to go through each tab sequentially. The list of tabs includes the following:

  • The System tab displays a list of information related to your system configuration. This information includes the current date and time, your computer's name and operating system version, the language setting, the system manufacturer and model, your system BIOS version, the type of processor you have installed, the amount of system RAM, page file statistics, and the version of DirectX that's currently installed on your system.

  • The DirectX files tab shows you all of the installed files that are related to DirectX. Also displayed are the version numbers for each file, the date they were created, and the size of each file on the hard disk. Below the file list is a Notes box that displays any error messages that the diagnostic tool generates concerning any of the files.

  • The Display tab gives you detailed information on your video adapter, including its name and manufacturer, the chip and digital-to-analog (DAC) type, the amount of onboard video memory, your current display mode, and the type of monitor you have installed. This screen also lists the driver files being used for your video adapter. Below this information, you'll find three diagnostic tests you can run on your system. The first diagnostic tests DirectDraw acceleration, which controls display memory management. The second test checks Direct3D acceleration, which provides 3D graphics support via the video adapter hardware. The third diagnostic checks the AGP texture acceleration, which is a graphics feature that only exists on certain video cards. Below these three diagnostic tests is a dialog box that displays any warning messages generated by the tests.

  • The Sound tab contains information on your system's audio components . This includes the name and device ID of your sound card, a manufacturer and product ID, and the drivers associated with the device. This screen offers one diagnostic that's used to test DirectSound, a DirectX component that controls how audio is presented on your system. Again, error messages are displayed in a dialog box near the bottom of the screen.

  • The Music tab is similar to the Sound tab, but is more specialized in that it focuses on a DirectX component called DirectMusic. On this screen, you'll find information on any Musical Instrument Digital Interface (MIDI) devices you have configured on your system, and a diagnostic that tests the functionality of DirectMusic.

  • The Input tab shows a list of all of the input devices you have attached to your system, including keyboards, mice, and other input devices such as gamepads, joysticks, and trackballs. There are no diagnostics you can perform on this screen, but a dialog box displays any error messages that the DirectX Diagnostic Tool detects.

  • The Network tab offers information on DirectPlay components. DirectPlay is a networking API that controls networking services at the transport and session protocol levels. DirectPlay is responsible for moderating the function of network-based games such as massive multiplayer role-playing games (MMPORGs). The Network tab displays a list of registered DirectPlay service providers, a list of registered DirectPlay applications, and two diagnostic tests. The first test checks the DirectPlay Voice functionality, which is used with games that offer players the ability to speak to each other using headsets. The second diagnostic tests the DirectPlay function of DirectX.

  • The More Help tab offers four options that are accessed by clicking onscreen buttons . The first option launches the DirectX Windows Troubleshooter. The second button launches the Audio Windows Troubleshooter. (You'll take a closer look at Windows Troubleshooters later in this chapter.) The third button loads the Microsoft System Information Tool, which provides an extremely detailed look at your system's overall hardware, software, and Internet configurations. The fourth button is used to override the default refresh rate used by DirectDraw. Generally speaking, you should leave this button alone, unless you are absolutely sure of what you're doing.

Dr. Watson

Dr. Watson is a software debugging program that, in the event of an application crash, writes debugging information to a log file that can be used by a programmer or software technical support expert to troubleshoot the application. To view the Dr. Watson setup dialog box from the Start menu, select Run, type DRWTSN32 , and press Enter (see Figure 12.9).

Figure 12.9. Use the Dr. Watson dialog box to configure how debugging data is generated.


There are a number of options you can configure in the Dr. Watson dialog box. The changes that you make using this interface are saved in the Windows Registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DrWatson .

The first time you open the Dr. Watson dialog box, the program automatically creates a folder that it uses to store any log files it creates. By default, the path to this folder is Documents and Settings\All Users\Application Data\Microsoft\Dr Watson . You can select a different location for this folder by using the Log File Path setting at the top of the Dr. Watson dialog box.

In addition to the log files, Dr. Watson is capable of creating a binary dump file that a programmer can load into a software debugger program in order to troubleshoot the error. Activate this option by checking the Create Crash Dump File check box in the Options section of the Dr. Watson dialog box. As with the log files, you can indicate a different default path for the crash dump file by entering it into the Crash Dump line near the top of the Dr. Watson screen.

The Number of Instructions entry tells Dr. Watson how many instructions it should disassemble before and after the program counter for each thread state dump. (A program counter is a register that holds the memory location for a thread's point of execution.) The Number of Errors to Save entry sets a limit on the number of errors Dr. Watson will save in a log file.

In the Options section of the Dr. Watson dialog box, there are six variables that you can check or uncheck to switch on or off. Dump Symbol Table configures Dr. Watson to include the symbol table for each software module. Activating this option can cause your dump files to become very large. Activating Dump all Thread Contexts will cause Dr. Watson to log a state dump for every thread in the program that is crashing. If this option is left unchecked, Dr. Watson will only create a state dump for the thread that is causing the error in the program. The Append to Existing Log File option decides whether Dr. Watson should add error data to the end of the existing DRWTSN32.LOG file, or if it should create a new log file for each program error. If you check this option, you should monitor the size of the DRWTSN32.LOG file, as it can grow to a cumbersome size. You can check the Visual Notification and Sound Notification options if you want to receive visual or audible cues when Dr. Watson detects a program error. Finally, there is the Create Crash Dump File option that I mentioned earlier in this section.

Unless you are a software programmer, the log and dump files created by Dr. Watson will be of limited personal use. However, these files can be sent to a Microsoft support specialist or to the creator of the software that is experiencing errors. Usually, a programmer will use the information in these files to determine the exact point in the program's lines of code where the error is taking place, and examine the specific variables in the code that might be responsible for causing the problem.

Program Compatibility Wizard

The Program Compatibility Wizard, which is also discussed in Chapter 9, "Windows Commands and Scripting," is used as a workaround for compatibility issues with a program that was released for an earlier version of Windows that has trouble functioning under Windows XP.

The Program Compatibility Wizard can be launched from the Start menu by choosing All Programs, Accessories. Alternatively, you can right-click on a program's launch file or shortcut, select Properties, and then click on the Compatibility tab.

You can choose to run a program in one of the following Windows compatibility modes for Windows 95, 98, Me, NT4.0 (SP5), and 2000. The Program Compatibility Wizard also offers three display options for older programs:

  • Run in 256 Colors

  • Run in 640x480 Screen Resolution

  • Disable Visual Themes

Tip

If you are running an application in a Windows Compatibility mode, you should close any active antivirus and antispyware programs. These programs can cause problems when running an application in Windows Compatibility mode.


System Configuration Utility

The System Configuration Utility is a powerful troubleshooting tool that allows you to configure a number of Windows startup variables (see Figure 12.10). To access the System Configuration Utility from the Start menu, select Run, and enter MSCONFIG .

Figure 12.10. Using the Microsoft System Configuration Utility to manually set startup variables.

From the General tab, you can choose to alter the startup method that Windows will use the next time you reboot the machine. Diagnostic Startup is essentially the same as Safe mode; you can further configure this option by selecting which services you want to start by clicking on the Services tab. Selective Startup allows you to further customize startup on a more granular level.

The SYSTEM.INI and WIN.INI tabs contain services and programs that are primarily meant to provide backwards compatibility for programs designed for earlier versions of Windows. The SYSTEM.INI and WIN.INI files are not necessary to run Windows XP, but may be required by older drivers and programs.

The BOOT.INI tab gives you convenient access to the BOOT.INI file. This file normally contains information on any other operating systems installed on the computer. You can also use the BOOT.INI tab to add certain switches to the Windows startup process. These switches are

  • /SAFEBOOT Sets the computer to always boot into Safe mode. You can choose additional switches for this option, including MINIMAL (normal Safe mode), NETWORK (Safe mode with Networking), DSREPAIR (Directory Services Repair, normally only used on servers in an Active Directory environment), and MINIMAL/ALTERNATE SHELL (Safe mode using an alternate preconfigured Windows GUIthis option is normally not used)

  • /NOGUIBOOT Same as Safe Mode with Command Prompt

  • /BOOTLOG Writes a detailed log of the boot process to a file named NTBTLOG.TXT

  • /BASEVIDEO Windows will start up using a generic VGA driver rather than the installed video driver (useful if the installed video driver isn't working)

  • /SOS Displays the driver filenames as each driver is loaded during startup (can help to pinpoint where Windows startup is bogging down)

At the bottom of the Boot Options section of the BOOT.INI tab is a button labeled Advanced Options. There are four additional switches that can be added to the Windows startup process via this button:

  • /MAXMEM Allows you to set a limit on how much RAM Windows is able to access (can be used to test if a RAM module is faulty)

  • /NUMPROC Lets you limit the number of processors Windows has access to on a multiprocessor system

  • /PCILOCK Prohibits Windows from assigning IRQ resources to PCI-based hardware; the devices remain as configured by the BIOS settings

  • /DEBUG Starts Windows in debugging mode (this is used when you have a second system hooked up to debug the malfunctioning system)

The Services tab can be used to enable or disable specific services. This can be very useful if you are troubleshooting a Windows startup problem, and want to disable services without uninstalling the associated software. You can view only the third-party services in the list by clicking on the Hide All Microsoft Services check box.

The Startup tab allows you to enable or disable software programs that are started when Windows is started. Common examples of such programs include antivirus software, instant message clients , and third-party control panels for display adapters and audio cards. Again, disabling all unnecessary programs and enabling them one at a time can help to isolate and identify the cause of a Windows startup problem.

If you would like to know what some of the more cryptically named startup items are, you can try looking them up at www.sysinfo.org.

Windows Troubleshooters

Windows Troubleshooters are mini-programs that are used to troubleshoot a minor problem with normal Windows operations. The Windows Troubleshooters are similar in design and function to expert systems. An expert system is a software program that contains knowledge gathered from one or more human experts. When the program is run, it asks a series of questions to collect information from the user, and then uses this information in concert with its internal knowledge to diagnose a problem or analyze a given situation. An expert system possesses an internal logic structure that enables it to follow a deductive process much like someone who is troubleshooting a Windows problem.

Windows XP will offer to open a Windows Troubleshooter when you encounter certain specific problems. However, you can always access the full list of Troubleshooters by selecting the Help and Support option from the Start menu.

In the Help and Support Center, type List of Troubleshooters into the Search box located in the topleft corner of the screen, and press Enter. In the Search Results box, click on the List of Troubleshooters link that appears.

Table 12.2 lists all of the Windows Troubleshooters and what each one should be used for.

Table 12.2. Windows Troubleshooters

Windows Troubleshooter Name

Subject Area Covered

Digital Video Discs (DVDs)

DVD-ROM drives and decoders

Display

Display adapters, monitors , and drivers

Drives and Network Adapters

Hard drives, floppy drives, CD and DVD drives, network adapters, tape drives

File and Print Sharing

Workgroups and networks, sharing files and print devices, logon issues

Hardware

Covers a wide variety of hardware, including input devices, USB devices, modems, audio cards, and so on

Home Networking

Home network setup, file and print sharing, Internet connections

Input Devices

Mice, keyboards, trackballs, cameras , and scanners

Internet Connection Sharing (ICS)

Sharing an Internet connection between two or more computers

Internet Explorer

Using Internet Explorer as your web browser

Modem

Internal and external modem connections and operation

Multimedia and Games

Games, multimedia programs, DirectX, audio, and controllers

Outlook Express

Using Outlook Express as your email client

Printing

Installing and operating print devices

Sound

Audio and audio adapters

Startup/Shutdown

Starting and shutting down a system, standby mode, and hibernation mode

System Setup

Installing and configuring Windows

USB

All USB hubs and peripherals


Note

There is a fair amount of crossover between the various Windows Troubleshooters in terms of what subject area each Troubleshooter covers. You should always try to use the Troubleshooter that is most specific for the problem you are working on. For example, if you are dealing with a malfunctioning modem, you should choose the Modem Troubleshooter over the Hardware Troubleshooter, as the first troubleshooter is more relevant to the issue.


With certain Windows Troubleshooters, you may be asked to restart the computer or to exit out of the Troubleshooter before completing a step. Because of this, it is recommended that you manually track your progress through the Troubleshooter on a piece of paper, making a note of the questions asked and your responses to each question. By doing this, you can restart the Troubleshooter after closing it, and get back to where you were.

Installing Additional Windows Support Tools

As you have seen, there are a number of troubleshooting tools and resources available in a normal Windows XP installation. However, Microsoft has also provided a large collection of additional programs known as the Windows Support Tools. These tools are meant for use by Microsoft support specialists and experienced Windows users to help diagnose and solve Windows issues. The Windows Support Tools are not installed by default when you install Windows XP, but they can be installed at a later time from the Windows XP installation CD.

To install Windows Support Tools, place the Windows XP installation CD into your system while Windows is running. Open the contents of the CD in My Computer or Windows Explorer and browse to the Support\Tools folder. Double-click the SETUP.EXE file to install the Windows Support Tools.

Note

If you are running Windows XP Service Pack 2, you should not install the Windows Support Tools from the Windows XP installation disk. Microsoft has an updated version of this package, Windows XP Service Pack 2 Support Tools , available as a free download on its website. To download this newer version, visit http://www.microsoft.com/downloads/details.aspx?FamilyID=49ae8576-9bb9-4126-9761-ba8011fabf38&displaylang=en.


There are nearly fifty different command-line programs available in the Windows Support Tools. Thankfully, a help file that describes each tool in depth is placed in the Windows Support Tools item created in the Start menu after installation. Each entry in the help file includes an overview of the support tool, notes on how to use the tool from the command line, the syntax you should use when typing the command as well as all of the available switches, one or more examples of the tool's functionality, and a list of related support tools that may be applicable to the issue you are troubleshooting.

Here are some examples of the types of tools included in the Windows Support Tools:

  • Dependency Walker ( DEPENDS.EXE ). Dependency Walker displays a hierarchical diagram showing all of the child modules that a parent module (such as an .EXE , .DLL , or .SYS file) is dependent on in order to function properly. This tool can be used to troubleshoot Windows errors that are based on module load issues. When Dependency Walker scans a parent module such as an .EXE file, it automatically detects and reports several common application errors such as missing modules, invalid modules, and circular dependency errors.

  • Disk Manager Diagnostics ( DMDIAG.EXE ). Disk Manager Diagnostics displays the system state and configuration data related to disk storage. This information includes the computer name and the operating system installed, the physical disk type, any existing hard disk mount points, drive letter usage, and disk partition configuration. You can write all of the information produced by this diagnostic to a text file by including a directory path and filename as part of the command (for example, type dmdiag > C:\diskinfo\diskinfo.txt at the command line, and the tool will write the information to a file named diskinfo.txt in the C:\diskinfo directory).

  • Pool Byte Monitor ( POOLMON.EXE ). Pool Byte Monitor is used to monitor memory tags such as total paged and non-paged pool bytes. This tool is most commonly used to attempt to detect possible memory leaks. Memory leaks occur when a program or service reserves memory for itself, but doesn't relinquish it once it is finished running. Eventually, a memory leak will result in inadequate memory being available for the operating system to function properly, resulting in system errors or lockups. Pool Byte Monitor can be used to track which memory tag's byte levels are increasing over time without being released, which is a common symptom of a memory leak.




Upgrading and Repairing Microsoft Windows
Upgrading and Repairing Microsoft Windows (2nd Edition)
ISBN: 0789736950
EAN: 2147483647
Year: 2005
Pages: 128

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net