Xeon E5-26xx V4 ES & ASUS x99-A II

[JMicro]

but i think my xeon has cpuid=0x406F1, not 0x406F0

Look at your screenshot: stepping is 0, not 1.

you are right, my fault

   

but then the problem is clear, there is no support for that cpuid in every bios i checked

included UBU, which add support ONLY for 406f1

is there a method for rescue ES microcodes for that particular cpu from another board?



today i received a release 2638L v3 SR209 "new" CPU, if nothing else works im going to change with the unsupported one
I prefer the 2630 v4, if i can make the board works with it


Thank you so much for your help and time

[DeathBringer]

is there a method for rescue ES microcodes for that particular cpu from another board?

What's donor motherboard?

[aleksandrphp]

It's not microcode problem because BIOS versions 1504, 1701 and 1801 have the same microcode for this ES CPU with CPUID=0x406F0.
Try to flash previous versions of BIOS: https://rebyte.me/en/asus/149096/#bios

I have same problem. M/b Asus X99-A USB 3.1 and Xeon E5-2650Lv4 ES (406F0) and ERROR 19.
May be Asus specially spoils microcode? Otherwise with what to explain that Asrock, MSI, Gigabyte, Evga works normally with Xeon ES, but Asus no?

[DeathBringer]

Read this this topic attentively. It's not microcode problem.

[aleksandrphp]

Read this this topic attentively. It's not microcode problem.

Read absolutly attentively. Asus and Asrock m/b consist same chipset, same other components. But result is different. I think, diffference in BIOS.

[DeathBringer]

diffference in BIOS.

Yes, in BIOS code, but not in microcode.

[aleksandrphp]

Yes, in BIOS code, but not in microcode.

Yes. For experiment extract microcode 06F0 from Asrock X99 Fatality Gaming i7 and Asus (in Asus two them, see attach. Why?), calc MD5 hash and compare. Identical

[joseperal]

Yes, in BIOS code, but not in microcode.

Yes. For experiment extract microcode 06F0 from Asrock X99 Fatality Gaming i7 and Asus (in Asus two them, see attach. Why?), calc MD5 hash and compare. Identical

Hi all, same problem here, I bought on ebay an E5-2630L v4 M0 stepping CPU and I´m getting Q-code 19 on bootup on my Asus X99-E-10G WS motherboard.

Checking on the BIOS menu, CPU signature is 406F1, and uCode patch: b00001a

If I boot pressing the clear CMOS button on the mother board it boots and enters the BIOS. Then in the BIOS menu, pressing F8 and clicking on my Windows partition, the system boots sucessfully. I stressed the CPU and it seems genuine, 10 cores and 20 threads all working as expected.

But, it is a pain booting the computer trought the BIOS every time, and if I try to save any config on the BIOS then I got trapped on the Q-code 19 trap again.

I updated the bios to latest from ASUS for my board but issue still present (v1101), I checked it with MM tool and the CPU microcodes present are:

  vol3 no1 06F6F23D - 6F - 06F2 - 3D - 2018-04-20 - 8400bytes
  vol3 no2 0EF6F113 - EF - 06F1 - 13 - 2013-10-02 - 8800bytes
  vol3 no3 0EF6F12E - EF - 06F1 - 2E - 2018-04-19 - 7000bytes
  vol3 no4 0EF6F014 - EF - 06F0 - 14 - 2015-07-02 - 7C00bytes

I checked on the eBay CPU description and the seller adverted that Asus Z10PE-D8 supported E5-2630L V4 M0 CPU, so I downloaded the latest official bios (v4001) and I compared the microcodes with MMTool v5.

I realized that the Asus Z10PE-D8 board supporting E5-2630L v4 have 2 microcodes for 06F0, revision 17 and revision 14. While my BIOS only has revision 14 on it.

vol4 no1 06F6F23D - 6F - 06F2 - 3D - 2018-04-20 - 8400 bytes
vol4 no2 0EF6F114 - EF - 06F1 - 14 - 2014-01-10 - 8800 bytes
vol4 no3 0EF6F017 - EF - 06F0 - 17 - 2013-07-30 - 6C00bytes
vol4 no4 0EF6F12E - EF - 06F1 - 2E - 2018-04-19 - 7000 bytes
vol4 no5 0EF6F014 - EF - 06F0 - 14 - 2015-07-02 - 7C00bytes

Why the revision 17 has 2013 date, and revision 14 has 2015 date??!!

I patched my bios replacing revision 14 (7C00 bytes) by revision 17 (6C00 bytes). Revision 17 is smaller, so I padded the end of the file with zeros.

Result was unsucessfull   I could´t flash the file at all.

When I saved the image I got the suspicius message from MMTool: ´Saving Secure Capsule as unsigned´

When I tried to flash the BIOS from the BIOS itself I got the error message: ´Selected file is not UEFI Bios´. 

Find here attached the files I played with and MMtool v5.

Does anyone know what is going on here?!
How to sign the Capsule?

[massimo.cressoni]

Hi everyone, I'm new, I hope I'm not bothering you or having the wrong page, this forum was recommended to me regarding bios changes, I own an Asus x99-A II, I have a xeon and 5 2699 V3s, my problem is which stops at 2.8 ghz and doesn't go into turbo boost at 3.6, I was told that to make it work completely the bios must be modified, by any chance do you already have the bios set up here? Thanks for your help