Windows Live Messenger has stopped working

Discussion in 'Windows Live Messenger' started by Phil, Jun 17, 2010.

  1. Phil

    Phil Guest

    This message pops up everytime I try to start messenger. after a few seconds
    another window pops up and states that Windows Live Messenger encountered a
    problem and I will be notified when a solution is found.

    I have uninstalled and reinstalled, I have run repair and still no luck

    My family is getting on my case about resolving this issue so Please Help Me.
    Phil, Jun 17, 2010
    1. Advertisements

  2. Don't hold your breath for that. You might get some clues about the crash
    from the Application Event log. In fact, I would try turning on the
    WLMessenger troubleshooting logging too; e.g. if there are error symptoms in
    there immediately before the crash it would probably be a good idea to try
    to deal with those first.


    Robert Aldwinckle
    Robert Aldwinckle, Jun 17, 2010
    1. Advertisements

  3. Phil

    Phil Guest

    Hi Robert,

    Checking my event viewer, I found nothing but the wdlcore.dll was the fault.

    I have removed everything to do with Windows Live including all the
    essentials. I even removed the essentials directory.

    I rebooted before reinstalling Essentials again and the same problem occurs.
    Phil, Jun 18, 2010
  4. Phil

    Phil Guest

    Phil, Jun 20, 2010

  5. Assuming you mean the wldcore.dll that is in the WL Mail directory, that
    would mean the crash is in one of WLMail's modules, so I would suspect that
    to be a victim rather than a culprit module. Unfortunately, by default you
    can't get any more diagnostics which would help give you clues about your
    crash. Apparently the MS approach is to go to the other extreme and expect
    the user to get a full dump and do an analysis of it. However, I think the
    next simplest and easiest step would be getting a Stack Back Trace of the
    crash event or at least a list of modules which were loaded at the same
    time. You could try using either ProcExp or ProcMon to get such a list and
    supposedly even a pseudo Stack Back Trace for either the crashed thread
    (from ProcExp) or for the crash event (from ProcMon). In either case I
    would be expecting to see the possibility of unnecessary third-party modules
    involved in the crash. For example, so called crash preventer or crash
    analysis programs are notorious for actually being crash causers.


    Robert Aldwinckle, Jun 20, 2010
  6. Phil

    ksaf Guest

    Remove the following entry from the registry:

    ksaf, Jun 22, 2010
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.