If you used the MSCONFIG command to set your computer into Diagnostic mode and this resolved your issue, it is likely that one of the Startup items is conflicting with the program.

We recommend you print these directions, as the steps involve restarting your computer.

To determine which program is causing the conflict:

  1. Click the Start button.
  2. Click the Run option.
  3. On the Run window, type in "msconfig" without the quotes in the Open field and click the OK button. This will open the System Configuration window.
  4. Click the Startup tab. Each item listed here are programs that are supposed to launch when you boot up your computer.
  5. Place a check next to the first three items or so.
  6. Click the OK button.
  7. A window will open with a message indicating that it will need to restart. Click the Restart button.
  8. When the computer comes back up, test to see if the problem came back.
  9. Repeat these steps until the problem starts again.

When the problem starts again, it will be related to the last set of programs that were enabled. Now, you will turn those off one at a time.

  1. Click the Start button.
  2. Click the Run option.
  3. On the Run window, type in "msconfig" without the quotes in the Open field and click the OK button. This will open the System Configuration window.
  4. Click the Startup tab.
  5. Remove a check next to the one of the last group that was enabled.
  6. Click the OK button.
  7. A window will open with a message indicating that it will need to restart. Click the Restart button.
  8. When the computer comes back up, test to see if the problem came back.
  9. Repeat these steps until the problem comes again.

The last program turned off will be the problem program. Disable that program and enable the others. This should keep your issue from occurring in the future.


Note: None of the programs listed in the Startup tab are required by Windows to operate. However, other programs may need these programs loaded to speed accessing those programs or providing full functionality. When you determine which program is causing the problem, you may need to check which program it is related to and see if it is a critical component to that program.