Windows Live Communications Platform has stopped working

Discussion in 'Windows Live Messenger' started by Bikkit, Jan 18, 2009.

  1. Bikkit

    luiz Guest

    hi i got the same problem tried everything and it didn t work.previous
    version of messenger worked just fine but it can t be used anymore.microsoft
    should solve the problems before obligating to use the new version.my crash
    idProblem signature
    Problem Event Name: APPCRASH
    Application Name: wlcomm.exe
    Application Version: 14.0.8098.930
    Application Timestamp: 4ac41a12
    Fault Module Name: ADVAPI32.dll
    Fault Module Version: 6.0.6002.18005
    Fault Module Timestamp: 49e03717
    Exception Code: c0000005
    Exception Offset: 00033bea
    OS Version: 6.0.6002.2.2.0.768.3
    Locale ID: 1033
    Additional Information 1: 8053
    Additional Information 2: 0a945b62bf6469ba48c1bcd048acbbc6
    Additional Information 3: f04f
    Additional Information 4: ecfb9aff96b377aba6a3616ab8ef1875

    Extra information about the problem
    Bucket ID: 1522589265
     
    luiz, Oct 25, 2009
    #41
    1. Advertisements

  2. This fix did not work for me... the tread should remain open
     
    Philly_nb2005, Oct 30, 2009
    #42
    1. Advertisements

  3. Bikkit

    JrFanGirl88 Guest

    I have done everything you did. I have USA Vista Home Preminum 64 Bit
     
    JrFanGirl88, Nov 1, 2009
    #43
  4. Bikkit

    Wonderjava Guest

    heres mine too, all of a sudden it doesnt work now.

    Problem signature:
    Problem Event Name: APPCRASH
    Application Name: wlcomm.exe
    Application Version: 14.0.8064.206
    Application Timestamp: 498cddf7
    Fault Module Name: 85410F35.x86.dll
    Fault Module Version: 0.0.0.0
    Fault Module Timestamp: 4ac9e74d
    Exception Code: c0000005
    Exception Offset: 00005874
    OS Version: 6.0.6002.2.2.0.768.3
    Locale ID: 1033
    Additional Information 1: e09c
    Additional Information 2: c51c8044d90d8dfc1100f685e590f320
    Additional Information 3: e806
    Additional Information 4: b56afe53145e6a66ff2d0db3b4d49b4d
     
    Wonderjava, Nov 2, 2009
    #44
  5. Bikkit

    Cyber Guest

    i updated new vista.. install uninstall bla bla....... all i do.. but can;t
    fix............ so who is SUCK ???? my laptop company or
    microsoft.............. i;m really disappointed.


    i hate it....
     
    Cyber, Nov 3, 2009
    #45
  6. Bikkit

    pealip123 Guest

    Log Name: Application
    Source: WindowsLiveMessenger
    Date: 02/11/2009 17:29:19
    Event ID: 7
    Task Category: None
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: tylerpeal-PC
    Description:
    The description for Event ID 7 from source WindowsLiveMessenger cannot be
    found. Either the component that raises this event is not installed on your
    local computer or the installation is corrupted. You can install or repair
    the component on the local computer.

    If the event originated on another computer, the display information had to
    be saved with the event.

    The following information was included with the event:

    WindowsLiveMessenger
    127.0.0.1
    127.0.0.1
    49189
    10061

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="WindowsLiveMessenger" />
    <EventID Qualifiers="49392">7</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2009-11-02T17:29:19.000Z" />
    <EventRecordID>15027</EventRecordID>
    <Channel>Application</Channel>
    <Computer>tylerpeal-PC</Computer>
    <Security />
    </System>
    <EventData>
    <Data>WindowsLiveMessenger</Data>
    <Data>127.0.0.1</Data>
    <Data>127.0.0.1</Data>
    <Data>49189</Data>
    <Data>10061</Data>
    </EventData>
    </Event>
     
    pealip123, Nov 8, 2009
    #46
  7. Bikkit

    Rania Guest

    I have the same problem, I got my crash ID, and now I don't know what to do.
    I'm all confused, is the problem from computer?? This is the crash ID:

    The description for Event ID ( 5000 ) in Source ( Windows Live Messenger )
    cannot be found.
    The local computer may not have the necessary registry information or
    message DLL files to display messages from a remote computer.
    You may be able to use the /AUXSOURCE= flag to retrieve this description;
    see Help and Support for details.
    The following information is part of the event: msnmsgrdiagnostic,
    msnmsgr.exe, 8.5.1302, login, 0, 80072745, NIL, NIL, NIL, NIL, NIL.

    Help!!!
     
    Rania, Nov 8, 2009
    #47
  8. Bikkit

    Stoli Guest

    Nick H please help... ive tried everything anyones posted on fixing this
    problem and nothing has helped. heres my error log info..... hopefully able
    to fix, thanks

    Problem signature
    Problem Event Name: APPCRASH
    Application Name: wlcomm.exe
    Application Version: 14.0.8098.930
    Application Timestamp: 4ac41a12
    Fault Module Name: StackHash_1dd5
    Fault Module Version: 6.0.6001.18000
    Fault Module Timestamp: 4791a7a6
    Exception Code: c0000374
    Exception Offset: 000b015d
    OS Version: 6.0.6001.2.1.0.768.3
    Locale ID: 1033
    Additional Information 1: 1dd5
    Additional Information 2: 583ee25c983f37ce763ef82c0f228976
    Additional Information 3: cf62
    Additional Information 4: fb3853697e809884c28759f380ae9aed

    Extra information about the problem
    Bucket ID: 1522772739
     
    Stoli, Nov 10, 2009
    #48
  9. Bikkit

    Stoli Guest

    FINALLY THANK YOU 2k7... I tried everything listed, and once located nVidia
    forceware access manager and uninstalled i finally got the messenger to work.
    Cool thanks again
     
    Stoli, Nov 10, 2009
    #49
  10. Bikkit

    pearl k Guest

    i am getting the same problem and i tried all the suggestions mentioned but
    nothing worked out i am so deperate now and i need ur help please
    here are the following info abt the error i get always :


    Faulting application wlcomm.exe,
    version 14.0.8098.930,
    faulting module kernel32.dll,
    version 5.1.2600.5781,
    fault address 0x000322af.


    AppName: wlcomm.exe AppVer: 14.0.8098.930 ModName: kernel32.dll
    ModVer: 5.1.2600.5781 Offset: 000322af
     
    pearl k, Nov 12, 2009
    #50
  11. Bikkit

    hossie Guest

    Hi same problem. This is my information.

    Problem signature
    Problem Event Name: APPCRASH
    Application Name: wlcomm.exe
    Application Version: 14.0.8064.206
    Application Timestamp: 498cddf7
    Fault Module Name: ADVAPI32.dll
    Fault Module Version: 6.0.6002.18005
    Fault Module Timestamp: 49e03717
    Exception Code: c0000005
    Exception Offset: 00033bea
    OS Version: 6.0.6002.2.2.0.768.3
    Locale ID: 4105
    Additional Information 1: 8053
    Additional Information 2: 0a945b62bf6469ba48c1bcd048acbbc6
    Additional Information 3: f04f
    Additional Information 4: ecfb9aff96b377aba6a3616ab8ef1875

    Extra information about the problem
    Bucket ID: 1254008455
     
    hossie, Nov 18, 2009
    #51
  12. Bikkit

    Cesca.x Guest

    Please help
    I am issuing problems with windows live mesenger 9 and use the home ultimate
    vista. Here's my Crash ID:
    Product
    Windows Live Messenger

    Problem
    Stopped responding and was closed

    Date
    25/10/2009 13:43

    Status
    Report Sent

    Description
    A problem caused this program to stop interacting with Windows.

    Problem signature
    Problem Event Name: AppHangB1
    Application Name: msnmsgr.exe
    Application Version: 14.0.8089.726
    Application Timestamp: 4a6ce533
    Hang Signature: 51ca
    Hang Type: 2048
    OS Version: 6.0.6002.2.2.0.256.1
    Locale ID: 2057
    Additional Hang Signature 1: 2e54ac6cd0fb75a4e2c755dade721fc2
    Additional Hang Signature 2: 97c4
    Additional Hang Signature 3: 5c3353313d54bb042727d1a629f8c1ef
    Additional Hang Signature 4: 51ca
    Additional Hang Signature 5: 2e54ac6cd0fb75a4e2c755dade721fc2
    Additional Hang Signature 6: 97c4
    Additional Hang Signature 7: 5c3353313d54bb042727d1a629f8c1ef

    Extra information about the problem
    Bucket ID: 701140611
     
    Cesca.x, Nov 26, 2009
    #52
  13. Bikkit

    sheila Guest

    Please help! I've tried re-installing and other stuff recommended but doesn't
    work!!!!

    Problem signature
    Problem Event Name: APPCRASH
    Application Name: wlcomm.exe
    Application Version: 14.0.8098.930
    Application Timestamp: 4ac41a12
    Fault Module Name: ESENT.dll
    Fault Module Version: 6.0.6001.18000
    Fault Module Timestamp: 4791a717
    Exception Code: c0000005
    Exception Offset: 0013c402
    OS Version: 6.0.6001.2.1.0.768.3
    Locale ID: 4105
    Additional Information 1: 73a5
    Additional Information 2: fef3ecf69fe874d496a1b3431f56b028
    Additional Information 3: 7dd1
    Additional Information 4: 437fcd2ca486837d07a03eb5533bbe57

    Extra information about the problem
    Bucket ID: 1523809947
     
    sheila, Dec 1, 2009
    #53
  14. Bikkit

    Markla709 Guest

    Same Problem


    Problem signature
    Problem Event Name: APPCRASH
    Application Name: wlcomm.exe
    Application Version: 14.0.8064.206
    Application Timestamp: 498cddf7
    Fault Module Name: RPAWINET.DLL
    Fault Module Version: 1.2.4.1
    Fault Module Timestamp: 45a53541
    Exception Code: c0000005
    Exception Offset: 00001496
    OS Version: 6.0.6002.2.2.0.256.6
    Locale ID: 1033
    Additional Information 1: fe86
    Additional Information 2: 347c86cedfab3f0e577c410b9ae62000
    Additional Information 3: 10b3
    Additional Information 4: 6396426a330f7d79153aa52e1a75d558

    Extra information about the problem
    Bucket ID: 1156522943
     
    Markla709, Dec 21, 2009
    #54
  15. Bikkit

    Rajeev Guest

    Problem signature
    Problem Event Name: BEX
    Application Name: msnmsgr.exe
    Application Version: 14.0.8089.726
    Application Timestamp: 4a6ce533
    Fault Module Name: unknown
    Fault Module Version: 0.0.0.0
    Fault Module Timestamp: 00000000
    Exception Offset: 69527f03
    Exception Code: c0000005
    Exception Data: 00000008
    OS Version: 6.0.6002.2.2.0.768.2
    Locale ID: 1033

    Extra information about the problem
    LCID: 1033
    Bucket ID: 693259636
    this is the stuffs what it shows after i followed what u said.
     
    Rajeev, Jan 4, 2010
    #55
  16. Bikkit

    Rajeev Guest

    Problem signature
    Problem Event Name: BEX
    Application Name: msnmsgr.exe
    Application Version: 14.0.8089.726
    Application Timestamp: 4a6ce533
    Fault Module Name: unknown
    Fault Module Version: 0.0.0.0
    Fault Module Timestamp: 00000000
    Exception Offset: 69527f03
    Exception Code: c0000005
    Exception Data: 00000008
    OS Version: 6.0.6002.2.2.0.768.2
    Locale ID: 1033

    Extra information about the problem
    LCID: 1033
    Bucket ID: 693259636
     
    Rajeev, Jan 4, 2010
    #56
  17. Bikkit

    donpistole Guest

    hey i also need your help.....here is my info.

    Problem signature
    Problem Event Name: APPCRASH
    Application Name: wlcomm.exe
    Application Version: 14.0.8098.930
    Application Timestamp: 4ac41a12
    Fault Module Name: ADVAPI32.dll
    Fault Module Version: 6.0.6001.18000
    Fault Module Timestamp: 4791a64b
    Exception Code: c0000005
    Exception Offset: 0002b68e
    OS Version: 6.0.6001.2.1.0.768.3
    Locale ID: 1033
    Additional Information 1: 8053
    Additional Information 2: 0a945b62bf6469ba48c1bcd048acbbc6
    Additional Information 3: 382d
    Additional Information 4: f3dbe13fe220264cbfaefeb75248fdf4

    Extra information about the problem
    Bucket ID: 1522601708
     
    donpistole, Jan 7, 2010
    #57
  18. Bikkit

    MR. NADIM Guest

    Well... thanks to someone called j0eStER i've finally got rid of this
    *bleep*** error...

    Everyone, you need to try by:

    * Closing MSN completely. Do not leave the MSN icon on the clock.
    * Delete the file: C: \ Program Files \ Windows Live \ Contacts \
    wldlog.dll
    * Open and connect MSN

    THIS IS WORKING HERE, HOPE IT WILL WORKS FOR YOU TOO.....


    See ya, and i hope this works for you... i know how frustrating this msn
    trouble can be
     
    MR. NADIM, Jan 8, 2010
    #58
  19. Bikkit

    MR. NADIM Guest

    Well... thanks to someone called j0eStER i've finally got rid of this
    *bleep*** error...

    Everyone, you need to try by:

    * Closing MSN completely. Do not leave the MSN icon on the clock.
    * Delete the file: C: \ Program Files \ Windows Live \ Contacts \
    wldlog.dll
    * Open and connect MSN
    THIS IS WORKING FOR ME .... TRY THIS
    if this works, you can thank that j0eStER dude...

    See ya, and i hope this works for you... i know how frustrating this msn
    trouble can be
     
    MR. NADIM, Jan 8, 2010
    #59
  20. Bikkit

    JP Guest

    I have the same problem.. have you come up with any resolution to this?
     
    JP, Jan 17, 2010
    #60
    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.