"Memory could not be Read" error

When I try to run Q2004 (R5) Update, I get the following error message:

The instruction at "0x03113e19" referenced memory at "0x019cb1a0". The memory could not be "read"

Click OK to terminate the program

Clicking OK terminates the error.

This sounds like a hardware problem and I may have to replace or re-seat my memory cards. Are there any other troubleshooting suggestions? Could it it be Virtual Memory corrupted? XP SP2

Reply to
Arnie Goetchius
Loading thread data ...

Nevermind. I re-installed it and it works okay now.

Reply to
Arnie Goetchius

Arnie Goetchius:

I've reported this error several times over the years since I upgraded to Q2004. It started for me with R3 and has continued to the present with Q2004 R5.

If you search this Usergroup, you will find similar errors back to at least Q2002. (I jumped from Q2001 to Q2004, so I cannot speak from experience). But interestingly, I cannot recall anyone complaining about memory read errors in Q2005 or Q2006. I have seen messages in this Usergroup stating that the newer versions just stopped. Maybe Intuit eliminated the error message?

I would doubt that it is a physical memory issue. Do you have this problem with other software? I don't, and I may have a dozen applications open at any one time.

I think it is a software bug that is harmless until you have either lots of data (I started using one of the early DOS versions, my transaction history goes back to 1990, and my investment history goes back to 1967 (a gift of stock which I still own), lots of accounts (some 100+, though most are closed), lots of investments over the years (but I usually stop keeping current price history on stuff I've dumped), or something similar which causes an internal table to expand to a size greater than the software engineer thought was necessary.

That's all I'm saying. But it would be interesting to hear a report in a few weeks if you in fact solved this issue.

-dll

Reply to
dllapides

Thanks for the report on your experiences. Uninstalling and re-installing 2004 solved the problem for me so I'm going any further with this unless it happens again.

Reply to
Arnie Goetchius

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.