Member Avatar for Josh Connerty

Hey,

Okay my mums laptop is a pile of junk and she has managed to break it even more then it already is.

She is a windows live messenger obsessive so she really can't live without it. After updating Java it has signed in then crashed. I have checked the event viewer and I get the following report:

- System 

  - Provider 

   [ Name]  Application Error 
 
  - EventID 1000 

   [ Qualifiers]  0 
 
   Level 2 
 
   Task 100 
 
   Keywords 0x80000000000000 
 
  - TimeCreated 

   [ SystemTime]  2009-09-06T18:59:12.000Z 
 
   EventRecordID 9482 
 
   Channel Application 
 
   Computer Diane-PC 
 
   Security 
 

- EventData 

   wlcomm.exe 
   14.0.8064.206 
   498cddf7 
   0A09AAD4.x86.dll 
   0.0.0.0 
   4a97f4f7 
   c0000005 
   00005874 
   1d14 
   01ca2f241a61e291

Does this help anyone? She really can't do without it.

  • 3 Contributors
  • 3 Replies
  • 197 Views
  • 3 Weeks Discussion Span
  • Latest Post Latest Post by szeegers

Dani AI

Generated

A concise troubleshooting summary and practical triage steps to add context to the posts by , and .

The Event Viewer entry shown by points to wlcomm.exe crashing while a non-Microsoft module is implicated. Similar reports in this thread (see on third‑party screensavers and reporting a third‑party network component) indicate the fault is often caused by an interfering driver/service rather than Messenger itself. The following steps are ordered to isolate the cause with minimal risk.

  • Check the Application log in Event Viewer and note the “faulting module” filename and full path. Right‑click that file in Explorer and check Properties -> Details to identify the installing vendor.
  • Perform a clean boot (msconfig) to disable all non‑Microsoft services and all startup items, then reboot and test. Re-enable items in small groups to find the offender.
  • Test in Safe Mode with Networking to see whether the crash appears in a minimal environment.
  • If the faulting module belongs to a network access manager, firewall, AV suite, screensaver, or other third‑party utility, create a restore point and temporarily uninstall or disable that software; then retest.
  • If the issue persists, uninstall and reinstall Windows Live Essentials / Messenger. Also run sfc /scannow to check system files.

Run these commands if helpful:

msconfig
sfc /scannow

For deeper diagnosis, use Autoruns/Process Explorer/ProcMon (Sysinternals) to watch what loads when wlcomm.exe starts, or capture a user‑mode dump for analysis. When asking for additional help, include the exact Event Viewer text (not a paraphrase), the faulting module filename and full path, Windows edition + service pack, Messenger version, and a short list of installed security/network utilities. Always create a restore point before removing drivers or network components.

Recommended Answers

All 3 Replies

Member Avatar for szeegers

Anyone found a solution for this?
I have the same problem with my XP SP3

Member Avatar for demenace

Anyone found a solution for this?
I have the same problem with my XP SP3

I have seen some references to some screen savers causing this issue. You may want to try removing any screen savers, especially third party types; and see if that helps.

Member Avatar for szeegers

I have seen some references to some screen savers causing this issue. You may want to try removing any screen savers, especially third party types; and see if that helps.

Hi, I have removed NVIDIA ForceWare Network Access manager.
This caused the problem at my computer!
So it's solved for me!

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.