BIOS A49 Updates:

• Corrects EventID 46 error when two CPU's are installed

---

CD/DVD Installation - Recommended installation method

• Download the correct .zip file below for your motherboard:

              W555_A49.zip

• First go into your BIOS and load defaults, save and exit
• Go into the folder where you unzipped this package and run the appropriate batch file.
  • For Windows XP, Vista or 7 32Bit: AFUWIN32.BAT
  • For Windows XP, Vista or 7 64Bit: AFUWIN64.BAT
  • If in DOS Mode: AFUDOS.BAT
• Press Y in CAPITAL LETTERS to start the flash process
• DO NOT TURN OFF POWER OR RESET DURING THE FLASH PROCESS
• After the flashing is finished, shut down the computer. Then power on again and go into BIOS, Load Defaults, Save and Exit.

Warning:
**Do not restart or interrupt your PC while the flash is ongoing
**Do not Flash BIOS on overclocked settings
**It is always recommended to power-down after flash and Clear CMOS

There should be no problems updating my stock SR-2 to this, correct? (I did not flash the previous version of the sr-2 bios)

Confirmed the unusable overclocking profile issue is fixed.
But the uncore multiplier is still not effective and CPU settings show B0 stepping for my XEON X5650 (Which is retail boxed and should be B1 stepping), also the wake up capabilities is still not available. I can't wake the SR-2 up from S5 status and there are no settings about waking up from PCI-E devices available. Can anyone please help?

sunderstan

Confirmed the unusable overclocking profile issue is fixed.
But the uncore multiplier is still not effective and CPU settings show B0 stepping for my XEON X5650 (Which is retail boxed and should be B1 stepping), also the wake up capabilities is still not available. I can't wake the SR-2 up from S5 status and there are no settings about waking up from PCI-E devices available. Can anyone please help?

Same issue here, Retail B1 Xeon X5650 showing as a B0 in BIOS and uncore not working/sticking.

sunderstan

Confirmed the unusable overclocking profile issue is fixed.
But the uncore multiplier is still not effective and CPU settings show B0 stepping for my XEON X5650 (Which is retail boxed and should be B1 stepping), also the wake up capabilities is still not available. I can't wake the SR-2 up from S5 status and there are no settings about waking up from PCI-E devices available. Can anyone please help?

 
I hope the profiles is fixed - it is a giant waste of time not being able to rely on them...
 
How do you tell what uncore is actually set from in windows? I have been playing with uncore in the A47 bios and have not noticed any difference. 

Ditto -- uncore mutiplier won't go lower than 20x on x5680 retail (with 10x memory multiplier).
However, uncore multiplier can go lower with x5650 (ES).
 
EVGA -- can you confirm this is a known/expected issue and whether a fix will come? 
 

jwmiele

I have same on retail boxed 5680's as well.. Joe

The following issue is still pending for a fix...
 
1. System date time reset after clear CMOS.
2. Unable to use E-LEET to tune CPU1 related voltage when CPU0 is disabled
3. When saving the overclocking profile, after save and exit, other profile data will be deleted except the saved one. For example, I saved 4Ghz profile to Profile3, then save, then go back and save 3.6Ghz profile to Profile4, then profile3's data will be deleted and cannot be used. To make things worse, after saving the profile and reboot, the PC will never boot up again, stucked at debug code "06" but after a HARD RESET the system will post just fine
4. Lack of capability to wake up by PCI-Express devices <= Confirmed can wake up from external LAN Cards but not Marvell 88E8057 built in LAN.

I think it would be nice to be able to name the presets like in... almost every mobo haha :/

Guys, did anyone get this message after updating the latest bios?
 
Warning: BIOS doesn't have EC. EC progrmaming canceled.
 
 

Thanks worthy.

Just reseat them, it will fine. It happened to mine as well.

Jacob - any new bios update comming soon? it seems we all have various valid issues which i am sure a bios update could fix easily.