Search the Community

I recently built my new rig and I am running some stress tests on my system to ensure stability. Everything works fine when using Asus' ROG RealBench software but when I use AIDA64 I start running into issues. The first time I ran AIDA64 I ran the stress test with stock preferences and settings for the trial version and the CPU, FPU, Cache, Memory, and GPU boxes checked. The test ran for 4 1/2 hours before a hardware failure was detected. I then tried running the test again and this time it only lasted 20 minutes. I then unchecked the 'Stress GPU' box and tried again, and it only lasted about 20 minutes again. I am now running the test without the 'Stress Memory' box checked as well now (leaving only CPU, FPU, and Cache left checked) and it's been 2 hours with no faults yet. My guess is that it has something to do with my RAM, but I have no idea as to why or how. And if it is my RAM causing issues, is it a fatal error or will I be ok and I should just move on? Is there anything I can do to fix this? I am including some screen shots of my system specs and numbers. On the picture with the red circle around my RAM speed, just ignore that, my memory is actually running at 3000 (I am using G. Skill Ripjaws V DDR4-3000 RAM) as you can see in the CPU-Z pics. On the screenshot of my BIOS settings, on the line for my DRAM Frequency, that has also been changed to Auto instead of [DDR4-3000 30x10...] Let me know if I need to provide any more info. I do not really know how to use AIDA64 so this is new to me. UPDATE: The stress test on the CPU, FPU, and Cache has been running for 11 hours now. I am now fairly certain that my hardware failure had to do with my memory during it's stress test. Will this cause a problem later on or should I just leave it alone? UPDATE 2: Sadly the stress test failed at 11 hours 28 minutes. I'm not really sure what I should try next. Screenshots of failed test is now also attached. Any tips on what I can do to make this more stable would be much appreciated.

I 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.