I get this pop up;
"The instruction at "0x629133b1" referenced memory at "0x629133b1". The memory could not be "read". Click an OK to terminate the program."
In Google I typed in the memory reference, located several sites refering to it, but no solution.
What is this ??
Thanks
read" problem
Moderator: Wiz Feinberg
-
Joe Delaronde
- Posts: 1037
- Joined: 4 Aug 1998 11:00 pm
- Location: Selkirk, Manitoba, Canada
-
Darren Harkins
- Posts: 23
- Joined: 18 Apr 2005 12:01 am
- Location: Benton, Illinois, USA
- Contact:
Generally it means one of three things:
1. You have run out of memory (RAM). This is generally caused by too many programs running in the background, or a program has a memory 'leak' and is slowly eating up your available RAM
2. One of the sticks of RAM in your computer has a 'bad spot'. The computer wrote information to a sector, then when it tried to read it, failed so it caused the error you saw.
3. A program you are running was poorly written and is looking in the wrong places for information it stored, or it has a memory leak.
1. You have run out of memory (RAM). This is generally caused by too many programs running in the background, or a program has a memory 'leak' and is slowly eating up your available RAM
2. One of the sticks of RAM in your computer has a 'bad spot'. The computer wrote information to a sector, then when it tried to read it, failed so it caused the error you saw.
3. A program you are running was poorly written and is looking in the wrong places for information it stored, or it has a memory leak.
-
Ray Minich
- Posts: 6429
- Joined: 22 Jul 2003 12:01 am
- Location: Bradford, Pa. Frozen Tundra
The instruction pointer register in the CPU (the microprocessor) was telling the microprocessor to go to a memory location that either doesn't exist or maybe it ain't supposed to go there for other reasons. This is a program error at the most very basic (operating instruction) level of operation of the PC. Probably a program bug...
-
Jack Stoner
- Posts: 22087
- Joined: 3 Dec 1999 1:01 am
- Location: Kansas City, MO
If it only happened one time, it's not something to be concerned with. However if it happens every time you run that particular program then there is an issue and as noted probably a program bug. Reinstalling the program or if the program has a "repair" option running the repair may fix it.
You didn't mention what program caused it and what Operating System so other than "it had a problem" no one really can tell you anything other than just general info.
You didn't mention what program caused it and what Operating System so other than "it had a problem" no one really can tell you anything other than just general info.