Created
November 1, 2023 07:49
-
-
Save sharedstuff/308c3339e507eef0b26eeec22bd48056 to your computer and use it in GitHub Desktop.
Testing & Validating PC Hardware (after a new build)
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Prerequisites | |
- a machine with installed Windows, including the following tools: | |
I recommend to use chocolatey as a package manager: | |
```choco install -y cpu-z hwinfo furmark gpu-z prime95``` | |
- CPU-Z | |
- HWInfo | |
- Furmark | |
- GPU-Z | |
- Prime95 | |
- Memtest Stick | |
https://www.memtest86.com/ | |
Download -> Create a bootable USB Stick | |
--- | |
## 1. Test CPU temperature | |
Goal: | |
Put maximum load on the CPU to see if we got thermal issues OR the CPU starts to throttle | |
Prerequisites: | |
- Information | |
- max temp of your CPU according to its spec-sheet | |
example: | |
https://www.amd.com/en/products/cpu/amd-ryzen-7-7700x | |
has a "Max. Operating Temperature (Tjmax)" of 95°C | |
- Tools | |
- HWInfo | |
- Prime95 | |
Process: | |
- Launch HWInfo sensor view | |
- Launch Prime95 | |
- Start a torture test "Small FFTs" (maximum power/heat/stress) | |
- Watch/monitor the CPU temperatures AND max clocks | |
Definition of Success: | |
- The CPU doesnt reach Tjmax while still maintaining its max base clock as a min! | |
--- | |
## 2. Validate CPU performance | |
Goal: | |
Compare your CPU performance to a reference | |
Prerequisites: | |
- Information | |
- expectation / a compare-able reference processor | |
CPU-Z offers a wide range of reference data of each generation to compare to | |
example: We want to compare a 7700X (8c/16t) to 7950X (16c/32t) | |
that would result in the following expectation: | |
same single-core performance | |
half the multi-core performance | |
- Tools | |
- CPU-Z | |
Process: | |
- Launch CPU-Z | |
- Start a "bench" | |
- Compare the scores to the reference | |
Definition of Success: | |
- The CPU scores are within the expectation we made up | |
--- | |
## 3. Test RAM for errors | |
Goal: | |
Test your RAM for errors | |
Prerequisites: | |
- Memtest Stick | |
Process: | |
- Boot the Memtest Stick | |
- Run the Memtest | |
example: https://www.youtube.com/watch?v=LA7ua19snzc | |
Definition of Success: | |
- No errors / at least 1 full cycle tested |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment