Hi everyone, I have some questions regarding the AIDA64 Engineer system stability test.
Here are the specs for my Windows 10 PC, which was custom-built for me by a local IT company here in Melbourne, Australia:
In a follow-up email, Michael explained what the AIDA64 Engineer system stability test does: “The application synthetically simulates a load that stresses the CPU, motherboard, RAM, GPU and drive(s). These are all the components that can be tested by any software package, and are the key points of failure.”
I totally forgot about running the stress test for months. I got around to running it yesterday. Michael has since left my local IT company. I rang the IT company yesterday and spoke to Ryan G. He informed me that he’s not familiar with AIDA64.
I was unsure whether to tick the box for “stress local disks” before running the system stability test. After re-reading Michael’s email which said that the AIDA64 system stability test “synthetically simulates a load that stresses the CPU, motherboard, RAM, GPU and drive(s)”, I decided to tick the box for “stress local disks”. I then ran the system stability test for three hours and 32 minutes with the following boxes ticked:
I stopped the system stability test after three hours and 32 minutes because I discovered an AIDA64 message board thread which said: “It’s not recommended to use the write tests on SSD drives, due to them wearing out SSD flash memory cells.”
I then ran the system stability test for one hour, 11 minutes and 57 seconds with the following boxes ticked:
Here are my questions:
Here are the specs for my Windows 10 PC, which was custom-built for me by a local IT company here in Melbourne, Australia:
- AMD Ryzen 9 3900X 3.8 GHz Processor (12 Core / 24 Thread)
- Gigabyte X570 Aorus Elite WiFi Motherboard
- Motherboard has WiFi and Bluetooth Built-In
- 64 GB DDR4 3200 Team T-Force Vulcan RAM
- 1 TB PCIe Generation 4 Gigabyte NVMe Solid State Drive
- Gigabyte Nvidia GeForce GTX-1050Ti 4GB Graphics Card
- Gigabyte Case with 750-Watt Power Supply
In a follow-up email, Michael explained what the AIDA64 Engineer system stability test does: “The application synthetically simulates a load that stresses the CPU, motherboard, RAM, GPU and drive(s). These are all the components that can be tested by any software package, and are the key points of failure.”
I totally forgot about running the stress test for months. I got around to running it yesterday. Michael has since left my local IT company. I rang the IT company yesterday and spoke to Ryan G. He informed me that he’s not familiar with AIDA64.
I was unsure whether to tick the box for “stress local disks” before running the system stability test. After re-reading Michael’s email which said that the AIDA64 system stability test “synthetically simulates a load that stresses the CPU, motherboard, RAM, GPU and drive(s)”, I decided to tick the box for “stress local disks”. I then ran the system stability test for three hours and 32 minutes with the following boxes ticked:
- Stress CPU
- Stress FPU
- Stress cache
- Stress system memory
- Stress local disks
- Stress GPU(s)
I stopped the system stability test after three hours and 32 minutes because I discovered an AIDA64 message board thread which said: “It’s not recommended to use the write tests on SSD drives, due to them wearing out SSD flash memory cells.”
I then ran the system stability test for one hour, 11 minutes and 57 seconds with the following boxes ticked:
- Stress CPU
- Stress FPU
- Stress cache
- Stress system memory
- Stress GPU(s)
Here are my questions:
- Are the results of my first system stability test good?
- Are the results of my second system stability test good?
- How much did I wear out the flash memory cells in my 1 TB PCIe Generation 4 Gigabyte NVMe SSD when I ran the system stability test for three hours and 32 minutes with the “Stress local disks” box ticked?
- Going forward, which boxes should I tick when I run a system stability test using AIDA64?
- Going forward, how long should I run the AIDA64 system stability test for on my PC?