You must forgive me for my sudden departure: I was repeatedly called away on business and have spent much of the last two months+ travelling while sometime being at home. I finally am now returning to a normal schedule, and with it, a return to the problems of my PC that is still giving me problems with Yahoo Messenger.
Okay, so here all the solutions I have attempted to do to fix the problem.
1. Uninstall TVersity - nope. Not the culprit! Yahoo crashes without it on my system at all. I've not had it on for a week and I've had crashes every day.
2. Download and install a new version of MSVCR71.dll. Nope, did not work. I even replaced the version of the .dll in Yahoo. This did not work.
3. Uninstalled all my Windows Visual Basic C++ updates (which were redundant and took up an incredible amount of space) and reinstalled the newest one (x86 2010 redistributable). Nope!
4. Configured Malwarebytes to ignore Yahoo Messenger, and both instances of MSVCR71.dll. This did nothing.
5. Configured my network. This did nothing and was unnecessary. It was not a network issue - that was just a shot in the dark.
6. Tried installing other old versions of Yahoo. Nope, this didn't work. The new versions of YIM aren't fit for what I need to use it for, although as a last ditch effort, I may consider it. Even though I think the problem may go deeper (See below).
I do, however, have two leads:
1. I have been routinely getting an error, near to start up on Windows, that a program called Cyberlink Media Library Server is crashing with this message in Event Log:
Faulting application CLMLSvc.exe, version 2.3.2203.0, time stamp 0x48e5cfa5, faulting module CLMediaLibrary.dll, version 4.3.2203.0, time stamp 0x48e5cfe0, exception code 0xc0000005, fault offset 0x0002c873, process id 0xa34, application start time 0x01cccf2d4f50a5ef.
I did not even know I had this program and it seems to be linked to the Lightscribe functionality of my DVD burner. I never use lightscribe. Would I be well served to remove it?
I do not think this will resolve the issue, but it seems that it could be related.
2. More importantly, I have traced back the origin of the program through Event log to 7-15-2011 (with the closest instance before that on 7-7-11) after which the problem became consistent (every day often multiple times).
Possibly connected to this: About a month prior I see many folders had to be recreated on the same date - in fact, most of the major folders on my computer all seem to have been remade on 6-6-11. This makes me think this was the date of a malware (a Rogue antivirus) attack that I suffered from last year. In that attack, I was hit with a rogue anti-virus that made it appear that I lost all my data, that my hard drive was corrupted, and that everything on my computer went away. To fix it, I had to not only blast it with Malware Bytes, but I also had to do a system restore to get all my folders out of being set hidden - a process that would have taken me HOURS upon HOURS otherwise.
Is it possible that there is some registry matter that has to be attended to that eventually caused Yahoo to have problems related to this? It seems to me to be one of the last things I have not tried to fix. If so, how might I go about fixing it? Is there a program I can use that would check my registry to fix it for this sort of problem?
Also, should I post some details of the date in my eventlog for someone to look over from 7-15-2011?
Lastly, is there anyway I can make sure that, at the very least, my Yahoo crashing doesn't screw up my explorer.exe? As I said: At times the error message becomes unclickable as it makes Explorer.exe non-responsive. This forces me to logoff windows, which often interrupts my work and what I am doing even more than having a crashing program constantly. Is there anyway to fix that? This makes me think there is something wrong with explorer.exe. Should I replace the file from my windows disk?
Thank you again and my apologies once more. Your help ais always appreciated and I did not mean to vanish on all of you.
EDIT: One thing I forgot to mention. Many of the above fixes appeared, tantalizingly, to offer some rectification. Sometimes for up to two days my Yahoo would not crash, all for it to begin to do so again. I do not know what that says, and why there was any reprieve, but I sometimes have these instances of unproblematic operation uninterrupted by these errors. This only compounds the UTTERLY random behaviour of the problem.
