My NWN Explorer is bugged?

[Legacy_Sheldomar]

               

Yesterday I downloaded Vaei's custom respawn panel HAK from the new vault. While using NWN Explorer 1.63 to check out the modified GUI file in it, the program crashed. Since then, it refuses to open .hak files or even expand the hak directory. All other directories, etc still work fine, but when I select anything hak related, an error screen comes up, saying:

 

Microsoft Visual C++ Runtime Library - Runtime Error... This application has requested the Runtime to terminate it in an unusual way.

 

I tried downloading a new copy of  NWN Explorer 1.63 and even this fresh version is getting the same error. I don't know much about computers' inner workings (beyond turning it off, then turning it on again), so I was wondering if anyone might have an idea how to get the program working again. Thanks.

               
               

               
            

[Legacy_Michael DarkAngel]

               

Something makes me want to say remove a file or two from your hak folder and try again.

 

[EDIT]

Confirmation can be found -->> here <<--

 

 MDA

               
               

               
            

[Legacy_Sheldomar]

               

Thanks a lot for the help! In the process of removing haks, I found out that it was a hak called alva_bioelves that was causing the crash. I took it out of the folder, and now everything works fine.

               
               

               
            

[Legacy_Jedijax]

               

If the file causing the crash has been in your folders for some time and never crashed the explorer, it is due to one of two things. Either it got somehow corrupted while making changes to it, or your Hard Drive is starting to have faulty sectors. If the file reads as 0 kbs or such, you should move your stuff to a new HD as soon as possible.

               
               

               
            

[Legacy_Proleric]

               

This is a well-known issue with NWNExplorer, which is fixed by reducing the number of files in the hak folder. This is the first time I've seen the problem traced to a particular hak, though. I've never had that file myself, so evidently it's not the only one that might contribute to the problem.