docmem problem?

profdlpprofdlp The Holy City Of Westlake, Ohio
edited July 2003 in Hardware
As some of you may remember, I recently had a memory problem with a new motherboard. You can read about it here.

Since my daughter took her computer back home with her a week ago, I had to check the memory in another computer. I stuck it in my girlfriend's Asus A7A266. Just a few seconds into the test, the computer rebooted. Tried docmem a second time, with the same result. (This was the Burn-In test both times). Since I was working on her computer anyway, I removed the suspect ram and re-ran the test. The same thing happened with her original ram. I made a new docmem boot disc, and darned if it didn't happen again. I then removed her original ram and tried the test a fourth time with just the iffy memory installed. You guessed it.
:scratch:

My girlfriend's computer has been running for a year-and-a-half with no problems. She has gobs of stuff loading on startup; so much crap that I believe that if her original memory was bad she would have had trouble long ago. She has been on temporary duty at a Veteran's hospital, so she hasn't been home for several weeks. During that time her computer has run constantly without a reboot - Folding like a big dog the whole while. Both memory sticks are PC2700, same specs.

Anyone else ever have this happen?


Prof
(Confused, as usual...:rolleyes: )

Comments

  • SpinnerSpinner Birmingham, UK
    edited July 2003
    Usually when docmemory finds errors with a memory module it just hangs, it, at least for me, shouldn't force a reboot. Firstly, you should always test the modules individually, with only one in the system at a time, especially if they are different modules (it doesn't really matter if they are the same spec). I suspect that the problem might be with the config of the memory module/s in the BIOS. I suggest you try and make sure they are set up correctly, i.e they are assigned the correct CAS rating, and all their timings are at default level. Also, check to make sure none of the other motherboard timings are running too high. I don't think this is an indication that your either module is bad, I think its just a problem with docmemory having trouble testing the memory properly. Have another fiddle then get back to us, and I'll try and have another think if the problem remains.

    The obvious most likely quick fix though, would be to shove the memory modules in yet another machine.
  • WuGgaRoOWuGgaRoO Not in the shower Icrontian
    edited July 2003
    i concur with dr. spinner
  • profdlpprofdlp The Holy City Of Westlake, Ohio
    edited July 2003
    I'll give that a try.

    Thanks for the advice,

    Prof
  • jj Sterling Heights, MI Icrontian
    edited July 2003
    profdlp said

    I stuck it in my girlfriend's Asus (Confused, as usual...:rolleyes: )


    These words prob. should not go together
  • profdlpprofdlp The Holy City Of Westlake, Ohio
    edited July 2003
    MicroMan said
    profdlp said

    I stuck it in my girlfriend's Asus (Confused, as usual...:rolleyes: )


    These words prob. should not go together

    Oh, my!!! What have I done?:banghead: :banghead:

    She seemed pretty happy about it, though...


    Prof
    (Banned any moment now...:rolleyes2 )
  • dodododo Landisville, PA
    edited July 2003
    Try MemTest86 as a memory test alternative.

    ~dodo
  • SpinnerSpinner Birmingham, UK
    edited July 2003
    MicroMan said
    profdlp said

    I stuck it in my girlfriend's Asus (Confused, as usual...:rolleyes: )


    These words prob. should not go together

    There's always one. Tsk!:rolleyes2 ;)
Sign In or Register to comment.