- May 15, 2013
- 4,626
- 19
- 38
Update:
Needed to do some more testing and had to reinstall Windows again for testing.
This is the highest score I've gotten before the latest undervolting revisions with PBO enabled.
12th August.
But, I started getting random shut downs even with PBO on default setting which is now auto - the default setting for PBO is AUTO as opposed to disabled.
However, ever since disabling PBO I have experienced zero random shut downs. That's with a clean install with latest AMD drivers for GPU and Chipset. Additionally, did a clean install with no drivers, no av, did a clean install with latest drivers + AV/Firewall installed, clean install with latest drivers with no av/firewall installed. No shut downs with PBO disabled, shut downs with PBO enabled in certain work loads. Verifiable crashes when running R20.
So I decided to go very aggressive on the undervolting as the difference is about 120 points with PBO enabled.
Revision Test with no PBO 13th August:
1) 2) 3) 4)
There is one caveat that is really not mentioned by folks who do benchmarking videos - you are going to lose points on any daily driver PC as installed Apps like steam, firewalls, antiviruses also take up CPU cycles.
16th August with 13th Aug Undervolt Settings - installed Applications - Steam, MSI afterburner, RivaTuna, Mytube Beta, AV+Firewall, Deezer, Latest Chipset drivers, No GPU Drivers.
Disclaimer: If you do copy the settings below - you do so at your own risk - I nor this forum will bear in responsbility for any issues or damage caused to your components. These settings are for a reference guide for those who know how to recover a none booting PC after an aggressive undervolt via a CMOS reset or worse case scenario - a bios flashback.
Took me sometime to figure out that the first partition on my usb stick had to Fat32 for the bios to save screenshots... As I never had issues saving screenshots before. I'm guessing Rufus did something wonky to the USB stick as the old versions didn't use to create a seperate UEFI partition on the stick and you don't have disable secure boot to use a bootable W10 install using rufus - all you have to do is delete this small UEFI partition using diskpart or any other partition manager (it does not show up in disk manager however).
Idle with above settings.
Continued in next post.
Needed to do some more testing and had to reinstall Windows again for testing.
This is the highest score I've gotten before the latest undervolting revisions with PBO enabled.
12th August.
But, I started getting random shut downs even with PBO on default setting which is now auto - the default setting for PBO is AUTO as opposed to disabled.
However, ever since disabling PBO I have experienced zero random shut downs. That's with a clean install with latest AMD drivers for GPU and Chipset. Additionally, did a clean install with no drivers, no av, did a clean install with latest drivers + AV/Firewall installed, clean install with latest drivers with no av/firewall installed. No shut downs with PBO disabled, shut downs with PBO enabled in certain work loads. Verifiable crashes when running R20.
So I decided to go very aggressive on the undervolting as the difference is about 120 points with PBO enabled.
Revision Test with no PBO 13th August:
1) 2) 3) 4)
There is one caveat that is really not mentioned by folks who do benchmarking videos - you are going to lose points on any daily driver PC as installed Apps like steam, firewalls, antiviruses also take up CPU cycles.
16th August with 13th Aug Undervolt Settings - installed Applications - Steam, MSI afterburner, RivaTuna, Mytube Beta, AV+Firewall, Deezer, Latest Chipset drivers, No GPU Drivers.
Disclaimer: If you do copy the settings below - you do so at your own risk - I nor this forum will bear in responsbility for any issues or damage caused to your components. These settings are for a reference guide for those who know how to recover a none booting PC after an aggressive undervolt via a CMOS reset or worse case scenario - a bios flashback.
Took me sometime to figure out that the first partition on my usb stick had to Fat32 for the bios to save screenshots... As I never had issues saving screenshots before. I'm guessing Rufus did something wonky to the USB stick as the old versions didn't use to create a seperate UEFI partition on the stick and you don't have disable secure boot to use a bootable W10 install using rufus - all you have to do is delete this small UEFI partition using diskpart or any other partition manager (it does not show up in disk manager however).
Idle with above settings.
Continued in next post.