Memory errors 1

[Preka]

Getting a rather aggravating error with some, but not all, reports and forms in an access database.

The error(s):

The instruction at "0x77f83905" referenced memory at "0x00000000". The memory could not be "written".

Which is followed by...

"The instruction at "0x77f58dc5" reference memory at "0xfffffff8". The memory could not be "read".

This occurs while trying to open the form or report in any mode.

A few significant notes:
1. This began yesterday. I have several assorted copies of this database stretching back over months. Even the very old ones are experiencing this problem - on the exact same forms and reports. They have not been changed at all.

2. This problem is local not only to my machine, but to this specific account on my machine. If I log off and log on as a seperate user, voila - no problems to be had.

 

[BobStubbs]

I would use a diagnostic tool, to check the physical RAM in your workstation for errors. The symptoms you describe, suggest:

-- The problem is not within your database, as you can use the database OK on another machine, and with a different user account
-- The problem is not within your Access installation - assuming all user accounts on the PC are using the same copy of Access
-- The problem may be physical RAM - when you log in as a different user, this account's profile will be different, and so the amount of memory used in the PC will be different. This is especially true if you create a new, test account just to check for a problem.

There are plenty of free diagnostic tools around, e.g. take a look at:

http://www.benchmarkhq.ru/english.html?/be_memory.html

I hope that this helps.

Bob Stubbs

 

[Preka]

Well, I got my problem resolved.

Memory utilities didn't return any problems, so I bounced this off a friend of mine, and he says, "Have you checked your printer? They can cause office to freak in a weird way sometimes."

I came in this past weekend and wiped a few of the computers, including the one whose printer I had been using over the network.

Sure enough, I deleted the bad leftover printer setting and, voila, problem solved.

 

[BobStubbs]

That's a really obscure (and hence really useful to know!) reason for a memory error, which I had not come across before. I'll definitely keep a record of this, in case I ever see it on my PCs. Have a star!


Bob Stubbs

 

[LLBP]

I'm having the same issue. It worked fine for several weeks though. It will print once then at the next print job, it will freeze and give the memory access violation. I've deleted the printer and reinstalled it several times with the latest driver (Sato CL408e label printer). The app works fine using other printers.

I'm using W2K Pro. On WXP, after installing the printer, upon reboot it it gives a print error and creates a "<printername>(Copy 1)" printer on its own. I deleted the printer and renamed this one to just printername and it works on WXP so far.

Anyone have any ideas?