An Unhandled win32 exception occured

System Win2k Sp4
Memmory 512 MB

When I try to start yahoo messenger I get "An Unhandled win32 exception occured in YahooMessenger.exe [368]" In The debugger I get "First-chance exception at 0x001366d0 in YahooMessenger.exe: 0xC0000005: Access violation writing location 0x00cc0004."    This problem seems to be spreading to other programs that I opperate like vmware and download accelerator plus.  I have uninstalled and reinstalled this multiple times with no success
elaps01Asked:
Who is Participating?
 
kodiakbearConnect With a Mentor Commented:
Closed, 500 points refunded.
kb
Experts Exchange Moderator
0
 
AnthonyP9618Commented:
You may need to check your physical memory for problems.

http://www.memtest86.com/
0
 
elaps01Author Commented:
Just checked the ram.  I even took it out and put it back in to makes sure that it was not loose.  Still nothing has changed
0
Introducing Cloud Class® training courses

Tech changes fast. You can learn faster. That’s why we’re bringing professional training courses to Experts Exchange. With a subscription, you can access all the Cloud Class® courses to expand your education, prep for certifications, and get top-notch instructions.

 
jkrCommented:
Since you can debug it - any chance that the access violation always occurs in the same DLL, also for different programs?
0
 
elaps01Author Commented:
The only thing I see in the debugger is the address "001366C0  add         byte ptr [eax],al"  and I can not see the acutal Dll file that is having the problem.  I think this is a file that is responsible for tcip or something.  I do not know.  But every program that goes out and checks for updates has this same proble.  Internet explorer works fine.
0
 
elaps01Author Commented:
The other thing that I have found is that every program is failing that is try to Write to location 00cc0004.  Is this a hard drive problem, ram problem, pagefile problem or is it a file that it is trying to access
0
 
jkrCommented:
To me it seems more like a faulty DLL that is mapped to every process, especially if the the address is always the same. You should be able to determine the name of the DLL using either DrWatson or running the application in the Profile mode of the DependencyWalker (www.dependencywalker.com)
0
 
elaps01Author Commented:
Ok,  I got the program and did profile,  however,  I don;t know what I am looking for
0
 
jkrCommented:
You are looking for the crash to happen, then you should find the faulty module in the output.
0
 
elaps01Author Commented:
Turned out to be a virus
0
 
jkrCommented:
That's what I was afraid of.
0
 
jkrCommented:
Sorry for having been away for a week. I would have objected.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.