TechSpot

Bobcat1132 · #**121** 06-03-2005

my suggestion replace each piece of hardware until you figure it out because it could be any thing maybe even try the hdd and make sure everything is connected correctly

cpc2004 · #**122** 06-03-2005

Quote:

Originally Posted by TheGreatAnt

My error is:
"The instruction at 0x241f94f7 referenced memory at 0x00ff0cc0. The memory could not be "read"

Click on OK to terminate the program"

The specific memory instruction changes from error to error.

I have not gotten a BSOD. Error occurs when playing games (specifically HL2 and Guild Wars). Usually I'll have been playing for about 10 minutes, but it can be up to an hour. I have not tried playing movies of any sort on this computer yet, so I don't know if that would also generate the error.

The machine was put together by myself with all new parts (except the floppy drive). It was built within the past 2 weeks. OS is XP w/ SP2. I wanted to stick with SP1, unfortunately it won't retail anywhere that I found. It turns out I can't roll back from where I'm standing right now.

The machine has few programs installed on it. No anti-virus or anti-spyware is present. Only things running that are not directly associated with windows would be the nVidia desktop manager and the creative volume controller. Also, the two things that currently launch at startup are Trillian and Steam.

No Dr. Watson folder exists, I don't think I have the app. If I do, it hasn't done anything yet. Neither is there any folder named minidump on my computer.

Computer specs (also in profile):
Important stuff
AMD 64 3800+ Newcastle
2x1gb Corsair XMS 3200PRO (passed an extensive memory test last night)
DFI Lanparty SLI-DR
eVGA GeForce6800Ultra 256 PCIx
Creative Audigy 2 ZS Platinum Pro

Less-Important stuff
560w PS
2 SATA hd, 1 74gb Raptor, 1 250gb
DVD burner
DVD reader

OK, so instead of leaving that there, I'm with the captain on trying to find the root cause. Currently, I've noticed a few things.

OSs that experience this problem seem to be XP, XP SP2, 2000, and 2003. XP SP1 does not seem to experience this problem as much (at least not with the games) and that matches my personal experience. I personally have gotten the problem with both XP and XP SP2. When I've had SP1, I have not experienced this. If you DO have a different OS from those listed and are experiencing this, please let us know.

CPU has been both AMD and Intel, though mostly AMD

Memory has been everything from a lot to a little, by multiple companies.

GPU, same thing, everything from onboard to high powered.

Causes have been everything from closing IE to starting the computer to being in the middle of a game.

SOLUTIONS have ranged from deleting random software to changing settings in IE to buying new hardware.

So (and I know this is obvious) the error message clearly has no single solution. It is not software exclusively, nor is it hardware exclusively. Unfortunately, it is the interaction between the two, which is definitely the most obnoxious type of problem, as neither company can really be contacted with any hope of getting the necessary supported. The only similarity we have to work with is Windows here. That's not a bash against windows however, it is merely the realization that this error message is a generic response for a memory problem that can be caused by any number of things. One thing that does seem to be a theme with this message is it's relation to somehow utilizing the graphics card, either for playing a movie or for gaming. That is not true in every case, though. IE has been related in many cases as well.

Essentially, I need to figure out how I can get error logs of what is going on, and then find someone who can interpret them and let me know what is wrong with my specific system. cpc2004, you look like the potential person to help me - if you are up for it - but if anyone knows of a website that has any additional info on this at all, please let me know.

And if anyone needs any info from me about my computer, feel free to ask.

GreatAnt,

Your problem may be related to virus, software problem or faulty ram. The DrWatson log has the most useful diagnostic information of your problem. Maybe you disable DrWatson. Refer the following URL to activate DrWatson

http://support.microsoft.com/default...b;en-us;308538

TheGreatAnt · #**123** 06-03-2005

Not a virus, the situation occurred twice on two different OSs on this comp (windows XP and XP SP2), one of which had not been attached to the internet. Problem is possibly a pure software problem, but that's very unlikely. Faulty RAM is not the cause, as far as all the extensive memory checkers I've run can tell.

