Nwn>menu>play and then Crash (Vista)

[Legacy_oldNWNplayer]

               When I start nwn (also tried nwmain) I get to the menu *press play* I then get the logo lil' screen and nothing happens

Got everything on Admin + service pack something on2

I install'd it on Vista.

I had some problems first with gettin the new patch but now got version 1.69 (finally)

And another side note: I play'd / had this game already once before on this laptop

Can any1 help me plz I really would like to play this game again used to play it on the first few days of havin my Laptop
               
               

               

                     Modifié par oldNWNplayer, 12 novembre 2011 - 11:27 .
                     
                  

            

[Legacy_Knight_Shield]

               Try running the patch again and turn off your UAC.
               
               

               
            

[Legacy_oldNWNplayer]

               So like installing, again?
               
               

               
            

[Legacy_Knight_Shield]

               No I would just try running the 1.69 patch first ,not the whole game.
               
               

               
            

[Legacy_oldNWNplayer]

               Okay, well it's doing it without messages like aboard or ignore a specific file now so hopefully it'll work after this...
               
               

               
            

[Legacy_oldNWNplayer]

               You just solved my problem in 15 minutes
(me looking on forums for 2 evenings without a clue)

Your a genius '> yay!!!

Ty so much for your help x3
               
               

               
            

[Legacy_itsmeian17]

               I'm experiencing the same issue, and after about 6 hours of work, I'm no closer to getting the game running. Game was purchased through GOG games. I'm going to jsut copy/paste my post form their forum.

Just downloaded and installed, still encountering this issue
" Operating System: Windows 7 Home Premium 64-bit
System Manufacturer: Dell Inc.
System Model: Inspiron 518
BIOS: Phoenix - AwardBIOS v6.00PG
Processor: Intel® Core™2 Quad CPU Q8300 @ 2.50GHz (4 CPUs), ~2.5GHz
Memory: 6144MB RAM
Available OS Memory: 6142MB RAM
Page File: 2175MB used, 10107MB available
DirectX Version: DirectX 11

Card name: ATI Radeon HD 4600 Series
Manufacturer: Advanced Micro Devices, Inc.
Chip type: ATI display adapter (0x9490)"

Drivers have been updated, I've sought out and installed
the older directX 9 drivers (as I read somewhere that DX11 might not contain everything)
I've run the critical patch (and redownloaded it twice), with and without kingmaker, and even uninstalled .NET 4.0 as I read that it can cause compatibility issues.

