|
List Home > Development Tools > Microsoft Visual Foxpro > [ Post New Problem ]
Welcome back !
| TrackingID : | 252 |
| Posted : | Tuesday, December 02nd, 2003 10:29:44 AM |
| By : | carosu |
| Application Error- Memory could not be read | Configuration: |
When running my application I am getting the error message "The instruction at "0x18004160" referenced memory at "0x18004160". The memory could not be "read"". This happens sporadically about once every 20 times. It is getting really annoying. I have been looking on the internet for possible solutions but I have yet to see a similar message where the instruction location is referencing the memory at the same location. When checking the disassembly code using C++, there is nothing at all at this location. It occurs on more than one machine and the memory reference is always the same.
Additional Comments:
This is for VFP 8 running on Windows XP.
| Operating System : Microsoft Windows XP Home Edition
|
Related Problems :
Comments :
Re: Application Error- Memory could not be read by Anonymous Ghost on January 02nd, 2004 10:56:21 AM
fd |
Re: Application Error- Memory could not be read by Anonymous Ghost on January 07th, 2004 04:37:46 AM
Lovely ! |
Re: Application Error- Memory could not be read by saif75309 on November 11th, 2004 03:16:07 AM
RESOLUTION
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Internet Explorer 6 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
please gets back to me on saif75309@rediffmail.com |
Re: Application Error- Memory could not be read by Anonymous Ghost on December 12th, 2004 02:30:03 AM
I get the 'Memory could not be read'
problem with RTERM98 which i
use for win98 driver development in windows NT(host).
I was looking for the solutions and have got a link in the microsoft site itself.
Maybe, it would be useful for you also.
I think, applying that patch will solve our 'Memory could Not read" problem.
It is available in ->
http://support.microsoft.com/kb/299444/EN-US/
Refer the following in that page ->
267858 "Memory could not be read" error message while doing file operation
Am I right ? It must me the solution ...(( i have to check it out... i got it just now via our friend google !!!)).
R there some other solution for
win 2k/NT for the above problem ?
R there some other things with respect
to RTERM98 ?
Do kindly let me know quickly , if there are some other things .
Thanx and Regards,
karthik bala guru
linladn@yahoo.co.in
Thanx in advance,
karthik bala guru |
Re: Application Error- Memory could not be read by Anonymous Ghost on December 13th, 2004 11:18:47 AM
I get the same error. Clicked on your link but didn't see anything regarding the reference memory error. Eventually I found it though at this link.
http://support.microsoft.com/kb/267858
Microsoft says its caused by having by a file extension that contains more than 260 characters to the right of the period.
Install SP4 ??? dunno if it works yet |
Re: Application Error- Memory could not be read by Anonymous Ghost on December 22nd, 2004 04:08:09 AM
im getting the same error in xp, sp2.
cs:source crashes as soon as it loads the menu, which has a 3d background, are there any patches/methods to stop this from happening?
if anyone finds anything
killspm@hotmail.com |
WINLOGON.EXE by Anonymous Ghost on January 26th, 2005 10:29:36 AM
Application error. The instruction at "0x012a32aa" reference memory at "0x000000008".The memory could not be read.Ok to terminate. Cancel to debug.
Any solution Gurus???
Please Help.
Thanks in advance
Ghost. |
Re: Application Error- Memory could not be read by Anonymous Ghost on July 26th, 2006 06:06:32 PM
We have been having the very same problem, also with the instruction location and referenced memory being identical. For us, this is occuring on xpsp2 and server 203 terminal server when trying to load a procedure on a client from a remote server application written for specific types of data transmission. It occurs when a specific window is loaded, but intermittently and haphazardly. The developer is investigating, but has not noticed the problem outside our environment. Transmission is over a vpn but that doesn't seem the issue. Can anyone comment on the 'hotfix' referenced above and if this actually worked? Many thanks. |
Related Problems :
List Home > Development Tools > Microsoft Visual Foxpro > [ Post New Problem ] |
|