I would guess that this is just a compatibility issue between certain applications and hardware. Though some of it seems to be tied very directly to IE, none of the fixes involving that work, and I do not seem to crash when using IE. I generally use Firefox, but of course IE is pretty much throughout the windowXP operating system.

I did a heck of a lot of research on this. For those of you with crashes that seem to relate to video cards, media playing, and/or gaming, here is a potentially helpful website.

http://steampowered.custhelp.com/cgi...php?p_faqid=56

While the fixes listed on that website do not necessarily work, I DID manage to extend the overall life of any game I am running from approx. 15 minutes to about 45 minutes. Still not good for all types of gaming, but certainly more functional for campaign modes.

Microsoft also released a patch for this exact problem in both WindowsNT and Windows2000. Apparently they didn't fix the overall problem, so we will have to wait for the patch to come out for XP and use temporary solutions and workarounds until then. Also, if gaming is where you are experiencing issues, game companies are also working on patches to stop this from happening.

For the extreme of us out there, the problem for NT and 2000 was:

"This problem is caused by a file extension that contains more than 260 characters to the right of the period. The buffer overfills and causes the error message to occur."

Quoted from http://support.microsoft.com/kb/267858/

If you research it for NT exclusively, you will find the same thing. Not sure if it is that exact same problem for all the XP cases that have been cropping up, but it could certainly explain a few of them that I have seen on this thread.

More research into the gaming aspect will bring you this:

http://forums.steampowered.com/forum...hreadid=225994

"The #1 cause of this problem is the memory on your motherboard.

If you have a modern motherboard and you have more than one memory module installed, and the modules are different speed ratings or diferent sizes there is a very good chance this is causing your problem.

Especially on Nforce2 and Nforce3 motherboards (AMD processors) this has been historically the most reported error, with VIA motherboard chipsets next followed by a very small number of Intel motherboards."

Apparently the memory sticks become desynced with the CPU through the mobo, as someone was saying earlier. Good call, whoever that was.

Removing all but one stick of memory and seeing if you still get the problem can let you know if that is causing it.

Note that none of the components are faulty when this is the case, they simply refuse to work together properly.

If anyone else finds anything more, please post it here, I will continue to moniter this thread closely.

cpc2004 · #**124** 06-03-2005

Some faulty ram can pass memtest as memtest is not a reliable tool to test the memory

Bobcat1132 · #**125** 06-03-2005

use mozilla not ie?

TheGreatAnt · #**126** 06-04-2005

I didn't use just memtest, used several. Clear on all counts, including the extensive tests that are done. It is very unlikely that it is bad memory as a result.

This looks like it could be a XP to DirectX compatability issue. I've activated Dr. Watson, next time it crashes I'll make sure to check that out. After that, I'll try pulling sticks and perhaps adjust my latency levels up. Also might try raising my DRAM voltage.

MJL54 · #**127** 06-05-2005

Quote:

Originally Posted by cpc2004

MLJ54,

DrWatson log has the most useful diagnostic information of your problem. Attach the following files at any webspace. I will study your log and dumps.
C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\drwtsn32.log
C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dmp

cpc2004

I've been trying to upload my log but I keep getting a message that the document has no data it it. Help? I'll try again to day but after that... I tried copying/pasting, that didn't work either.
MJL54
:knock:

TheGreatAnt · #**128** 06-05-2005

I've now had the error twice, and I have no log generated for/from Dr. Watson. Does it only take info down in the case of a full crash? As I keep looking all over the internet for this, it seems to affect mostly newer games directly after either installing XP SP2 or upgrading DirectX to 9.0c OR upgrading various device drivers.

At this point, I can't wait for the next directx model to come out, or something else to happen in relation to this problem. I'm still experiencing the problem and will remove a stick of memory to see if that helps.

sarellan · #**129** 06-22-2005

The instruction at "0x0572e115" referenced memory at "0x000000401". The memory could not be "written".

Click on OK to terminate the program
Click on CANCEL to debug the program

I experienced this same type of error at work today on a user's machine - it also started with Juno. Then it started happening to Internet Explorer. We uninstalled both of the Juno apps she had listed under Add/Remove programs and it resolved the problem.

