Results 1 to 4 of 4

Thread: sysfader:iexplorer - application error

  1. #1
    Solarz Guest

    sysfader:iexplorer - application error

    Hello,
    i am experiencing problems when accessing a website through a VPN. It gives
    me the error message below:

    sysfader:iexplorer.exe - application error
    The instruction at "0x7c350440" referenced memory at "0x00000000". The
    memorey could not be "read"
    Click ok to terminate
    Click cancel to debug

    It just shuts internet explorer down immediately. I am running windows xp
    pro and using IE7. Any and all help woul dbe appreciated. Thank you!

  2. #2
    MowGreen [MVP] Guest

    Re: sysfader:iexplorer - application error

    http://www.liutilities.com/products/...rary/sysfader/

    sysfader is part of Nvidia's Graphics Utility. Perhaps there is an
    updated file that Nvidia offers that would mitigate this issue ?
    Perhaps it's only an issue with IE7 and the above Graphics Utility ?
    Suggest you check Nvidia for a solution.


    MowGreen [MVP 2003-2007]
    ===============
    *-343-* FDNY
    Never Forgotten
    ===============


    Solarz wrote:

    > Hello,
    > i am experiencing problems when accessing a website through a VPN. It gives
    > me the error message below:
    >
    > sysfader:iexplorer.exe - application error
    > The instruction at "0x7c350440" referenced memory at "0x00000000". The
    > memorey could not be "read"
    > Click ok to terminate
    > Click cancel to debug
    >
    > It just shuts internet explorer down immediately. I am running windows xp
    > pro and using IE7. Any and all help woul dbe appreciated. Thank you!


  3. #3
    Robert Aldwinckle Guest

    Re: sysfader:iexplorer - application error

    "Solarz" <Solarz@discussions.microsoft.com> wrote in message
    news:9001EB15-CC43-432D-90B3-E7F467DF7C7D@microsoft.com...
    > Hello,
    > i am experiencing problems when accessing a website through a VPN. It gives
    > me the error message below:
    >
    > sysfader:iexplorer.exe - application error
    > The instruction at "0x7c350440" referenced memory at "0x00000000". The
    > memorey could not be "read"
    > Click ok to terminate
    > Click cancel to debug



    Usually when this (sysfader) is reported the user has disabled drwtsn32.
    and this then seems to be some kind of minimal error handler without drwtsn32.

    See if you can change your symptom by making sure that drwtsn32
    is the default debugger. E.g. Run... (press Win-R) and enter:

    drwtsn32.exe -i


    FWIW if that was a crash on my system it would be somewhere in msvcr71.dll.
    I would suspect interference from third-party programs.

    Try running in IE7's No Add-ons mode to test this idea or selectively
    disable add-ons using the Manage Add-ons tool. Etc.


    >
    > It just shuts internet explorer down immediately.



    That's default handling of most crashes.


    > I am running windows xp
    > pro and using IE7. Any and all help woul dbe appreciated. Thank you!



    BTW this has nothing to do with WU. You may get better assistance from
    a newsgroup which specializes in your OS.


    Good luck

    Robert Aldwinckle
    ---



  4. #4
    Tim Guest

    Re: sysfader:iexplorer - application error

    I am having the same problems -
    Just started after the most recent HUGE security update from WinUpdate!
    or maybe it started with IE-7 but has been less obvious.
    I was trying to blame it on zonealarm -- but I have disabled ZA and not
    fixed the problem.
    It seems to happen most on sites that use flash.

    Tim McKnight

    "Robert Aldwinckle" wrote:

    > "Solarz" <Solarz@discussions.microsoft.com> wrote in message
    > news:9001EB15-CC43-432D-90B3-E7F467DF7C7D@microsoft.com...
    > > Hello,
    > > i am experiencing problems when accessing a website through a VPN. It gives
    > > me the error message below:
    > >
    > > sysfader:iexplorer.exe - application error
    > > The instruction at "0x7c350440" referenced memory at "0x00000000". The
    > > memorey could not be "read"
    > > Click ok to terminate
    > > Click cancel to debug

    >
    >
    > Usually when this (sysfader) is reported the user has disabled drwtsn32.
    > and this then seems to be some kind of minimal error handler without drwtsn32.
    >
    > See if you can change your symptom by making sure that drwtsn32
    > is the default debugger. E.g. Run... (press Win-R) and enter:
    >
    > drwtsn32.exe -i
    >
    >
    > FWIW if that was a crash on my system it would be somewhere in msvcr71.dll.
    > I would suspect interference from third-party programs.
    >
    > Try running in IE7's No Add-ons mode to test this idea or selectively
    > disable add-ons using the Manage Add-ons tool. Etc.
    >
    >
    > >
    > > It just shuts internet explorer down immediately.

    >
    >
    > That's default handling of most crashes.
    >
    >
    > > I am running windows xp
    > > pro and using IE7. Any and all help woul dbe appreciated. Thank you!

    >
    >
    > BTW this has nothing to do with WU. You may get better assistance from
    > a newsgroup which specializes in your OS.
    >
    >
    > Good luck
    >
    > Robert Aldwinckle
    > ---
    >
    >
    >


Similar Threads

  1. Replies: 3
    Last Post: 10-02-2011, 03:27 PM
  2. sysfader: iexplore.exe - application error
    By clayjr22 in forum Operating Systems
    Replies: 5
    Last Post: 13-07-2010, 04:26 PM
  3. sysfader iexplore application error
    By philtor in forum Windows XP Support
    Replies: 2
    Last Post: 26-09-2009, 10:50 PM
  4. SysFader: iexplore.exe Application Error
    By Kajj in forum Windows XP Support
    Replies: 8
    Last Post: 18-09-2009, 12:07 PM
  5. IExplorer Application Error Event ID: 1000
    By Iraiyavan in forum Windows XP Support
    Replies: 1
    Last Post: 16-11-2004, 05:28 AM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,711,671,808.01452 seconds with 17 queries