Announcement

Collapse
No announcement yet.

F2-8500CL6D-4GBNQ - Not functioning properly in Dual-Channel?

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

  • F2-8500CL6D-4GBNQ - Not functioning properly in Dual-Channel?

    model of the motherboard: DFI LP DK X48-T2RSB PLUS LGA 775 Intel X48 ATX Intel

    model of the memory: F2-8500CL6D-4GBNQ DDR2-1066 PC2-8500 CL 6-6-6-18 2.0~2.1v

    model of the CPU: Intel Core 2 Duo E8400 3.0 Ghz @ 3.0 Ghz

    what is the problem:

    Bought this RAM about a month an a half ago from Newegg and initially it seemed to be working properly. I believe I even tested it with Memtest86+ to make sure. However, this could have been when it was defaulted to an underclocked setting by the bios.

    Once I figured out that my ram wasn't running at the correct speed, I went into bios and got it to the 6-6-6-18 settings with voltage ~2.05. After that, I went back and checked with memtest86+ and it seemed to give me errors, only on Test #5.

    In case I had to send the ram in, I decided to test each stick individually (and in different slots of the motherboard just for good measure). When I did this, neither stick had a problem running individually. So it seems it's only when they're being used together (hence, not working in Dual channel?)

    Also to verify this problem, I used Orthos Stress-testing program and again, the same ordeal. I never got a halting error on Orthos when testing the sticks individually, but only when I used them together.

    Basically, I'm getting weird errors in 3D games (Counter-Strike: Source, Farcry 2, Left 4 Dead). After playing a certain amount (probably 30 to 45 minutes) my videocard would artifact. Showing distorted colors / missing textures / blown-up textures / weird renders of models.

    Again, I supplied the same testing method and did not appear to have random crashes / artifacting in 3D games when using only one stick of ram.

    Sorry for the length, but I wanted to be informative as possible.

    Also, I THINK (not sure) I tried testing the ram at a lower clock rate.... the 5-5-5-15 and if I recall correctly, it did not give me ram errors on test #5 in memtest86+

    So what's the verdict? Bad faulty ram? Incompatibility? Solutions?

    (Also, I just placed both ram sticks back in, so I'm going to play these games over to verify that I'm getting errors.)

    Thanks,

    -Michael

    EDIT:

    Just after posting this. I went into Far Cry 2, played maybe not even 20 minutes and I received a BSOD.

    DRIVER_IRQL_NOT_LESS_OR_EQUAL

    IMAGE_NAME: kmixer.sys

    (if you would like the debugging log, I have it available, let me know.) Guess I'll test some more and see what else happens.

    EDIT:

    Did some more testing. Decided to have Far Cry 2 running with both RAM sticks in to see if it would artifact or blue screen while I was in shower. Turns out it did.

    Decided to test ram separately and did not receive a blue screen. I then placed both ram sticks back in and appear to not be getting a blue screen yet (35 minutes into the game). I'm not sure what to make of it.

    EDIT:

    Now I'm completely baffled. After running Far Cry 2 last night with both sticks and not receiving anything bad. I decided I'd leave on Orthos for stress testing overnight. I would expect to receive error well within 20 minutes of testing. Turns out...it's been running for 6 hours and not any kind of error. Since only 3.25 of the ram is used (32-bit system) Could that just mean the bad ram just hasn't been accessed? Or...what?
    Last edited by kidintheshadows; 02-28-2009, 09:34 AM. Reason: NO BSOD

  • #2
    we checked the error code and found it could be caused by video or audio driver
    so, would you like to reinstall different version of driver and try again
    thanks


    G.S

    Comment


    • #3
      When you refer to error code, I assume you mean the "DRIVER_IRQL_NOT_LESS_OR_EQUAL"

      On the second blue screen I received a different error...
      +++++++++++++++++++++++++++++++++++++++++
      PAGE_FAULT_IN_NONPAGED_AREA (50)
      Invalid system memory was referenced. This cannot be protected by try-except,
      it must be protected by a Probe. Typically the address is just plain bad or it
      is pointing at freed memory.
      Arguments:
      Arg1: eca095b8, memory referenced.
      Arg2: 00000001, value 0 = read operation, 1 = write operation.
      Arg3: bf0eafc0, If non-zero, the instruction address which referenced the bad memory
      address.
      Arg4: 00000002, (reserved)

      Debugging Details:
      ------------------


      Could not read faulting driver name

      WRITE_ADDRESS: eca095b8

      FAULTING_IP:
      nv4_disp+d8fc0
      bf0eafc0 897d08 mov dword ptr [ebp+8],edi

      MM_INTERNAL_CODE: 2

      CUSTOMER_CRASH_COUNT: 2

      DEFAULT_BUCKET_ID: DRIVER_FAULT

      BUGCHECK_STR: 0x50

      PROCESS_NAME: farcry2.exe

      LAST_CONTROL_TRANSFER: from bf0ead20 to bf0eafc0

      STACK_TEXT:
      WARNING: Stack unwind information not available. Following frames may be wrong.
      b089dba0 bf0ead20 eca095b0 b089dc7c 00000000 nv4_disp+0xd8fc0
      b089dc1c bf84c4ea bf18bba7 00000000 b089dc7c nv4_disp+0xd8d20
      b089dc2c bf961a2e b089dc7c e1cb19e4 bf9619f3 win32k!dhpdevRetrieveNode+0x32
      b089dc7c e8a09558 00000000 00000000 00000000 win32k!WatchdogDdLockD3DBuffer+0x3b
      b089dcb0 bf80197c bf80635b 00000000 bf002cad 0xe8a09558
      b089dcb4 bf80635b 00000000 bf002cad 8a3248b0 win32k!GreReleaseSemaphore+0xa
      b089dcbc bf002cad 8a3248b0 bf002ffc e1cb12d8 win32k!EngReleaseSemaphore+0x21
      b089dcc4 bf002ffc e1cb12d8 00000000 e1670528 dxg!DdHmgReleaseHmgrSemaphore+0xb
      b089dd54 8054162c 0e40198c 044aed60 044aed94 dxg!DdHmgLock+0x82
      b089dd54 7c90e4f4 0e40198c 044aed60 044aed94 nt!KiFastCallEntry+0xfc
      044aed94 00000000 00000000 00000000 00000000 0x7c90e4f4


      STACK_COMMAND: kb

      FOLLOWUP_IP:
      nv4_disp+d8fc0
      bf0eafc0 897d08 mov dword ptr [ebp+8],edi

      SYMBOL_STACK_INDEX: 0

      SYMBOL_NAME: nv4_disp+d8fc0

      FOLLOWUP_NAME: MachineOwner

      MODULE_NAME: nv4_disp

      IMAGE_NAME: nv4_disp.dll

      DEBUG_FLR_IMAGE_TIMESTAMP: 4990a78c

      FAILURE_BUCKET_ID: 0x50_nv4_disp+d8fc0

      BUCKET_ID: 0x50_nv4_disp+d8fc0

      Followup: MachineOwner

      Also, even before requesting help from you all, I had tried updating Audio and Video drivers, but still got the blue screens.

      But as it stands now, I'm not receiving any errors in games. So I'm hoping everything is working correctly.

      Comment


      • #4
        no...what we checked is "IMAGE_NAME: kmixer.sys"

        it's not the latest driver the best
        and sometimes 64bit driver is not as mature as 32bit one
        thanks


        G.S

        Comment


        • #5
          Well, I updated both the audio driver and video driver to latest versions. Like I said, it seemed to be going fine even before that incident. However, just a few mornings ago, my computer randomly restarted on it's own. It did not have a blue screen message, nor did it create a minidump file. I even checked the event viewer to see if there was some kind of windows error. Nothing odd showed up. Also, I decided to retest the ram with Memtest86+ overnight and it again seems to still fail Test #5. Here are the screenshot:

          http://img83.imageshack.us/img83/7307/error.jpg

          So is this bad ram?

          Comment


          • #6
            try to set tRFC to 60 or larger to see if it could be fixed
            if there is still error, please RMa with us
            thanks


            G.S

            Comment


            • #7
              I RMA'd the ram with you all and got the new one back. Now it seems there are even more errors than there were before. I'd be able to boot into windows, but it would frequently freeze within the first few minutes of use. I also got a blue screen: DRIVER_FAULT mentioning csrss.exe (or something). Sometimes I couldn't even post, and would receive DISK BOOT ERROR or something. However, I performed a Reformat of Windows XP SP3, and still got issues. It was only until I under clocked the RAM to 5-5-5-16 v2.0 that I could use Windows successfully and play games with no error.

              Are there certain settings I should be using in bios? Because 6-6-6-18 doesn't seem to work, even on an intel chipset and processor computer.

              I guess I'm just stuck with 800 MHZ speed. :\

              Comment


              • #8
                Is the 5-5-5-16 settings with the speed at 1066 or 800? If that's @ 800, I would try 6-6-6-18-2T @ 2.0 v
                (make sure it's at 2T, not 1T. if that doesn't go try 6-7-7-18 2T @ 2.0V


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

                Tman

                Comment


                • #9
                  That's the thing. I was trying to run @ default: 6-6-6-18 2T @2.0 1066 (533 ea.). But it seems that's when I'd get errors. I will attempt your suggestion of 6-7-7-18 2T 2.0v and see what happens.

                  And yes, with the 5-5-5-16 (I know it should be 5-5-5-15) I was running at 800 (400 ea.)

                  But will try this. Thanks.

                  Comment


                  • #10
                    Alright. I tried your suggestion. I couldn't even post, couldn't even load BIOS screen with 6-7-7-18 on 1066 MHZ. Currently I'm on 6-6-6-18 2T @ v2.0 but only @ 800 Mhz. So I guess 1066 just won't work for me. :\

                    EDIT:

                    I've decided to add screen shots. Here are the first four.
                    Last edited by kidintheshadows; 03-23-2009, 12:54 PM.

                    Comment


                    • #11
                      Could try @ 2.1, should be within tolerance - is the NB and VTT voltage at stock? sometimes just a little extra juice there will help stabilize the RAM


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

                      Tman

                      Comment


                      • #12
                        VTT currently is at 1.09 and North Bridge is at 1.25..... I'm not sure if that's stock or not? I've never really messed with overclocking, just default settings. :]

                        Comment


                        • #13
                          try to add vtt voltage to 1.4v and memory voltage to 2.1v
                          and did you increase tRFC to more than 60 yet?


                          G.S

                          Comment


                          • #14
                            I set the vtt voltage to 1.4v and the memory voltage to 2.1v and put the ram timings at 6-6-6-18 2T @ 1066. I used both a tRFC of 62 and 68. I was able to boot into windows, but only within a matter of minutes, the system froze, and I was forced to restart.

                            On 62 tFRC it frozen during an application. On 68 it froze playing a 3D computer game.

                            I am currently back on 5-5-5-15 2T @ 800 mhz. I reset my vtt voltage and kept my ram voltage @ 2.1v

                            Any other ideas? Would screen shots of my bios help you see what other options I might need to adjust?

                            Comment


                            • #15


                              And this: http://s122.photobucket.com/albums/o...=DramSpeed.jpg

                              PLEASE NOTE: The numbers listed on the screen shots may not be the current values on my system. These screen shots are about a month old.
                              Last edited by kidintheshadows; 03-23-2009, 12:59 PM.

                              Comment

                              Working...
                              X