I've changed safemovie to 1, tried compatibility modes on all the files to XP service pack 2 AND 3. Installed inside the Program files (x86) folder, and direct to a new folder on the C: drive. Tried different framerate and resolution settings in the config. Also opened the toolset first, thinking it might get something working correctly.
Admin access, and disabling visual themes and those other settings.
Been a busy 4 hours.
Once play is hit, (or nwnmain.exe is used), the process starts, but hangs at about 15.7k memory, and sits there, slowly sucking up more (after about 10 minutes, it's up to 16,432k)

Anyone know what the next step is?

(just tried disabling UAC, still no luck)
               
               

               
            

[Legacy_Lightfoot8]

               First try running the nwmain program directly with admin right and in XP mode.  If that does not work see if you can find the error in the event viewer.  

Wyldhunt wrote...
Have you checked windows event viewer for errors?
http://windows.microsoft.com/en-US/windows7/What-information-appears-in-event-logs-Event-Viewer

               
               

               

                     Modifié par Lightfoot8, 14 décembre 2011 - 10:03 .
                     
                  

            

[Legacy_itsmeian17]

               Event viewer has told me this (yup, tried in compatability modes for SP 2 & 3, in case one made a difference, tried launching it from literally every executable file in the folder):
Faulting application name: nwmain.exe, version: 1.6.9.0, time stamp: 0x486cfadc
Faulting module name: ntdll.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba58
Exception code: 0xc0000005
Fault offset: 0x0002e39e
Faulting process id: 0x984
Faulting application start time: 0x01ccbaa4c693443b
Faulting application path: C:\\GOG\\Neverwinter Nights Diamond Edition\\nwmain.exe
Faulting module path: C:\\Windows\\SysWOW64\\ntdll.dll
Report Id: 04520778-2698-11e1-b25a-0024e80be4db
               
               

               
            

[Legacy_wyldhunt1]

               That's a kernel issue. It sounds like you have something not quite right somewhere.
This can be caused by regestry errors or other software that utilizes the win API's, since they sometimes try to install new versions of base Windows components.

Do you happen to have (or ever had) any emulators or Wine installed on your PC?
I know that they can play around with the base OS stuff. So can a lot of antivirus software.
I once managed to start getting similar faults after I uninstalled Norton Antivirus.

Unfortunately, I'm not sure about the best way to fix it.

Does any of your other software ever act strangely/crash/fail/etc?
               
               

               
            

[Legacy_wyldhunt1]

               I did some Googling on the issue and it seems that drivers in general can cause this issue too.
I found this example of a similar problem:
http://www.sevenforu...-dll-error.html

They fixed it by unplugging their microphone, which was completely unrelated. It just happened that the mic drivers were breaking whatever process their other drivers were trying to access.

Try this:
Uplug everything from your PC that isn't required. Remove printers, external drives, microphones, etc. Just leave the monitor, keyboard, and mouse.
Re-boot your computer and try NWN.
If it works, start plugging stuff back in one at a time until it fails again. Then you know what isn't compatible.

If that doesn't work, try rolling back your graphics and /or sound drivers to an older version.
(If you haven't updated your sound drivers yet, update those first. Sound drivers can also cause issues.)
That will give you drivers that may try to do things in a different way that may not confuse your ntdll.

EDIT:
I also found multiple threads which discussed ntdll crashes caused by antivirus software. Most were different types of antivirus (AVG was mentioned a few times though). Unfortunately, it looks like disabling the antivirus isn't always enough to test. Often, they had to uninstall the antivirus software entirely to fix the issue.

So, there's something else to consider.
               
               

               

                     Modifié par wyldhunt1, 14 décembre 2011 - 11:03 .
                     
                  

            

[Legacy_Lightfoot8]

               It still looks to be a graphics driver problem. Try installing an eariler version of the driver.

EDIT:
Exception code: 0xc0000005  is a memory Access Violation

When ntdll  gets the error at Fault offset: 0x0002e39e  It seems to be related to the graphics driver more often then anything else.  
               
               

               

                     Modifié par Lightfoot8, 14 décembre 2011 - 11:54 .
                     
                  

            

[Legacy_wyldhunt1]

               I agree that it's probably your graphics driver. However, nearly everything I've read on the specific ntdll crashing issues on Vista have all been related to other software/drivers on the system which were blocking the failing driver (Graphics, in this case).
Here is an example thread of the types of things I'm talking about:
http://social.techne...2-244d5bc08d7f/
 
The 'cause' of the driver fault is nearly always a 3rd party program that is just incompatible.
 
I do, however, agree that changing graphics drivers may fix it since the drivers will be using a different technique which may not argue with the offending 3rd party software.
               
               

               

                     Modifié par wyldhunt1, 14 décembre 2011 - 11:55 .
                     
                  

            

[Legacy_Lightfoot8]

               @ wyldhunt:  Yes I have read a lot the them But they are at differand offsets then the 0x0002e39e.   nine out of ten times the  0x0002e39e is graphics related.  Is there a better error dump with that Event viewer?   I would love to get a better look at the call stack.   When I run NWN that location in ntdll never excutes on my machine.  It make it hard to trace back to where it is being called from.
               
               

               
            

[Legacy_Pstemarie]

               I'm starting to notice something a lot of these folks have in common - ATI cards...

As for installing to ProgramFiles(x86) - no, no, no!!! The GOG installer is fraked.

1. UAC MUST BE DISABLED BEFORE INSTALLING NWN.

2. The game MUST be installed to C:\\\\NeverwinterNights\\NWN. If you install the game anywhere else it seems to produce a laundry list of errors.

3. If you have to move the files there you also have to manually update the registry keys to point to the new location or the critical rebuild might not work correctly. Most often the critical rebuild will abort, other times its does a partial update and really messes up the game.

4. The GOG version tells you its 1.69. The GOG version is CORRUPT. You MUST run the critical rebuild.

5. Make sure you are setting compatibility mode on the .exe files, NOT the shortcuts. Only setup compatibility mode for nwnmain.exe, nwserver.exe, and nwtoolset.exe. Do NOT set compatibility mode for nwupdater.exe or nwconfig.exe.

6. The first time you run the game it should run the config utililty. This utility is broken for newer versions of Windows. After it runs you MUST go into to your .ini file and manually adjust some of the settings to reflect your hardware configuration and OS.

I have installed the NWN on several computers (6 of my own and an equal number belonging to friends) using my original disks, GOG Diamond, and Impulse Diamond editions. In all cases the above method was proven to make the game work in 100% of the installations.

Given the very nature of UAC anything you do in the venue of installing pre-Vista/Win 7 software or drivers (including Direct X 9.0c and OpenGL) risks being corrupted by this "security feature". The installers for such software and driver were designed to hve full access to your system. Under UAC, even when it claims to grant the level of access these installers require, it does NOT. Hence the reason for this message from Microsoft's own settings utility for UAC...

This is the original text from the setting window for UAC:

Not
 recommended. Choose this only if you need to use programs that are not 
certified for Windows 7 because they do not support User Account Control

The first thing I do with any computer, BEFORE installing anything is DISABLE UAC. I even disable before the first update gets installed.
               
               

               

                     Modifié par Pstemarie, 15 décembre 2011 - 12:29 .