Anonymous edits have been disabled on the wiki. If you want to contribute please login or create an account.

Difference between revisions of "Troubleshooting guide/Hardware problems"

From PCGamingWiki, the wiki about fixing PC games
m (updated template usage)
Line 60: Line 60:
 
Memory stability testing is performed using the [http://www.memtest.org/ memtest86+ utility].
 
Memory stability testing is performed using the [http://www.memtest.org/ memtest86+ utility].
  
Windows 7 has a built in memory tester also, which can be found by running mdsched.exe.
+
Windows Vista+ have a built in memory tester also, which can be found by running mdsched.exe.
 +
 
 +
In case errors don't present in a random pattern (meaning the issue is confined only to determinate RAM addresses) it might be possible to just bypass the affected locations<ref>[http://unix.stackexchange.com/a/76188/163877 linux - How to blacklist a correct bad RAM sector according to MemTest86+ error indication? - Unix & Linux Stack Exchange]</ref><ref>[https://superuser.com/a/490522/567466 memory - Running Windows with defective RAM - Super User]</ref>.
  
 
===Disks===
 
===Disks===

Revision as of 13:32, 25 March 2017

This page may require cleanup to meet basic quality standards. You can help by modifying the article. The discussion page may contain useful suggestions.

Hardware diagnosis software can be used to determine whether the problems on your PC are being caused by faulty or broken hardware. There are many utilities that are designed to scan the physical components of your computer to check whether they are in good condition.

Technique

Windows

Open the DirectX Diagnostic Tool:

  • Windows Vista and later: open the Start Screen/Start Menu, type dxdiag and press Enter.
  • Windows XP: press Win+R, type dxdiag and press Enter.

Linux

Through the Terminal

$ lspci
$ lsusb

See also Linux.

General Troubleshooting

To successfully troubleshoot a problem, it helps to obey the following rules:

  1. Never change more than one thing at a time.
  2. Write down everything.

The general troubleshooting procedure is:

  1. Think about the problem to determine whether it results from unintentional side effects. If so, stop.
  2. Reboot the computer and determine if the problem is repeatable. If the problem does not occur again, stop.
  3. Read the game's documentation and web site to determine if it is a known problem and a solution is available. If so, try it and stop if it works.
  4. Search the Internet to determine if a solution from a reliable source is available. If so, try it and stop if it works.
  5. Examine records of the problem and classify the problem as deterministic or nondeterministic.
  6. Verify the computer operation assumptions are true.
  7. Perform stability tests on the computer.
  8. Perform data integrity tests on the computer's software.

Problems are classified as deterministic or non-deterministic. Deterministic problems happen the same way every time, non-deterministic problems happen differently each time. Deterministic problems are often caused by software or data corruption. Non-deterministic problems are usually caused by bad hardware.

Computer designs assume that all the following things are true. If any one of these assumptions is not true, it may be the source of the problem.

  • The computer is not overheating. Fans are clean and have enough space in front and behind them to cool the electronics.
  • The computer's real-time clock is set correctly.
  • The computer's user is in full control of the computer, and the computer is not being given conflicting commands by other users or software from the network.
  • The computer does not have unreliable or faulty peripherals attached to it.
  • The computer has a reliable power supply.
  • The computer's memory is perfectly reliable.
  • The computer has enough extra disk storage for any virtual memory it may need.
  • The computer is fast enough and has sufficient cooling for the work it is being asked to do.
  • The computer's internal connectors are clean and signals pass through them reliably.
  • The computer user is not actively attempting to run the computer outside specifications (over-clocking, under-volting, etcetera.)
  • The computer's user is not actively trying to deceive the hardware or software.

Stability Testing

Many parts of a PC work together to run a game. Crashes are often caused by problems where two or more parts interact. The first question to be asked when a crash occurs is whether the PC is stable without the game running.

Power Supply Unit

Non-deterministic problems are sometimes caused by a bad power supply unit (PSU)[1]. If the power supply is not stable, it is futile to test other parts of the system because they will yield inconsistent results. Power supplies do not indicate whether they are having problems because they generally do not include self-testing hardware. Sometimes electrical noise (buzzing) may be heard though.

The best way to test a power supply is with a special PC power supply tester. If one is not available, try to load the PSU as much as possible, generally by running all stress tests and connecting as many external devices as available (preferably in "cold" conditions). If this hamper system stability in any way, swapping the PSU with a different known working one should be enough to rule out or not the problem.

Memory

Memory stability testing is performed using the memtest86+ utility.

Windows Vista+ have a built in memory tester also, which can be found by running mdsched.exe.

In case errors don't present in a random pattern (meaning the issue is confined only to determinate RAM addresses) it might be possible to just bypass the affected locations[2][3].

Disks

Disk stability testing is performed using smartmontools. Using the -x argument to the utility, verify the following:

  • The disk is not overheating. (SSDs may not have a temperature sensor, measure their temperature some other way.)
  • The disk is not reporting read or write faults in its error log.
  • The disk is not reporting a pre-fail condition.

If each of those items are true, then follow the directions to perform a short self-test. Verify that the disk executes and passes this test. If not, go to the disk vendor web site support section and follow the directions to download their disk analysis software. Follow the directions to obtain a specific problem report and return the disk if it is under warranty. If the disk is not under warranty, swap the disk for a new one.

CPU

Intel CPU testing is performed using the Intel Processor Diagnostic Tool.

AMD does not release diagnostic software for end users. Use Prime95 to stress test the CPU and see if it fails. The Windows Event Log may record a machine check error code; this will provide more specific information on what caused the problem.

GPU

If you are experiencing visual artifacts or sluggishness in visual applications, then there may indeed be a problem with you GPU. First, use a utility such as GPU-Z or HWMonitor to see if your card is running over the recommended temperature (the max is usually around 80 Celsius), if so, then you card will be throttling itself in self-preservation. Check then, to see if the fans or blocks on your card are functioning correctly, and blow out any dust or debris build-up with a can of compressed air. If that isn't the problem, check the video drivers, and see if there is a new version or if the one you are using is reported as being unstable, in either case, perform a clean install of the drivers.Next, if you have integrated video as well as a discreet card, make sure that the computer switches when in game to your discreet card correctly instead of staying on integrated. Last try to stress test it with FurMark. If all else fails, check the warranty on your GPU (most are 2-3yrs) and RMA the card for repairs or a rebate of some sort.

CPU + GPU

Run both tests together. Remember to lower CPU test priority to avoid bottlenecks in the GPU one. [4]

How to ask questions the smart way

How to ask questions the smart way

Recommended software


References