C++ Runtime Error in MSN Messanger

Recently (maybe 3-4 weeks ago), when I'm using MSN Messenger (no matter the version) after a period of time (not set) a pop-up box appears saying words to the effect of a C++ Runtime error for the application. Sometimes the box shows a button to 'debug', but usually has just an "OK" button. Click that and messenger quits. It happens on only one of the computers I normally use. I run Spybot, adaware, Zonealarm, windows firewall (paranoid, eh??). If anyone has any ideas why my messenger keeps doing this, I'd appreciate them. I don't recall making any change(s) that would make this happen.

 

sounds like you have Visual Studio or some other development/programming enviroment installed on that one machine.
Try c:\> DRWTSN32 -i
This will reregister the doctor as your default exception handling. The bad news is that you are getting some crashes you will need to investigate still, this way youll get some dumps to look at.

 

Thanks for your thoughts. I did re-register Dr Watson, but in answer to your statement about programming environment - No - unless someone snuck in and did it for me (highly doubtful), 'cause I ain't no programmer! by any stretch. And you know what, today I got the same error with Internet Exploder and it just up and crapped out. YIKES! Any other ideas??

 

MSN Messenger C++ Error and Quits

Well, apparently no one has a clue as to what the real problem might be. Guess I'll just stop using MSN Messenger, because Yahoo has no problems whatsoever.

 

If you can easily do without it, that is certainly a way to go.

But if you want to try to track down the cause, I imagine Joe was waiting on word of more crashes and then to take a look at a dump file from the good Doctor to see exactly what is going on.

 

We will all be talking about you behind your back on MSN.

Need some data in order to help you further. After you registered Drwatson, what happened? Did you get a crash, did it write a dump?

 

Messenger and Dr Watson

Joe, I apologize for the comment I made. I know everyone gets busy and don't always have time for 'immediate replies.' Color me stupid, too, cause I thought the good Dr would run in the background with no action needed on my part, but I found out otherwise. As a matter of fact, Messenger 'shelled out' on me not too long before I opened the BBS , so have started DrW and will reopen messenger and see what happens and try to catch a data dump to post. Thanks for your patience.

 

if the doctor wont catch it, i have some alternative ideas if you are on nt/2000/xp on how to capture the exception.

 

MSN Messenger and Dr Watson

Joe,

Well, MSN Messenger just crapped out on me. It's been running about 6 hours now. Here's the error:
[top bar] Microsoft Visual C++ Runtime Library
[main box] Runtime Error!

Program: C:\Program Files\MSN Messenger\msnmsgr.exe

This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information.

[ok box] OK


I checked in with the Dr, and there were no faults detected. . Guess I need help from your other sources.

Thanks.

 

Ok, this aint gonna be pretty-

Donwload the debugging tools: http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx

open a dos prompt
Run messenger
type this at the c prompt

Code:

SET  _NT_SYMBOL_PATH=SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

use task manager to find the PID of the messenger (you may have to turn on the column)
cd "\program files\debugging tools for windows" (where you installed the tools)
at the prompt: adplus -crash -fullonfirstover -p THEPIDFROMTASKMGR

This will do all kinds of exciting things, but will eventually setup to monitor for exceptions. At some point, it will blow up with your usual error message. Youll want to run this tool: http://www.windowsbbs.com/showthread.php?t=33471

If you watch the dialogs, it will tell you where its going to put the dumps. C:\Debuggers\Crash_Mode__Date_08-02-2004__Time_18-25-07PM or something along those lines.

Post the results of running the tool against the first chance exception dump.

 

for those of you following along, the problem here is that the application in question is throwing an exception. The app has a 'first chance' to handle the exception itself (not all exceptions are bad). This app is handling something it really should be throwing to the OS DrWatson(second chance), but is not. Since we arent getting a dump, we have to use a debugger script called ADPLUS to monitor first chance exceptions and write out dumps when they occur.

 

C++ Runtime error in MSN Messenger

Joe,

Did what you said. I have 3 dump files:
1. 1st_chance_Process_Shut_Down_full_2004-08-0309-06-10-953_0400.dmp
2. 2nd_chance_CPlusPlusEH_full_2004-08-03_09-06-05-234_0400.dmp
3. Date_08-03-2004_Time_08-56-17AM_1st_chance_CPlusPlusEH_full.dmp

I ran the DebugWiz on each one. Here's the text for #1:
"Opened log file 'c:\debuglog.txt'
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Program Files\Debugging Tools for Windows\Crash_Mode__Date_08-03-2004__Time_08-56-17AM\PID-1024__MSNMSGR.EXE__1st_chance_Process_Shut_Down__full_2004-08-03_09-06-10-9]
Could not open dump file [C:\Program Files\Debugging Tools for Windows\Crash_Mode__Date_08-03-2004__Time_08-56-17AM\PID-1024__MSNMSGR.EXE__1st_chance_Process_Shut_Down__full_2004-08-03_09-06-10-9], Win32 error 2
"The system cannot find the file specified." "

Not sure what that means, as the .dmp file is plainly there in the crash_mode subdirectory.

 

haha! you found a bug in my tool! i didnt allocate enough buffer space to handle a file name with such girth. I didn't consider that i'd have people running those crazy long adplus dump names through it.

Using this file, Date_08-03-2004_Time_08-56-17AM_1st_chance_CPlusPlusEH_full.dmp, move it up to a shorter directory name and rename the file to dump1.dmp or something and try again.

 

Here ya go!!

Opened log file 'c:\debuglog.txt'
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Program Files\Debugging Tools for Windows\dumps\dump1.dmp]
User Mini Dump File with Full Memory: Only application data is available

Comment: '1st_chance_CPlusPlusEH_exception_in_MSNMSGR.EXE_running_on_DEANHAYES'
Windows XP Version 2600 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: SingleUserTS
Debug session time: Tue Aug 03 09:05:53 2004
System Uptime: 1 days 1:05:54.913
Process Uptime: 0 days 0:14:49.000
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
...........................................................................................
(400.b20): C++ EH exception - code e06d7363 (!!! second chance !!!)
eax=0176fbac ebx=00000320 ecx=00000000 edx=015e2640 esi=0176fc3c edi=0176fc3c
eip=77e73887 esp=0176fba8 ebp=0176fbfc iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000206
kernel32!RaiseException+0x51:
77e73887 5e pop esi
0:003> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************

*** WARNING: Unable to verify checksum for
*** ERROR: Symbol file could not be found. Defaulted to export symbols for -

FAULTING_IP:
kernel32!RaiseException+51
77e73887 5e pop esi

EXCEPTION_RECORD: ffffffff -- (.exr ffffffffffffffff)
.exr ffffffffffffffff
ExceptionAddress: 77e73887 (kernel32!RaiseException+0x00000051)
ExceptionCode: e06d7363 (C++ EH exception)
ExceptionFlags: 00000001
NumberParameters: 3
Parameter[0]: 19930520
Parameter[1]: 0176fc5c
Parameter[2]: 014e7c10
!cppexr ffffffffffffffff
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: msvcrt!EHExceptionRecord ***
*** ***
*************************************************************************

BUGCHECK_STR: e06d7363

DEFAULT_BUCKET_ID: APPLICATION_FAULT

PROCESS_NAME: msnmsgr.exe

ERROR_CODE: (NTSTATUS) 0xe06d7363 - <Unable to get error code text>

THREAD_ATTRIBUTES:
LAST_CONTROL_TRANSFER: from 77c21a29 to 77e73887

STACK_TEXT:
0176fbfc 77c21a29 e06d7363 00000001 00000003 kernel32!RaiseException+0x51
0176fc3c 01442363 0176fc5c 014e7c10 015e2640 msvcrt!_CxxThrowException+0x34
WARNING: Stack unwind information not available. Following frames may be wrong.
0176fc80 0144267d 00000000 0176fcdc 00000000 imslsp!ims_set_block+0x12681
0176fc98 014502de 0176fcb8 01412aef 015e2648 imslsp!ims_set_block+0x1299b
0176fcf0 014754cc 015dea2c 00000001 0176fd30 imslsp!ims_set_block+0x205fc
0176fd44 01435fc9 015de9e0 00000001 000002d4 imslsp!ims_set_block+0x457ea
0176fd70 0148765a 015dbad8 00000001 015d86e0 imslsp!ims_set_block+0x62e7
0176fd88 014ac66b 0176fdc4 00000001 0000008a imslsp!ims_set_block+0x57978
0176ff0c 014ac79c 0176ffb4 014acbbf 01401850 imslsp!ims_set_block+0x7c989
0176ff14 014acbbf 01401850 015090b0 00000320 imslsp!ims_set_block+0x7caba
0176ffb4 77e7d33b 00000320 01401850 015090b0 imslsp!ims_set_block+0x7cedd
0176ffec 00000000 014ac79e 00000320 00000000 kernel32!BaseThreadStart+0x37


FOLLOWUP_IP:
msvcrt!_CxxThrowException+34
77c21a29 5f pop edi

SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: msvcrt!_CxxThrowException+34

MODULE_NAME: msvcrt

IMAGE_NAME: msvcrt.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 3d6dfa27

STACK_COMMAND: .ecxr ; kb

BUCKET_ID: e06d7363_msvcrt!_CxxThrowException+34

Followup: MachineOwner
---------

eax=0176fbac ebx=00000320 ecx=00000000 edx=015e2640 esi=0176fc3c edi=0176fc3c
eip=77e73887 esp=0176fba8 ebp=0176fbfc iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000206
kernel32!RaiseException+0x51:
77e73887 5e pop esi
ChildEBP RetAddr Args to Child
0176fbfc 77c21a29 e06d7363 00000001 00000003 kernel32!RaiseException+0x51 (FPO: [Non-Fpo])
0176fc3c 01442363 0176fc5c 014e7c10 015e2640 msvcrt!_CxxThrowException+0x34 (FPO: [Non-Fpo])
WARNING: Stack unwind information not available. Following frames may be wrong.
0176fc80 0144267d 00000000 0176fcdc 00000000 imslsp!ims_set_block+0x12681
0176fc98 014502de 0176fcb8 01412aef 015e2648 imslsp!ims_set_block+0x1299b
0176fcf0 014754cc 015dea2c 00000001 0176fd30 imslsp!ims_set_block+0x205fc
0176fd44 01435fc9 015de9e0 00000001 000002d4 imslsp!ims_set_block+0x457ea
0176fd70 0148765a 015dbad8 00000001 015d86e0 imslsp!ims_set_block+0x62e7
0176fd88 014ac66b 0176fdc4 00000001 0000008a imslsp!ims_set_block+0x57978
0176ff0c 014ac79c 0176ffb4 014acbbf 01401850 imslsp!ims_set_block+0x7c989
0176ff14 014acbbf 01401850 015090b0 00000320 imslsp!ims_set_block+0x7caba
0176ffb4 77e7d33b 00000320 01401850 015090b0 imslsp!ims_set_block+0x7cedd
0176ffec 00000000 014ac79e 00000320 00000000 kernel32!BaseThreadStart+0x37 (FPO: [Non-Fpo])
start end module name
00400000 008be000 msnmsgr msnmsgr.exe Fri May 28 17:22:15 2004 (40B7BB97)
00f50000 00f5b000 LGMSGHK LGMSGHK.DLL Thu Nov 21 15:51:50 2002 (3DDD5576)
00f80000 00fbc000 lockbox lockbox.dll Thu Oct 23 15:43:41 2003 (3F983D7D)
00fc0000 00fcb000 IMregexp IMregexp.dll Fri Oct 10 04:55:38 2003 (3F86821A)
01400000 0151b000 imslsp imslsp.dll Thu Oct 23 15:47:46 2003 (3F983E72)
01520000 015c9000 LIBEAY32_0_9_6g LIBEAY32_0.9.6g.dll Wed Aug 20 09:38:54 2003 (3F4387FE)
01aa0000 01b00000 dpnet dpnet.dll Sat Dec 07 01:08:35 2002 (3DF19E73)
01cb0000 01cb7000 itchhk itchhk.dll Sat Nov 23 13:57:13 2002 (3DDFDD99)
01cf0000 01cf7000 msdmo msdmo.dll Wed Dec 04 03:33:08 2002 (3DEDCBD4)
03090000 030a1000 SPGRMR SPGRMR.dll Thu Aug 29 03:11:51 2002 (3D6DD747)
030c0000 0311b000 SKCHUI SKCHUI.DLL Wed Feb 07 03:09:58 2001 (3A8110E6)
0ffa0000 0ffc1000 dssenh dssenh.dll Sat Apr 27 15:18:04 2002 (3CCB077C)
0ffd0000 0fff3000 rsaenh rsaenh.dll Mon Apr 29 17:35:28 2002 (3CCDCAB0)
10000000 10007000 LgWndHk LgWndHk.dll Thu Nov 21 15:51:51 2002 (3DDD5577)
11000000 1111b000 nzdd nzdd.dll Wed Sep 06 17:47:28 2000 (39B6C980)
1a400000 1a47a000 URLMON URLMON.DLL Wed Jan 21 18:20:36 2004 (400F1754)
35680000 35690000 devenum devenum.dll Sun Jun 01 19:38:45 2003 (3EDA9C95)
4b080000 4b08d000 agthook agthook.dll Mon Dec 22 19:23:53 2003 (3FE79929)
4b280000 4b294000 agtctrl agtctrl.dll Tue Dec 23 02:30:12 2003 (3FE7FD14)
4b480000 4b49c000 agtpchnt agtpchnt.dll Tue Dec 23 02:29:50 2003 (3FE7FCFE)
4b680000 4b687000 agtcmpnt agtcmpnt.dll Tue Dec 23 02:29:30 2003 (3FE7FCEA)
4b880000 4b888000 agtproc agtproc.dll Tue Dec 23 02:30:00 2003 (3FE7FD08)
4ba80000 4ba87000 agtthook agtthook.dll Tue Dec 23 02:30:03 2003 (3FE7FD0B)
55900000 55961000 msvcp60 msvcp60.dll Thu Aug 29 05:39:11 2002 (3D6DF9CF)
5ad70000 5ada4000 uxtheme uxtheme.dll Thu Aug 29 05:39:22 2002 (3D6DF9DA)
5c2c0000 5c2fc000 SPTIP SPTIP.dll Thu Aug 29 05:39:33 2002 (3D6DF9E5)
5e080000 5e0b8000 dplayx dplayx.dll Wed Apr 14 16:56:43 2004 (407DB39B)
60300000 60307000 idle idle.dll Thu Jun 10 15:47:29 2004 (40C8C8E1)
605d0000 605d8000 mslbui mslbui.dll Thu Aug 29 05:39:49 2002 (3D6DF9F5)
63000000 63096000 WININET WININET.DLL Fri Feb 06 20:05:03 2004 (402447CF)
63580000 63832000 MSHTML MSHTML.DLL Wed Jul 07 20:37:07 2004 (40ECA543)
69200000 69239000 msgslang msgslang.dll Fri May 28 17:17:10 2004 (40B7BA66)
6b700000 6b790000 jscript jscript.dll Mon Jan 13 16:57:53 2003 (3E234471)
70a70000 70ad4000 SHLWAPI SHLWAPI.DLL Wed Jul 07 20:48:37 2004 (40ECA7F5)
71700000 71849000 SHDOCVW SHDOCVW.DLL Wed Jan 21 18:15:45 2004 (400F1631)
71950000 71a34000 comctl32 comctl32.dll Fri Apr 16 19:56:03 2004 (408080A3)
71a50000 71a8b000 mswsock mswsock.dll Sat Aug 18 00:33:37 2001 (3B7DFE31)
71a90000 71a98000 wshtcpip wshtcpip.dll Sat Aug 18 00:33:39 2001 (3B7DFE33)
71aa0000 71aa8000 ws2help ws2help.dll Sat Aug 18 00:33:38 2001 (3B7DFE32)
71ab0000 71ac4000 ws2_32 ws2_32.dll Thu Jul 10 14:19:08 2003 (3F0DBC2C)
71ad0000 71ad8000 wsock32 wsock32.dll Sat Aug 18 00:33:37 2001 (3B7DFE31)
71c20000 71c6e000 netapi32 netapi32.dll Tue Jun 08 17:02:21 2004 (40C6376D)
722b0000 722b5000 sensapi sensapi.dll Thu Aug 29 05:40:07 2002 (3D6DFA07)
746c0000 746e7000 msls31 msls31.dll Sat Aug 18 00:33:22 2001 (3B7DFE22)
746f0000 74716000 MSIMTF MSIMTF.dll Thu Aug 29 05:40:16 2002 (3D6DFA10)
74720000 74764000 MSCTF MSCTF.dll Thu Aug 29 05:40:16 2002 (3D6DFA10)
74770000 747ff000 mlang mlang.dll Sat Aug 18 00:33:19 2001 (3B7DFE1F)
74c80000 74cac000 oleacc oleacc.dll Sat Aug 18 00:33:18 2001 (3B7DFE1E)
74e30000 74e9a000 riched20 riched20.dll Thu Aug 29 05:40:19 2002 (3D6DFA13)
75a70000 75b15000 userenv userenv.dll Thu Aug 29 05:40:26 2002 (3D6DFA1A)
75f40000 75f5f000 apphelp apphelp.dll Thu Aug 29 05:40:27 2002 (3D6DFA1B)
76170000 761f8000 shdoclc shdoclc.dll Sat Aug 18 00:33:10 2001 (3B7DFE16)
762a0000 762b0000 msasn1 msasn1.dll Mon Mar 29 19:48:36 2004 (4068D1F4)
762c0000 76348000 crypt32 crypt32.dll Mon Sep 23 17:10:25 2002 (3D8F9151)
76360000 7636f000 winsta winsta.dll Thu Aug 29 05:40:29 2002 (3D6DFA1D)
76380000 76385000 msimg32 msimg32.dll Thu Aug 29 05:40:29 2002 (3D6DFA1D)
76390000 763ac000 imm32 imm32.dll Thu Aug 29 05:40:29 2002 (3D6DFA1D)
763b0000 763f5000 comdlg32 comdlg32.dll Thu Aug 29 05:40:29 2002 (3D6DFA1D)
76400000 76601000 msi msi.dll Thu Aug 29 05:40:29 2002 (3D6DFA1D)
76670000 76757000 setupapi setupapi.dll Thu Aug 29 05:40:30 2002 (3D6DFA1E)
767f0000 76814000 schannel schannel.dll Mon Mar 29 19:48:36 2004 (4068D1F4)
76b40000 76b6c000 winmm winmm.dll Thu Aug 29 05:40:32 2002 (3D6DFA20)
76b70000 76bae000 es es.dll Fri Mar 05 20:16:11 2004 (4049346B)
76c00000 76c2d000 credui credui.dll Thu Aug 29 05:40:33 2002 (3D6DFA21)
76c30000 76c5b000 wintrust wintrust.dll Sat Aug 18 00:33:06 2001 (3B7DFE12)
76c90000 76cb2000 imagehlp imagehlp.dll Thu Aug 29 05:40:33 2002 (3D6DFA21)
76d60000 76d76000 iphlpapi iphlpapi.dll Thu Jul 10 14:19:06 2003 (3F0DBC2A)
76e80000 76e8d000 rtutils rtutils.dll Sat Aug 18 00:33:05 2001 (3B7DFE11)
76e90000 76ea1000 rasman rasman.dll Thu Aug 29 05:40:34 2002 (3D6DFA22)
76eb0000 76edb000 tapi32 tapi32.dll Thu Aug 29 05:40:34 2002 (3D6DFA22)
76ee0000 76f17000 rasapi32 rasapi32.dll Thu Aug 29 05:40:34 2002 (3D6DFA22)
76f20000 76f45000 dnsapi dnsapi.dll Thu Aug 29 05:40:34 2002 (3D6DFA22)
76f50000 76f58000 wtsapi32 wtsapi32.dll Thu Aug 29 05:40:34 2002 (3D6DFA22)
76f60000 76f8c000 wldap32 wldap32.dll Thu Aug 29 05:40:34 2002 (3D6DFA22)
76f90000 76fa0000 secur32 secur32.dll Thu Aug 29 05:40:34 2002 (3D6DFA22)
76fb0000 76fb7000 winrnr winrnr.dll Sat Aug 18 00:33:05 2001 (3B7DFE11)
76fc0000 76fc5000 rasadhlp rasadhlp.dll Sat Aug 18 00:33:05 2001 (3B7DFE11)
77050000 77115000 comres comres.dll Sat Aug 18 00:33:04 2001 (3B7DFE10)
77120000 771ab000 oleaut32 oleaut32.dll Thu Aug 29 05:40:34 2002 (3D6DFA22)
771b0000 772d4000 ole32 ole32.dll Fri Mar 05 20:16:11 2004 (4049346B)
773d0000 77bca000 shell32 shell32.dll Thu Jun 10 14:51:26 2004 (40C8BBBE)
77c00000 77c07000 version version.dll Sat Aug 18 00:33:03 2001 (3B7DFE0F)
77c10000 77c63000 msvcrt msvcrt.dll Thu Aug 29 05:40:39 2002 (3D6DFA27)
77d40000 77dcc000 user32 user32.dll Thu Sep 25 11:49:01 2003 (3F731C7D)
77dd0000 77e5d000 advapi32 advapi32.dll Thu Aug 29 05:40:40 2002 (3D6DFA28)
77e60000 77f46000 kernel32 kernel32.dll Thu Aug 29 05:40:40 2002 (3D6DFA28)
77f50000 77ff7000 ntdll ntdll.dll Thu May 01 18:56:10 2003 (3EB1B41A)
78000000 78087000 rpcrt4 rpcrt4.dll Fri Mar 05 20:16:11 2004 (4049346B)
7c340000 7c396000 msvcr71 msvcr71.dll Fri Feb 21 06:42:20 2003 (3E561EAC)
7c890000 7c911000 clbcatq clbcatq.dll Fri Mar 05 20:16:11 2004 (4049346B)
7e090000 7e0d1000 gdi32 gdi32.dll Mon Mar 29 19:48:36 2004 (4068D1F4)
Closing open log file c:\debuglog.txt

 

yuk. no prublic symbols for this one. No garbage in the stack. A nice generic software exception. Unfortunatly, there isnt much analysis that we can do out here in the field. The good news is that you should be able to take that same dump to microsoft and they will be able to crack that stack to figure out whats going wrong. Sorry i cant provide a targeted solution for you on this one.

 

OK, I certainly appreciate your efforts!! You guys do good work. BTW, would you happen to know a valid e-mail address for the MSN Messenger support team?