| NEWS | HISTORY | DOWNLOAD | TIPS&TRICKS |
As you probably know, both NVidia and Intel companies have developed its own extensions to the DDR3 SPD JEDEC specification known as Intel XMP and NVidia EPP2.0 respectively. These extensions enable users to over-clock memory modules automatically in accordance with predefined settings for memory timing parameters – profiles. Unfortunately, DIMM vendors used not to integrate both the competitive profiles on a single memory module for some reason. We suspect Intel do not authorize to use any third-party SPD extensions on XMP-certified products. Therefore, Intel’s partners would not make relationship with Intel worse and to get involved into troubles. As to NVidia, its over-clocking EPP2.0 extension is not very popular comparing to XMP, because the EPP2.0 Specification is confidential for years and it has never been available for public use. The company seems to not care of the future of its technology. As you remember, NVidia is the first company that dared to violate JEDEC’s DDR2 SPD Specification and proposed an absolutely new method of memory over-clocking through the EPP1.0 profiles. The idea was too excellent to go unnoticed by such a major player as Intel. Beginning from Thaiphoon Burner 6.6.0.0 it is possible to convert XMP profiles to EPP2.0 profiles as easy as to piss off two fingers. This unique feature enables both end-users and independent of Intel PC memory producers to integrate profiles from different vendors, but with identical timing parameters making memory modules to be compatible both for Intel- and NVidia-based platforms with over-clocking capabilities. This article will explain how to use XMP Enhancer Professional and NVidia EPP2.0 Enhancer add-in modules of Thaiphoon Burner to create an EPP2.0 profile to be timing compatible with a XMP profile. First of all, run Thaiphoon Burner and load XMP-enhanced DDR3 SPD firmware into Hex Editor.
As you see on the picture above, the SPD address range from 96h to AFh is not used and filled with zeros. This means EPP2.0 profiles are not implemented in the current SPD firmware. Bytes B0h-F4h are blue colored in the HEX Editor to confirm a presence of XMP-related data. Press F7 or select XMP Enhancer from the Tools main menu. Make sure you have selected a proper profile to be converted. We are going to convert Profile 1. Therefore the Profile 1 button has to be down. Now click on Profile and select the Save as NVIDIA EPP2.0... command.
For the first time you may save a converted XMP-profile in any folder you want. But before conversion we recommend you to create EPPTemplates folder which is used by EPP2.0 Enhancer to store EPP-files. This folder should be created in the root folder of Thaiphoon Burner. Anyway, the EPPTemplates directory is created automatically by EPP2.0 Enhancer when importing EPP-files to the EPP2.0 template list. So, let’s save converted data to C:\OCZ3X16001G.ep2 file. Close XMP Enhancer. Press F5 or click Tools and select EPP2.0 Enhancer to be appeared.
As you see, there is no any data regarding EPP2.0 profiles and all the fields are empty. Since XMP Enhancer Professional converts Intel profiles to NVidia profiles of Full type, we will create an EPP2.0 profile of Full type as well. The Full type is preferred comparing to Basic type, because it provides more timings to be defined. But now we are going to import our converted XMP profile. Note, it is the EPP2.0 profile already. So, click on the Profile main menu, select Profiles List and click on Import to List from File.
Open your saved OCZ3X16001G.ep2 file. Now it appears in the EPP2 Profiles List dropped-down box and can be used to configure all timing parameters at once. To create a new profile click on the Profile main menu, select Create New and click on the Full Format Profile command. Now select the OCZ3X16001G profile from the EPP2 profile List to fill empty Profile 1 with data from the selected template. Click the Next button and apply changes.
To check if the profile has been converted and integrated properly switch Thaiphoon Burner to the Report mode and compare your EPP2.0 Profile 1 with XMP Profile 1. Now you can make sure everything is done correctly.
Since SPD firmware features two XMP profiles you may use the steps described above to create the second EPP2.0 profile. |
||||||||||||||||||
|
||||||||||||||||||
Project by Vitaliy Jungle |
Company Location |