Error Message - Memory could not be read : Part 2

I found this while searching the US support data base (the link was session related, so I cut/pasted the article)

Title Error: "qbw32.exe - Application Error: The instruction at OX([###]) referenced memory at OX([###]). The memory could not be 'read'." KB ID#:

319032 Categories: Data and Utilities Question: Why do I receive the following error when I exit QuickBooks?

qbw32.exe - Application Error: The instruction at OX([###]) referenced memory at OX([###]). The memory could not be 'read'. Possible Cause: This error may occur when exiting QuickBooks immediately after synchronizing contacts with Microsoft® Outlook® or Symantec ACT! TM. Answer: The error will not affect functionality or data. You can close it and continue normal activities. Note: The error will not occur if you perform other functions in QuickBooks after synchronizing contacts. Last Modified: 10/22/2003 Created: 10/22/2003

I should mention that in the search there are other possibilities listed. The UK website did not yeild any results. I found three possible responses on the US website at

Navigate to Error Messages. Select 'Basic and Pro' for the Product, Select '2005 for Windows' as the Version. Enter the phrase 'the memory could not be "read"'

Of all the error possibilities listed, I posted the above, because you had stated the file itself is not damaged, and that the error only happens when you open on your pc.

According to the knowledge base, you should close the error window, rather than clicking OK to terminate the program.

If you are able to successfully open the file the error should (hopefully) be resolved upon next closing the program - provided you 'perform other functions' in QuickBooks.

Tx for the suggestions - no luck I'm afraid with the one you pasted or the others on the QB support website.

R

What version of Windows? If XP, post the above to:

microsoft.public.windowsxp.general

on the

msnews.microsoft.com

news server and I'll bet you'll get the correct answer in half a jiffy.

Ya got a virus.

Ah... I thought you were getting a BSOD on the memory error, which is what would have occurred with defective RAM.

Since the problem doesn't occur in safe mode, I bet the problem is due to a conflict with another process -- either a service, or application started from the registry "run" key or the "startup" program group. I would try killing processes that were started by "startup" first, one at a time. If that doesn't work, check the HKCU and HKLM \Software\Microsoft\Windows\CurrentVersion\Run keys and see if anything looks suspicious. If you are familiar with editing the registry, you could backup the key and then remove entries, again one at a time.

One wild thought would be to compare which services are running in the current windows user ID vs the new one. It might reveal which service(s) are causing a problem.

I am having a similar problem when I shut down my computer. Posting to the windows newsgroup basically told me that a service is the problem. Which one, I don't know.

You can turn off services in batches via msconfig, Services tab. Choose the checkbox at the bottom that says Hide All Microsoft Services so you don't inadvertantly turn off something the OS needs.

To save time, since each sequence requires a shut down & restart, deselect batches of 10 services at a time. You should find that deselecting some service batches won't duplicate your problem (clearing them of wrongdoing) while one batch does. You can then narrow down from inside that batch.

-- Tara

Do you recommend just disabling Non microsoft services or all services 10 at a time?

BTW, there have been some reports of the August updates causing some problems but using a Restore point prior to early August does not always cure the problem. It did not help me.

Thanks to all.

I finally traced it to 'Onguard' which is part of PCTools Spyware Doctor utility.

I've disabled it temporarily and asked PCTools tech support for a fix.

-- Tara

Only non-MS services. Select the option to hide MS services so you don't even have to deal with them.

I haven't had problems. HP & Norton updates are usually the culprits of my occasional glitches.

-- Tara

How did you find it?

Thanks RFJ. I had the same problem with Quickbooks & the same err msge . I disabled PC Tools Spyware Doctor & I now have no problems with Quickbooks

Thanks

Told you you had a virus, all be it one you want. It wasn't installed under other users on the machine, so it didn't cause a problem. BTW what good is a spyware detector if it doesn't run no matter who is logged on?

I used msconfig.

In the startup group I unchecked everything that I wasn't certain of (mainly specialist utilities including one from Quickbooks). Once I rebooted the pc and found that QB worked, it was just a question of finding out which of the ten unchecked items it was.

I looked at the ten and guessed which were more reliable than other, enabled another seven and QB continued working.

That left me with 3. I was then lucky, I enabled everything except PCTools and voila - I knew the culprit.

Just to be sure I did it the other way. I disabled everything in the Startup group except PCTools and QB again did not work.

Excellent detective work! Congratulations. I applaud your diligence and logical abilities.

Many would have just moaned and groaned, wrung their hands, and accused the evil-de-jour (Microsoft, Intuit, George Bush) of perfidy and bunny-stomping.

But your task is not yet over: You must get on the blower to PCTools and bitch like the third monkey on Noah's gangplank!

Glad it was of help. It took the best part of 2 days to sort out with the help of this newsgroup and the windowsxp.general

Have you contacted PCTools to report the problem? If not it might help if you do- since if only one user complains they might think it is a problem just to that person

Rob