Windows Crashes

From HoN Wiki

Jump to: navigation, search

Contents

Please Consult the Following to Find the Solution to Your Errors

If you can't find the error message you are receiving in the list below, please PM IAmRoot on the forums.

Please note that crashes are only errors that result in HoN closing. Errors such as Packet Overflow, which are not client side and don't result in the program exiting, are either going to be network or server related. Please see those sections for more details about those errors.

K2 Exceptions

When HoN crashes, it pops up a K2 Exception message box. "K2 Exception" is meaningless when diagnosing the cause of a crash; K2 is simply the engine HoN uses. K2 Exceptions are the only type of crashes that are caused by HoN.

The vast majority of K2 Exceptions are caused by virtual memory problems. Please see K2 Memory Usage.

Crashing on startup with an NVIDIA 5xxM/4xxM/3xxM

Nvidia Optimus driver version 275.33 resolves this issue. Search your manufacturers product / support page for new video drivers and install them. If this doesn't help, take a look at this thread. (Link to drivers in here)

BuildBlockList: Truncated block

Truncated Block errors are the result of corrupted or unreadable data. They are usually caused by incorrect file permissions, UAC, antivirus, or missing, damaged, or incomplete files. Rare causes are corrupted system ram or corrupted video ram.

Solutions

  1. Disable UAC, all antivirus software, and make sure HoN is running as Administrator.
  2. Disable UAC and all antivirus software, then uninstall HoN, delete the Documents\Heroes of Newerth and Program Files\Heroes of Newerth directory, then reinstall HoN using the latest installer.
  3. If you only get this error after patching and have tried the above solutions, check your console.log for errors. If you need help fixing the error, post on the Tech Support Forums.
  4. If nothing else has worked, there's a good chance that something is seriously wrong with your windows installation or your hard drive, ram, or graphics card is failing. Reinstall windows, run memtest, and check the S.M.A.R.T. for your hard drive.

Next Step

If the above solutions do not help, please continue on to the next step

  1. Posting on the Windows Crash Forum

D3D_RegisterK2Model(): CreateVertexBuffer failed

D3D_RegisterK2Model(): CreateVertexBuffer failed errors occur largely for the same reasons as Truncated block crashes. However, they can also be caused by buggy graphics drivers or failing hardware.

Solutions

  1. Update your graphics drivers
  2. Disable UAC, all antivirus software, and make sure HoN is running as Administrator.
  3. Disable UAC and all antivirus software, then uninstall HoN, delete the Documents\Heroes of Newerth and Program Files\Heroes of Newerth directory, then reinstall HoN using the latest installer.
  4. If you only get this error after patching and have tried the above solutions, check your console.log for errors. If you need help fixing the error, post on the Tech Support Forums.
  5. If nothing else has worked, there's a good chance that something is seriously wrong with your windows installation or your hard drive, ram, or graphics card is failing. Reinstall windows, run memtest, and check the S.M.A.R.T. for your hard drive.

Next Step

If the above solutions do not help, please continue on to the next step

  1. Posting on the Windows Graphics Issues Forum


CHost::execute() - CHost::frame() - Bad Packet From Server

CHost::execute() - CHost::frame() - Bad Packet From Server is caused by packet corruption on your network. Use a wired connection and update your router firmware and network card drivers. If the problem persists, contact your Internet Service Provider (ISP).

Next Step

  1. Test your internet connection
  2. Check the Support Announcements page for any known problems with the servers

Random Generic K2 Exceptions

Generic K2 Exceptions (ones without a more detailed error message) are almost always the result of your system failing to allocate memory. This occurs when windows tries to use more than 2GiB of RAM for 32 bit applications (3GiB if the /3GB boot flag is set). These memory related crashes have become much rarer recently, but are still possible.

Solutions

  1. Shut down background programs before running HoN
  2. Turn down texture quality in HoN's graphics options
  3. Enable the /3GB boot flag
  4. Install a 64 bit operating system

Enable/Disable Volume Crash

