bstsimo Posted December 14, 2008 Share Posted December 14, 2008 Hello everyone,I have been using Media Center Edition since a month now.. And it was going smooth until the last format a week ago I noticed that the Windows Live Messenger crashes every now and then, I tried to uninstall it and then reinstall it again but that didn't work... I'm now p***ed off and I don't wish for another format... So if anyone have any advice please give it to me...Thanx in advance... Link to comment Share on other sites More sharing options...
weEvil Posted December 15, 2008 Share Posted December 15, 2008 You're not going to get an answer if you're so vague.There are thousands of different solutions to your problem. Link to comment Share on other sites More sharing options...
cluberti Posted December 15, 2008 Share Posted December 15, 2008 Get a dump of the process crashing and then compress it and upload it somewhere - then we can try to determine what is happening. Link to comment Share on other sites More sharing options...
bstsimo Posted December 19, 2008 Author Share Posted December 19, 2008 Thank you very much Cluberti,I hope I did the right procedures... Here is the file uploaded: http://rapidshare.com/files/174737648/adplus.rarIf there is anything else that can help plz let me know...Thanx in advance Link to comment Share on other sites More sharing options...
cluberti Posted December 19, 2008 Share Posted December 19, 2008 There's no crash dump file here. Try again please. Link to comment Share on other sites More sharing options...
bstsimo Posted December 19, 2008 Author Share Posted December 19, 2008 (edited) Ooops!!! yeah it was my fault...Here is the dump file again: http://www.badongo.com/file/12559085and this is an image was generated by Ms Visual Studio when i had it on my pc that i hope it could help: Edited December 19, 2008 by bstsimo Link to comment Share on other sites More sharing options...
cluberti Posted December 19, 2008 Share Posted December 19, 2008 I can only see first chance exceptions, and seeing this detour in GdiPlus causing this A/V is actually expected behavior when the debugger is attached.0:000> kChildEBP RetAddr 0006ebd0 4ed991de GdiPlus!LZWDecompressor::FHandleNext+0x10a0006f2a4 4ed99fc1 GdiPlus!GpGifCodec::ProcessImageChunk+0x9350006f34c 4ed9a0e7 GdiPlus!GpGifCodec::DoDecode+0x1d60006f380 4eca846a GdiPlus!GpGifCodec::Decode+0x910006f394 4eca8425 GdiPlus!GpDecodedImage::InternalPushIntoSink+0x2e0006f3ac 4ec94b74 GdiPlus!GpDecodedImage::PushIntoSink+0x2e0006f414 4ec94ac8 GdiPlus!GpMemoryBitmap::InitImageBitmap+0xcc0006f440 4eca87ba GdiPlus!GpMemoryBitmap::CreateFromImage+0x490006f478 4ec68040 GdiPlus!CopyOnWriteBitmap::LoadIntoMemory+0x9e0006f51c 4ec67d48 GdiPlus!CopyOnWriteBitmap::LockBits+0xd70006f548 4eca684e GdiPlus!GpBitmap::LockBits+0x6d0006f578 0047bc58 GdiPlus!GdipBitmapLockBits+0x7f0006f598 0047bbab msnmsgr!Gdiplus::Bitmap::LockBits+0x1c0006fa14 0047b6d1 msnmsgr!ATL::CMSGRImage::CreateFromGdiplusBitmap+0x1d30006fab4 0047b9ac msnmsgr!ATL::CMSGRImage::Load+0x1c50006fadc 006e1654 msnmsgr!ATL::CMSGRImage::Load+0x360006fb0c 006e198a msnmsgr!CCustomEmoticons::HrGetCImageFromObjectStoreData+0x300006fb50 0047ff1e msnmsgr!CCustomEmoticon::OnObjectGot+0x860006fb6c 00436967 msnmsgr!CEventHandler1<CEventingNode<CObjectStoreEventSinkGot,CObjectStoreRequestResultWithObject,Unused,Unused,Unused,Unused>,CObjectStoreRequestResultWithObject>::operator()+0x2c0006fb78 0048009a msnmsgr!CEventingNode<CMainWnd,enum EOmRecvErr,CRefCountedPtr<COfflineMessage>,Unused,Unused,Unused>::RaiseEvent+0x340006fbb8 00480058 msnmsgr!CEventingNode<CObjectStoreEventSinkGot,CObjectStoreRequestResultWithObject,Unused,Unused,Unused,Unused>::Invoke+0x3d0006fbf4 0047ffdd msnmsgr!CEventSinkList<CObjectStoreRequestResultWithObject,Unused,Unused,Unused,Unused>::InvokeHandlersInternal+0x450006fc2c 0047f83b msnmsgr!CEventSinkList<CObjectStoreRequestResultWithObject,Unused,Unused,Unused,Unused>::InvokeHandlers+0x2c0006fc78 0052b25b msnmsgr!CRetrieveRequest::OnComplete+0xc60006fca0 0051f7f0 msnmsgr!CP2PRetrieveRequest::OnReceived+0x840006fccc 0051b463 msnmsgr!CSlaveNotifier::OnReceive+0x1030006fd44 0051eb33 msnmsgr!CP2PTransport::OnReceived+0x8b60006fd98 0051dcd7 msnmsgr!CTCPTransportBridge::OnSocketRead+0x2840006fdb4 00419934 msnmsgr!CTCPTransportBridge::OnMessage+0x17b0006fdc8 7e418734 msnmsgr!CMsgrWndBase::WndProc+0x5f0006fdf4 7e418816 user32!InternalCallWinProc+0x280006fe5c 7e4189cd user32!UserCallWinProcCheckWow+0x1500006febc 7e418a10 user32!DispatchMessageWorker+0x3060006fecc 004032cb user32!DispatchMessageW+0xf0006fef8 004af31a msnmsgr!CMessengerModule::RunMessageLoop+0x650006ff08 004b8dba msnmsgr!ATL::CAtlExeModuleT<CMessengerModule>::Run+0x1e0006ff10 004b8d32 msnmsgr!RunMessageLoop+0xc0006ff24 004bd41a msnmsgr!CMSBLApp::main+0xfa0006ff30 004bd458 msnmsgr!WinMain+0x120006ffc0 7c817067 msnmsgr!__tmainCRTStartup+0x1400006fff0 00000000 kernel32!BaseProcessStart+0x23Please post back when you have a SECOND CHANCE exception. Link to comment Share on other sites More sharing options...
bstsimo Posted December 20, 2008 Author Share Posted December 20, 2008 Anyway, thanx for ur time Cluberti...Anyway, am trying to cope with that problem till I find another version of windows...thanx again 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