Long time licensed owner of Aida64 Extreme. Current version: AIDA64 v6.10.5200. Benchmark Module 4.5.811-x64 (recently upgraded)
Hello everyone. I am new here and this is my first post. I am a senior citizen (tech-head like most of you) and wanted to share an interesting experience that happened to me today as I was experimenting with OCing my i7 8700k after upgrading from a SATA III Samsung SSD 860 EVO to an M.2 Samsung 970 EVO Plus SSD.
Let's start off the Aida64 FPU Stress Test. This test is for extreme overclockers who use full water cooled systems or use liquid nitrogen to acheive incredibly high CPU overclocks. For fun and knowing my system would crash, I tested my new OC of the CPU at 5Ghz per core. About 10 seconds into the FPU stress test the CPU overheated and the system crashed - as expected.
Now to real life Stability Testing. My CPU is nicely cooled with a Noctua D15 CPU Cooler. A giant of an air cooler. My normal, very stable overclock runs at 4.8Ghz. Never overheating during any stress test or demanding PC Video Gaming and Video Production.
Now here's the surprising experience I had today. After migrating my Primary drive with W10 OS and all installed programs from the Sata III 870 SSD to the M.2 970 SSD I decided to go into the UEFI BIOS and simply set the multipliers from 48 to 50. I ran all stress test (excluding FPU) and amazingly I was stable at 5Ghz! I can only attribute this to the new speed of the M.2 SSD. There is nothing new in my system, BIOS was updated to the latest version two months ago and all things you see below in these screenshot are what I purchased when I built this Desktop PC in 2018-2019.
I am curious if anyone with a similar build has tried overclocking their particular CPU after installing an M.2 SSD and found the would increase their CPU performance to a higher GHz and keep it stable.
I endorse Aida64 for all my benchmarking needs. I enjoy building a new Desktop PC every five years and have done so for 15 years. That's three new builds using Aida64 Extreme as my Stress Tester and Benchmarker.
NOTE: Cinebench R20 crashed my system at 5Ghz. I lowered the multiplier to 49 and ran it again. It did not crash the system.
Idle System in the screenies below: (gaming or heavy loads show average of 55 to 68 Celsius)
AIDA64 Stability test failed. Fluctuating fraphic of GPU Power draw (MSI B450M Gaming Plus + Ryzen 3 1200 + Inno3D GTX 750)By G3k0S
CPU - Ryzen 3 1200
MB - MSI B450M Gaming Plus
Video - Inno3D GTX 750 2Gb - 4 years
PSU - Chieftec CHP - 500A - 8+ years
MEM - Kingston HyperX KHX2666C16/8G 2 bars by 8Gb.
HDD - WDC WD1002FAEX-00Z3A0 (931 GB).
SYS - Microsoft Windows 10 Pro 1809 Build 17763.379
Bios last update. Default settings.
Sometimes Kernel-Power (41) mostly in games and tests Aida64.
Tests that I conducted (prime95(1 hour), OCCT(~40min), Memtest86(in bios (1 hour)), TestMem5), all is ok. Sometimes the sound hangs. As if the whole system hangs for ~0.2-0.4sec.
I was running a stress test on a my new Pc and within 2 mins of the test I get a hardware failure message. I've discovered that the test fails on the FPU stress test i'm kind of stuck on how to fix the issue
RYZEN 5 1400 (OC 3.7ghz)
ASUS B350I MOTHERBOARD
CORSAIR DOMINATOR PLATINUM 16GB 3000MHZ
EVGA 1080TI FTW3
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?