explorer.exe ref error
|
Original Message
|
Name: kris
Date: January 27, 2002 at 19:30:18 Pacific
Subject: explorer.exe ref error |
Comment: every other time I hit any icon, I get explore.exe application error.insturction at "0x0166139e"reference memory cannot be read.upgrade didn't help
Report Offensive Message For Removal
|
|
Response Number 1
|
Name: Maurice Reed
Date: January 28, 2002 at 01:24:39 Pacific
Subject: explorer.exe ref error |
Reply: (edit)Are you running NT4 or Windows2000? What level of service pack has been applied? NT4 should be SP6, Win2k should be SP2.
 Report Offensive Follow Up For Removal
|
|
Response Number 2
|
Name: Mark Leonhartsberger
Date: May 7, 2002 at 09:58:09 Pacific
Subject: explorer.exe ref error
|
Reply: (edit)I get the same error with numerous applications. I have Win2k with SP2. I have done a clean install 3 times with no luck.
Report Offensive Follow Up For Removal
|
|
Response Number 3
|
Name: Marc Verbeke
Date: May 9, 2002 at 01:40:23 Pacific
Subject: explorer.exe ref error
|
Reply: (edit)Explorer.exe Application error.
The instruction at ..... referenced memory at ... (memory location varies since it seems to be random). The memory could not be read.
Explore tried to read memory that is no longer allocated to the program explorer.exe.
I got his problem on a W2K SP2 + windows update fixes. (I execute windows update each
week.
The problem started after applying one of those many security fixes Microsoft is providing.(probably the one from FEB 2002)
It never happens when I am "using" the PC.
When I leave the PC for a while I got this message, even with a screen saver active.
It is always recovering. No applications or folders are lost. But this shouldn't happen.
I have no idea of the why yet.
So, a reinstall and apply SP2 + windows update won't solve the problem, unless it is related to something that is running from the desktop (e.g. performance metering,...)
Your experiennce pls, including the fixes applied.
Report Offensive Follow Up For Removal
|
Use following form to reply to current message:
