Memory Address Error 0x0….. read 0x0…. written 0x0….

  • This topic is empty.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #1183
    75joe75
    Member
    • Total Post: 41
    • Frequent Flyer
    • ★★★

    All,

    Need help with this one. Been going crazy for the past month. I’m getting a “0x****** referenced memory at 0x00000001. The memory could not be “read” or “writtten”

    I get this on a V90 with the latest image with many applications, none microsft

    Thanks In Advance

    #12924
    thinkthin
    Member
    • Total Post: 1686
    • Jacked into The Matrix
    • ★★★★★★

    Hi,

    Its been a while since I have seen you on the forums!

    Is this error on the same unit? I had an image that was corrupt once and I kept getting the same error until the image was re-built. Also is the the same app with the error or a differing one?

    Image up a different unit with the existing image first to check.

    Cheers,
    -TT

    #12939
    75joe75
    Member
    • Total Post: 41
    • Frequent Flyer
    • ★★★

    Hi TT,

    Yup its been a while, can’t complain these Wyse devices are awesome. I’ll pop in more often with some replies to people’s msgs.

    The error is on several units with several apps incuding Microsoft products such as “write filter”. I have reimaged several sets and the error seems to be intermitten on the reimaged and out of the box devices.

    Loaded on these devices which are not part of the base image are:
    McAfee Antivirus 8.0i
    McAfee Antispyware module add on to version 8.0i
    IE7 (from Wyse Labs)

    Hope this helps with more info

    #16776
    ATLJason
    Member
    • Total Post: 1
    • Newbie

    I am having the same problem. I recently upgraded my V90 units from HAgent version 4.2.1.2 to 5.1.1.10. Now, any time I try to push a Microsoft security update to these units, I get an error that says “The instruction at “0x0…..” referenced memory at “0x0…..” The memory could not be read”. I then lose communication with the unit and someone on the other end (remote branch hundreds of miles away) has to reboot the unit.

    How can I fix this? Is there a way to go back to the old agent? Or is there a newer agent that might fix this problem?

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.