Some bad Explorer.exe crashing.. not Blaster - Tilted Forum Project - TFP - Sexuality, Philosophy and Political Discussion

Realizm · 08-14-2003, 09:31 PM

Explorer.exe of late has been crashing quite often.. no idea why. This first error that I list is the most common one.. it's almost always this exact error.. instruction at 77f57ec4, and same referenced memory. Any ideas guys? This is bad stuff...

Application popup: Explorer.EXE - Application Error : The instruction at "0x77f57ec4" referenced memory at "0x00000067". The memory could not be "written".

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

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

First time this one has happened :

Application popup: Explorer.EXE - Application Error : The instruction at "0x021f35b6" referenced memory at "0x02820ca8". The memory could not be "read".

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

08-15-2003, 02:40 PM

I think you should run a check on your memory and see if it is defective. Maybe increasing your pagefile size will help too.

sipsake · 08-15-2003, 03:12 PM

What operating system are you running? What service pack?

Realizm · 08-15-2003, 06:29 PM

XP Professional. SP1.

I've had this computer a year now.. and the crashing hasn't been going on even a month..

charliex · 08-16-2003, 12:17 AM

it could be just about anything

bad memory
overheating
bad card, incorrectly seated
damaged software
bad software

Its impossible to help you without getting sheer luck in guessing whats causing it, if you do the "submit info to MS" does it give you any clues?

also if you get the full dump of the error, that'd help more (possibly not much though ) usually it shows you in the "what is contained in this message)

Also if you do have a debugger (usually vc or .net) let it go in and just see what the call trace is..

If its nearly always the same address, its quite unlikely to be overheating or memory problems, thats usually bad software..

Try a spyware / virus scan too. some stuff hooks in badly

HeAtHeN · 08-16-2003, 12:20 AM

Sounds like RAM to me.... but do the usual first:

Check for viruses
Check for spyware
Repair XP

08-14-2003, 09:31 PM	#1 (permalink)
Realizm Insane Join Date: Apr 2003 Location: A fuzzy cloud.	Some bad Explorer.exe crashing.. not Blaster Explorer.exe of late has been crashing quite often.. no idea why. This first error that I list is the most common one.. it's almost always this exact error.. instruction at 77f57ec4, and same referenced memory. Any ideas guys? This is bad stuff... Application popup: Explorer.EXE - Application Error : The instruction at "0x77f57ec4" referenced memory at "0x00000067". The memory could not be "written". Click on OK to terminate the program Click on CANCEL to debug the program For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. First time this one has happened : Application popup: Explorer.EXE - Application Error : The instruction at "0x021f35b6" referenced memory at "0x02820ca8". The memory could not be "read". Click on OK to terminate the program Click on CANCEL to debug the program

08-15-2003, 03:12 PM	#3 (permalink)
sipsake Psycho Join Date: Apr 2003 Location: Memphis	What operating system are you running? What service pack? __________________ When life hands you a lemon, say "Oh yeah, I like lemons. What else you got?" Henry Rollins

08-15-2003, 02:40 PM	#2 (permalink)
hello.jpg Guest	I think you should run a check on your memory and see if it is defective. Maybe increasing your pagefile size will help too.

08-15-2003, 06:29 PM	#4 (permalink)
Realizm Insane Join Date: Apr 2003 Location: A fuzzy cloud.	XP Professional. SP1. I've had this computer a year now.. and the crashing hasn't been going on even a month..

08-16-2003, 12:17 AM	#5 (permalink)
charliex Junkie Join Date: Apr 2003 Location: North Hollywood	it could be just about anything bad memory overheating bad card, incorrectly seated damaged software bad software Its impossible to help you without getting sheer luck in guessing whats causing it, if you do the "submit info to MS" does it give you any clues? also if you get the full dump of the error, that'd help more (possibly not much though ) usually it shows you in the "what is contained in this message) Also if you do have a debugger (usually vc or .net) let it go in and just see what the call trace is.. If its nearly always the same address, its quite unlikely to be overheating or memory problems, thats usually bad software.. Try a spyware / virus scan too. some stuff hooks in badly