Build 8.0.0812.00 now crashes multiple times daily

Hi guys,

Have been using the live messenger beta for some months now but since the
latest update its stability has gone downhill fast. About ten days ago I was
prompted to upgrade when I logged in, which I did. Soon after, I tried a new
userpic (gif when I usually use jpg) and within about 20 minutes the client
hung with 100% cpu usage and had to be exited by killing the process in task
manager. I presumed there had been an issue with the encoding of the gif, so
switched back to an older user pic. However, the problems continued.

I have been prompted one time since to upgrade again, which I did, but the
problem still continues ... possible even more frequently now. I have not
spotted any correlation between activities and the crashes. They occur now
several times a day. Please let me know if there is anything you would like
me to run alongside msn or anything I can do to pull off debugging
information while the CPU is spinning.

Cheers,


Victoria

running WLM version 812 with many betas installed in my system
so far there's no major problems

"Victoria Wilson" <Victoria > wrote in message
news:79E5848D-1DFF-4F1F-8F06-...
> Hi guys,
>
> Have been using the live messenger beta for some months now but since the
> latest update its stability has gone downhill fast. About ten days ago I was
> prompted to upgrade when I logged in, which I did. Soon after, I tried a new
> userpic (gif when I usually use jpg) and within about 20 minutes the client
> hung with 100% cpu usage and had to be exited by killing the process in task
> manager. I presumed there had been an issue with the encoding of the gif, so
> switched back to an older user pic. However, the problems continued.
>
> I have been prompted one time since to upgrade again, which I did, but the
> problem still continues ... possible even more frequently now. I have not
> spotted any correlation between activities and the crashes. They occur now
> several times a day. Please let me know if there is anything you would like
> me to run alongside msn or anything I can do to pull off debugging
> information while the CPU is spinning.
>
> Cheers,
>
>
> Victoria

I haven't seen this one before, so I can only offer educated guesses:

