Announcement

Collapse
No announcement yet.

Problem configuring RipjawsX F3-12800CL9D-8GBXL on ASUS P8P67 EVO motherboard

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Problem configuring RipjawsX F3-12800CL9D-8GBXL on ASUS P8P67 EVO motherboard

    Hi guys,
    I'm new on this whole running DDR3 at 1600MHz thing and need some help on configuring my PC.

    I just bought a ASUS P8P67 EVO motherboard and got myself a G.Skill DDR3 1600MHz 8GB (F3-12800CL9D-8GBXL).

    I was trying to install Windows 7 64-bit but it keeps crashing and gives me a blue screen.

    I just can't understand why it keeps crashing. Is is that my memory is incompatible? I don't see any other obvious errors in the hardware. Everything seems to be working fine.

    I initially tried to install the OS with DDR3-1333Mhz, but it crashed. Then I changed the Ai Overclock Tuner to X.M.P so I can enable the DDR3-1600 9-9-9-24-2N at 1.5V but it still kept crashing.

    Do I need to change these CAS settings??

    I've already been through 2 Gigabyte motherboards and got my money back and bought an ASUS and it too seems to have the same problem. I don't think they are motherboard problems anymore. It has to be something to do with the memory.

    Perhaps I should just buy the DDR3-1333 8GB instead of trying to run the 1600.

    Can someone please help. Need urgent help.

    D.

  • #2
    Test one at a time with XMP. Seems like one is defective causing a problem. This memory should work flawlessly with XMP enabled, nothing else.

    Thank you
    GSKILL TECH

    Comment


    • #3
      Hi mate,

      I tried that and it still didn't work. Unfortunately, I must say that the G.Skill Ripjaws and Ripjaws X has been nothing but trouble for me.

      The whole P67 chipset has been a total nightmare. Having to QA Gigabyte, ASUS and now G.Skill products just to get a PC working is a nightmare. It was never like this back in the days. They worked very well.

      I guess this is the risk/agony you have to put up for trying to get the latest hardware out there.

      Comment


      • #4
        Do yo have the latesst BIOS, they've been updating fairly fast to fix their problems


        Pls offer comments on support I provide, HERE, in order to help me do a better job here:

        Tman

        Comment


        • #5
          Yup, I updated to the latest BIOS and it still didn't work. I tried each module by itself and it still failed.

          I spoke with to a guys who does PC building and he said they don't recomend using XMP and they seem to (I think) overclock the memory to run at 1600MHz. If that makes sense. I'm not an overclocking person and don't know much about it... so I hope what I just wrote doesn't wound stupid.

          I did try with XMP and non XMP but they all failed.

          Even running at 1333 fails.

          Comment


          • #6
            Crashes like this are usually indicative of a hardware failure. If testing individually with each stick causes crashes I'd lean to the problem lying in the mobo or CPU. Might see if you can borrow a stick from a friend or co-worker, etc and try it...if you know the stick works fine in another system then that should eliminate the sticks. Could also try pulling, cleaning and reseating the CPU...have recently had a few people let some thermal compound seep under the CPU and/or not had the CPU fully seated.


            Pls offer comments on support I provide, HERE, in order to help me do a better job here:

            Tman

            Comment


            • #7
              I was pretty convinced that it was the CPU at the beginning, but then after doing some test it looked like it was the motherboard and then gave one of the PC builders to check it out as well and they said it was the motherboard. At the same time I did run MemTest86 but it freezes at 5% when both modules are running as 8GB. When I run each module as 4GB the test runs fine.

              The problem is that since this is a new set of 1600 Mhz ram there is no one that I know who's got a 1156 or 1155 chipset to test it against.

              Besides, I did test it with the new Asus P8P67 EVO that I bought 4 days back and it was the same problem. When I took the mb to return it they tested it with their ram and it didn't cause any problems at all. I didn't actually ask them what brand RAM it was though.

              Anyways, I've returned everything back except for the CPU and will take it to the place where I bought the CPU and get them to build it for me when the new motherboards are out in April. This way, if there is a problem with the CPU, they will have to replace it and then I can say, well I told you so... hahhaha...

              It's much more easier when you buy all from the one place, that way no one can pass the buck and keep wasting my time.

              Comment


              • #8
                Agreed, let us know how the new components work


                Pls offer comments on support I provide, HERE, in order to help me do a better job here:

                Tman

                Comment


                • #9
                  Hi mate,

                  I finally got the new P67-GA-UD5-B3 motherboard. Got the shop that I bought the motherboard to install it for me and I replaced the memory with another brand, which was the Corsair 1600GHz 8GB modules.

                  They set the memory to run at 1600 and it worked without a hitch for quite a long time. Until it decided to crash and reset the BIOS. So I had to re-configure the timing of the memory modules to 1600 as it defaulted to 1333 when it crashed.

                  I'm not using XMP as some say it's not that safe as the voltage is increased beyond the safe level. So I didn't want to try it.

                  I think G.Skill memory has some kind of issue 'cause when I had the G.Skill I had heaps of problems. Manually setting it to 1600 didn't work and crashed. It definitely doesn't work at 1333 even though it's the default and should downgrade it to that speed.

                  I'll monitor the situation with this memory but if it does crash every now and then, I'll change it to the 1333 modules and that should guarantee to work.

                  Regards,
                  D.

                  Comment

                  Working...
                  X