Hello,
 
If I am not mistaken, you are referring to the microcode? There was a BIOS update in April for the X99 FTW K that addressed this: https://www.evga.com/support/download/showdlinfo.aspx?id=15431&type=N&acctype=BIOS&accversion=2.05&part_number=151-BE-E097
 
Hopefully this is what you were looking for!
 
-Jacob B.

Probably the new vulnerabilities that have been found after the Spectre/Meltdown one. IIRC, they were similar to them.

bcavnaugh
It is about not being able to Overclock on the Broadwell E CPU on the X99 FTW K Motherboard under the Prerelease Version of Windows 10 1809.
So hey...any chance of a fix for Windows RS5 KILLING ALL OVERCLOCKING ON X99?
Maybe
Broadwell-E users intel microcode update KB4100347 kills Broadwell-E overclock
 
It is not an issue on the Haswell-E CPU on the X99 FTW K Motherboard running the RTM version of Windows 10 1809.

Yes, since it isn't an issue with the RTM version of 1809, I wrote it off as not the reason for his request 23 hours ago. So what is his request? Is it for spectre/meltdown protection? No, that microcode update was already released by EVGA. So, again, what is his request? It is a mystery.

That's what I did. My response to you was to show that your input was not helpful in answering that question.

EVGATech_JacobB
Hello,
 
If I am not mistaken, you are referring to the microcode? There was a BIOS update in April for the X99 FTW K that addressed this: https://www.evga.com/support/download/showdlinfo.aspx?id=15431&type=N&acctype=BIOS&accversion=2.05&part_number=151-BE-E097
 
Hopefully this is what you were looking for!
 
-Jacob B.

Of course not. I'm already running 2.05. Why would I be looking for an old BIOS update when I am specifically asking for the ucode update to address the latest issue of overclocking being disabled via in OS ucode update by intel? They ARE INCOMPATIBLE. Holy cow....you must know of this issue.

Removed

Removed

bcavnaugh

HeavyHemi

bcavnaugh

HeavyHemi

ty_ger07

bcavnaugh
It is about not being able to Overclock on the Broadwell E CPU on the X99 FTW K Motherboard under the Prerelease Version of Windows 10 1809.
So hey...any chance of a fix for Windows RS5 KILLING ALL OVERCLOCKING ON X99?
Maybe
Broadwell-E users intel microcode update KB4100347 kills Broadwell-E overclock

It is not an issue on the Haswell-E CPU on the X99 FTW K Motherboard running the RTM version of Windows 10 1809.

Yes, since it isn't an issue with the RTM version of 1809, I wrote it off as not the reason for his request 23 hours ago. So what is his request? Is it for spectre/meltdown protection? No, that microcode update was already released by EVGA. So, again, what is his request? It is a mystery.

Actually you're wrong and confusing the issue.  April is not addressing the current issue of the ucode being used my MS and provided by intel is INCOMPATIBLE with our X99 BIOS ucode.
In other words, without using the older .dll file overclocking is broken. Please exit this thread if you can't read.  Jaysus.

You are confusing the issue, what Issue I have no issue on none of my X99 MB's the X99 Classified or FTW K Motherboards.

I don't care if you don't have the issue with your processor. Folks with Broadwell-E, do.  Why are you arguing with me in my thread with my issue? Holy cow.

I am not arguing with you, we are only tying to find out what the Issue Really IS.
You said I was wrong at what I posted and linked So hey...any chance of a fix for Windows RS5 KILLING ALL OVERCLOCKING ON X99? and Broadwell-E users intel microcode update KB4100347 kills Broadwell-E overclock because that is what I thought you were taking about.
 
You need to calm down and be Civil on this Forum we are only trying to fine the truth with your Problem.
 
