Every program I open an error window pops up with that
program's name - Application Error stating:
********
The instruction at "0x7c883f9c" referenced memory at "0x7c883f9c". The
memory could not be "written".
Click on OK to terminate the program
Click on CANCEL to debug the program
********
I am able to run the program that I start, however as soon as I click on the
OK button to close the error box, the program closes also.

What is going on with my pc?
Please help out.
Thanks. Greatly appreciate your help

" Gino" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Every program I open an error window pops up with that
> program's name - Application Error stating:
> ********
> The instruction at "0x7c883f9c" referenced memory at "0x7c883f9c". The
> memory could not be "written".
> Click on OK to terminate the program
> Click on CANCEL to debug the program
> ********
> I am able to run the program that I start, however as soon as I click on
> the OK button to close the error box, the program closes also.
>
> What is going on with my pc?
> Please help out.
> Thanks. Greatly appreciate your help
>

How old is the computer? You may have a memory module that is bad or has
corrosion on the tiny contacts.

If you have more than one module. Remove one and restart. If the problem
persists, swap the modules and restart again. If the problem disappears you
found the bad module. Sometimes simply removing memory module(s) and
re-seating module(s) in the mainboard will fix this problem. If you are not
an expert then take it to someone who is!

Mark

The error messages do not come up every day. Is there a software that can
check which memory chip is bad? I have take one of them off, so far it's
good, however I cannot be sure since the error may come up later on.
Gino


"Mark F." <(E-Mail Removed)> wrote in message
news:468143dc$0$20589$(E-Mail Removed)...
>
> " Gino" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> Every program I open an error window pops up with that
>> program's name - Application Error stating:
>> ********
>> The instruction at "0x7c883f9c" referenced memory at "0x7c883f9c". The
>> memory could not be "written".
>> Click on OK to terminate the program
>> Click on CANCEL to debug the program
>> ********
>> I am able to run the program that I start, however as soon as I click on
>> the OK button to close the error box, the program closes also.
>>
>> What is going on with my pc?
>> Please help out.
>> Thanks. Greatly appreciate your help
>>
>
> How old is the computer? You may have a memory module that is bad or has
> corrosion on the tiny contacts.
>
> If you have more than one module. Remove one and restart. If the problem
> persists, swap the modules and restart again. If the problem disappears
> you found the bad module. Sometimes simply removing memory module(s) and
> re-seating module(s) in the mainboard will fix this problem. If you are
> not an expert then take it to someone who is!
>
> Mark
>
>

Try Memtest86+
Google for it.

"Gino" wrote:

> The error messages do not come up every day. Is there a software that can
> check which memory chip is bad? I have take one of them off, so far it's
> good, however I cannot be sure since the error may come up later on.
> Gino
>
>
> "Mark F." <(E-Mail Removed)> wrote in message
> news:468143dc$0$20589$(E-Mail Removed)...
> >
> > " Gino" <(E-Mail Removed)> wrote in message
> > news:%(E-Mail Removed)...
> >> Every program I open an error window pops up with that
> >> program's name - Application Error stating:
> >> ********
> >> The instruction at "0x7c883f9c" referenced memory at "0x7c883f9c". The
> >> memory could not be "written".
> >> Click on OK to terminate the program
> >> Click on CANCEL to debug the program
> >> ********
> >> I am able to run the program that I start, however as soon as I click on
> >> the OK button to close the error box, the program closes also.
> >>
> >> What is going on with my pc?
> >> Please help out.
> >> Thanks. Greatly appreciate your help
> >>
> >
> > How old is the computer? You may have a memory module that is bad or has
> > corrosion on the tiny contacts.
> >
> > If you have more than one module. Remove one and restart. If the problem
> > persists, swap the modules and restart again. If the problem disappears
> > you found the bad module. Sometimes simply removing memory module(s) and
> > re-seating module(s) in the mainboard will fix this problem. If you are
> > not an expert then take it to someone who is!
> >
> > Mark
> >
> >
>
>
>

" Gino" <(E-Mail Removed)> wrote
> The error messages do not come up every day. Is there a software that can
> check which memory chip is bad? I have take one of them off, so far it's
> good, however I cannot be sure since the error may come up later on.

<snip>

Run at least two of these. Let each one run for 24 hours or so, not just a
single pass. Test with individual sticks and with all together.

Memtest86+
http://www.memtest.org/

Windows Memory Diagnostic
http://oca.microsoft.com/en/windiag.asp

DocMemory Memory Diagnostic
http://www.simmtester.com/page/produ...c/download.asp

--
Rock [MS-MVP User/Shell]

