Member Avatar for jackknob

I have a user who is receiving the following message on a laptop running windows XP, sp1, and IE 6.0.

Unhandled exception in IEXPLORER.EXE (SHDOCVW.DLL): 0xC0000005: Access Violation


The message occurs every time the user attempts to close internet explorer. It doesn't seem to affect IE in any other way except when it is closed. He has to ctl+alt+del and end task from task manager to close it completely. It has not happened while he was using IE or when he is running other apps.

  • 2 Contributors
  • 1 Reply
  • 381 Views
  • 4 Months Discussion Span
  • Latest Post Latest Post by davidredwine

Dani AI

Generated

A few focused steps that narrow the root cause quickly (covers gaps in the replies from and ):

This crash on close (SHDOCVW.DLL / 0xC0000005) is often caused by a third‑party browser extension, BHO/toolbar, ActiveX or an Explorer/IE shell extension rather than the IE process itself. Start with low-risk diagnostics so you can identify the offending module instead of reinstalling components blindly.

Run Internet Explorer without add‑ons to test whether an extension is responsible. From Run (or a Command Prompt) launch:

iexplore.exe -extoff

If IE closes cleanly with add‑ons disabled, re-enable add‑ons in small groups or one‑by‑one (Tools → Manage Add‑ons) until the crash returns; that reveals the culprit. See Microsoft’s IE add‑on troubleshooting for the exact workflow. (learn.microsoft.com)

If the no‑add‑ons test points to an extension, use Autoruns (Sysinternals) to list and disable BHOs, toolbars, AppInit DLLs and other IE/Explorer hooks. Export/save the Autoruns output before changing anything. Uncheck non‑Microsoft entries to test, reboot, and retest IE. (learn.microsoft.com)

Collect diagnostic evidence if the problem is intermittent or the offender isn’t obvious: check the Application log in Event Viewer for the faulting module name and exception details, and enable Dr Watson / user crash dumps so you get a .log/.dmp you can read or hand to support. Typical commands:

drwtsn32 -i
drwtsn32

Use the Event Viewer + dump to match the faulting DLL to the product shown in Autoruns (or Programs & Features) and then uninstall, update, or unregister the DLL (regsvr32 /u <dll>) only after making a restore point. ()

If add‑ons and BHOs aren’t the cause, perform a clean boot (msconfig) to rule out non‑Microsoft services, then try resetting IE or applying available service packs/IE fixes. Because this machine is XP SP1, plan an OS/browser upgrade: Windows XP is out of support and carries long‑term risk—upgrading to an updated OS/browser is the safest resolution. Make backups and a restore point before registry or DLL changes. (support.microsoft.com)

Quick checklist (in order)

  • Run iexplore.exe -extoff.
  • If fixed: binary search re‑enable add‑ons (Manage Add‑ons).
  • If not fixed: enable Dr Watson / capture crash dump; check Event Viewer.
  • Run Autoruns, hide Microsoft entries, disable suspicious BHOs/toolbars, reboot and retest.
  • Use Clean Boot to isolate services; reset IE or repair system files as last steps.

Notes and cautions: do not delete or unregister DLLs until you identify their publisher; avoid disabling Microsoft‑signed entries unless you know what they are; always create a restore point and backup user data before making registry or system changes.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.