BIOS version: 1202 Date:05/23/2007

Checksum: A800H

01.Update NV RAID ROM to 6.98
02.Update NVMM to 4.A72.24
03.Support wolfdale CPU.
04.Release EZflash B322
05.Add microcode not found & update fail message.
06.Modify CPU fan speed warning item value.

============================================================ =======================
BIOS version: 1201 Date:05/09/2007

Checksum: 1200H

01.Use new French translation.
02.Modify General Help string.
03.Use new B5 translation.
04.Fixed floppy item value error.
05.Skip checking 2nd Checksum for some memory patch
06.Disable unused PCIE Bridge to fix
a.DTM -PCI Compliance issue
b.ATI Crossfire fail issue.
07.Use new GB translation.
08.Patch Hynix HYMP512U64CP8-S5-AB when Full Loading for stability
09.Release EZ Flash2 version B321.
10.Update new microcode :
a.New Micro Code for CPU: 06FBH Patch ID=B3H Platform ID =10h (Kentsfield-G0).
b.New Micro Code for CPU: 06FBH Patch ID=B3H Platform ID =01h (Conroe-G0).
c.New Micro Code for CPU: 06FDH Patch ID=A1H Platform ID =01h (Conroe-M0).
11.Use new Japanese translation.
12.Support post message in Japanese
13.Added SATA trap for MCP55.
14.Fixed L1 and L2 cache size will show incorrect in DMI with Conroe-L CPU.
15.Update Micro Code for CPU: 10661H Patch ID=32H Platform ID =01h (Conroe-L-A1).
16.Fixed Conroe-L CPU L2 cache size show incorrect issue.
17.Update Micro Code for CPU=0F65H ID=09H Platform ID=04h. (Cedar Mill/Cedar Mill ICP/Presler)
18.Fixed when Post96h update DMI data and AC power loss.The DMI data might be destroyed.

1.Fix incorrect display of Vcore value when above 1.80V.
2.Fixed CPU Vcore cannot be set by user when Overclocking at some frequency.
3.Support new CPUs, please refer to our website at: http://support.asus.com/cpusupport/c...iker%20Extreme

Striker Extreme Release BIOS 0701
1. Fixed NB Core voltage setting error when CMOS fail
2. Enable support for Conroe 1333MHz processor
3. Fixed VID incorrect after OC to 1201Mhz(FSB)
4. Added New Micro Code to support new CPU
5. Finetune CPU temperature calculation algorithm
6. Displays "Press TAB to display BIOS POST Message" string even when full screen logo is enabled.
7. Correct incorrect info under Summary screen.
8. Correct "SLI-Ready Memory Detected" display problem at POST
9. Fixed CPU not restore back to original frequncy after CPR
10. Add help string for HPET item.

Striker Extreme release BIOS version 0505
1. Support Max LDT Frequency from 5X to 8X
2. Fine tune CPU Temperature detection code
3. Fixed some default value can't save when using BIOS Profile function.
4. Enable adjustments for tRD and TrFC item
5. Enhance DDR667 memory compatibility
6. Enhance performance for Corsair CM2X1024-9136C5D
7. Fixed CPU Voltage max option drops to 1.60V when set Multi-Language option to 'Tri Chinese' , 'Sim Chinese' or 'Japanese'.

AI Tuning: Manual
Nvidia GPU Ex: Disabled
LinkBoost: Disabled

FSB - Memory Clock Mode: Unlinked
x FSB - Memory Raio: N/A
FSB (QDR), Mhz: 1066 (means 266FSB)
Actual FSB (QDR), Mhz: 1066.7
MEM (DDR), Mhz: 667 (means 333mhz speeds)
Actual MEM (DDR), Mhz: 666.7

Vcore Voltage:
Memory Voltage:
1.2v HT Voltage:
NB Core Voltage:
SB Core Voltage:
CPU VTT Voltage:
DDRII Controller Ref Voltage:
DDRII Channel A Ref Voltage:
DDRII Channel B Ref Voltage:

tCL (CAS Latency): 4
tRCD: 4
tRP: 4
tRAS: 12
Command Per Clock (CMD): 2 clock (2T)

Advance Memory Settings
tRRD: AUTO
tRC: AUTO
tWR: AUTO
tWTR: AUTO
tREF: AUTO
Async Latency: AUTO

CPU Spread Spectrum: Disabled
PCIE Spread Spectrum: Disabled
MCP PCIE Spread Spectrum: Disabled
SATA Spread Spectrum: Disabled
LDT Spread Spectrum: Disabled

CPU Internal Thermal Control: Disabled
Limit CPUID MaxVal: Disabled
Enhanced C1 (C1E): Disabled
Execute Disable Bit: Disabled
Virtualization Technology: Disabled
Enhanced Intel Speedstep Tech: Disabled
LDT Frequency: 5x

PCIEX16_1 Frequency (Mhz): 100
PCIEX16_2 Frequency (Mhz): 100
PCIEX16_3 Frequency (Mhz): 100
SPP<->MCP Ref Clock, Mhz: 200

Drew Henry Interview

Drew Henry, General Manager of MCP Business at NVIDIA, took time to answer some pointed questions that will hopefully give you the solid answers you need in reference to the nForce 680i problems.

Q: Concerning the 680i issues, what EXACTLY is the problem? BIOS, driver, MCP/chipset, or other hardware? Or combination thereof?

A: The problem that some users were experiencing related to signal timings on the motherboard. The new BIOS (P32) corrects this.

Q: Is the fix a workaround that compromises other technology on the motherboard?

A: Absolutely not. We should have caught this in our internal QA process. Unfortunately, we didn't, and we have adjusted internal processes to make sure that this does not happen again. As the manufacturer of these products, we need to be absolutely certain that the quality of the product that is brought to market is top-notch and that the experience that consumers will be receiving is nothing but positive.

Q: Are there “bad” 680i MCPs/chipsets out there?

A: No. This is not a MCP issue. It's really a board issue, and in this case, only with the motherboards that were designed and manufactured by NVIDIA. In fact, boards built by other manufacturers that use the same MCPs, including the ASUS Striker Extreme, ASUS P5N32-E SLI, and the ASUS P5N-E SLI motherboards, are NOT affected. When you hear of customer issues, your first thought is "how widespread is this," but it was pretty clear early on that it related only to the boards that we designed and manufactured. Talk about embarrassing!

Q: Why would the issue impact one board and not another on the same exact hardware/software install?

A: There are statistical variations in electrical characteristics between boards, which in some cases, can mask the underlying issue. The BIOS adjusts timing in a way that avoids this condition.

Q: Is this P23 BIOS going to cure all 680i users' SATA problems?

A: We believe so. We are releasing a BETA BIOS version so that customers can use it. We are completing our testing and will release a final version soon.

Q: So what do you have to say customers that have had to endure this frustrating set of events?

A: We are sorry they had to go through it. We've spent all of this time, money and engineering resources to make the best possible platform for Intel CPUs, and then just as our customers and partners are experiencing awesome success with the new NVIDIA nForce 680i SLI motherboard, this happens. The bottom line is that our QA process missed this condition. Once we identified the problem it became our top priority to solve it. The information provided by the forum members proved to be very valuable. They were really instrumental in helping us identify this issue and provide a solution.