also @ TechSpot: Top PC Games for this Holiday Season and Beyond
Welcome to the TechSpot OpenBoards. Please read the FAQ if you have any questions. Login to participate.

Go Back   TechSpot OpenBoards > Operating Systems & Software > Software & Utilities in General

Referenced Memory error

Closed Thread
Bookmark Thread Tools
  #1  
Old 09-09-2003
aheffner's Avatar
Newcomer, in training
 
Member since: Sep 2003, 2 posts
Referenced Memory error

I'm getting the following error when attempting to print to pdf using Fine Print PDF Factory:

Instruction at "OX2603DE97". Referenced memory at "OXF816AFF8". The memory could not be read. Click on OK to terminate the program. Click Cancel to debug the program.

I have rebooted. Uninstalled and reinstalled the driver and the program that it is giving me the error with.

I have searched google and yahoo and didn't find much. I am running WIN 2000. Any suggestions would be greatly appreciated!!
  #2  
Old 09-09-2003
MattG's Avatar
TechSpot Member
 
Location: Maine
Member since: Aug 2003, 147 posts
You might want to take a look and make sure your memory timings and all settings in BIOS are correct to your type of memory.

To me this sounds like it cant read your memory for some reason. Whether it be your actual program your using, or your memory itself.

Try cleaning out your memory areas...get the dust out of there, and put 1 chip in at a time and try again..see if it actually is a bad memory chip. If this isnt. just post back here and we will see what else we can do.
To remove this ad, sign in. To register for a new account, click here.
  
  #3  
Old 09-09-2003
Nic's Avatar
Nic Nic is offline
TechSpot Paladin
 
Location: UK
Member since: Jan 2003, 1,920 posts
Try running the system file checker to make sure your system files are original and undamaged. From the 'run' command type 'sfc.exe /scannow'. Make sure you have your windows cd in the cdrom drive when you do this. If that doesn't work, then see if there is an update for that program, or download it again to see if things improve. That error is normally caused by buggy or damaged software.
  #4  
Old 09-10-2003
aheffner's Avatar
Newcomer, in training
 
Member since: Sep 2003, 2 posts
Well, I don't know what happened, but it is working now!? It'll probably happen again so I haven't got my hopes up! Thanks for the advice. If/when it happens again I will give your suggestions a try. Thanks.
  #5  
Old 09-10-2003
TechSpot Member
 
Member since: Mar 2003, 88 posts
it's just a normal run of the mill access violation. just see if there is an update from the vendor.

every process is assigned it's own virtual memory map and it's only allowed to use certain regions of it. simply put, the programmer was probably lazy with a calculation of sorts and it tried to read where there was no data or beyond the bounds of a buffer, that sort of thing. OXF816AFF8 is well beyond the program's normal bounds of virtual memory. it exists for that program but the program isn't allowed to directly access it because it's the 'kernel mode' portion which is where windows does stuff. i wouldn't worry about it being a system wide problem unless many applications start giving the exact same message all the time.

Last edited by filthy_mcnasty; 09-10-2003 at 11:01 AM..
  #6  
Old 09-10-2003
StormBringer's Avatar
TechSpot Guru
 
Location: USA
Member since: Apr 2002, 2,871 posts
this might be of use to you.
http://support.microsoft.com/?kbid=262490
  #7  
Old 08-08-2005
Newcomer, in training
 
Member since: Aug 2005, 1 posts
I have been dealing with this error for months now..I tested ram, installed new ram, ran every cleaner I could find.. Never could get it to stop..I even reinstalled Windows 2000 & fully updated it etc.. I did all the proper things.. The error continued..then one day recently, (last week) it "went away"..
..I cannot figure out what I did or stopped doing using to cause this..
I think it was a setting or an app but am clueless asto which one.. I know this is not of any great help to anyone other than to illustrate how tricky a problem it might be. Mybe it was just a loose ram module..dunno.. but the problem has not occurred for a week now..but if it returns I will be in touch & post any discovery made . cheers... g..
  #8  
Old 08-08-2005
Tedster's Avatar
TechSpot Evangelist
 
Location: Fort Stewart, GA
Member since: Feb 2005, 9,599 posts
System specs
if you think your memory is bad, it could also be a bad slot on the motherboard instead of your stick

also run memtest86 to see if your memory is bad.
  #9  
Old 08-30-2005
Newcomer, in training
 
Member since: Aug 2005, 1 posts
Hi all,

As said filthy_mcnasty, it's pure software bug and checking your hardware will not help. I got this message when MS Word tried to save a document in the motherboard's PROM (or was it in the PCI chip) :-)

As was said above it most likely is due to a buffer overflow, or access to memory through an un-initialized pointer. Anyway, some part of the memory which wasn't allocated for the culprit application's usage.

Eric
To remove this ad, sign in. To register for a new account, click here.
  
  #10  
Old 08-30-2005
Tedster's Avatar
TechSpot Evangelist
 
Location: Fort Stewart, GA
Member since: Feb 2005, 9,599 posts
System specs
hmmm. I wonder if there is a patch for it.

In any case, I switched to openoffice a long time ago. Never had anyproblems.
  #11  
Old 09-27-2005
Newcomer, in training
 
Member since: Sep 2005, 2 posts
Finally

:hotbounce Finally, after all this time and effort... I feel so free! The memory error seems to have disappeared since getting rid of Norton's Internet Security, including Anti-Virus stuff. In fact, some other annoying little problems are gone too.
  #12  
Old 12-18-2008
Newcomer, in training
 
Member since: Dec 2008, 1 posts
Okay, I'm getting the message "The instruction at 0*00401082 referenced memory at 0*00000000. The memory could not be written." This occurs every time I start up my computer. It gives me the option of either continuing or debuging something. When I click either choice, it just gives me a blank screen which will never load into anything else. Is there something I can do about this?
  #13  
Old 12-18-2008
Newcomer, in training
 
Member since: Dec 2008, 1 posts
Quote:
Originally Posted by musisat View Post
getting the message "The instruction at 0*00401082 referenced memory at 0*00000000. The memory could not be written." This occurs every time I start up my computer. It gives me the option of either continuing or debuging something. either choice just gives me a blank screen which will never load into anything else
i'm seeing the exact same issue ... running Windows XP ...

the only option seems to be power cycling the PC, then hitting F10, system recovery, which basically restores the PC to its original state (while saving user data files) ... it warns that applications must be reinstalled after recovery

thought i'd check in here before i wipe out my applications ...

any help would be greatly appreciated !
Closed Thread

Tip: Download Advanced SystemCare 3 Freeware - 1 Click A Day to Clean, Repair, Protect & Optimize your PC.

Thread Tools


Similar Topics
Topic Category Replies Last Post
Win 98 memory above 512meg Windows OS 17 03-21-2008 03:49 AM
Memory Reference Error Windows OS 4 10-01-2007 07:50 PM
Referenced Memory Error Windows OS 271 03-03-2007 03:43 PM
memory has error General Hardware 2 01-21-2004 12:07 AM
Instruction at 0x77fc8f11 referenced memory at 0x9486f4f8 Windows OS 1 01-06-2004 02:29 AM


All times are GMT -4. The time now is 10:33 PM.