Crosshair VI Hero: UEFI build update thread

[Red Core]

Not Meltdown/Specter specifically, but there's always this: http://seclists.org/fulldisclosure/2018/Jan/12 This is going to fall more on OS/kernel level fixes.

The truth is, they made it intentionally or do you really think they suddenly found this out?
A mistake which wasnt discovered by these companys for over 20 years?

This is made intentionally, america spy always and they made a small backdoor for this.
Most chats.. social media all infos goes to america, this is obvious.

Now updates will fix this.. and make again one other backdoor open for "special acces" of course just to KEEP YOU SAFE.
... and everybody else too, so we need to know what you do, if we get somehow suspicious infos from your google search etc.
Welcome to America

The safety of a country goes above the rules and rights of each citizen.
Thats how they justify it. They created a system with rules and dont care about the rules.
Rather acting like a God.

And ive read such problems doesnt exist at phone processor...
Well.. there is everything already open, there was never a security, google was and is always able to see your data,
where you are and who did you call. Since google is preinstalled into the OS and android is much supported by google.
You might imagine the influence.

Short explained: They know..
Where you are, who you called/call
What you think or do via social media messages/chat messages.
What your favorites are, what you dislike.
Its even possible that they can see your through your phone camera if that is really needed.
Or public camera's.

Even if people argue, thats no true, well there is a high chance that this is true and even if its happen, you dont recognize it.
For real security, dont use a phone, dont use internet, play at a computer in your own home network.
If not, thanks for your sharing

[Xxela]

The truth is, they made it intentionally or do you really think they suddenly found this out?
A mistake which wasnt discovered by these companys for over 20 years?

This is made intentionally, america spy always and they made a small backdoor for this.
Most chats.. social media all infos goes to america, this is obvious.

Now updates will fix this.. and make again one other backdoor open for "special acces" of course just to KEEP YOU SAFE.
... and everybody else too, so we need to know what you do, if we get somehow suspicious infos from your google search etc.
Welcome to America

The safety of a country goes above the rules and rights of each citizen.
Thats how they justify it. They created a system with rules and dont care about the rules.
Rather acting like a God.

And ive read such problems doesnt exist at phone processor...
Well.. there is everything already open, there was never a security, google was and is always able to see your data,
where you are and who did you call. Since google is preinstalled into the OS and android is much supported by google.
You might imagine the influence.

Short explained: They know..
Where you are, who you called/call
What you think or do via social media messages/chat messages.
What your favorites are, what you dislike.
Its even possible that they can see your through your phone camera if that is really needed.
Or public camera's.

Even if people argue, thats no true, well there is a high chance that this is true and even if its happen, you dont recognize it.
For real security, dont use a phone, dont use internet, play at a computer in your own home network.
If not, thanks for your sharing

You spoke the truth my friend.

[FoxTech]

@Red Core

Exactly. I mentioned this in another forum aswell.
I don't wanna wake dogs but this "security patches" they roll out now, could be more worst in privacy reasons.
Probably this update is a compatibality update to Governments new data-collecting servers.
Why I say this? Never saw such a reaction to any ohter security leak or ransomware attack, virus threat...
The whole world goes nuts atm about this. Something, Not a single hacker knew about this before.
In my eyes, this behavior is strange

[Darth Ender]

no need for the conspiracy theory in relation to the fixes to this.

The reason why this is a big deal vs previous similar hardware errors is because of the ecosystem we currently have (cloud computing) and the ease of which it can be exploited (anyone can run the exploit on their virtual computer and glean data from any other virtual computer and nothing can be done to stop them via virus scanners or etc). if the F00F bug was discovered today it would get the same exact reaction, though it is relatively easy to patch vs this new errata.

The only real conspiracy-like question would be just how long black hats (or more plausibly, state actors) knew about it before someone at google discovered it. Though we haven't really had an issue where any major data leaks that have ever been publicized needed such an unknown bug to explain how the hack was done.

I think this was just a blind mistake. All effort was being put into speed and nobody was spending time on security. I dont think intel knew about it far in advance of what has been publicly noted already. I think they got caught with their pants down.

Either way, it's a good time to be a 20+ year amd customer. While not entirely free and clear, it's far better than what intel customers will be dealing with if they patch their system.

[Red Core]

no need for the conspiracy theory in relation to the fixes to this.

