Is it my memory?

DragonofthedarknessDragonofthedarkness
edited January 2004 in Hardware
Ok first let me tell you that my memory is being overclocked. I have PC2100 266Mhz, I believe, ram running at 333MHz because my CPU's FSB is 333MHz. When I built my computer I sort of overlooked that. Anyways my question is, with the memory being overclocked, is it possible that when playing games the computer would restart and pick a slower FSB and then work correctly because that seems to be whats happening. Before it would resart and my Barton 3000+ processor speed would be at 1.08GHz, probably due to my computer overheating , but now that I have it running around 10-15 degrees cooler external CPU temp I believe that the restart has to be because of the memory being overclocked and then the system rebooting at a lower FSB because after the restart the system runs near perfectly for hours but prior to that it only last about 5-10 minutes playing a computer game before a restart.
And no I haven't ever gone into Bios to see if anything changed, I just want to know if my idea is possible, the FSB speed change.

Comments

  • primesuspectprimesuspect Beepin n' Boopin Detroit, MI Icrontian
    edited January 2004
    I would say that the memory could very easily be the culprit, as you are running it quite a bit higher than it was designed to be.

    With the overclock as is, go to www.memtest86.com and download the 3.0 boot disk maker. Make a disk and boot off of that and run it for an hour or so. If you don't get any errors at all, it's your RAM.

    If you DO get errors, then back off your overclock, go to stock speeds, and run memtest again. If you don't get any errors at stock, then your RAM is being "over-overclocked"... :wtf:
  • mmonninmmonnin Centreville, VA
    edited January 2004
    I saw prime post in a memory thread, I come here and what else do I see him posting about? The usual.:rolleyes:

    Yes most likely the RAM may not be able to handle the extra speed.

    If you want to try you can go into the BIOS you can relax the memory timings some. Change them to higher numbers.

    What type of memory and motherboard do you have BTW?
  • qparadoxqparadox Vancouver, BC
    edited January 2004
    I think Prime missed a word:

    If you don't get any errors at all, it's your RAM
    should read:
    If you don't get any errors at all, it's NOT your RAM :D

    But follow his advice, memtest will find 99% of memory problems.
  • primesuspectprimesuspect Beepin n' Boopin Detroit, MI Icrontian
    edited January 2004
    qparadox got me.. if you run it for a while and there are no errors, it is NOT your ram. :D
  • ThraxThrax 🐌 Austin, TX Icrontian
    edited January 2004
    If you run it for a while, it still COULD be your RAM, even if there are no listed errors.

    For some quirky reason, there have been a few scenarios at S-M as of late where memory was error-free in testing, but problems persisted inside of Windows. Swapping the memory for another brand resolved all errors.

    It's still best to try another memory after testing just to be sure.
  • Straight_ManStraight_Man Geeky, in my own way Naples, FL Icrontian
    edited January 2004
    Correct, you want RAM tested with machine hot (at normal temp after 24 hours run time) if possible. Then you will get weak module errors that would not show if box was allowed to cool for an hour before testing. can replicate by testing RAM for 18 hours if you want, though. Weak or bad individual modules will overheat faster than good ones. Reason, small failures in mfring can result in increased resistance, higher amperage needed to overcome increased resistance, more heat in that place in module results, heat increase makes problem worse.

    That kind of thing will result in what you have, BIOS will resync to slowest module adn widnows can spontaneously reboot when BIOS resyncs RAM speed and frequently WILL do this. One reason for extended RAM test is to heat up RAM to temps it is normally running in when machine is under heavy load for along time, which is why OEM mfrs burn boxes in for 24-36 hours when building, to test under full load and find cooling failures and lemon parts.

    If you do not want to run a long memtest, apply 1200 Watt hair dryer to 1 inch from RAM stick, and run for 5 min, then immediately test RAM for 6 hours.

    John.
Sign In or Register to comment.