TechSpot

Mysterious reboot

By esbo
Jul 13, 2010
Topic Status:
Not open for further replies.
  1. esbo

    esbo TS Rookie Topic Starter Posts: 161

    Well 4 hours on this stick, should be a boot soon if it is the same problem.
  2. esbo

    esbo TS Rookie Topic Starter Posts: 161

    Right so I am over 5 hours on this stick in slot 2 without a reboot, that is a long time.


    Not sure what to do if this stays stable , I could try the other stick in the same slot which is a good test.


    Also I could try this stick in slot one and try and get it to boot, hard to see why it won't boot in slot 1.
  3. esbo

    esbo TS Rookie Topic Starter Posts: 161

    Well thats 6 hours.
    Smooth running.
    I guess if i whack the other stick in this slot and it starts rebooting again that does point to the new memory being bad.

    However this stick beeped in the first slot!! That clouds things!!
  4. Route44

    Route44 TechSpot Ambassador Posts: 12,140   +29

    Check your motherboard manual for the correct memory configuration.
  5. esbo

    esbo TS Rookie Topic Starter Posts: 161

    I had actually been running fine with an unspecified configutation is a module in dimm 2 only.


    However apparently it aill take high and low density channel as long as they are not mixed on a channel.


    Furtthermore it seems none of my memory modules are high density despite what I though earlier.

    There is only one suspect module and the new one, the old one ran fine by itself for
    10 hours.

    So I am now try the new one in the same slot for 10 hours or more and see what happens.
  6. esbo

    esbo TS Rookie Topic Starter Posts: 161

    Well I have been going for four hours on this module now, this is the time period which is due a crash.
    I am hoping cleaning the slot by repeated re-insertions of the module has cleaned the contacts up an cured the problem, but it's a little to early to say.

    I suppose that a slot which has had the same module in for year and years is likely to get rather corroded and tarnished and when yuo put in another module it may be resting on some of the corrosion causing a poor contact, which could explain my problems.

    It crashed at about 5 or 7 hours after boot up.
    not too sure as I was using the post time to timestamp posts but the mods do not like me
    replying to my self so I was discourages from posting and providing useful information here.

    I also seemd to get a crash burning memtest, (unless it is supposed to reboot after burn which seems
    unlikely) it was burning an ISO so it does not know what it was burning.

    Memtest showed errors, but because I was unfamiliar with memtest I did not notice for a while
    it seemed to report them straight away.
    I ran it again and it found no errors.
    Will try another burn.
  7. esbo

    esbo TS Rookie Topic Starter Posts: 161

    Final post on this, the memory has failed sevreral times on memtest so I am sending it back.
    My old memory was fine.
  8. Route44

    Route44 TechSpot Ambassador Posts: 12,140   +29

    Corrupted memory will cause all kinds of issues. Hope it works out for you in the future and thanks for keeping us updated.
  9. esbo

    esbo TS Rookie Topic Starter Posts: 161


    Yes I am just hopinpg there are no problems getting a refund.
    I would have saved a lot of time if I had got memtest earlier, but you can't use your PC when running it.
    Windows should have something to test memory.
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.