Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Firefox will NOT Open...Crash report appears...WHY?

  • 1 baphendule
  • 20 zinale nkinga
  • 8 views
  • Igcine ukuphendulwa ngu WJEC

poormozillauser
poormozillauser
more options

AdapterDeviceID: 68a1 AdapterVendorID: 1002 Add-ons: videosurf_enhanced@videosurf.com:0.79,{dc572301-7619-498c-a57d-39143191b318}:0.3.8.5,{BBDA0591-3099-440a-AA10-41764D9DB4DB}:2.0,{B7082FAA-CB62-4872-9106-E42DD88EDE45}:3.3.1,{972ce4c6-7e08-4474-a285-3208198ce6fd}:4.0 AvailableVirtualMemory: 4080922624 BuildID: 20110318052756 CrashTime: 1301350093 EMCheckCompatibility: true FramePoisonBase: 00000000f0de0000 FramePoisonSize: 65536 InstallTime: 1301336545 Notes: AdapterVendorID: 1002, AdapterDeviceID: 68a1, AdapterDriverVersion: 8.713.3.3000 D3D10 Layers? D3D10 Layers-

ProductName: Firefox ReleaseChannel: release SecondsSinceLastCrash: 395 StartupTime: 1301350092 SystemMemoryUsePercentage: 27 Theme: classic/1.0 Throttleable: 1 TotalVirtualMemory: 4294836224 Vendor: Mozilla Version: 4.0 Winsock_LSP: MSAFD Tcpip [TCP/IP] : 2 : 1 : %SystemRoot%\system32\mswsock.dll 

MSAFD Tcpip [UDP/IP] : 2 : 2 :  
MSAFD Tcpip [RAW/IP] : 2 : 3 : %SystemRoot%\system32\mswsock.dll 
MSAFD Tcpip [TCP/IPv6] : 2 : 1 :  
MSAFD Tcpip [UDP/IPv6] : 2 : 2 : %SystemRoot%\system32\mswsock.dll 
MSAFD Tcpip [RAW/IPv6] : 2 : 3 :  
RSVP TCPv6 Service Provider : 2 : 1 : %SystemRoot%\system32\mswsock.dll 
RSVP TCP Service Provider : 2 : 1 :  
RSVP UDPv6 Service Provider : 2 : 2 : %SystemRoot%\system32\mswsock.dll 
RSVP UDP Service Provider : 2 : 2 :

This report also contains technical information about

AdapterDeviceID: 68a1 AdapterVendorID: 1002 Add-ons: videosurf_enhanced@videosurf.com:0.79,{dc572301-7619-498c-a57d-39143191b318}:0.3.8.5,{BBDA0591-3099-440a-AA10-41764D9DB4DB}:2.0,{B7082FAA-CB62-4872-9106-E42DD88EDE45}:3.3.1,{972ce4c6-7e08-4474-a285-3208198ce6fd}:4.0 AvailableVirtualMemory: 4080922624 BuildID: 20110318052756 CrashTime: 1301350093 EMCheckCompatibility: true FramePoisonBase: 00000000f0de0000 FramePoisonSize: 65536 InstallTime: 1301336545 Notes: AdapterVendorID: 1002, AdapterDeviceID: 68a1, AdapterDriverVersion: 8.713.3.3000 D3D10 Layers? D3D10 Layers- ProductName: Firefox ReleaseChannel: release SecondsSinceLastCrash: 395 StartupTime: 1301350092 SystemMemoryUsePercentage: 27 Theme: classic/1.0 Throttleable: 1 TotalVirtualMemory: 4294836224 Vendor: Mozilla Version: 4.0 Winsock_LSP: MSAFD Tcpip [TCP/IP] : 2 : 1 : %SystemRoot%\system32\mswsock.dll MSAFD Tcpip [UDP/IP] : 2 : 2 : MSAFD Tcpip [RAW/IP] : 2 : 3 : %SystemRoot%\system32\mswsock.dll MSAFD Tcpip [TCP/IPv6] : 2 : 1 : MSAFD Tcpip [UDP/IPv6] : 2 : 2 : %SystemRoot%\system32\mswsock.dll MSAFD Tcpip [RAW/IPv6] : 2 : 3 : RSVP TCPv6 Service Provider : 2 : 1 : %SystemRoot%\system32\mswsock.dll RSVP TCP Service Provider : 2 : 1 : RSVP UDPv6 Service Provider : 2 : 2 : %SystemRoot%\system32\mswsock.dll RSVP UDP Service Provider : 2 : 2 : This report also contains technical information about

All Replies (1)

WJEC
WJEC
more options

This was one of my first results on Google searching for this problem, so I thought I should give it a reply now that I can reply from Firefox.

I'm really not sure what fixed it. One of the pages I read when I was reading about mswsock.dll suggested any issues with it might be caused by spyware or a virus. This seemed likely since I'm running a fresh install of Windows 7 64-bit and had yet to protect it. I downloaded and installed Microsoft Security Essentials, and when I restarted my computer to finalize the install of MSE, Windows updated. When I got back into Windows I immediately started a scan, but the second thing I did was try to open Firefox, which actually opened. So three possible fixes:

-Merely installing Microsoft Security Essentials. Least likely to have fixed it.

-Updating Windows. More likely to have fixed it, but still doubtful.

-Restarting my computer. Most likely to have fixed it. It seems to me that rebooting hasn't been a magic fix since I ran Windows 98, so I often forget to try it, but honestly most of the time that's all a computer needs is to be turned off and on.

Good luck.