-You might have some bad data WLM's trying to read. Try clearing your object
store. That is, C:\Documents and Settings\<username>\Local
Settings\Application Data\Microsoft\Messenger\ (that's the object store) and
C:\Documents and Settings\<username>\Application Data\Microsoft\MSN
Messenger\ (this is the contact cache)

Note that if you clear them, you will lose any custom display pictures
including ones you paid for, any custom backgrounds, etc.

--
Edward Chow [1067064]
Windows Live Butterfly - Messenger

<DIV>&quot;Victoria Wilson&quot; &lt;Victoria
&gt; wrote in message
news:79E5848D-1DFF-4F1F-8F06-...</DIV>> Hi guys,
>
> Have been using the live messenger beta for some months now but since the
> latest update its stability has gone downhill fast. About ten days ago I
> was
> prompted to upgrade when I logged in, which I did. Soon after, I tried a
> new
> userpic (gif when I usually use jpg) and within about 20 minutes the
> client
> hung with 100% cpu usage and had to be exited by killing the process in
> task
> manager. I presumed there had been an issue with the encoding of the gif,
> so
> switched back to an older user pic. However, the problems continued.
>
> I have been prompted one time since to upgrade again, which I did, but the
> problem still continues ... possible even more frequently now. I have not
> spotted any correlation between activities and the crashes. They occur now
> several times a day. Please let me know if there is anything you would
> like
> me to run alongside msn or anything I can do to pull off debugging
> information while the CPU is spinning.
>
> Cheers,
>
>
> Victoria

"Edward Chow [Windows Live Butterfly- Mes" wrote:

> I haven't seen this one before, so I can only offer educated guesses:

Hi Edward,

Thank you for your message. I have tried quitting messenger, deleting the
files in both these directories, and then restarting messenger. This did not
fix the problem (I have just come back from lunch and it had hung again).

Am running Win XP Pro version 2002 SP2 if this helps at all. Have the same
issue whether connected via a normal wifi router or on the company network,
so it cannot be the network configuration here that is effected it.

Cheers,


Victoria

Besides anti-virus or malware scanners/monitors or anything else that hooks
the Windows kernel, I'm running out of ideas. There's not much I can do
without actually seeing your computer.

--
Edward Chow [1067064]
Windows Live Butterfly - Messenger

<DIV>&quot;Victoria Wilson&quot;
&lt;&gt ; wrote in message
news:7160A551-1706-45CD-B552-...</DIV>>
>
> "Edward Chow [Windows Live Butterfly- Mes" wrote:
>
>> I haven't seen this one before, so I can only offer educated guesses:
>
> Hi Edward,
>
> Thank you for your message. I have tried quitting messenger, deleting the
> files in both these directories, and then restarting messenger. This did
> not
> fix the problem (I have just come back from lunch and it had hung again).
>
> Am running Win XP Pro version 2002 SP2 if this helps at all. Have the same
> issue whether connected via a normal wifi router or on the company
> network,
> so it cannot be the network configuration here that is effected it.
>
> Cheers,
>
>
> Victoria

"Edward Chow [Windows Live B'fly-M'sgr]" wrote:

> Besides anti-virus or malware scanners/monitors or anything else that hooks
> the Windows kernel, I'm running out of ideas. There's not much I can do
> without actually seeing your computer.
>

Is there no way I can run any diagnostics to determine what is spinning the
CPU, like a stack trace? Or perhaps install a version that has been compiled
with debugging enabled?

I think this problem is something to do with opening the messenger window,
perhaps after a period of absence. It could be to do with loading a new
advert, as I understand this also happens when the window is re-maximised or
opened. The reason for this suspicion is that I use a laptop, and when the
CPU spins at 100% for a length of time the fan comes on. However, wlm had
hung this morning when I had left it logged in overnight, and the fan on the
laptop only came on once I had tried to reopen the window.

I appreciate issues with specific system setup, but I have been running with
live messenger betas for months now, at least six months, on the same system
without these issues. I am not aware of any other changes on the system
during this time, and the problem is also replicated on my home laptop which
has different applications surrounding wlm - this system has had even less
changes as I worked in germany for the last three months and didn't use it!
So no new software there!

This is a very real problem.


Victoria

i would suggest you try remote assistance

While sipping a glass of green tea, I read that Victoria Wilson wrote in
news:715F3B95-B9F3-4A15-9CF8-


>
> "Edward Chow [Windows Live B'fly-M'sgr]" wrote:
>
>> Besides anti-virus or malware scanners/monitors or anything else that hooks
>> the Windows kernel, I'm running out of ideas. There's not much I can do
>> without actually seeing your computer.
>>
>
> Is there no way I can run any diagnostics to determine what is spinning the
> CPU, like a stack trace? Or perhaps install a version that has been compiled
> with debugging enabled?
>
> I think this problem is something to do with opening the messenger window,
> perhaps after a period of absence. It could be to do with loading a new
> advert, as I understand this also happens when the window is re-maximised or
> opened. The reason for this suspicion is that I use a laptop, and when the
> CPU spins at 100% for a length of time the fan comes on. However, wlm had
> hung this morning when I had left it logged in overnight, and the fan on the
> laptop only came on once I had tried to reopen the window.
>
> I appreciate issues with specific system setup, but I have been running with
> live messenger betas for months now, at least six months, on the same system
> without these issues. I am not aware of any other changes on the system
> during this time, and the problem is also replicated on my home laptop which
> has different applications surrounding wlm - this system has had even less
> changes as I worked in germany for the last three months and didn't use it!
> So no new software there!
>
> This is a very real problem.
>
>
> Victoria

"D@annyBoy" wrote:

> i would suggest you try remote assistance
>

How do I do that?


Victoria

get someone who is running MSN (without removing Windows Messenger) and needless
to say, a geek and then connect to he/she and allow he/she to take over your
system and trying to diagnose the problem and provide a solution

While sipping a glass of green tea, I read that Victoria Wilson wrote in
news:88FAEA0C-AB50-4024-8B4B-


>
>
> "D@annyBoy" wrote:
>
>> i would suggest you try remote assistance
>>
>
> How do I do that?
>
>
> Victoria