Ever since last weeks Windows update, my Skype keeps crashing shortly after logging on (if I even get that far). I have tried all the suggested solutions from both the Skype forums as well as from just a Google search. To wit, I have:
- Uninstalled and reinstalled Skype at least 3 times to no avail.
- Gone through the "Run>%appdata%" and changed and/or deleted the shared files (as well as every other type of file) at least 3 times to no avail.
- Checked the "compatability" settings to no avail.
- Installed "beta" versions of Skype to no avail.
- Rebooted my system more times than I can remember to no avail.
Is anyone else having this problem and have they found a solution? I rely on Skype to communicate with a number of off site offices numerous times a day and not having it work is not acceptable.
Having the same problem..
would like to add something but you've covered everything.
I remember when skpe use to work with every camera and lower bit rates. Now it doesn't work worth a **bleep** at all. Of course I started having problems right after I upgraded to a Pro membership. Now I paid for something THAT DOESNT WORK!!!
Open Windows Event Viewer -> Custom Views -> Administrative Events. Look for any recent error messages with timestamp corresponding to Skype crash. You may copy and paste here the text from the General tab.
This exact same thing is happening to me. I have also tried all the above solutions. I also attempted to downgrade skype to previous legacy versions. Nothing has worked.
If this doesn't get fixed soon I'm going to recomend switching my whole development team over to a different chat client.
Faulting application name: Skype.exe, version: 126.96.36.199, time stamp: 0x4ff2e373
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x746e696f
Faulting process id: 0x1a74
Faulting application start time: 0x01cd636068716dcb
Faulting application path: C:\Program Files (x86)\Skype\Phone\Skype.exe
Faulting module path: unknown
Report Id: c3920efa-cf53-11e1-80eb-74de2b99d0b4
There were a ton of them. Here are a few:
|C:\Program Files (x86)\Skype\Phone\Skype.exe|
0000: 00000000 00320001 00000000 C00010DF
0000: 00 00 00 00 01 00 32 00 ......2. 0008: 00 00 00 00 DF 10 00 C0 ....ß..À 0010: 05 01 00 00 8C 01 A8 C0 ....Œ.¨À 0018: 03 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........
My apologies, I just realized you wanted the "General View"
Error Message Example 1:
Log Name: System Source: NetBT Date: 7/16/2012 10:47:18 AM Event ID: 4319 Task Category: None Level: Error Keywords: Classic User: N/A Computer: StephenG-PC Description: A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/ev
Error Message Example 2:
Log Name: Application Source: Application Error Date: 7/16/2012 10:26:36 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: StephenG-PC Description: Faulting application name: Skype.exe, version: 188.8.131.52, time stamp: 0x4ff2e373 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x0000001d Faulting process id: 0x22b8 Faulting application start time: 0x01cd635efeacfc50 Faulting application path: C:\Program Files (x86)\Skype\Phone\Skype.exe Faulting module path: unknown Report Id: 3f8f4215-cf52-11e1-add7-782bcbf04b7e Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/ev
Try to start your Windows in “Safe mode with networking” and then to start Skype.
16-07-2012 17:21 - edited 16-07-2012 17:23
The error message may indicate a problem with some system devices or services. In “Safe mode with networking” Windows loads only the most necessary devices and services and if (just if!) Skype appears to work in this safe mode, then the next step would be to identify the offending application. However, no guaranty that this will work.