Announcement

Collapse
No announcement yet.

RAM degrading? bad batch?

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

  • RAM degrading? bad batch?

    About 3 months ago i picked up a Crucial Ballistix 2x2gb kit, BL2KIT25664AA804. after a while i figured out how to unlock the EPP 4-4-4-12 timings from the 5-5-5-18, and did that in my bios.
    Now all of a sudden i'm getting lots of memory bluescreens with IP_MISALIGNED when attached to windows debugger, various other bluescreens, etc. Ran memtest+ today and got 35 errors after 8 hours, all in the same spot. AFAIK, running at the 5-5-5-18 timings didn't generate errors in memtest, but bluescreen windows still with memory errors (PFN_LIST CORRUPT, etc.)

    This is on an ASUS P5N-D motherboard.
    Did my ram just suddenly degrade on me, or was it a bad batch? over the past 2 weeks or so a bunch of the same comments on that ram popped up on newegg, that it was wroking fine, and all of a sudden stopped working/bluescreened. Checked with an online customer service associate and none of the Crucial chips listed in the qualified vendor list are manufactured anymore.

    <04:11:24> *** You are now talking in channel: "TFP - Task Force Proteus"
    <04:16:25> "|TG-XV| Tralic": this channel is so gay
    DICE needs to make a comical boxing glove attached to a spring punch the player in the face 40% of the time they get into a helicopter or jet.


  • #2
    Re: RAM degrading? bad batch?

    Have you tried other sockets, other ram, removing? Have you tested each stick independently? Are you using the right voltage? Are they in securely? Have you set the entire bios back to default?

    Memtest errors can be cause by PSU, motherboard as well.

    If you are confident it's the ram. Send it back and buy Corsair. If it's too late to send back, Crucial has a lifetime warranty.

    Comment


    • #3
      Re: RAM degrading? bad batch?

      I haven't tried other sockets as other sockets besides the 1st and 3rd would force it into non dual-channel mode as per the motherboard manual (dual channel needs to be A1 and B1, or A1, A2, B1, and B2).

      I have no other ram that will fit in this motherboard, as this was the stuff i bought when building the computer.

      I reset everything in the BIOS to auto again and ran memtest and went for work, churns out errors on tests 6 and 7 every pass. Currently testing sticks individually.

      To enable the EPP mode that's advertised for the ram, i need to set the voltage to 2.2v, CAS 4, trcd 4, trp 4, tras 4, and command rate t2. setting it to default changes them to 1.8v, 5, 5, 5, 18, command rate 1

      <04:11:24> *** You are now talking in channel: "TFP - Task Force Proteus"
      <04:16:25> "|TG-XV| Tralic": this channel is so gay
      DICE needs to make a comical boxing glove attached to a spring punch the player in the face 40% of the time they get into a helicopter or jet.

      Comment


      • #4
        Re: RAM degrading? bad batch?

        Have you tried clearing your CMOS (using the pin-shorting method)? Sometimes that helps when you think your new settings aren't working.

        Can't think of anything else that might help other than a Windows Repair or clean wipe (which I doubt would solve your problems).

        You could always RMA the RAM. Companies usually keep a reserve cache of popular products for replacements and such.
        |TG-18th| Acreo Aeneas
        TG World of Tanks Clan Executive Officer
        Former 9th & 13th

        Pronounciation: Eh-Cree-Oh Ah-Nay-Ess
        Still can't say it? Call me Acorn then. -.-





        SSDs I Own: Kingston HyperX 3K (240 GB), Samsung 840 Pro (256 GB), Samsung 840 EVO (250 GB), Samsung 840 x 2 (120 GB), Plextor M5S (120 GB), OCZ Vertex (30 GB)

        TG Primer and Rules

        Comment


        • #5
          Re: RAM degrading? bad batch?

          Reset the RAM's configuration to its factory settings. If 5-5-5-18 works but 4-4-4-12 doesn't, then the fix is rather easy. :)

          If you're hellbent on sticking to 4-4-4-12, you could always MacGuyver yourself a fan near the RAM just in case the errors are due to overheat.
          GOD IS DEAD. THE N00BS TEAMKILLED HIM.


          Titan specialist!

          Comment


          • #6
            Re: RAM degrading? bad batch?

            Testing individually, one of my sticks got decently hot but none of them developed errors in the short tests (microsoft memory diagnostics, test 6-7 on memtest) and i ran them both in single-channel 4-4-4-12 timing overnight and no errors developed. rather wierd. It doesn't seem to be a failure on the motherboard RE slots, because i tested them individually on the slots too. Maybe a BIOS memory mapping error? I don't know.
            Would there be a much significant performance loss in single-channel rather than dual-channel?

            This is the QVL list for my motherboard as per ASUS, none of the ram listed by Crucial is being made anymore, and the only Corsair ram is rather old. To the point, both memory manufacturers say that thier other memory is compatible with the motherboard, but the motherboard manufacturer says not? Rather odd imo that a performance motherboard manufactured within the last 3 months wouldn't have support for 2048 MB DDR2-800 DIMMs, only DDR2-667.

            <04:11:24> *** You are now talking in channel: "TFP - Task Force Proteus"
            <04:16:25> "|TG-XV| Tralic": this channel is so gay
            DICE needs to make a comical boxing glove attached to a spring punch the player in the face 40% of the time they get into a helicopter or jet.

            Comment


            • #7
              Re: RAM degrading? bad batch?

              My Corsair 1066 ram had the same thing happen. Worked for a few weeks, then bluescreens started. Same time a lot of commentes started showing up in the reviews on Newegg, and while looking through posts in tech forums, saw other people had the problem too. And with the same revision #. So I RMAed back to Corsair, and it took about a month because they were on back order due to all the other people having problems.
              New sticks were a completly new revision, and have been problem free since.
              I think, even if you kind of get them working again, you might want to RMA anyway, since other people are having the same issue. Just to be on the safe side. Also go to the manufactures web forum and read the posts there. Chances are you will find other people with the same problem, and will make it easier to RMA.
              You could even go a pick up a cheap set of RAM from like bestbuy and return it after you get your sticks back, just so you still have a running computer. Just make sure you are very gentle opening the BestBuy package.

              LINKS

              * *


              Stoop and you'll be stepped on; stand tall and you'll be shot at.

              -Carlos A. Urbizo-

              Comment


              • #8
                Re: RAM degrading? bad batch?

                Well, seeing as it's past the 30 day return period, i'd only be offered a warranty repair, and something would have to be wrong for that.

                <04:11:24> *** You are now talking in channel: "TFP - Task Force Proteus"
                <04:16:25> "|TG-XV| Tralic": this channel is so gay
                DICE needs to make a comical boxing glove attached to a spring punch the player in the face 40% of the time they get into a helicopter or jet.

                Comment


                • #9
                  Re: RAM degrading? bad batch?

                  There is obviously something wrong if you are still getting blue screens at stock settings.
                  Check the companie's forums.

                  LINKS

                  * *


                  Stoop and you'll be stepped on; stand tall and you'll be shot at.

                  -Carlos A. Urbizo-

                  Comment


                  • #10
                    Re: RAM degrading? bad batch?

                    PUT the RAM Back!

                    i dont know if anyone mentioned this as its tricky but ive had this work on some older machines it might work on yours .. ish

                    before attempting read your motherboard documents to see if this will cuase any conflict or damage as i said before ive had this work on older machines.

                    go into CMOS and write down ALL settings then unplug your machine and remove the CMOS battery (coin battery normally a CR2032)

                    leave the battery out and the machine unplugged for about 5 mins then Bam put the battery in and restart go to cmos make sure everything is at defualt and then run your checks.
                    I will not place claymores in my front yard.
                    I will not place claymores in my front yard.

                    Comment


                    • #11
                      Re: RAM degrading? bad batch?

                      Haha, Capt. Obvious stays true to his name. :D

                      That is what Acreo Aeneas asked if he had tried above. And new machines usually require you to change a little jumper around on some pins on the motherboard. Pretty easy to do once you look up the instructions.

                      LINKS

                      * *


                      Stoop and you'll be stepped on; stand tall and you'll be shot at.

                      -Carlos A. Urbizo-

                      Comment


                      • #12
                        Re: RAM degrading? bad batch?

                        Originally posted by Bamboo View Post
                        Haha, Capt. Obvious stays true to his name. :D

                        That is what Acreo Aeneas asked if he had tried above. And new machines usually require you to change a little jumper around on some pins on the motherboard. Pretty easy to do once you look up the instructions.
                        Check your motherboard manual on how to clear CMOS. If it allows you to clear the CMOS by shorting pins 2, 3 (or 1, 2), then do so. It beats having to remove parts from your motherboard in trying to remove the darn battery.

                        If you can't find any spare jumpers, remove the one from your CD/DVD master drive (or slave drive). Just make sure you put it back or else you'll get a duplicate master/slave drive error. ;)
                        |TG-18th| Acreo Aeneas
                        TG World of Tanks Clan Executive Officer
                        Former 9th & 13th

                        Pronounciation: Eh-Cree-Oh Ah-Nay-Ess
                        Still can't say it? Call me Acorn then. -.-





                        SSDs I Own: Kingston HyperX 3K (240 GB), Samsung 840 Pro (256 GB), Samsung 840 EVO (250 GB), Samsung 840 x 2 (120 GB), Plextor M5S (120 GB), OCZ Vertex (30 GB)

                        TG Primer and Rules

                        Comment


                        • #13
                          Re: RAM degrading? bad batch?

                          Heres an example from one of my minidumps.


                          Loading Dump File [C:\WINDOWS\Minidump\Mini062208-01.dmp]
                          Mini Kernel Dump File: Only registers and stack trace are available

                          Symbol search path is: C:\WINDOWS\Symbols
                          Executable search path is:
                          Unable to load image ntoskrnl.exe, Win32 error 0n2
                          *** WARNING: Unable to verify timestamp for ntoskrnl.exe
                          Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
                          Product: WinNt, suite: TerminalServer SingleUserTS
                          Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
                          Debug session time: Sun Jun 22 19:23:57.921 2008 (GMT-4)
                          System Uptime: 0 days 0:05:46.697
                          Unable to load image ntoskrnl.exe, Win32 error 0n2
                          *** WARNING: Unable to verify timestamp for ntoskrnl.exe
                          Loading Kernel Symbols
                          .................................................. .................................................. .................................
                          Loading User Symbols
                          Loading unloaded module list
                          .........
                          ************************************************** *****************************
                          * *
                          * Bugcheck Analysis *
                          * *
                          ************************************************** *****************************

                          Use !analyze -v to get detailed debugging information.

                          BugCheck 4E, {99, ab094, 0, 0}

                          Probably caused by : hardware ( nt!KeForceResumeThread+1 )

                          Followup: MachineOwner
                          ---------

                          0: kd> !analyze -v
                          ************************************************** *****************************
                          * *
                          * Bugcheck Analysis *
                          * *
                          ************************************************** *****************************

                          PFN_LIST_CORRUPT (4e)
                          Typically caused by drivers passing bad memory descriptor lists (ie: calling
                          MmUnlockPages twice with the same list, etc). If a kernel debugger is
                          available get the stack trace.
                          Arguments:
                          Arg1: 00000099, A PTE or PFN is corrupt
                          Arg2: 000ab094, page frame number
                          Arg3: 00000000, current page state
                          Arg4: 00000000, 0

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


                          BUGCHECK_STR: 0x4E_99

                          CUSTOMER_CRASH_COUNT: 1

                          DEFAULT_BUCKET_ID: DRIVER_FAULT

                          PROCESS_NAME: TurbineLauncher

                          MISALIGNED_IP:
                          nt!KeForceResumeThread+1
                          804f9deb 5d pop ebp

                          LAST_CONTROL_TRANSFER: from 805220a8 to 804f9deb

                          STACK_TEXT:
                          b802f688 805220a8 0000004e 00000099 000ab094 nt!KeForceResumeThread+0x1
                          b802f6b8 80522e47 08876000 c0600220 c00443b0 nt!MiResolveMappedFileFault+0x1f
                          b802f6e8 80523283 c00443b0 08876000 00000000 nt!MiAddViewsForSection+0x24b
                          b802f7b0 80519954 00000130 089d5fff 00000000 nt!MiPfPutPagesInTransition+0x715
                          b802f7cc 805b1e24 08850000 089d5fff b802f884 nt!CcPinFileData+0x42c
                          b802f86c 8054086c ffffffff 0012e818 0012e81c nt!NtQueryInformationJobObject+0x5ff
                          b802f884 7c90eb94 badb0d00 0012e7f4 07750000 nt!RtlIpv4StringToAddressExA+0x149
                          WARNING: Frame IP not in any known module. Following frames may be wrong.
                          b802f898 b802f8b4 00000001 805353cd 00001fa0 0x7c90eb94
                          b802f89c 00000000 805353cd 00001fa0 7ffde6cc 0xb802f8b4


                          STACK_COMMAND: kb

                          FOLLOWUP_IP:
                          nt!KeForceResumeThread+1
                          804f9deb 5d pop ebp

                          SYMBOL_STACK_INDEX: 0

                          SYMBOL_NAME: nt!KeForceResumeThread+1

                          FOLLOWUP_NAME: MachineOwner

                          IMAGE_NAME: hardware

                          DEBUG_FLR_IMAGE_TIMESTAMP: 0

                          MODULE_NAME: hardware

                          FAILURE_BUCKET_ID: IP_MISALIGNED

                          BUCKET_ID: IP_MISALIGNED

                          Followup: MachineOwner
                          ---------

                          <04:11:24> *** You are now talking in channel: "TFP - Task Force Proteus"
                          <04:16:25> "|TG-XV| Tralic": this channel is so gay
                          DICE needs to make a comical boxing glove attached to a spring punch the player in the face 40% of the time they get into a helicopter or jet.

                          Comment


                          • #14
                            Re: RAM degrading? bad batch?

                            On a whim, i ran Prime95 torture test. it didn't even get into a full minute before
                            FATAL ERROR: Rounding was 0.5, expected less than 0.4
                            Hardware failure detected, consult stress.txt file.
                            posted.

                            <04:11:24> *** You are now talking in channel: "TFP - Task Force Proteus"
                            <04:16:25> "|TG-XV| Tralic": this channel is so gay
                            DICE needs to make a comical boxing glove attached to a spring punch the player in the face 40% of the time they get into a helicopter or jet.

                            Comment


                            • #15
                              Re: RAM degrading? bad batch?

                              Originally posted by Bisclaveret View Post
                              On a whim, i ran Prime95 torture test. it didn't even get into a full minute before
                              FATAL ERROR: Rounding was 0.5, expected less than 0.4
                              Hardware failure detected, consult stress.txt file.
                              posted.
                              At this point it doesn't sound like it's the RAM. To be sure go to Best Buy like Bamboo said and put in another set of RAM from another manufacturer. Then run the torture test.

                              Comment

                              Connect

                              Collapse

                              TeamSpeak 3 Server

                              Collapse

                              Advertisement

                              Collapse

                              Twitter Feed

                              Collapse

                              Working...
                              X