Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

iexplorer


  • Please log in to reply

#1
ruffus

ruffus

    Member

  • Member
  • PipPip
  • 35 posts
What is the meaning of the message,
instruction 0x62304320 memory could not be "read" :whistling:
  • 0

Advertisements


#2
Jrenter2

Jrenter2

    Member

  • Member
  • PipPipPip
  • 435 posts
Hi Ruffus,

From what I understand about this error, you are probably experiencing this error due to an ActiveX control on a web page that you are visiting. Essentialy what the message states is that the instruction at the executing address (here its at 0x62304320) tried to read from the same memory block that is currently executing. In basic terms it tried to read 2x at the exact same moment on the same location which cannot be done.

There have also been reports of Add-ons causing this problem such as Yahoo, Google Toolbars. If you have installed any of them lately, you may want to try and disable them to see if your problem continues.

Hope this helps.

Jrenter2
  • 0

#3
b1caez01

b1caez01

    Banned

  • Banned
  • PipPipPip
  • 445 posts
If you stick to Windows DEFRAG as your only defragger, you may solve these problems ...some 3rd party defraggers will attempt to fill every nook and cranny, leading to this very problem... It conserves space, but does it enhance efficiency under all conditions? It is also good policy that after you delete a prog and you have the time, do a clean defrag, to fill [overwrite] in those bare spots. Then when you install something new, Windows has to go searching for a new location to put it in, rather than plopping it down in the vacated old spaces.

Edited by b1caez01, 15 December 2006 - 11:10 AM.

  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP