2016/05/11 17:56:48
ValkyrieStar
Introduction
Some of you may have read a few of my posts, in particular those about my lack of success running my memory at its 3200 XMP Profile. Recently I've been modifying BIOS's to add support for NVMe booting and other Samsung SSDs to be bootable. Out of curiosity, I updated the CPU MicroCode in the BIOS for my X99 Micro 2 in attempt to get C-States stable while overclocking, unfortunately it didn't help - it did however change another thing - I can now run my 3200 XMP Profile! So here's my updated versions of the BIOS's for EVGAs X99 series boards.
 
Release Version 1
 • Downloads
 • Updated Haswell-E MicroCode (revision 37).
    - Improved Memory Compatibility
 
Release Version 2
 • Downloads
 • Updated Broadwell-E MicroCode (revision 19).
    - Preliminary Broadwell-E Support
 
Release Version 3
 • Downloads
 • Updated Intel Management Engine Firmware (version 9.1.37.1002).
    - Broadwell-E Support (untested as of 20-May-2016)
    - Might Break BLCK Overclocking
 
Disclaimer
I cannot be held responsible for your actions! I provide these files for you to try and use AT YOUR OWN RISK.
2016/05/11 18:16:19
V84x4
WOW thank you very much.........and congrats on running your ram @ 3200
you must be some very smart person 
 
However I will not attempt this until I see and hear from others (Based on your disclaimer)
I am hoping evga Tech support will test your files and maybe make them a "Sticky"
 
I am not having a problem as far as I can tell
I am able to achieve 3200 stable and have ran tests to make sure I was getting a true 3200
 
But again I thank you for your support and efforts for the Micro 2 issues
 
I am happy to be able to learn from this community
 
Best Regards, Rick
 
2016/05/11 18:30:20
ValkyrieStar
V84x4
WOW thank you very much.........
you must be some very smart person 
 
However I will not attempt this until I see and hear from others (Based on your disclaimer)
I am hoping evga Tech support will test your files and maybe make them a "Sticky"
 
I am not having a problem as far as I can tell
I am able to achieve 3200 stable and have ran tests to make sure I was getting a true 3200
 
But again I thank you for your support and efforts for the Micro 2 issues
 
I am happy to be able to learn from this community
 
Best Regards, Rick
 




Haha thanks! I've been modding away at other BIOSes too, over at LTT Forum i've a thread about adding boot support for NVMe and Samsung M.2 SSDs into bioses too.
If you're already at 3200 with no issues, then there's probably not much of a reason to try this. It's mainly for those with having problems with memory.
 
Hopefully EVGA will take this onboard and perhaps incorporate the latest microcode into their new bioses.
 
Things that could be updated by EVGA:
-MicroCode
-ME Firmware
-RAID/Sata OpROMs
-Ethernet PXE/OpROMs
 
I see no reason why they shouldn't be updated. All 4 of those things are provided by Intel, so it can't make anything worse, so why not?
I'll look into trying to find out how to update those myself in the meantime though.
2016/05/12 02:01:10
eckertt001
Appreciate the work put into this.  I though was unable to set my memory to 3200, still received blue screens.  This was using either M.2 compatibility on or off.
 
Are their other specific settings you used?
2016/05/12 02:06:39
ypsylon
OK, now that's what I call a constructive input.
 
Well done sir. Now if you could help with RAID controllers compatibility (EVGA so far ignored this problem despite repeated problems) I would be eternally grateful. :)
2016/05/12 03:32:45
SuperConker
This might be because the new CPU MicroCode adds support for Broadwell-E CPU's
(Broadwell-E supports DDR4 at 2400 Mhz instead of 2133 Mhz on Haswell-E, a difference of 267 mhz).
 
With 267 extra Mhz to work with, it should be possible to use RAM modules with speeds of up to 2933 mhz,
without any issues (and possibly higher speeds).
 
With Haswell-E, DDR4 speeds higher than 2666 Mhz was a problem.
2016/05/12 07:37:59
ValkyrieStar
SuperConker
This might be because the new CPU MicroCode adds support for Broadwell-E CPU's
(Broadwell-E supports DDR4 at 2400 Mhz instead of 2133 Mhz on Haswell-E, a difference of 267 mhz).
 
With 267 extra Mhz to work with, it should be possible to use RAM modules with speeds of up to 2933 mhz,
without any issues (and possibly higher speeds).
 
With Haswell-E, DDR4 speeds higher than 2666 Mhz was a problem.


The CPU microcode is specific to haswell e only right now, there are broadwell e microcodes out, but ill let evga sort that themselves, i have no means to test any btoadwell chip.
2016/05/12 07:39:59
ValkyrieStar
ypsylon
OK, now that's what I call a constructive input.
 
Well done sir. Now if you could help with RAID controllers compatibility (EVGA so far ignored this problem despite repeated problems) I would be eternally grateful. :)


Whag in particular is the problem with the raid controllers?
No boot support or not detecting at all?

I doubt id be able to do much in the way of this but i can look into it.
I have no raid controllers to test either
2016/05/12 07:44:21
ValkyrieStar
eckertt001
Appreciate the work put into this.  I though was unable to set my memory to 3200, still received blue screens.  This was using either M.2 compatibility on or off.
 
Are their other specific settings you used?


There was no other specific setting that i used.
I just flashed the bios, and put in all my normal config values, except this time i enabled xmp profile 1, which previously boot looped, and it worked.

What memory kit are you using? My kit is Corsair LPX 3200 C16 (4x8GB).
2016/05/12 12:39:41
ValkyrieStar
Update
I have managed to get Broadwell-E microcode into the BIOS!
This should allow Broadwell-E cpus to be supported!
 
I have updated links in the main post to point to the updated files.
 
Disclaimer
I cannot be held responsible for your actions! I provide these files for you to try and use AT YOUR OWN RISK.

Use My Existing Forum Account

Use My Social Media Account