18 réponses à ce sujet

[Glomoro Soravek]

I just recently reinstalled NWN2, following directions in the Self Help Starts Here post. Got my settings all just right for my rig to run it smoothly and look as good as possible, and then 15 minutes later the crashing began. I've tried changing my settings every which way, tried installing several times since to see if that fixed it, installed some of the community made things that have been known to fix some crashing issues for the game, rolled back my GPU drivers to several older versions to try them, tested with my crappy Radeon HD integrated but can't get the problem to happen again with that.

Also kept track of some windows event viewer data as well as data from a blue screen this also managed to cause several times if anyone wants me to upload those somewhere so you can take a look. As far as I can see though, those point to "nvlddmkm.sys," and with the searching I've done other people have the same problem I do but I'm not sure I quite understand how to "fix," it using the suggestions I've seen for it. Something about editing the registry so timeout detection and recovery waits longer for the driver to reset? I tried it following the directions I found, and it seemed to work for a while but then the crashes started happening again faster than the registry addition was supposed to allow. Was wondering what any of you might have to offer on this? I can play as long as I save way more often than I really need to from a gameplay perspective, but I'd really rather fix this if at all possible.

Oh, and here's the information list the Self Help post requests people post, answered to the best of my knowledge.
Game Version: NWN 2 1.23 MotB and SoZ installed
Game Language: English
Retail or Digital: NWN2 and MotB retail, SoZ digital
Processor Manufacturer: AMD
Processor Type: Phenom II X4 965 Black Edition (No, I've not overclocked it.)
Processor Speed: 3.4 GHz
Operating System / Service Pack: Windows 7 64bit with SP1
System RAM: 4GB single channel 1333mhz
Video Card Manufacturer: NVIDIA
Video Card Model: Geforce GT 240
Video Card RAM: I believe mine is 1 GB, if not the other possible one for this card is 512 MB
Video Card Driver Version: 301.42
Sound Card: this one I'm not sure about, I thought
it was using the video card for this as well given what was installed
with the drivers. If that sounds wrong and it's relevant I'll try to
figure this out at request
CD/ROM Type:
and
DVD Type: if these refer to my drive, DVD/RW. If the discs, NWN2 OC was on CD/ROM while MotB was DVD/ROM, SoZ from the digital edition installer I've kept around since I bought it
Hard Drive Type: SATA
Free Disk Space:  Game is installed in C:\\Program Files (x86)\\Atari\\Neverwinter Nights 2
Second folder for modules/hak paks and such is in My Documents folder on the same drive. Free space is 67.9 GB
Power Supply: 650 watts and I believe the 12-volt rail is 20 A. If that sounds wrong I can check again, there's a lot of different values where I'm looking. That one is for DC Output "+12V1"

Any advice or input at all on this is much appreciated, just let me know if you guys want/need the .dmp file and such as well. I'll get whatever you need from that to you however you want to get it.

[kevL]

this may sound silly but, DirectX 9.0c ?

[ShinsFortress]

Funnily enough, I've recently started having this problem. Only thing that has changed for me is that I'm temporarily using a 3G connection while waiting for a new broadband supplier to install. Weird.

[Glomoro Soravek]

I had issues installing DirectX 9.0c when the game tried to do it, so I manually installed it alongside DirectX 11. It should be working but I could have done that wrong I suppose. Is there a way to verify it installed properly? DirectX Diagnostic only says anything about 11, wasn't sure if it was supposed to list both.

[kevL]

i don't know how to check dx9 when 11 is there also - suppose there's a list of files & file version #s but that'd be a hassle. Personally I've never had any problem with microSoft's redistributable web installation ( dxwebsetup.exe ), though i should archive the full package ( directx_Jun2010_redist.exe )

...

The reason i suggest it, is because the random crashes sound similar to what was happening on my system when I forgot to install dx9. Since others say NwN2 is working pretty fine in win7, and you've already hashed out a lot of stuff, you could give a shot at reinstalling 9c from M$

[Glomoro Soravek]

My thoughts exactly when I saw your first post. I've just done so and am about to open the OC save file I have and see if I can make it crash again. I'm pretty sure the hang ups happened the most easily when I had full view distance and the camera spins very quickly all of a sudden. Gonna go toggle my settings properly and spin the camera around like crazy, if that doesn't do it I'll try playing normally for a while. I'll post an update if it still crashes or if I go much longer without any issues than I've been able to since reinstalling the game. The longest I've gone without a full crash was an hour, but the screen still showed signs of drivers crashing but recovering during that time frame. That will be my target time frame for this test.

[Glomoro Soravek]

Well, didn't even make it past that initial test with turning in place, which is actually slower than the camera can move sometimes. I also just remembered I might not have done the part of the installation directions about viewing the first conversation, closing and then installing MotB. Is there any way that's the problem? I wasn't really sure what that was supposed to fix or prevent.

[kevL]

well, I just notice a general thing about programs in general; they take a bit of nudging to settle in and behave. The more complex the program, the more nudging ( rebooting, opening and closing the program, etc )

My own policy on installing NwN2 is to start as fresh as possible, clean up the hard drive, defrag, examine the registry for outdated entries (w/ CCleaner). Install OC and play it till i get a conversation (no updates yet). Install MotB and do the same. Back-up 'vo_x1.zip' before installing SoZ; put 'vo_x1.zip' back into \\Data folder, play for a bit. Only then will I do updates to v1.23 (others do this a bit differently). btw Dx9c and .NET3.5 ( for toolset ) go in first,


I've heard there's problems with newer nVidia cards, but i think it's just a texture issue and the GT240 is okay ...

[Glomoro Soravek]

Yeah, I mean I got this card around the time MotB or SoZ came out so it's not all that new. The drivers it uses are for a lot of different cards now though, that's why I tried rolling back a few times, since I know it did used to work fine. I'm going to give your installation procedure a try, I do have CCleaner and my drive could probably use a cleaning anyway. I hadn't seen anything about vo_x1.zip until now though, does SoZ do something to that you would prefer it didn't?

[kevL]

yeah. SoZ accidentally deletes 'vo_x1.zip' from the \\Data folder * bork *


So before installing SoZ just copy that file to a temp directory somewhere safe, then after SoZ is in copy the file back to \\Data before updating

it's not a big issue because updating does notice it's not there and redownloads it (usually without problems, but the file is 333mb so ... faster to do the copy-paste)

[ShinsFortress]

Update:-
Take a look at http://social.biowar...1/index/3116438 maybe it will help.

Modifié par ShinsFortress, 03 août 2012 - 05:57 .

[Glomoro Soravek]

That's one of the things from the vault I did try already, unfortunately it did not help me. Also, finally got the chance to do that reinstall and try this again, still happening. I'm just going to play something else for a while, see if anything occurs to me to try (my best ideas often come when I'm not thinking about the problem I want to address at all). I'll check back again later here to see if any other suggestions get posted, if not and I can't come up with anything I'll either continue saving every five minutes or more if more than one important thing occurred within five minutes, or I'll try the integrated graphics out again with much, much lower settings (thing doesn't even have video memory at all, let alone the recommended amount). If that continues not being able to reproduce the problem I'll put one more check in the "pros" column. I was already considering trying an AMD video card as my next upgrade since my GT 240 is starting to get a bit old to do what I want with it, issues like this with one of my favorite games might just cement that decision.

[kevL]

well put, any chance you can borrow a non-nVidia card for a test?

[Glomoro Soravek]

Nah, but the integrated one on my motherboard is AMD and seems to use the same drivers as better cards I might consider getting. It can't get great framerate but it didn't crash despite my attempts to make it do so. Which probably says more since the performance was bad to start with on top of me trying to force a performance related crash.

[Glomoro Soravek]

Just an update, the exact same problem was sourced for the first system crash to happen without the game running since I started collecting data on this. Despite the connection between nvlddmk.sys and NWN2 that others have noticed, my problem seems to be a bit more general. Gonna have to start looking for information on this without NWN2 included as search criteria.

[kevL]

It's sounding more like hardware now. new vidcard -> and consider upgrading powersupply to 800+ watts.

/thoughts

[GFallen01]

kevL wrote...

It's sounding more like hardware now. new vidcard -> and consider upgrading powersupply to 800+ watts.

Well Watts aren't everything.

http://www.overclock...wer_Supply_Unit
http://psucalc.tk/

But frankly with these things a LOT of stuff can go wrong. Try out a stability test:

http://www.ozone3d.net/benchmarks/fur
http://www.mersenne.org/freesoft/

Also know that there are specialised forums for BSODs:

http://www.sevenforu...shes-debugging/
http://www.bleepingc...s/forum167.html

And quite a few others (use google)

Modifié par GFallen01, 06 août 2012 - 06:52 .

[kevL]

yeh, 650 watts from a good one is fine ... ( depending ) but after seeing two hard drives insidiously blown out I don't fool around with them anymore.

[Glomoro Soravek]

Sorry for not replying sooner, had some internet issues the past few days (if it's not one thing out here it's another). Looking back at the logs I misidentified a power outage because of a blue screen dump file from before then. I must not have noticed the date on the file, just that it had a different name than the one I had been working off of. I wasn't in the house when any of this happened and no one mentioned it until I asked why one of our clocks was slow by an hour.

I did just try stress testing with FurMark program linked above anyway, but even 30 solid minutes of that wasn't doing it. For comparison, it capped out at 62 degrees Celsius and 8-10 FPS using the settings I did, meanwhile NWN2 is crashing at about 41 degrees Celsius with the game going at 50-60 FPS on high settings. Now, it can fluctuate anywhere from mid 40s to low 70s, so I tried with vsync to see if I could keep that at a more stable number. Was keeping it pretty tight around 45 FPS that way but the crash is still occurring pretty rapidly if I mess with the camera angles suddenly.

I can't even get my computer to lag much in Arkham City, which is supposedly beyond my GT 240 for minimum specs. No crashes, no black screen while the drivers try to right themselves like I see if NWN2 doesn't crash to desktop or go blue screen. All the other games I have from before, during or after NWN2's prime time for still being officially supported seem to work just fine despite all my poking and prodding to produce this or any other crashes with them. I'm just as stumped as I was before the false alarm, and I think the solution is still probably what I said about continuing to save way too often until it's time to upgrade my video card for more than just one game.