https://hothardware.com/news/intel-broadwell-e-overclocking-wrecked-by-windows-10-update
Fortunately, it's reported that KB4346084 resolves the issue.
Fortunately, it's reported that KB4346084 resolves the issue. Several users report that uninstalling KB4100347 and installing KB4346084 restores the overclocked settings, though it's not clear if the former update actually needs uninstalled—the latter one is supposed to override it.
 
 
You have too many Threads on this Issue and that is not helping maters for you as well.

 
I'm on RS5 there's no KB to remove. It is now integrated into the OS. You do not know what you are talking about. Please stop posting in this thread. Thanks.

Removed

Removed

HeavyHemi

ty_ger07
I wasn't trying to crap on your parade. It is just really hard to know what you want if you don't say it. You see where assumptions got us? It turned into a mess, didn't it?

No, I see where you two started arguing. Don't even try to blame me. FFS

What were we "arguing" about? Guessing what your request was.
By the way, I wasn't arguing. But Bcav came in swinging for some reason.

Sorry about your thread! Maybe you can edit the first post to clearly state what you want, and then ask a moderator to "clean up" the rest into the trash can.

EVGA's representative didn't even know what "ucode" meant nor what you wanted. I clarified that ucode was an abbreviation for microcode and encouraged you to respond and clarify what you were after. The rest was needless.

ty_ger07

HeavyHemi

ty_ger07
I wasn't trying to crap on your parade. It is just really hard to know what you want if you don't say it. You see where assumptions got us? It turned into a mess, didn't it?

No, I see where you two started arguing. Don't even try to blame me. FFS

What were we "arguing" about? Guessing what your request was.
By the way, I wasn't arguing. But Bcav came in swinging for some reason.

Sorry about your thread! Maybe you can edit the first post to clearly state what you want, and then ask a moderator to "clean up" the rest into the trash can.

"Yes, since it isn't an issue with the RTM version of 1809, I wrote it off as not the reason for his request 23 hours ago."
 
You're just flat out wrong, so I don't care what you wrote off and argued about. Is that clear?  I would like a fix for the BIOS for the specific issue I have identified before.  My bad for not adhering to your standards. Argue with someone else.

ty_ger07

HeavyHemi

ty_ger07

HeavyHemi

ty_ger07
I wasn't trying to crap on your parade. It is just really hard to know what you want if you don't say it. You see where assumptions got us? It turned into a mess, didn't it?

No, I see where you two started arguing. Don't even try to blame me. FFS

What were we "arguing" about? Guessing what your request was.
By the way, I wasn't arguing. But Bcav came in swinging for some reason.

Sorry about your thread! Maybe you can edit the first post to clearly state what you want, and then ask a moderator to "clean up" the rest into the trash can.

"Yes, since it isn't an issue with the RTM version of 1809, I wrote it off as not the reason for his request 23 hours ago."
 
You're just flat out wrong, so I don't care what you wrote off and argued about. Is that clear?  I would like a fix for the BIOS for the specific issue I have identified before.  My bad for not adhering to your standards. Argue with someone else.

Ok, fine. I was wrong. So was everyone else in this thread. So what? No one knew what you wanted. EVGA's rep didn't even know what "ucode" meant.

I was trying to help by confirming the meaning of "ucode" and encouraging you to clarify your request.

I was trying to help. Sorry you didn't want it. Feel free to be more clear next time and feel free to guide the direction of your own thread.

Good luck!

And there you go blaming me again for the way you acted with YOUR assumptions. Grow up.

ty_ger07
I am not blaming anyone. I am not even arguing. Now we are arguing about whether we are arguing. It's getting dumb. Just accept that I was trying to help. Or leave it be.

 
You didn't ask me what I meant, you made assertions:
 
"Yes, ucode = μcode = microcode.
I don't know which specific update he is requesting either. It's very cryptic due to complete lack of details."
 
From that point on, you were making noise arguing.
I'm sorry, but apparently you just can't let it go. You, leave it be, now.

If EVGA is unwilling for any reason, you could make a request directed at Regeneration.