tRFC 228 put up a really good fight with me, but in the end i have managed to knock it back in line
Had multiple runs where testmem simply would stop running without giving any errors, with timer still running, often at cycles between 15 and 24
What fixed it in the end was higher voltages.. +20mv to VDDP, CCD and IOD fixed testmem from stop running between cycles
I'm pretty sure this will be my finalised profile for awhile now..
View attachment 219164
Lots of things going on in this screen, so i will also write what it show:
25 cycles testmem 1usmus cfg
3000% Karhu ramtest
30min OCCT Large AVX
Aida64 memory benchmark
CPU-Z cpu bench, ST 709 and MT above 14k
And a quick and easy gaming test in SotTR with
daily 24/7 settings. (done in windows10)
View attachment 219165
Seems like i have to wait for Alder lake for someone else to cross the 300 fps line and i can start pushing again..
My old record with everything maxed and not stable was 314 average cpu fps i think, with these new memory stick and settings it should be good for ~320-330 fps when running bench settings
Looking forward what the 5950 xt 3dnow! edition can do in this bench when i get it
For those running windows11:
View attachment 219170
Far Cry New Dawn is the outlier here, which barely shrugs at VBS, with just a 5% reduction in frame rate. But Horizon Zero Dawn drops by some 25%, Metro Exodus by 24%, and
Shadow of the Tomb Raider by 28%. Interestingly, the 3DMark Time Spy score only dropped by 10%.
"In our testing with pre-release builds of Windows 11," UL tells us, "a feature called Virtualization-based Security (VBS) causes performance to drop.
VBS is enabled by default after a clean install of Windows 11, but not when upgrading from Windows 10. This means the same system can get different benchmark scores depending on how Windows 11 was installed and whether VBS is enabled or not. "
If you are affected:
"HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\DeviceGuard and add a new DWORD value named EnableVirtualizationBasedSecurity and set its value to 0 "
or
- Run gpedit.msc
- Go to Local Computer Policy > Computer Configuration > Administrative Templates > System > Device Guard
- Double click Turn on Virtualization Based Security
- Select Disabled
- Click OK
- A reboot might be required.