Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works

Explore.exe - Application Error. The instruction at

  • Please log in to reply



    New Member

  • Member
  • Pip
  • 1 posts
Hi. Please help. Not sure exactly what is going on with my computer right now. I have a Dell and am running Windows Vista. Whenever I click on the start button, it never opens up, and instead, I get the following message:

Explorer.exe - Application Error (the heading)
The instruction at "0x3e204103" referenced memory at "0x3e204103" The required data was not placed into memory because of an I/O error status of "Oxc000009c"

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

I always click on OK, but have accidentally clicked on CANCEL like twice, and each time it takes about 2 minutes, and then I get an error message saying the Dr. Watson's debugger failed to open or something of that sort.

It is also worth noting that I get this same message if I try to open up Internet Explorer but not Mozilla or Google Chrome, and also that at the same time that this started happening, I started getting the Windows Explorer error message continuously where it says: "Windows Explorer has encountered a problem and needs to close. We are sorry for the inconvenience. Then says I could send Error Report or Don't Send.

No idea what happened to the computer. Any help would be greatly appreciated. Thank you, and have a nice day.
  • 0




    Member 1K

  • Member
  • PipPipPipPip
  • 1,293 posts
It could be any one of a number of things but simply removing then re-seating all the RAM modules very carefully may fix it, as it did for me a while back when I was getting exact same error.
  • 0

Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP