Memtest's hidden power?

[foxy]

Back in March, I started this thread about my puter's slowing down with certain functions. You don't have to read the whole thing, just the first post.
http://discussions.virtualdr.com/sho...-memory-defect

I really hate doing troubleshooting, and I just got around to running Memtest86+ yesterday. I ran the program through 16 cycles, and it found nothing in the memory.

Feeling frustrated, because the memory would have been the cheapest fix, I rebooted. This is weird and inexplicable: All the hesitating and freezing had stopped. Is there a hidden function in Memtest?

[Train]

I have found rebooting fixes a lot of problems, but then once in a while I had to just shutdown, wait a minute, then boot back up.

That cures/removes the flipped/corrupt stuff in the ram when the electricity disappears.

[foxy]

But between February and July I had already shut down and restarted over 150 times.

[Train]

Daily shutdown sounds about right, But XP , yes I had to shut it down more than a few times over the years. Fact is, I gave up and did clean install every 2 years.

[foxy]

I meant the problem's solution had no connection to shutdowns because I shut down every night.

Just for fun, I posted this on another forum, and they were mystified too.

Only slightly related to that--It's the most trouble-free puter I've ever had, and it was a refurb. Scratch on the case. I just put more memory into this workhorse, so I'll be re-using it for Win 7.

[Midknyte]

Did you reseat the RAM? It's possible that the long diags caused thermal expansion, thus providing better contact. Usually, you'd get the opposite result. It's AKA "chip creep".

[foxy]

I did nothing but let the program run. I'm slow; I haven't opened the case, the additional RAM sticks are still sitting on my desk.

"Chip creep" sounds spooky, like something from a monster movie.