EFUPW Forums

Main Forums => Off-topic Discussion => Topic started by: Ladocicea on August 25, 2013, 12:52:47 PM

Title: NWN Crashing
Post by: Ladocicea on August 25, 2013, 12:52:47 PM
I'm crashing too often to make the game playable in the long run, so I'm throwing it out there to see if anyone has any solutions.

Bit of info:

Was crashing as soon as I logged in without the haks. With haks I can play for a bit but usually crash in built up areas like Upper Sanctuary or the House of trade. Changing armour can also cause a crash.

Weirdly, if I make it to an area transition and go backwards and forwards through it 5 or 6 times I seem to gain some stability and can play for long(er) periods of time without crashing, so long as I avoid Upper and the trading house and other high stress areas.

When playing offline I immediately crash when changing armour, and also crash if I open certain doors into areas populated by NPCs, although I think if I make it to an area transition I can then avoid crashing from armour changes and opening doors, etc.

This is the same install as I've always had on my computer and it previously played NWN 1.69 flawlessly, windows 7 running in XP SP3 compatibility + administrator and running directly from the nwnmain.exe.

Tried disabling audio, tried windowed/fullscreen, tried running with no other windows open, tried fixing registry issues. None of them seem to have an effect.

Cheers.
Title:
Post by: Paha on August 25, 2013, 01:08:35 PM
Graphic drivers, memory issue with windows 7 (ram problem), audio drivers.

These are things I personally had experienced in past in some points when I changed my system and settings. I also found few of the lastest windows 7 security updates to cause online problems with some games, so who knows.

You could also try to find the animation override that fixed some crashing in past for some people.
Title:
Post by: Howlando on August 25, 2013, 01:41:52 PM
Let's figure this out, guys.

Maybe these links will help:

Here (http://www.rage3d.com/BOARD/archive/index.php?t-33625814.html) and here (http://arelith.com/node/1592).
Title:
Post by: Paha on August 25, 2013, 01:53:12 PM
I suggest also you either try to use game through launcher, or by making a shortcut and putting in the target line something like this:

( This being your nwn directory) -- \NwN\nwmain.exe +connect nwn.efupw.com

It'll work same as launcher, and direct connects to efu without launching through the nwnmain options - which usually launch up aero / graphical memory issues with windows 7.

Other is, I'd like you have provide basic information of your PC. Processor, memory, graphic card and if you have updated either windows or graphic drivers recently.

Last pointer is that if you got low ram and video memory, you should avoid having a lot of programs running the background while playing.
Title:
Post by: The Band Played On on August 25, 2013, 01:58:28 PM
This is going to sound like a weird suggestion, but rename your portraits folder something like "portraitstest" and try to log on and see if you crash. If this is your old install you perhaps have accumulated too many portraits. It sounds implausible, but this happened to me, and once I discovered this I cleared out my portraits folder, took the EfU pack only, and it's been fine since.

Your problem seems to suggest something different than this, but this is a very easy thing to try, and at least rule out.
Title:
Post by: Ladocicea on August 25, 2013, 03:26:19 PM
Thanks for the suggestions.

I haven't added any portraits to my folder since NWN last ran without issue so it's probably not that.

Paha, just going to copy stuff out from my dxdiag as I'm too computer illiterate to know what's important:

Pentium dual core t4300 @ 2.10ghz
4096mb RAM
page file 1817mb used, 6050available
dx11
Mobile intel 4 series express chipset family
1759mb

I don't seem to be able to add +connect nwn.efupw.com to my shortcut's target without it bringing up an error.

I think my computer has probably done one or two of those annoying windows updates since I last ran NWN on it but I'm not sure how I could revert it to how it used to be or even what has been changed by those updates.

And I tried to do the disabling of the Video RAM cachable thing in the link you provided Howl but my BIOS virtually has no options on it other than changing the time the computer displays. I think that's only applicable if you have a graphics card or something. I dunno?
Title:
Post by: Paha on August 25, 2013, 03:33:42 PM
You don't exactly got a graphic card, just build in. That is more than enough to cause problems with any graphical matter. And it is nearly impossible to diagnose if that is the case or not. That is if I am getting it right. That is a laptop what's the deal?
Title:
Post by: Ladocicea on August 25, 2013, 03:37:49 PM
But it has run NWN perfectly before, which is what's so annoying. I don't know what could've changed between then and now to make this happen.
Title:
Post by: Paha on August 25, 2013, 03:49:20 PM
Try finding chipset updates for it from the manufacturers site? It might help.
Title:
Post by: Kotenku on August 25, 2013, 04:35:56 PM
Have you tried the ClientCPUAffinity fix?
Title:
Post by: Ladocicea on August 25, 2013, 07:13:05 PM
Early days and need to do a lot more testing but I think Kotenku takes gold.
Title:
Post by: Doc-Holiday on August 26, 2013, 12:48:14 AM
How long have you had NWN installed?
If very recent, ignore this reply
 
How frequently have you added haks?
 
 
It is an ancient issue that installations of NWN can, over the course of a year or so, become unstable and require a fresh installation.
Title:
Post by: Ladocicea on August 26, 2013, 10:19:21 AM
Sorry bud Kotenku's suggestion has fixed it I think. I haven't crashed once since. Thanks though.
Title:
Post by: Paha on August 26, 2013, 10:23:17 AM
Good to hear it works.
Title:
Post by: Gotham on August 26, 2013, 02:54:31 PM
Whats the client CPU affinity fix? I still have intermittent crashes from loading textures or shaders (or so I assume since it happens from loading certain torchlit area's or putting on armor.
Title:
Post by: Paha on August 26, 2013, 03:05:54 PM
http://nwn.wikia.com/wiki/Nwnplayer.ini

Check CPU affinity. Nwn does not handle attempts to run at multicore very well, so if you have problems, it's adviced to test couple settings to set it at 1 / 0.

Also

http://www.tomshardware.co.uk/forum/108010-13-running-newer-multi-core-cpus
Title:
Post by: TheTurboNerd on September 03, 2013, 03:42:49 AM
I love you. Finally got around to testing this, a setting of -2 has finally fixed my lockup problems - or so it seems at least. I tested by running through the tailor which always crashes me, and it seems to be fixed.