chispy

Congratulations on a job well done , absolutely a monster score !

Windows 10 it is absolutely not allowed ,please re run on windows 7. Ask Christian Ney and he will tell you why if you have any doubt. Please run on windows 7 as per hwbot rules , ( Allowed benchmark versions R15 ,Allowed operating systems ( All Windows based released before Windows 8 ! ) - HWBOT Cinebench R15 Benchmark Validation Regulations , also please read the frontpage news to understand clearly (http://forum.hwbot.org/showthread.php?t=167716 ) , Ryzen benchmarks under windows 10 are very bugged even while using 100 bclk or changing cpu multiplier ( and many more bugs under windows 10 ) on all x370 motherboards and B350 , there is quite a few bugs even on B350 and all motherboards x370 with and without clock generator , it gives bugged scores and results are not valid for that reason , scores are not reliable . Please do not take it personal it's not about you is about the overall integrity and accuracy of the benchmarks at play here , i have tested this myself on my Asus CH6 Hero x370 and ASRock B350 for weeks , both behave the same and both do give bugged scores while running windows 10 , i can replicate the bugs 100% of the time with 100% accuracy everytime , and i did a very deep and throughout investigation on this matter hands on testing myself for weeks so that i can confirm that it is absolutely true. Regards: Angelo

Windows 10 is absolutely NOT allowed , does not matter is bus clock is 100 , ask the moderators or Christian Ney

Windows 10 is not allowed Mr.BULLDOG239 , that is a one big bugged score there you have sir , sad situation but true. Please run on windows 7 ...

There is a Gazillion submissions with Ryzen cpus on windows 10 , all bugged scores , i have just look at it , all windows 10 scores on Ryzen cpus are bugged , tested and confirm by my own hands on testing ! Sad situation but it is happening ...

Monster score Vince Congratz !

Elmor , i'm having a really tough time getting anything decent in the Ram department with my Hynix Dual Rank ADATA AX4U2800W8G17-DRZ. The highest i can get them is 2666 at 18-18-18-36 2T at 1.35v and VDDSOC Voltage Override at 1.20v I have tried many combinations on my Hynix ram for testing purposes. The best i can do is 2666 at 18-18-18-36 2T. I have left Cas alone at 18 as anything lower does not work at all , so that confirms there is some kind of hole at anything below for that , same findings as infrared and Chew, can you comment on those findings ?. I cannot get any other timing changed as soon as i start to do baby steps starting to tight latencies it's a no go on the ram. Tried 18-17-18-36 did not boot , it hangs. tried 18-18-17-36 same , 18-17-17-36 same and so on ... Tried voltages from 1.20v to 1.50v for v.ram and v.ram boot voltage and did not work , tried VDDSOC Voltage Override from 1.0v all the way up to 1.25v did not make a difference. Any advice to get Hynix memory some decent speeds and timings ? Testing last night for a few hours and i end it up with a completely trashed and corrupted windows 10 due to many blue screens. I need to re install windows today to keep on memory testing on Hynix Dual Rank. Thanks in advanced. Regards: Angelo

Congtatz , nice clocking on that card. Rocking hwbot with the 1080tis !

Congratz Michael , huge score ....

Well done Vince ! Team PURE it's on fire ...

Infrared that's some awesome speeds right there :celebration: Lots of improvements with the latest Bios , thank you Jon ( Elmor ) for making this possible , without your support this would not be possible. Kind Regards: Angelo

Right now my DMM it's broken so i cannot confirm the voltage at this moment my friend , but i will try to get a new one or borrow one soon. Good to hear you are able to replicate this bug. Regards: Angelo

Finally made it home and had some free time to replicate the bug and film it on video. The Bug happens when booting from Bios at 1.38v and up using LLC 4 or 5 , when i open Turbo V to set the new voltage for v.core , on this video i set v.core in bios at 1.38v and LLC to 4 then boot straight to windows and applied 1.40v v.core in Turbo V but watch closely what happens to the v.core once i aplied the new voltage in Turbo V , it goes hay wire , crazy up and down bouncing from 1.61v to 1.025v to 1.613v to 1.112v to 1.635 to 1.49v back to 1.025v unstable , if i try to run any benchmark or put any load in the cpu it will immediately reboot. see the video attached here. Thank you Jon for all the help. Regards: Angelo

Jon i will update this when i get home so that i can tell you exactly how to replicate and maybe make a short video of the bug in action. Regards: Angelo

Elmor i think there is a Bug in TurboV Core 1.01.15 , when booting into windows at 1.38v or higher with the LLC set to 4 or 5 in Bios 0902 and using TurboV in windows the voltage goes hay wire crazy it goes from 1.09v to 1.38v to 1.81v sometimes , i can fix it by rebooting. It happens random. Thank you in advanced Jon. Kind Regards: Angelo

/ Awesome score Vincy !

Good read Pieter thanks for sharing.

Thank you for the PM Jon , appreciate it a lot :celebration:. With this new Bios now i feel confident using my boards again :ws:

Thanks for information Jon , no worries i will send it to rma. Regards: Angelo

Elmor is there's any way i can save my Board after it decided to auto update the bios all by itself and bricked during a reboot ? It happened out of nowhere ? It got stuck for an hour trying to update the bios all by itself all of the sudden. Now it does not do anything , i tried all the bios thru the Bios Flashback and it does not work. Any idea or help how can i save the mobo ? Any help will be appreciate it. Kind Regards: Angelo This is exactly what happened to me:

Great score ! keep pushing ...

Thanks for sharing your findings PJ !

Awesome , thank you Elmor ! Will put this to good use soon

Great job with Ryzen.

Awesome score Elmor , keep pushing !