Explorer.exe-Application Error

[TrigShorland]

When I try and run windows explorer I get the following error;
Explorer.exe-Application Error
The instruction at "0x100016cf" referenced memory at "0x00143010". The memory could not be "read"
Then gives me the option to terminate or debug. The error appears to occur randomly, or brings the error up every time its started for a while then starts every time with no problems. I seen the problem before but it normally sorts it's self out, any ideas???

 

[howrude]

Hello All,
To be clear the error that I am about to reply to is this
EventViewer records the system event with ID 26,
Explorer.exe - Application Error, Instuction at 0X????a730 refrenced memory "0.." and could not be written.

Also Check Thread616-175431

The error would show the error box, if you did not click the box you could do some work. In my case it appeared as soon as the desktop appeared. A diffrent profile could login.

I noticed I could not browse my documents, (Call this user1)
logining in as user 2 and browsing to the user1/my documents - crash exactly the same....
Its a file ERROR. One file in that directory is causing the problem.

Looking carefully just before the crash error the screen is showing the ICONS for the file associations.... when it hits the bad file... CRASH! You may see a file that has no icon for its file type.

using DOS prompt I proceded to move the file deaper down the tree.

Login as user1 presto Profile is happy.

The reason why some of the post works is file associations are recreated during an install of a product.

Copy the same file to another machine the same error.
If you place the bad file in MY documents that profile on start up will crash.

The person who stoped the MY documents from showing has still got the "BAD" file.

Also if you use "SEARCH" and cross the file. You will get the crash too. I am looking in to the file.

But the file was on I was working on late one day and saved as I was shutting down.

Other files of the same type work happily - I know from reading the POST this will help a lot of people.

Happy hunting.

Howrude

 

[mudskipper]

I have found just one reference to your exact error on a windows 2000 system. They began to have the issue after upgrading to IE 6. No fix listed though....

What service pack are you running on this win2k machine? Many people with similar "...could not be read..." errors were running service pack 1. After updating to 2 or 3, the issues went away.

If you are already running sp2 or 3, try to run windows explorer after ensuring that no other software is running. It is very possible that the issue is caused by something else running at the time.

Does your event viewer show any good info after this crash?

Please post back, as I am curious about the outcome on this issue!

BTW, here is the link on google if it helps

http://groups.google.com/groups?q=r...TF-8&selm=u0C9PR3JCHA.1008@tkmsftngp10&rnum=1

Mudskipper
___________________________________________________________________________________

Groucho said it best- "A four year-old child could understand this! Quick! Run out and find me a four year-old child: I can't make heads nor tails out of this!"

 

[Simpleman]

Suggest you go to W2K FAQ's index number 7 to review my solution to a very similar problem

First find the "Problem File"

Simpleman