Results 1 to 5 of 5

Thread: "Memory could not be 'read'" error

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1

    Default "Memory could not be 'read'" error

    I've recently reinstalled my RTW and patched it to 1.5. It plays great, but after I quit the game, I can't start it again - unless I reboot the computer. When I try to run the program I get the following error message:

    The instruction at "0x667c40e" referenced memory at "0x029ee43a". The memory could not be "read".

    OK to terminate . . . etc
    Cancel to debug . . . etc

    Naturally, neither of the options actually let me play the game. I just end up rebooting. I'd really rather not keep rebooting everytime I want to play. Any ideas?

  2. #2
    Virgil's Avatar Powered by Technicolor©
    Join Date
    Jun 2005
    Location
    Connecticut U.S.A.
    Posts
    1,342

    Default Re: "Memory could not be 'read'" error

    Have you installed new memory in your computer recently? Also, does this happen for any other games or programs.
    Patron to Shadows, The White Knight, Darkragnar, and
    Ramon Gonzales y Garcia. Under the patronage of Horsearcher.

  3. #3

    Default Re: "Memory could not be 'read'" error

    Nothing has been changed or added recently, and it doesn't happen to any other program. It's odd - if I reboot, then it works fine until the next time I want to play.

  4. #4

    Default Re: "Memory could not be 'read'" error

    The same happens here. It must be a bug. I have found a strange workaround though.

    1. Use your "My computer" or explore your computer.
    2. Making sure your CD or DVD drive that you used for running your game is empty; "look" at it.
    3. Close the file org. window.
    4. Reload your CD and wala.

    It refreshes where your file locations are stored and so it works. As to why it happens?

    I hope this works; it has for me.

    Fogcat

  5. #5

    Default Re: "Memory could not be 'read'" error

    Whaddya know, it worked.

    I also tried just ejecting the CD tray and pushing it back in . . . and it worked too.

    Doesn't fix the problem, but it's TONS better than rebooting. Thank you.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •