Live Messenger

Soldato
Joined
14 Dec 2005
Posts
12,488
Location
Bath
Is there a known bug in this or is mine just plain weird?
I've got the latest (non-beta) version and whenever I open it up (& @ boot) it logsin and then just hangs.
Yesterday I got it working after half an hour of fiddling, but its just soo annoying.

I'm running XP Pro x64, but I read the same version works on x32 & x64 fine.

Any ideas?
 
Addition: I've got the messenger 4.7 (the old one that comes standard with windows) working...
I've just reinstalled live messenger (the file I download is called 'Install_Messenger_nous' & reports to be 15,950kb) but the probelm still hapens.
After installation, it opened up, logged in, and now is reporting as "not responding". And the little logo in the corner shows as being signed-out.

Quick thought, it's not a dual core affinity probelm is it?
The reason I ask is that in Task Manager, Applications, It's listed twice (bot not responding)

EDIT2: It then woke up, told me something about connection lost, logged out etc. It then reconected and is froze again :eek:

And the annoying thing is that I presume the people I want to speak to, can see me as logged-in and think I'm just ignoring them :(
 
Last edited:
Are you also using Zone Alarm?

Zone Alarm stops messenger from working on my Pc, even though I've set it to allow it.
 
sam garland said:
Are you also using Zone Alarm?

Zone Alarm stops messenger from working on my Pc, even though I've set it to allow it.
Nope. The only firewalls in use are the standard windows one, and a hardware firewall in the ADSL router (Which I've never had any problems with, inc. P2P & gaming, and old messenger)
 
Just reinstalled . I'd uninstalled it throught Add/Remove Programs, removed the category HKEY_CURRENT_USER\Software\Microsoft\MSNMessenger , removed messenger related things from MSCONFIG & removed any leftovers in Application data (Me & All users).
Finally I emptyed Temp
Before all this I did all windows updates, & disabled Spybot S&D Active

Reinstalled it with the only option as include the quicklaunch & desktop icons.
Error Code: 81000395

It ran, then came up with the error:
Signing into Windows Live messenger failed because the service is temporarily unavailable. Please try again later.

Clicked retry, it logged me in, I could see people online, Welcome to Windows live messenger side-bar opened. But now the Windows Live Messenger window is blank, to Windows live messenger side-bar has paused, and after 45secs the icon in the tray changed to not-signed-in...

This link http://www.dotcomunderground.com/blogs/2006/09/19/windows-live-messenger-81-sign-in-error-81000395/ lists the error code for 8.1 and just says downgrade to older, but the Welcome to Windows live messenger side-bar is hung saying "Discover the new windows live messenger 8.0..."
 
Last edited:
No ideas? Yesteday after 2 hours of fiddling it worked, but guess what, today the problems back.

A clue as to what might be causing it: After logging in, it's fine for about 5secs then it crashes. So, what does Live Messenger do in the first ten seconds of running?
 
If I close the program whilst it's crashed I get the following error signature:
szAppName : msnmsgr.exe szAppVer : 8.0.812.0 szModName : hungapp
szModVer : 0.0.0.0 offset : 00000000

And
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\WERed46.dir00\msnmsgr.exe.mdmp
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\WERed46.dir00\appcompat.txt

It literally just finishes loading the icons on the left & then crashes.
 
Last edited:
Event logger shows the Application hang
Code:
Source: Application Hang, Category: (101), Event ID: 1002 
Hanging application msnmsgr.exe, version 8.0.812.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.
And thats down as 14:11:41

Then 3secs later the following is recorded
Code:
Source: Application Hang, Category: None, Event ID: 1001
Fault bucket 315410415.
And thats down as 14:11:44

Looking through all the logs, it seems that the second entry always happens upto 5secs after the first entry.

Today, I opened up messenger, left it for half an hour, fiddled a bit, and now it's working. (until I turn the computer off.)

Torrents, aswell as use of IE, do not effect it, the problem happens both with & without.
 
Back
Top Bottom