* Outdated old Java version. Update your java to the current version (1.6.0_26 in June 2011).
* Internet Explorer 5, 6 or 7. Old versions may not be fully compatible with current Vuze features. Use WindowsUpdate to update to Internet Explorer 8 or to the recently released Internet Explorer 9.
* Note: Please note that in Windows environment Vuze uses Internet Explorer components to display the search results and other web-like content despite the browser that you use for normal web browsing. So, even if you use Firefox or Chrome for surfing the web, Internet Explorer plays a role inside Vuze.
* Additional note: Also check your Internet Explorer’s “proxy settings”. There have been reports that some viruses have changed the IE proxy settings (in “Internet Options” of Windows) and that might also explain why some content is not shown.
* Safari 3 or other old versions. Update to current version (5.0.4 as of April 2, 2011) at http://www.apple.com/safari/download/
* Zone Alarm – old versions, see see Zone Alarm and update to current version
* AxShlex.dll : Alcohol 120%
Latest: Java 1.6.0 Update 4 resolves this issue (and many others it seems) – please update from http://java.sun.com/javase/downloads/?intcmp=1281
Note: Alcohol 120% is especially troublesome in combination with Java 1.6.0 Update 1. There are several ways to fix the issue:
o rename/delete AxShlex.dll that it doesn’t get loaded (alcohol itself will continue to work)
o don’t download torrents that contain files which are associated with alcohol 120%, such as .MDS files
o remove all “Shell Extensions” within the Alcohol settings panel by going to (File > Options > Virtual Drive > Shell Extensions subitem), then click on ‘Remove All’.
o uninstall Alcohol 120%
o downgrade to a previous java version (this might not work in all cases)
o run Vuze with the flag -Xcheck:jni – this traps the native floating point error causing the crash but has performance overheads
* D3DIM700.DLL : Microsoft DirectX 3D – upgrade to latest Java 6 (see Java bug 6275887). Also update Microsoft DirectX components.
* Flash.ocx : Adobe Flash player, which is used for displaying Vuze media browsing experienece through embedded IE components. Update Flash player and check through WindowsUpdate that your browser (IE?) is fully updated.
* FPServiceProvider.dll : FoxyProxy Video Add-on
* ForceInterfaceLSP.dll : HMA! Pro VPN. See forum discussion: http://forum.vuze.com/thread.jspa?threadID=96014
* gapsp.dll : Juniper Networks Neoteris client
* HMIPCore.dll : HideMyIP
* iFW_Xfilter.dll: iolo Firewall
* imon.dll : configure NOD32 firewall properly
* InjHook12.dll : Torrent Ratio Keeper (http://www.torrentratiokeeper.c0m)
* jvm.dll or ntdll.dll: raise the issue with Sun ( http://bugs.sun.com/bugdatabase/index.jsp )
* libxul.so: Linux systems may require Xulrunner components to be installed separately with Firefox 4. See this article.
* mclsp.dll : McAfee – uninstall the privacy service
* mshtml.dll: part of Microsoft IE (in your Windows), which Vuze uses for displaying web content. Check that IE is properly updated.
* MxAVLsp.dll : VCom Fix-It Utilities
* netdog.dll : Armor2net personal firewall
* niphk.dll: you might have to uninstall Norman Anti-virus completely.
* nl_lsp.dll : NetLimiter – uninstall
* nvappfilter.dll: please uninstall the NVIDIA Firewall and/or make Vuze run with only one cpu.
o (To make Vuze run only on one cpu, open the Task Manager (press ctrl-alt-del) and select the Processes tab. Right-click azureus.exe and click set affinity. Then uncheck all but one of the cpus (it shouldn’t matter which). Click ok.)
* radhslib.dll : Naomi internet filter from Radiant
* sarah.dll : FRITZ! Application Layer Firewall
* SDHook32.dll : Spybot – search & destroy
* urlmon.dll: part of Microsoft IE (in your Windows), which Vuze uses for displaying web content. Check that IE is properly updated.
* vlsp.dll : Venturi firewall or V-ONE SmartPass software (or possibly also Nvidia Network Access Manager)
* Winsflt.dll : PureSight Internet Content Filter
Note for developers: The .dlls listed here don’t necessarily cause the crashes, they’re just indicators for the presence of problematic applications.
 Debug Procedure
If you want to file a bug report please include the hs_err_pid.log file.
1. Check hs_err_pid.log files in the Vuze program directory. These files are created by java system as java crash logs. It is possible that it will help you identifying the cause of the crash.
The key part is looking for the java/DLL call stack thread leading to the crash. There should be something like:
JRE version: 6.0_15-b03
Java VM: Java HotSpot(TM) Client VM (14.1-b02 mixed mode, sharing windows-x86 )
In the example’s case the crash is caused by Adobe Flash player (used for displaying Vuze media browsing experienece through embedded IE components.)
2. Identify the failing DLL. Consider removing the problematic application to see if that would help.