ejfadrigo Posted April 13, 2008 Share Posted April 13, 2008 Good Day To All,Everytime I try to use Web (Java) based chat my Explorer crash....It say's "Internet Explore stopped responding" any idea how to fix this? Link to comment Share on other sites More sharing options...
cluberti Posted April 13, 2008 Share Posted April 13, 2008 If it's always when using java-based webchat, consider uninstalling the currently installed JRE from your system and upgrading to the latest version from http://java.sun.com... Link to comment Share on other sites More sharing options...
ejfadrigo Posted April 14, 2008 Author Share Posted April 14, 2008 I tried uninstall Java and restart.. then download the latest Java but same problem...please i need help... Link to comment Share on other sites More sharing options...
ejfadrigo Posted April 15, 2008 Author Share Posted April 15, 2008 Please anyone help me... Link to comment Share on other sites More sharing options...
cluberti Posted April 15, 2008 Share Posted April 15, 2008 Does it actually crash and go away? If so, generate a dump of an application crashing as per the instructions here. Link to comment Share on other sites More sharing options...
ejfadrigo Posted April 22, 2008 Author Share Posted April 22, 2008 thanks cluberti...where can i post the generated dump? Link to comment Share on other sites More sharing options...
cluberti Posted April 22, 2008 Share Posted April 22, 2008 If you .zip up the folder, how large is it? Link to comment Share on other sites More sharing options...
ejfadrigo Posted April 22, 2008 Author Share Posted April 22, 2008 its almost 13mb file...using winrar Link to comment Share on other sites More sharing options...
ejfadrigo Posted April 22, 2008 Author Share Posted April 22, 2008 done... file uploaded... thanks in advance Link to comment Share on other sites More sharing options...
cluberti Posted April 23, 2008 Share Posted April 23, 2008 Well, your dump capture didn't actually include a .dmp file, but the log file shows us this: # ChildEBP RetAddr Args to Child 00 104deae8 7c359aed e06d7363 00000001 00000003 kernel32!RaiseException+0x5801 104deb28 10022ab0 104deb68 100f522c 104ded80 MSVCR71!CxxThrowException+0x3402 104deb58 10037c4d 104ded80 100cfc04 0eaff438 winamptb!DllUnregisterServer+0x157a003 104deba4 100abd9d 0eaff400 04848cd8 04848cd8 winamptb!DllUnregisterServer+0x2a93d04 104debd4 100ab10a 104debec 04848ad0 04848cd8 winamptb!DllUnregisterServer+0x9ea8d05 104dede0 10097ab0 047f9428 00000000 047f9428 winamptb!DllUnregisterServer+0x9ddfa06 104dee14 1009d5f6 047f9428 06727154 00000000 winamptb!DllUnregisterServer+0x8a7a007 104dee4c 77520afa 000cae48 01070fd0 00000000 winamptb!DllUnregisterServer+0x902e608 104dee78 1009ec5b 104dee20 00000000 104def58 USER32!SendMessageW+0x4909 104deef8 100a0ee1 7750d80a 047f9428 104def58 winamptb!DllUnregisterServer+0x9194b0a 104def4c 100bf781 ffffffff 047f9eb8 100a1173 winamptb!DllUnregisterServer+0x93bd10b 104defe4 6c6f2400 0f2e5260 0001062a 0f2e5234 winamptb!DllUnregisterServer+0xb24710c 104df480 77520817 00000000 6c716ac1 0001061a IEFRAME!Ordinal218+0x190f0d 104df4dc 775139f7 0108b820 00000001 00000000 USER32!ReleaseDC+0x7a0e 104df5e0 77513cf7 77513b94 00000100 104df90c USER32!CharNextW+0xfe0f 104dfb74 7740e489 6c724117 0f507168 00000000 USER32!CharNextW+0x3fe10 104dfb78 6c724117 0f507168 00000000 00000000 ntdll!RtlInitializeExceptionChain+0x3611 104dfb7c 0f507168 00000000 00000000 00000000 IEFRAME!Ordinal224+0x10e2712 104dfb80 00000000 00000000 00000000 00000000 0xf507168It looks like we start the exception chain at frame 10, after we release a device context. I'd have to see an actual .dmp file to see (maybe) what is happening at f507168 to know more. It could still be the WinAmp toolbar, but it's hard to say here. Since this happens when using that web-based java app, I'd have to say it's possible that's it, but again, without an actual .dmp file I can only speculate. Link to comment Share on other sites More sharing options...
cluberti Posted April 24, 2008 Share Posted April 24, 2008 OK, got the new dump, and was able to open and analyze it. It's indeed a 2nd chance access violation (meaning the process will crash). Here's the analysis:// Thread showing the 2nd chance Access Violation, causing the crash:0:036> kbChildEBP RetAddr Args to Child 0fafef04 748a0a80 3a4f9e50 00000002 00000001 winmm!ValidateHandle+0x240fafef18 0e2021fd 3a4f9e50 0f8e0020 00000000 winmm!waveInClose+0x16WARNING: Stack unwind information not available. Following frames may be wrong.0fafef68 0e1f3854 ffffffff 00c2c770 00000000 c0!COM_ENTRY+0x4cac0fafefb0 0e1f9fee 00c2c770 0faff2e8 0e1f9fa6 c0+0x38540fafefec 6b6412df 0f8e0020 a4feffe5 0faff2e8 c0!DllUnregisterServer+0x6500faff070 6b63df66 00000001 00000000 0e220bc8 mfc42!CWnd::OnWndMsg+0x2730faff098 6b6ca5b3 00000001 00000000 0faff2e8 mfc42!CWnd::WindowProc+0x2e0faff0c0 6b63fa9d 00000001 00000000 0faff2e8 mfc42!COleControl::WindowProc+0x12f0faff128 6b63fbd1 00c2c770 00000000 00000001 mfc42!AfxCallWndProc+0xb50faff14c 0e21e0ea 00060334 00000001 00000000 mfc42!AfxWndProc+0x3e0faff178 7689f8d2 00060334 00000001 00000000 c0!COM_ENTRY+0x20b990faff1a4 76891912 0e21e0bc 00060334 00000001 user32!InternalCallWinProc+0x230faff21c 768a0817 00000000 0e21e0bc 00060334 user32!UserCallWinProcCheckWow+0xe00faff278 768939f7 00e5df78 00000001 00000000 user32!DispatchClientMessage+0xda0faff2a8 778f99ce 0faff2c0 00000078 0faff78c user32!__fnINLPCREATESTRUCT+0x8b0faff334 76893cf7 76893b94 80000004 0faff660 ntdll!KiUserCallbackDispatcher+0x2e0faff338 76893b94 80000004 0faff660 0faff388 user32!NtUserCreateWindowEx+0xc0faff5dc 76893cc3 80000004 0faff660 0faff674 user32!VerNtUserCreateWindowEx+0x1ac0faff688 7688fd91 80000004 6b62449c 0faff674 user32!_CreateWindowEx+0x1f90faff6c4 6b640d4a 00000004 6b62449c 6b70a690 user32!CreateWindowExA+0x330faff734 6b6cb27d 00000004 00000000 6b70a690 mfc42!CWnd::CreateEx+0xb80faff798 6b6cfb96 000402e8 00cee9c8 0faff7b8 mfc42!COleControl::CreateControlWindow+0x1d80faff7e0 6b6d11f9 00000000 00000000 a4fef789 mfc42!COleControl::OnActivateInPlace+0x2e60faff81c 6f0075b6 00c2c89c fffffffb 00000000 mfc42!COleControl::XOleObject::DoVerb+0x17d0faff894 6f00906a 00c2c89c 000402e8 00000000 mshtml!COleSite::InPlaceActivate+0xdd0faff938 6f00911c 00000003 00000000 0a634508 mshtml!COleSite::TransitionTo+0x5350faff958 6eeb6793 00000004 0a59d718 0a634508 mshtml!COleSite::TransitionToBaselineState+0x410faff978 6ef1ed69 00000001 00000000 00000052 mshtml!CView::EndDeferTransition+0xae0faff994 6edc57bf 0a634508 00000000 00000000 mshtml!CView::EndDeferTransitionCallback+0x2b0faff9c8 6edd1f67 0faffa64 00008002 00000000 mshtml!GlobalWndOnMethodCall+0x1010faff9e8 7689f8d2 000302ea 00000086 00000000 mshtml!GlobalWndProc+0x1810faffa14 7689f794 6edd1eb6 000302ea 00008002 user32!InternalCallWinProc+0x230faffa8c 768a0008 00000000 6edd1eb6 000302ea user32!UserCallWinProcCheckWow+0x14b0faffaf0 768a0060 6edd1eb6 00000000 0faffb68 user32!DispatchMessageWorker+0x3220faffb00 713143fd 0faffb18 00000000 00000000 user32!DispatchMessageW+0xf0faffb68 767e4911 044702a8 0faffbb4 778de4b6 ieframe!CTabWindow::_TabWindowThreadProc+0x2800faffb74 778de4b6 0a622870 782956d0 00000000 kernel32!BaseThreadInitThunk+0xe0faffbb4 778de489 71314117 0a622870 00000000 ntdll!__RtlUserThreadStart+0x230faffbcc 00000000 71314117 0a622870 00000000 ntdll!_RtlUserThreadStart+0x1b// Looks like the ValidateHandle function did not validate the handle// passed to it by WaveInClose, which in turn would have gotten it as// the return of the call function in c0!COM_ENTRY+0x4cac).// EAX shows the result of the call function, 0x3a4f9e50:0:036> reax=3a4f9e50 ebx=00000000 ecx=748a8290 edx=00000000 esi=3a4f9e50 edi=0fafefa0eip=7488490d esp=0fafef04 ebp=0fafef04 iopl=0 nv up ei ng nz ac po cycs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010293winmm!ValidateHandle+0x24:7488490d 8b40d4 mov eax,dword ptr [eax-2Ch] ds:0023:3a4f9e24=????????// Since we have no symbols for c0, we disassemble the previous function// to determine if this is doing the call, which it is:0:036> ub 0e2021fd c0!COM_ENTRY+0x4c93:0e2021e4 50 push eax0e2021e5 ff159808220e call dword ptr [c0!DllCanUnloadNow+0x2012 (0e220898)]0e2021eb 3bc3 cmp eax,ebx0e2021ed 7405 je c0!COM_ENTRY+0x4ca3 (0e2021f4)0e2021ef 83ce04 or esi,40e2021f2 eb09 jmp c0!COM_ENTRY+0x4cac (0e2021fd)0e2021f4 ff75ec push dword ptr [ebp-14h]0e2021f7 ff158008220e call dword ptr [c0!DllCanUnloadNow+0x1ffa (0e220880)]// Looking at the actual memory address shows that it is indeed invalid:0:036> dc 3a4f9e50 L13a4f9e50 ???????? ????0:036> dc 3a4f9e24 L13a4f9e24 ???????? ????// Checking the exception record does show us this as the culprit:0:036> .exr ffffffffffffffffExceptionAddress: 7488490d (winmm!ValidateHandle+0x00000024) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 3a4f9e24Attempt to read from address 3a4f9e24// c0 is apparently a Video&Voice Communication Control:0:036> lmvm c0start end module name0e1f0000 0e28c000 c0 (export symbols) c0.dll Loaded symbol image file: c0.dll Image path: C:\Program Files\LtUcx\1003\c0.dll Image name: c0.dll Timestamp: Mon Jun 13 03:50:20 2005 (42AD3ABC) CheckSum: 00033668 ImageSize: 0009C000 File version: 1.1.22.333 Product version: 1.1.22.333 File flags: 0 (Mask 3F) File OS: 4 Unknown Win32 File type: 2.0 Dll File date: 00000000.00000000 Translations: 0000.04b0 CompanyName: Lotuspond Software Technology (Beijing) Co.,Ltd. ProductName: Lotuspond IMC Video&Voice Communication Control InternalName: IMCv1 OriginalFilename: IMCv1.DLL ProductVersion: 1, 1, 22, 333 FileVersion: 1, 1, 22, 333 PrivateBuild: 1, 1, 22, 333 SpecialBuild: 1, 1, 22, 333 FileDescription: Lotuspond IMC Video&Voice Communication Control LegalCopyright: Lotuspond Software Technology (Beijing) Co.,Ltd. Copyright (C) 2002 All right reserved. LegalTrademarks: Lotuspond Comments: If you have any advice or question, please mail to sales@lotuspond.com.cn\nhttp://www.lotuspond.com.cnI couldn't find anything out about this module further, but it appears that this is the culprit. Link to comment Share on other sites More sharing options...
ejfadrigo Posted April 25, 2008 Author Share Posted April 25, 2008 Thanks Sir,Thank you for your time and effort sir, Soit means Lotuspond IMC Video&Voice Communication Progam are still not compatible in windows Vista? Link to comment Share on other sites More sharing options...
cluberti Posted April 26, 2008 Share Posted April 26, 2008 Thanks Sir,Thank you for your time and effort sir, Soit means Lotuspond IMC Video&Voice Communication Progam are still not compatible in windows Vista?I know nothing about Vista compatibility in the application, but it does mean it's causing your crashes.However, the .dll is from June of 2005, and Vista released November 2006, so I'd say Vista compatibility wasn't necessarily designed into the product (possible if they wrote it for a beta, but a good deal changed from June 2005 to November 2006). Link to comment Share on other sites More sharing options...
ejfadrigo Posted April 26, 2008 Author Share Posted April 26, 2008 thanks a lot sir.. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now