cpc2004 · #**130** 06-22-2005

Your Winodws may be infected by virus or faulty ram. Attach the following files at any webspace. I will study your log and dumps.
C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\drwtsn32.log
C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dmp

billls · #**131** 07-12-2005

Hate to respond to an old thread but I've had this error recently and Googled it. I think I've found the solution through "lack of" example. I've seen postings/replies of people that have reinstalled Windows; replaced memory; had the problem in many machines; and in multiple browsers as well. All of them, thankfully saved me some time by saying that none of the above solutions worked. I have found the following link, however,

http://www.java.com/en/download/help/ikernel.xml

Seems Java has owned up to it being their fault. Makes sense to me as:

Overlaying a Windows install wouldn't affect faulty Java
Replacing memory wouldn't affect faulty Java.
Maybe I'm wrong but I beleive multiple browsers use Java so it seems possible to get the error using different browsers.

I'm going to see if this helps; hope it helps someone else!

Teranova · #**132** 07-14-2005

i get the same error message, but only when playing games. It happens with all games. I have no idea what might be causing the problems. Any advice on where to start?

Teranova · #**133** 07-15-2005

okay i have totally solved my problem. I followed somebodies link to the steam forum which gave a variety of solutions. It turned out that one of my sticks of RAM was faulty, even though it passed various memory tests with flying colours. I have now removed that stick and my computer runs happily whilst playing games for hours. I've had this problem since i had the computer, which is about a year and a half. The guys in the shop sold me dodgy RAM. Annoyed this could have been sorted earlier, but so happy my gaming career can continue. HUZZAH!!!

sherlock84 · #**134** 07-21-2005

I have read through this long thread and found this site to be the most informative concerning this frustrating problem.
I get this error message:

Quote:

The instruction at "0x77805a10" referenced memory at "0x00225000". The memory could not be read. Click on Ok to terminate the program.

only when opening a specific app on a specific computer.
But now the problem has cropped up on another computer. This app runs fine on all the other computers.
We have all the same hardware. But after reading the posts, I have checked the video adapter drivers. When comparing computers that I do not get the error message on with the one that does, the Intel onboard video drivers are the same version.. But that version is different from other computers in our system that do not have this app on it.. ie they are older drivers.
This is a special program that users need to use and this has been a plaguing problem. I have changed hard drives, memory and given both users 'new' (different) computers with a new image and new install of the app. It worked fine in my lab.
Then the users would call after the first time they used the app to say that they could not open it and their data is inaccessable.

I will try activating Dr Watson. But unfortunately users will not be back until the end of August. I was hoping to have this problem resolved for their return.
I would appreciate it if cpc2004 would read this and make suggestions.

hrowder · #**135** 07-30-2005

For me the error comes when trying to access my home network. I thought it would be hardware, but I changed the card and got the same error. It reads: the instruction at 0x5ad8f6b9 referenced memory at 0x202c5004 the memory could not be read

I previously ran a memory check using some downloaded software... the long version... and it found no errors. Still, I removed, cleaned, then reinserted the memory sticks being sure to reverse the slots I put them in. Strangely, I can access the internet but not my other computers through this one.

Does anyone have a clue for me???

DeviousOverdose · #**136** 08-10-2005

The only time i ever had this issue I was getting Virtual Memory Low warning before hand. The computers I work with require specific logins. Im just curious if there is anyone out there might be able to continue this line of though and maybe it will come up with a solution thats helps all. If there is a holygrail in this case.

What if the memory reference had to do with the virtual memory file on the disk and windows inability to distinguish the difference between and administrative user and an owner.

I've had this problem for quite some time on my work computer along with another problem with "sharing violation" errors.

Ok my thoughts: Everytime you exit out of a program Windows writes all of your latest information into the virtual memory file. If for some unknown reason windows decided that you should no longer have full access to this file, then when the OS tries to read from it, it would be denied. Seeing as the OS thinks this file is memory, not a disk file, you get a reference error rather than a sharing violation error.

The above explanation would account for the seeming random memory range and the fact that it happens to multiple applications.

Now what I haven't figured out is how to fix it.

