Stop 0X00000067

RichPuke

unread,

Apr 10, 2003, 5:55:24 AM4/10/03

to

Microsoft say this is a Memory module problem. What is the best way to prove
it?
Any other ideas please ?
Cheers
Rich

tony

unread,

Apr 10, 2003, 8:13:51 AM4/10/03

to

Replace it! Or take out one stick at a time.

"RichPuke" <Rich...@btinternet.com> wrote in message
news:b73f2c$rv4$1...@sparta.btinternet.com...

RichPuke

unread,

Apr 13, 2003, 8:43:18 AM4/13/03

to

Changed memory. No difference. What next?

Cheers
RichPuke

"tony" <to...@burgessfurniture.com> wrote in message
news:b73n5p$2h$1$8300...@news.demon.co.uk...

RichPuke

unread,

Apr 13, 2003, 9:32:02 AM4/13/03

to

Do I need to reinstall win2000 after changing RAM?

"RichPuke" <Rich...@btinternet.com> wrote in message

news:b7bm15$a40$1...@sparta.btinternet.com...

RichPuke

unread,

Apr 13, 2003, 1:31:49 PM4/13/03

to

Reinstalled win2000. All is OK.

"RichPuke" <Rich...@btinternet.com> wrote in message

news:b7bosi$en6$1...@sparta.btinternet.com...

DeMoN_LaG

unread,

Apr 13, 2003, 11:15:52 PM4/13/03

to

"RichPuke" <Rich...@btinternet.com> wrote in news:b7c6u4$id9$1
@titan.btinternet.com:

> Reinstalled win2000. All is OK.
>

If this fixed your problem, then the RAM wasn't bad to begin with and
instead it was a corrupted file or something similar.

RichPuke

unread,

Apr 14, 2003, 2:42:17 PM4/14/03

to

I did change the memory first.

"DeMoN_LaG" <de_on-lag@co_cast.net> wrote in message
news:Xns935CECA...@216.168.3.30...

DeMoN_LaG

unread,

Apr 14, 2003, 8:03:13 PM4/14/03

to

"RichPuke" <Rich...@btinternet.com> wrote in news:b7eve9$93f$1
@titan.btinternet.com:

> I did change the memory first.
>

I'm saying if you changed the memory and still had the problem until you
reinstalled Windows, then the problem wasn't the memory to begin with.

RichPuke

unread,

Apr 15, 2003, 6:39:52 AM4/15/03

to

Why wasn't it. Please explain. It cured a problem no one else could answer.
What is your theory?
Cheers
RichPuke

"DeMoN_LaG" <de_on-lag@co_cast.net> wrote in message

news:Xns935DCC06...@216.168.3.30...

Thor

unread,

Apr 15, 2003, 7:18:12 AM4/15/03

to

The chain of events you listed explains it.

1. You got a stop error.

2. You changed out the RAM, and stated that the same problem still exists
despite having used different RAM. (this should tell you it most likely
wasn't the RAM)

3. Reinstalling windows fixes the trouble (indicating that it was most
likely a software problem to begin with).

"RichPuke" <Rich...@btinternet.com> wrote in message

news:b7gnhn$n4d$1...@titan.btinternet.com...

DeMoN_LaG

unread,

Apr 15, 2003, 10:10:28 AM4/15/03

to

"Thor" <m...@arms.com> wrote in news:3e9be9bc$0$86560$45be...@newscene.com:

> 1. You got a stop error.
>
> 2. You changed out the RAM, and stated that the same problem still exists
> despite having used different RAM. (this should tell you it most likely
> wasn't the RAM)
>
> 3. Reinstalling windows fixes the trouble (indicating that it was most
> likely a software problem to begin with).
>

Exactly. I'd wager a dozen fresh baked donuts that if the original memory
is swapped back in there wouldn't be any problems.87

derek / nul

unread,

Apr 15, 2003, 10:35:22 AM4/15/03

to

and I will make it an extra dozen.

Thor

unread,

Apr 15, 2003, 11:48:15 AM4/15/03

to

"DeMoN_LaG" <de_on-lag@co_cast.net> wrote in message

news:Xns935E6780...@216.168.3.30...

Specify Krispy Kremes. ;-)