Isolate Hardware Problems Affecting Team Foundation Server

Article
11/27/2007

This topic describes how to systematically isolate hardware problems that Team Foundation Server may experience.

Isolate Hardware Problems

When you troubleshoot hardware, start with and work toward the simplest configuration possible by disabling or removing devices. Incrementally increase or decrease complexity until you isolate the problem device.

Check Your Hardware

If your diagnostic efforts point to a hardware problem, you can run diagnostic software available from the manufacturer. These programs perform self-tests that confirm whether a piece of hardware has malfunctioned or failed and must be replaced. You can also install the device on different computers to verify that the problem is not caused by system-specific configuration issues. Replace defective hardware and diagnose problems on a spare or test computer to minimize the effect on the user because of the system being unavailable. If diagnostic software shows that the hardware is working, consider whether you should upgrade or roll back device drivers.

Reverse Driver Changes

If a hardware problem causes a Stop error that prevents Windows from starting in regular mode, you can use the Last Known Good Configuration startup option. The Last Known Good Configuration enables you to recover from problems by reverting driver and registry settings to those used during the last user session. If you can start Windows in regular mode after you use the Last Known Good Configuration, disable the problem driver or device. Restart the computer to verify that the Stop message does not recur. If the problem persists, repeat this procedure until you isolate the hardware that is causing the problem.

Isolate Hardware Problems Affecting Team Foundation Server