Search the Community
Showing results for tags 'stability test'.
Found 3 results
Ryzen infinity fabric for ZEN and ZEN+ (Ryzen 1X00 series and 2X00 series) make memory overclock more useful but complicated. Sometimes, overclock fails even if both memory modules and memory controller works well but infinity fabric fails. There are claims that AIDA64 Cache & Memory Benchmark is useful to see if that happens. If L3 performance significantly lower before overclock, it is fail even if every other test(Testmem5, HCI Memtest, Linpack, etc...) succeed. Because Ryzen (exclude APU) 1X00 and 2X00 series have distributed L3 cache across 2 CCX which connected by infinity fabric, infinity fabric fails affect L3 cache performance. So......how about allow us repeat L3 bench only (N times or time basic) ? Or, maybe adding options to see L3 performance results in already exist cache stress test ?
LurkerLito posted a topic in Benchmarking, system performanceI was running the Stability Test in v4.0 after I updated my bios to check the system stability. Well a little over 9 minutes in it stopped saying hardware failure detected and it stopped the test. I was looking at the graphs and all, and I see nothing that indicates anything was wrong. So is there anyway to see what tripped the stability test and made it stop? I reran the test for longer (just a bit over 11 minutes) and all went fine, but I did disable process lasso, which is a program that throttles the CPU in some instances to keep everything running smoothly even under a heavy load. I forgot to turn it off when I ran it before when I got the hardware failure message. I am thinking it did something and tripped whatever it is that made the stability test think some kind of hardware failure was about to happen. I know I should run it longer, but I just didn't want to do it, I only updated the bios so I was just going to run it for like 10 minutes originally. Anyway I am hoping you consider putting up some more detailed messages for the stability test because a simple message like hardware failure detected test stopped is just a bit too simple. I know you can't determine what hardware is failing, but you can tell me something more detailed, like what caused the hardware failure message that made the stability test stop running. Like voltage dropped below expected value, Temperature exceeded limits, or CPU process slowed down, because obviously the stability test code is definitely detecting something, so tell me what that something was. Thanks.