Troubleshooting
This page has been marked as a stub, having little or no useful content. This marking means it will probably get updated soon!
Can't find what you are looking for? Please feel free to visit the ISBoxer.com Forums, Chat Room, and our Discord server! You have the best chance of receiving immediate help in the Chat Room or Discord.
Contents
If ISBoxer won't start
The only known reason that the ISBoxer Toolkit will fail to launch is under Windows XP, and only if .NET 3.5 is not installed (4.0 does not count). Running ISBoxer on Windows XP without .NET 3.5 installed will show the following error message: The application failed to initialize properly (0xc0000135). Click on OK to terminate the application
If you get this error, just install .NET 3.5 from Microsoft, via this link: http://www.microsoft.com/downloads/details.aspx?FamilyId=333325fd-ae52-4e35-b531-508d977d32a6.
Game crashes
See http://isboxer.com/forum/viewtopic.php?f=22&t=1251
System crashes, BSODs, reboots, freezes
This type of problem can only be caused by a problem with your hardware or drivers, even if the problem only seems to manifest itself while multiboxing. This is by design of the Operating System.
The problem could typically be from overheating, a physical defect or incompatibility with other hardware, or most commonly a driver bug.
The most common solutions to this type of problem are as follows:
- Update drivers
- Remove dust from heat sinks and fans, which may be causing overheating
- Replace faulty hardware
Ventrillo/Teamspeak seems to not bind well in-game (Push-To-Talk)
This seems to be due to a problem with mouse binding. Try keyboard binding only to try to resolve this issue. If the problem persists, please see our IRC channel.