If your game is crashing while your enable or disable the sound, please just delete the startup.cfg located in C:\Users\[user]\Documents\Heroes of Newerth\game\ and start your game to regenerate a new startup.cfg with default sound settings. You can also edit the file, find the line SetSave "sound_disable" "false" and change "false" by "true" if you want to disable sounds.

K2 Exceptions/Crashes When Launching HoN

If you are experiencing crashes upon launching HoN, and those crashes are not Direct3D (D3D) or OpenGL related, your problem is extremely likely to be caused by file reading errors.

These errors come in two types: file corruption and file opening errors.

File Opening Errors

File opening errors can sometimes be tricky to diagnose, as there is a myriad of things that can cause files to be inaccessible.

Key console.log Lines

(paraphrased. You can help by updating this with the exact wording)

  • error opening (Note: These errors are not necessarily bad, as not all resources are actually used and weren't included in the archives. It is only a problem if there are many occurrences.)
  • failed to load library
Possible Solutions
  1. Delete all mods and reinstall (if you have mods)
  2. Disable UAC
  3. Ensure HoN is being run as Administrator
  4. Run HoN from a privileged account
  5. Disable antivirus
  6. Reinstall HoN to C:\HoN
  • (C:\ has slightly looser privileges than Program Files)
  1. Reinstall HoN to a folder owned by your account, ie. C:\Users\[Username] or My Documents
Next Step

If you have tried to find the cause to the best of your ability, please continue on by Posting on the Windows Crash Forum

File Corruption Errors

File corruption errors are usually much easier to spot in the console.log. Before continuing, verify that HoN installed successfully according to the installer and that you didn't bypass any NSIS integrity checks (you'll know if you did).

Key console.log Lines
  • Failed to load library
  • Other errors containing messages along the lines of "invalid format"
Possible Solutions
  1. Delete all mods and reinstall (if you have mods)
  2. Disable your antivirus and reinstall
  3. Scan for viruses
  4. Reinstall HoN. Something may have broken during the patching process
Next Step

If you have tried to find the cause to the best of your ability, please continue on by Posting on the Windows Crash Forum

Blue Screen of Death (BSoD)

BSoDs cannot be caused by problems in HoN (BSoDs are kernel crashes and HoN is entirely userland). However, the opposite is true for drivers and hardware used by HoN. The most common BSoDs are caused by buggy graphics drivers, sound drivers, or failing RAM.

Please take note of the exact error messages displayed, including the hex codes at the bottom (0x########). If you are unable to write everything down fast enough, you can disable the automatic restart:


Here is a good article on common BSoDs and suggested solutions. A lot of BSoDs can be caused by RAM failures, so it is a good idea to run memtest.

Next Step

  1. Google the error message and hex codes. There is a lot of information already available about their causes.
  2. Posting on the Windows Crash Forum

System Restarts

Like BSoDs, system restarts are not faults in HoN's code. They are almost always caused by your computer overheating, but can also be caused by inadequate power supplies. Sudden system restarts are always hardware problems. You can check your system temperatures with programs such as SpeedFan.

Run a stress testing programs like SETI@Home, GPUGrid, mprime, and furmark to see if any of those cause your system to restart after a while.

Possible Solutions

  • Clean the inside of your computer case with an air duster. NEVER run a computer on the floor, as it will collect dust much faster.
  • Add more fans to your case
  • Upgrade to a higher wattage power supply

Next Step

If you have tried to find the cause to the best of your ability, please continue on by Posting on the Windows Crash Forum

System Freezes

If your computer locks up and is completely unresponsive to any input, your system has been caught in a kernel level crash in which the drivers were not able to recover and the windows crash handler wasn't able to catch the problem and display a BSoD. Your only option is to update your drivers and other kernel modules and hope that the problem has been patched. This includes making sure that your antivirus and firewall aren't interfering and are up to date.

Possible Solutions

  1. Rollback all windows updates and uninstall all programs that have been installed since this problem first arose
  2. Check the manufacturer websites for each component in your system for updated drivers. Windows rarely knows about driver updates.