Member Avatar for blrouley

I've read many posts about "referenced memory at 0x00000014", but none of them address the problem I am having with IE7. On the first launch of the program, I get no error message. Subsequent attempts yield the error message in the title of this post.

I've run registry cleaner utilities and repaired all found errors. I am now most of the way through reinstalling IE7 after removing it from Windows. I will post again if I've solved the problem, but would like to hear from resident experts who've encountered the same problem.

Thank you.

BR

  • 2 Contributors
  • 2 Replies
  • 120 Views
  • 1 Month Discussion Span
  • Latest Post Latest Post by flogabbin

Dani AI

Generated

This type of "referenced memory" crash in Internet Explorer usually points to a third‑party component (browser helper object, toolbar, shell extension) or a driver/hardware interaction that only shows up after the process loads extra DLLs. Corrupt user profile data or system file/DLL mismatches can also produce the same symptom. The fastest way to narrow it down is to capture what exactly is failing (module name, exception code and offset) and then isolate whether it is a browser add‑on, a user profile, or system-level code.

Practical first checks (do these in order):

  • Open Event Viewer (eventvwr.msc) -> Windows Logs -> Application and copy the "Faulting module" / "Exception code" / "Fault offset" lines from the IE crash entry. Those values point to the offending DLL.
  • Start IE with add‑ons disabled (iexplore.exe -extoff). If stable, focus on BHOs/toolbars.
  • Test in a new Windows user account and in Safe Mode with Networking to rule out profile or shell-extension problems.

If the cause is still unclear:

  • Use Autoruns or ShellExView to disable non‑Microsoft BHOs, toolbars and shell extensions and re-test, re‑enabling one at a time until the crash reappears.
  • Turn off GPU hardware acceleration in IE's Advanced settings to check for video driver interaction.
  • Run sfc /scannow and a memory test (Windows Memory Diagnostic or memtest86) to exclude system file or RAM issues.
  • Capture a crash dump (DebugDiag or ProcDump with exception and full memory options) and analyze with WinDbg (!analyze -v) to get a reliable call stack and module list.

If a non‑Microsoft module shows up in the faulting module or call stack, updating or removing that component usually fixes the crash. Post the exact Event Viewer lines (faulting module, exception code, offset) and any dump-analysis output for targeted suggestions. This will let others here reproduce and diagnose the precise cause rather than guessing.

Recommended Answers

All 2 Replies

Member Avatar for flogabbin

I need help with this problem where should I post?
I keep getting popups saying different versions of referenced e memory could not be written / read
I found some confusing references to it from 2006. Is there anything more recent? Can anyone help me?
thanx
Flo


201-6454221

Member Avatar for flogabbin

I've read many posts about "referenced memory at 0x00000014", but none of them address the problem I am having with IE7. On the first launch of the program, I get no error message. Subsequent attempts yield the error message in the title of this post.

I've run registry cleaner utilities and repaired all found errors. I am now most of the way through reinstalling IE7 after removing it from Windows. I will post again if I've solved the problem, but would like to hear from resident experts who've encountered the same problem.

Thank you.

BR

How did u solve the problem?
flo

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.