Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Cannot Write Instruction To Memory error


  • Please log in to reply
1 reply to this topic

#1 computercoach

computercoach

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:07:28 PM

Posted 04 January 2005 - 05:07 PM

At least twice recently, I have encountered the following type of error: "The instruction at "0x1234567" references memory at "0x000007D0". The memory could not be read (or sometimes "the memory could not be written to this address". (NOTE: the numeric references are not real, just made up.)

I understand what this means - that the memory address that the particular program is trying to write the particular instruction is probably being used by other software.

My question is: What do I do to solve the conflict. Reinstalling the program doesn't work. Is there a utility, within or separate from WIN XP to re-direct the instruction to a vacant memory address and, if so, how is this done? Anyone?

BC AdBot (Login to Remove)

 


m

#2 Grinler

Grinler

    Lawrence Abrams


  • Admin
  • 43,400 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:USA
  • Local time:07:28 PM

Posted 06 January 2005 - 09:19 PM

This is usually caused by incompatbilities in hard drivers and/or shoddy programming in an application. Does the error tend to happen wtih a certain app?

You may want to try updating all the drivers for the hardware on your machine and see if that helps




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users