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.
Hello, I got a NVIDIA Gt 710 card graphic card so when I do the GPGPU benchmark test, it shows in the Single-Precision around 311.7 GFLOPS, But if you see the GPU specifications in the main window it says 366.0 GFLOPS @ 953 Mhz while running the GPGPU benchmark test.
I'm confused with that result, anyone can tell me why is that ? Thanks.
Hi, I've met a issue with the FPU stress test, the system would crash instantly when I click the "Start" buttom
it was ok to run a solo CPU stress test over 2 hour, but I just dont understand why it went wrong when conducting the FPU test. Any Ideas?
I've attached a AIDA64 report of my mobo
CPU:7940x (1.15volt, OC 4.5ghz)
RAM:Gskill 8G*4 4266mhz c17 (I set the frequency at 2133)
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?