Re: Memtest 86+ Died...Now What?

upgrade to Acrobat Reader 7.0.8 and see.

note that it is entirely possible that you've been running for four years
w/ "bad" ram and just didn't know it. I see it all the time, people have
random problems and running memtest reveals mem errors. [next most
frequent culprit: power supply]. Yes, ram can go bad, but most of the
time it was bad and is just now being diagnosed.

I never install an OS to a system w/o first doing a memtest to validate
the ram. 1 in 10 new builds will fail, yet moving the "bad" ram to a
different system works just fine. You have to get the MB and RAM to work
together before proceeding...

.

Relevant Pages

  • Re: Memtest 86+ Died...Now What?
    ... w/ "bad" ram and just didn't know it. ... random problems and running memtest reveals mem errors. ... I never install an OS to a system w/o first doing a memtest to validate ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: strange performance issues
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... on it - MS office, acrobat reader, etc. it is a dual cpu xeon ... that the cpu and ram were being reported as hardly used (10-30% ...
    (microsoft.public.windows.terminal_services)
  • Re: strange performance issues
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... on it - MS office, acrobat reader, etc. it is a dual cpu xeon ... that the cpu and ram were being reported as hardly used (10-30% ...
    (microsoft.public.windows.terminal_services)
  • Performance Acrobat Reader 6, 7
    ... Win2k Terminal Server, 2x2,8 GHz Prozessor, 3GB RAM ... Welche Version von Acrobat Reader verwendet ihr am TS? ... Prev by Date: ... Next by Date: ...
    (microsoft.public.de.german.win2000.termserv.apps)
  • Re: Memtest 86+ Died...Now What?
    ... I'll think I'll try a clean install of Acrobat Reader first, to see if that doesn't solve the problem. ... As for Memtest86+...yes, a problem with Acrobat Reader wouldn't cause Memtest to fail. ... I remember seeing that title on the window when this happened in the ... Windows was not running when you were testing the RAM. ...
    (microsoft.public.windowsxp.perform_maintain)