Announcement

Collapse
No announcement yet.

Gigabyte Z77X-UD5H with F3-1600C10D-16GAO BSOD

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

  • Gigabyte Z77X-UD5H with F3-1600C10D-16GAO BSOD

    Hi,

    I am having problems with running The 16GB(2x8GB) Ares on its advertised speed.

    When running the XMP profile for DDR1600 @ 10-10-10 V1.5, windows always crashes while running prime 95 small FFTs using ram (Custom mode with 12750MB memory to use) This test failed even though the cpu is in stock (no overclock/voltage change in bios). The crash occurs less than 10 minutes from the start of the test every single time.

    When running without XMP (DDR1333/667Mhz), the system is stable running the same test whether the cpu is stock, or overclock.


    My system is
    Intel 3770K/ Gigabyte Z77X-UD5H(BIOS F6)/ Memory F3-1600C10D-16GAO

  • #2
    Might check each stick with Memtest to see if maybe you got a bad stick, could also try raising DRAM voltage slightly in case the regulation is off and not getting full voltage, maybe up + .04


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

    Tman

    Comment


    • #3
      please make sure that you are using the F6 BIOS:

      F6 3.62 MB 2012/04/26
      Improve Sandy Bridge CPU overclocking
      Support Intel Xeon Processor

      http://www.gigabyte.com/products/pro...?pid=4139#bios

      Comment


      • #4
        I used the F6 BIOS.

        I ran memtest for 3 passes with no errors. Increasing the RAM voltage to 1.55V does not change anything (still crashes in the first 15 mins).

        The thing is @ 667Mhz, the computer passes 12hrs prime, I ran the RAM single stick at a time and it does not crash in the first 30-40 minutes (did not bother to run longer since when using both sticks, it always crashes/freezes in the first 10-15 minutes)

        I wish I have other sticks with similar bandwidth/timing to compare/isolate the issue but I have none, any ideas of what the problem is?

        Thanks

        Comment


        • #5
          Could you try it with the CPU OCed up just a couple of notches to 3.7 or so


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

          Tman

          Comment


          • #6
            I have 12hrs of prime stable on 4.5Ghz @667Mhz/1333MT(9-9-9-24). it crashes when I enable the XMP to run 800Mhz(10-10-10-30) though. the XMP crashes whether the cpu is OCed at 4.5Ghz or at stock (all default setting) @ 3.5Ghz

            Comment


            • #7
              Test one module at a time to see if each can pass.

              Thank you
              GSKILL TECH

              Comment


              • #8
                If you are talking about memtest, then I did test them one stick at a time and each stick have no error after 3-4 pass of memtest. Or did you mean run the Prime with one stick?

                Comment


                • #9
                  Might try raising the IMC voltage just a bit + .03 or so


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

                  Tman

                  Comment


                  • #10
                    As wierd as this sound, increasing the IMC to 0.95V(from default of 0.925) made it the computer reboot within the first 30 seconds of prime

                    Comment


                    • #11
                      What are the advanced timings showing as, especially the tRFC, but the others as well


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

                      Tman

                      Comment


                      • #12
                        I set things to auto after setting the profile through XMP, however the board gives timing beside the option which I assume is the default value loaded thorugh the profile. Those are:

                        CAS 10
                        tRCD 10
                        tRP 10
                        tRAS 30
                        tRC 40
                        tRRD 5
                        tWTR 6
                        tWR 12
                        tWTP 24
                        tWL 8
                        tRFC 208
                        tRTP 6
                        tFAW 24
                        tCMD 2
                        tRW 3
                        tWR 3
                        tREFI 6240
                        tREFIX9 54
                        tRRDR 1
                        tRRDD 3
                        tWWDR 3
                        tWWDD 3
                        tRWDRDD 3
                        tWRDRDD 1
                        tRWSR 3
                        tRRSR 4
                        tWWSR 4

                        Comment


                        • #13
                          By the way, I updated the BIOS to F7, but it has no effect in regards to running the RAM at 1600

                          Comment


                          • #14
                            Might try
                            tCMD 2
                            tRFC 173
                            tWR 16
                            tRRD 7
                            tWTR 8
                            tRTP 8
                            tFAW 26
                            DRAM Voltage 1.55


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

                            Tman

                            Comment


                            • #15
                              Hi, unfortunately, those timings does not improve the stability.

                              I finally got access to another set of RAM of the same model from my friend and tested it, so for its stable (1hr and counting right now). So I think this is a case of bad module (even though somehow memtest did not detect it). I will run a little bit more stability testing and if it is completely stable, I will RMA the module I have.

                              Thanks a lot for your time so far in figuring out this issue. I appreciate it.

                              Comment

                              Working...
                              X