The reason why this is a big deal vs previous similar hardware errors is because of the ecosystem we currently have (cloud computing) and the ease of which it can be exploited (anyone can run the exploit on their virtual computer and glean data from any other virtual computer and nothing can be done to stop them via virus scanners or etc). if the F00F bug was discovered today it would get the same exact reaction, though it is relatively easy to patch vs this new errata.

The only real conspiracy-like question would be just how long black hats (or more plausibly, state actors) knew about it before someone at google discovered it. Though we haven't really had an issue where any major data leaks that have ever been publicized needed such an unknown bug to explain how the hack was done.

I think this was just a blind mistake. All effort was being put into speed and nobody was spending time on security. I dont think intel knew about it far in advance of what has been publicly noted already. I think they got caught with their pants down.

Either way, it's a good time to be a 20+ year amd customer. While not entirely free and clear, it's far better than what intel customers will be dealing with if they patch their system.

Its just a theory but a company which produce for million companys wont dare to let a big security hole in the processor.
And its not only one company which produce processors. Its hard to believe that all didnt knew about this.
So all cpu manufacturer are guilty but i doubt that america's justice will even point with the finger on them.
I mean 20 years... are enough time to steal your life in digital shape.

I ve also read at one site that google is saying that Intel and AMD has this security problems. I dont know which source speak the truth.
AMD stated clear that they dont have this security problem, meanwhile there share increased, this could be also just marketing.

In one other source AMD answered to google's vulnerability scan, only 1 of the 3 security problems appear at AMD processors.
1. Bounds Check Bypass<< works
2. Branch Target Injection<< doesnt work
3. Rogua Data Cache Load<< doesnt work
Source(In German): https://www.heise.de/security/meldun...s-3932573.html

However do someone know when the next bios update arrive?
I want to OC my 1800X to 4Ghz but not with temp offset and forced 100% fanspeed.
It would run at 66°C witout offset and with 35% fan speed but the offset destroy it, 100% fan speed is to loud.
Im running it at 3,8Ghz at the moment, with 100% load it reach max 50°C.

[Syaoran]

Is there an ETA for a new BIOS? With the security issue needing a patch and the disappointing 3xxx BIOS's so far. Hopefully something better isn't too far away.

[looncraz]

http://www.overclock.net/t/1624603/r...#post_26542960

New beta BIOS 3501

- Update to latest AGESA with support for 2nd gen Ryzen processors. Version number is reset, this release is 1.0.0.0a.
- Supports additional DRAM ratios which might help you get closer to your max DRAM frequency without using reference clock. New ratios: 2733, 2866, 3000, 3133, 3266, 3400, 3533, 3666, 3800, 3933, 4066, 4133, 4200.
- Still has the S3 resume TSC frequency bug. Enable HPET or don't use sleep mode for now.
- Custom P-state overclocking seems to disable P1/P2 states

http://www.mediafire.com/file/e07ivw...-ASUS-3501.zip (sha256 9a3147f22908139f0150eab07abbeabc1a8040b541592879ad 215ec723eac958)
http://www.mediafire.com/file/e2ng10...-ASUS-3501.zip (sha256 c4bce19fd6d6a96b6487983d886a1ed61b6ac77163f1c87c55 2c7698f3397e1b)
http://www.mediafire.com/file/3j2fjp...-ASUS-3501.zip (sha256 738dbd3e33406845d6f52e1401e62205376254e5d805233bb5 a566a95eaeafd4)

[Syaoran]

http://www.overclock.net/t/1624603/r...#post_26542960

I should have checked that thread before asking. It's just so darn long that page numbers could actually be used for BIOS version numbers. :P If the posting times for the forums are the same, then that was put up about a half hour before I asked.

[kmaximo]

OMG - Finally since BIOS 1201 - The latest 3501 BIOS might finally be the magic BIOS. I can finally just pick Manual and choose Memory 3200 from drop down and don't even need to choose a D.O.C.P of any kind. I can finally use my GSkill TridentZ 4x16 Gig sticks (64Gig) at 3200. Awesome work Elmor, please keep the settings working for any future BIOS to come.

[jbasemoine]

Been messing around with 3501 bios the whole day
Still stuck on 3466 ram.
RGB headers don't work anymore (CPU fans are still the right colour but can't set case to Mobo color, cooler master c700p), i have tried everything with aura but am unable to set color of fans and case, somehow t saved the colour sceme of my fans and there still the wanted color.
CPU temp still jumping around on idle there is a +/- 10 degrees fluctuation... on load the fluctuation jumps around +/- 15 degrees... so it's somewhere between 44 and 59 degrees celcius :S