Results 1 to 6 of 6

Thread: Corsair Vengeance XMP profiles

  1. #1
    Join Date
    May 2011
    Posts
    450

    Corsair Vengeance XMP profiles

    Immediately got memory kit revenge - CMZ12GX3M3A1600C9 - as well as there were pair of XMP profile. Profile of a memory had in 1.50, 1.20 and VTT at instance of 9-9-9-24 2T. RAM Profile 2 was 1.50, 1.35 and VTT at the time of 6-9-9-24 2T. Is this so? The "6" appears to be out of shape online. Could be programmed SPD bad. Anyone have any knowledge about this issue can reply me with the solution and also let me all other difficulty related to it.

  2. #2
    Join Date
    May 2008
    Posts
    1,137

    Re: Corsair Vengeance XMP profiles

    Yellow – I have managed to recover my old RAM modules that you can use when processing an RMA. As the thread of the gentleman who jumped to here, I think I should do that exchange. Otherwise, just remain bothering me. I know a number of people might seem inconsequential; nevertheless .Others is cursed in the midst of thoroughness. Nevertheless I wonder what the manufacturer has to pronounce about this.

  3. #3
    Join Date
    Feb 2008
    Posts
    1,260

    Re: Corsair Vengeance XMP profiles

    CAS modification is not the simply thing that is dissimilar flanked by the two profiles XMP. The one in the midst of the 9 CAS, vtt of 1.2 volts plus the one with CAS 6 has vtt of 1.35 volts. According to discussion I read here, CPUs requires 1.2 volts and the other CPUs are theoretical to make use of 1.35. It actually could get into trouble if I use XMP to 1.35v. The computer is not likely post. You should put everything manually, which denies a bit to XMP.

  4. #4
    Join Date
    May 2008
    Posts
    1,295

    Re: Corsair Vengeance XMP profiles

    I just went to my case RMA #: 2015264 and I realized that 4 of the 6 modules I entered information RMA to have been dumped only 2 remain. After completing the missing fields and presents information in new-fangled, re-entry into the quantity of my case, two modules to put on show information, the further 4 missing. I have a 6 pack tuning modules, 24 GB: CMZ24GX3M6A1600C9.

  5. #5
    Join Date
    Nov 2008
    Posts
    866

    Re: Corsair Vengeance XMP profiles

    T hat is why I would not use the profile 2. Profile 1 (9-9-9-24 1.5v 1.2v) works very well, but that's not the point. My friend has modules for revenge has a profile like 9-9-9-24 2T 1.35v 1.5vy profile 9-9-9-24 1.20v 2 is 1.5v. Therefore, I would say that the profile of two of the modules we have is incorrect. There seems to be a manufacturing problem. I just want my modules are correct if it sells or moves to another machine.

  6. #6
    Join Date
    May 2009
    Posts
    857

    Re: Corsair Vengeance XMP profiles

    Well, I have a new set of modules installed revenge, and as I said, I'm not surprised at all! Different lot numbers except the version and the same unsolved problem! Although I am surprised that no one thought to confirm this claim before simply throw a spare pack in the mail that has resulted in a complete waste of time and money. The RMA cured nothing and I am returning this set until a definitive answer.

Similar Threads

  1. Replies: 1
    Last Post: 10-04-2012, 07:23 PM
  2. Corsair Vengeance Vs Corsair XMS3
    By Absolom in forum Motherboard Processor & RAM
    Replies: 7
    Last Post: 20-03-2012, 10:49 PM
  3. Does Corsair Vengeance 1500 compatible with PS3
    By Shrestha in forum Hardware Peripherals
    Replies: 9
    Last Post: 12-12-2011, 06:35 AM
  4. Corsair Low Profile Vengeance vs. Corsair Standard Vengeance
    By Martyna in forum Motherboard Processor & RAM
    Replies: 3
    Last Post: 02-10-2011, 10:30 PM
  5. Corsair Vengeance having heat spreaders
    By Wolf$Broad in forum Motherboard Processor & RAM
    Replies: 3
    Last Post: 25-07-2011, 08:34 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,713,260,947.38716 seconds with 17 queries