Vista - Windows Live Communications Platform has stopped working

Hi all,

I recently installed a couple new screen savers. They work exactly like they're supposed to but once I return to to my computer a warning appears saying "Windows Live Communication Platform has stopped working" and windows live messenger gets signed out. This is the "problem details" provided:

Problem signature:
Problem Event Name: BEX
Application Name: wlcomm.exe
Application Version: 14.0.8064.206
Application Timestamp: 498cddf7
Fault Module Name: saver1.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 42bb64e4
Exception Offset: 00013001
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 4105
Additional Information 1: 895c
Additional Information 2: cadfe13d9ae38195296ef71e43ac2414
Additional Information 3: f898
Additional Information 4: 65a67ba481b8f73de484359dc33e8238

Read our privacy statement:
Microsoft Online Crash Analysis

Any ideas on why these screen savers are affecting messenger like this?

Code presumably from the screen saver (saver1.dll) has been injected into the wlcomm process. There appears to be a problem in saver1.dll and that in turn makes the entire process crash.

I'd suggest either finding an updated version of the screen saver software, and in particular the saver1.dll module, or removing it. It's almost certainly a bug in the current version of saver1.dll.

I actually have the same issue. But its with almost any screen saver that wasn't already on my computer.

As soon as I move the mouse or whatever, same thing happens to me.

I've been looking everywhere to fix this issue. It was a really great screen saver.

I'm having the same problem but the fault module is ntdll.dll which is described as the NT Layer DLL.

The problem began when I upgraded MSN Live Messenger from V8 to V9, as a result of nagging messages to do so.

I have tried removing and reinstalling Live Messenger.

My PC is running AVG Internet Security V8.5.420 (paid-for version rather than free version).

The event viewer trace is

Faulting application wlcomm.exe, version 14.0.8064.206, time stamp 0x498cddf7, faulting module ntdll.dll, version 6.0.6001.18000, time stamp 0x4791a7a6, exception code 0xc0000374, fault offset 0x000b015d, process id 0x3168, application start time 0x01ca46bfd7f1bbfa.

Any suggestions?