I have removed 1 of 3 512mb DDR PC 2100 memory modules to isolate which one
is defective. I have gotten the same error.
I removed 2nd module and inserted the first one I have removed. I received
the same memory error.
I now have the 3rd one removed and re-inserted the prior 2 modules that were
good. Hopefully the error msg will not show up again and I will know that
it's this last module that is defective.
Before I had taken out the 3rd memory module, I had run windows memory
diagnostic from MS, and it didn't find any errors. I let it run from 10pm to
1pm the next day. I have stopped the process since and I am now logged on to
Windows XP, with the 3rd memory module out, and I'm waiting to see whether
the error msg comes up again.

I will post the update.
Thank you for your advices.
G

"Rock" <(E-Mail Removed)> wrote in message
news:urj%(E-Mail Removed)...
>" Gino" <(E-Mail Removed)> wrote
>> The error messages do not come up every day. Is there a software that can
>> check which memory chip is bad? I have take one of them off, so far it's
>> good, however I cannot be sure since the error may come up later on.
>
> <snip>
>
> Run at least two of these. Let each one run for 24 hours or so, not just
> a single pass. Test with individual sticks and with all together.
>
> Memtest86+
> http://www.memtest.org/
>
> Windows Memory Diagnostic
> http://oca.microsoft.com/en/windiag.asp
>
> DocMemory Memory Diagnostic
> http://www.simmtester.com/page/produ...c/download.asp
>
> --
> Rock [MS-MVP User/Shell]
>

2 more questions.
1. Since it gives an address of memory that cannot be read, is there
software that would point out which memory module that address refers to?
2. Should I test 512MB memory modules 1 by 1 using the memory test
softwares, or can I have all three in the motherboard?

Thanks
G


"Rock" <(E-Mail Removed)> wrote in message
news:urj%(E-Mail Removed)...
>" Gino" <(E-Mail Removed)> wrote
>> The error messages do not come up every day. Is there a software that can
>> check which memory chip is bad? I have take one of them off, so far it's
>> good, however I cannot be sure since the error may come up later on.
>
> <snip>
>
> Run at least two of these. Let each one run for 24 hours or so, not just
> a single pass. Test with individual sticks and with all together.
>
> Memtest86+
> http://www.memtest.org/
>
> Windows Memory Diagnostic
> http://oca.microsoft.com/en/windiag.asp
>
> DocMemory Memory Diagnostic
> http://www.simmtester.com/page/produ...c/download.asp
>
> --
> Rock [MS-MVP User/Shell]
>

" Gino" <(E-Mail Removed)> wrote in message
news:eQ9rS%(E-Mail Removed)...
>I have removed 1 of 3 512mb DDR PC 2100 memory modules to isolate which one
>is defective. I have gotten the same error.
> I removed 2nd module and inserted the first one I have removed. I received
> the same memory error.
> I now have the 3rd one removed and re-inserted the prior 2 modules that
> were good. Hopefully the error msg will not show up again and I will know
> that it's this last module that is defective.
> Before I had taken out the 3rd memory module, I had run windows memory
> diagnostic from MS, and it didn't find any errors. I let it run from 10pm
> to 1pm the next day. I have stopped the process since and I am now logged
> on to Windows XP, with the 3rd memory module out, and I'm waiting to see
> whether the error msg comes up again.
>
> I will post the update.
> Thank you for your advices.


Ok, let us know how it goes.

--
Rock [MS-MVP User/Shell]

" Gino" <(E-Mail Removed)> wrote

>2 more questions.
> 1. Since it gives an address of memory that cannot be read, is there
> software that would point out which memory module that address refers to?

Sorry I don't know about that.

> 2. Should I test 512MB memory modules 1 by 1 using the memory test
> softwares, or can I have all three in the motherboard?

Test all three together. If errors, remove one module and test the the
other two. Repeat as necessary.

<snip>

--
Rock [MS-MVP User/Shell]

" Gino" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>2 more questions.
> 1. Since it gives an address of memory that cannot be read, is there
> software that would point out which memory module that address refers to?
> 2. Should I test 512MB memory modules 1 by 1 using the memory test
> softwares, or can I have all three in the motherboard?
>
> Thanks
> G
>

It is doubtful. The only way to know if you have a problem with an
individual module is to test the module by itself. Software memory
diagnostics are not 100% reliable either. That's why you should run them on
a loop test for several hours. There is always the possibility that the
motherboard can be bad also (i.e., the DIMM slots themselves).

The best way is to take the memory to a computer or electronics shop and let
an expert with diagnostic equipment (hardware) to test the modules for you.

Their equipment will be similar to the one shown here:
http://www.testequipmentdepot.com/in...k/ramcheck.htm
http://www.testequipmentdepot.com/in...s/ramcheck.jpg
Such devices will give you a definative answer.

Mark