54 replies to this topic

[Willmaniam]

Hi

recently (past 2 days) I have been getting different errors on my computer regarding explorer.exe.

The error will say something along the lines of:

Application error

explorer.exe (then some numbers these seem to change everytime along the lines of 0x0000000, 0x000000) memory could not be read

click ok to exit
click cancel to debug

I will write the next error down and post it up couldn't remember it exactly this time.

As far as I am aware the only thing that has changed on my system in the last 2 days is unistalling .NET framework 1.1 & 2.0 and then reinstalling them and then installing SQL server 2005.

when I get the error message (seems to happen at random times) everything seems to disappear for a couple of seconds and then reappear. I have all the latest updates and have a run a full system scan which found nothing.

Any ideas?

[morefood2001]

Try repairing windows. Goto start, run, type in cmd. In the terminal, type in

sfc /scannow

If that finds nothing, you may need to do a repair installation on windows (hit esc while installing windows to repair an existing install). Explorer errors are hard to fix from experience.

[Willmaniam]

Will this delete all my files and stuff like that?

[morefood2001]

both options will not delete your files. The sfc utility will replace corrupt windows system files such as explorer, so this is even more safer (if it works).

The reinstall windows using the repair option right before selecting a new installation location will reinstall windows and de-update it, but should leave most programs in tact.

[Willmaniam]

ok thank you I will let you know how it goes.

[Willmaniam]

Ok well I id the sfc /scannow and that scanned the comp but it didn't say at the end if it did anything or not. What does that mean lol?

[morefood2001]

Sfc will automatically fix a problem if one exists, therefore keep an eye out for explorer errors and hopefully they went away :)

[Willmaniam]

ah ok. well thanks for your help. I hope it goes away too.

[Willmaniam]

Ha just when I thought it had gone away I get an error this time telling me memory could not be written I guess this means I need to do a repair install now?

[Xav]

Not necessarily. This error can be, I believe, caused by faulty connections to the RAM modules, or just faulty RAM. Check that?

[Willmaniam]

So could be a hardware problem?

[Xav]

Potentially, yes, that's what I've heard from these sorts of problems, but don't, like, trust me or anything. :)

It could just be faulty contacts. Try unplugging and replugging the RAM in or something, it might fix it. I've seen this error occasionally on two of our laptops at home, but it seems to have stopped now, so I dunno.