Suffice it to say, it is not specific to WinXP because I'm on a Win2K system, both of which have documented sharing and access problems.

sturgel · #**137** 08-10-2005

Could this be a JAVA update causing this problem? Anybody check this option out? I'm having the same problem with the "memory cannot be read" error with various programs. I wonder if a recent JAVA update did this?

Maybe worth checking out.

cpc2004 · #**138** 08-11-2005

Quote:

Originally Posted by sherlock84

I have read through this long thread and found this site to be the most informative concerning this frustrating problem.
I get this error message:
only when opening a specific app on a specific computer.
But now the problem has cropped up on another computer. This app runs fine on all the other computers.
We have all the same hardware. But after reading the posts, I have checked the video adapter drivers. When comparing computers that I do not get the error message on with the one that does, the Intel onboard video drivers are the same version.. But that version is different from other computers in our system that do not have this app on it.. ie they are older drivers.
This is a special program that users need to use and this has been a plaguing problem. I have changed hard drives, memory and given both users 'new' (different) computers with a new image and new install of the app. It worked fine in my lab.
Then the users would call after the first time they used the app to say that they could not open it and their data is inaccessable.

I will try activating Dr Watson. But unfortunately users will not be back until the end of August. I was hoping to have this problem resolved for their return.
I would appreciate it if cpc2004 would read this and make suggestions.

It may be related to virus, faulty RAM, faulty M/B and software error. Run HijackThis and make sure that your windows does not infected with virus. It is great if you can attach the DrWatson log here.

sturgel · #**139** 08-11-2005

I like others don't think it is an hardware problem. What I do think is that its a software problem and the software is a common software or Windows XP service pack 2 update itself. If you search Microsoft KB you will find numerous KB articles on the "memory can not be read" error from numerous programs!

My feeling is that a recent update be it Java, Windows, or some other common software causes this error. Another cause could be the DREADED/HATED/DISPISED/RESERVE A PLACE IN HELL FOR THESE PEOPLE spyware. Personally, I've never felt so much hatred for another person("fellow programmer") then I have dealing with the spyware. Almost any punishment is justifyable IMHO. And that scares me.

I've don't alot of reading on this on the net and there are ALOT of people having this problem. Which leads me to beleive that its a huge yet unidentified problem that Microsoft is not yet aware of.

hrowder · #**140** 08-11-2005

Quote:

Originally Posted by DeviousOverdose

The only time i ever had this issue I was getting Virtual Memory Low warning before hand. The computers I work with require specific logins. Im just curious if there is anyone out there might be able to continue this line of though and maybe it will come up with a solution thats helps all. If there is a holygrail in this case.

What if the memory reference had to do with the virtual memory file on the disk and windows inability to distinguish the difference between and administrative user and an owner.

I've had this problem for quite some time on my work computer along with another problem with "sharing violation" errors.

Ok my thoughts: Everytime you exit out of a program Windows writes all of your latest information into the virtual memory file. If for some unknown reason windows decided that you should no longer have full access to this file, then when the OS tries to read from it, it would be denied. Seeing as the OS thinks this file is memory, not a disk file, you get a reference error rather than a sharing violation error.

The above explanation would account for the seeming random memory range and the fact that it happens to multiple applications.

Now what I haven't figured out is how to fix it.

Suffice it to say, it is not specific to WinXP because I'm on a Win2K system, both of which have documented sharing and access problems.

Hi Devious...

Strangely, I did get some virtual memory shortage errors a few days before this occured. I then opened up abbout 4 gig more on another drive for virtual memory. I have not had as many of these errors lately, so I'll see how it goes. I also updated my video drivers just in case the other day (ATI Catalyst) on the recommendation of yet another user. Hopefully we will be able to zero in on this type of error soon. Microsoft seems unconcerned... or at least wants to charge a lot of money to try to fix this.

Similar Topics
Topic	Replies	Forum
Referenced Memory error	12	Software Apps
Memory Referenced Error	1	Windows OS
Referenced Memory error	1	Windows OS
Referenced Memory Error	2	Windows OS
What is this error about referenced memory?	4	Windows OS

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search

TechSpot

Referenced Memory Error