I've decided to experiment a little bit with overclocking since my system is starting to get old.
I've managed to take the cpu up to 4.5 Ghz with Cpu core voltage manual ovveride 1.27v and Cpu cache voltage manual ovveride 1.17.
I also overclocked the ram not with the xmp profile but manually entering the latency values 10-11-10-30, speed 1866MHz voltage 1.50 as tested on the manufacturer's site (Corsair vengance LP two banks of 4gb).
While doing the stability test with my previous setting (voltage 1.269 and 1.169) everything went well for about two hours. Today, however, it crushed (blue screen sad face error WHEA_UNCORRECTABLE_ERROR ) out of the blue (just normal office activities nothing stressful for the cpu)
So I turned up the voltage to 1.27 and 1.7 and everything went smoothly.
Tonight I did the aida64 test again and the pc restarted by itself without any error screen.
It's been a couple of days and no errors occured with 4.5 ghz, 1.27 cpu core voltage and 1.17 cpu cache voltage
Am I doing something wrong? Should I turn up the voltage again?
I attach the screens while I was doing the test, and the aida64 log. I frankly don't understand anything about all those voltage values, I don't know if they are correct.
Motherboard asus z97i plus
Temperatures are not a problem, the fans were running at low revs and anyway the temperature did not exceed 60 degrees.
Any advice is welcome :)
Hello,whenever I'm trying to run System Stability Test on Aida64 extreme and I check the "Stress GPU(s)" checkbox,the system crashes and I have to reboot my pc.Do you have any idea why? (when I run SST's with only GPU's box unchecked,it runs smoothly)
Also I'm trying to save the data from System Stability Test into a file (for instance .txt) but "Save" button only gives me a PNG image.Any ideas?
Using stable version 5.95.4500 in Win 10 64 bit and this is a bug that I have noticed: -
If I set aida64 to run on windows startup by checking the box in preferences then I get some mad lag and intermittent freezing while running the stability test - I'm just testing cpu.
(The elapsed time counter does not tick through as normal as in 1,2,3,4,5 etc but jumps to like 5, 21, 30 etc and if I switch from statistics to temperature tab there is a freezing delay and sometimes aida64 momentarily says its not responding)
I have seen on the net that this is totally normal when running the stability test as it maxes out resources.
If I manually run aida64 after windows has started up then this mad lag and intermittent freezing goes away - all works well.
This seems to be a problem with the way windows prioritizes aida64 while running on startup as opposed to manually running the program after windows starts?
Any ideas on how to fix this?
Please recommend how long to run, and by that I mean how long is long enough, if one's system is indeed stable enough to handle it for more than 7 or 12 or 20 minutes.Also, when interpreting the details of the test data, does the length of time it is run mean anything more than that it is stable? Are there categories of stabiltiy based on the length of time the test is run and the system is responding favorably.