none
Explorer.exe crashes with Memory could not be written

    Question

  •  Hello,

    This concerns a Windows Server 2003 Terminal Server installation on a HP Compaq DL 380 machine. 

    Explorer.exe crashes frequently (about 5 times a day) with the following error (translated from dutch):

    Explorer.EXE - Application error: The instruction on 0x00000000 referenced memory at 0x00000000.

    The memory could not be read.

    Or this one:

    Hungapp: iexplore.exe, versie: 7.0.6000.16705, vastgelopen module: unknown, versie: 0.0.0.0, vastgelopen op: 0x6448c66b.

    When the crash appears, the user desktop is blank for a few seconds (after a messagebox that says that explorer has crashed). The it returns to the state it was in, except for Internet explorer, which then has been terminated.

    I've done a few memory tests and found no problems. It seems to happen most often when users use Internet Explorer 7 but not al the time. It also appears when using the Windows Explorer. This problem is really bugging me (and the users). Maybe someone has a suggestion how to troubleshoot this? Help would be much appreciated.

    Stefan de Groot


    arfle barfle floop!
    Friday, December 05, 2008 9:23 AM

Answers

  • Hello,

         Please Perform a  clean boot and let us know how it behaves.


    Clean Boot

    ========

    1. Click Start, type "MSCONFIG" (without the quotations) in the Search Bar and Press "Enter" to start the System Configuration Utility.

     

    Note: Please click Continue if the "User Account Control" window pops up.

     

    2. Click the "Services" tab, check the "Hide All Microsoft Services" box and click "Disable All" (if it is not gray).

    3. Click the "Startup" tab, click "Disable All" and click "OK".

    4. Restart the computer and test the issue.

     

    Note: Clean Boot is a troubleshooting step. If some programs have been disabled, we can re-enable them later. If you see the System Configuration Utility, check the box of "Don't show this message" and then click "OK".

     

    Please test this issue in the Clean Boot environment. If the issue disappears, we can use a 50/50 approach to quickly narrow down which entry is causing the issue.



    Thanks and Hope it Helps  


     


    Syed Khairuddin
    Sunday, December 07, 2008 3:41 PM