BSOD with Neverwinter Nights

[dupla_X]

Hi,

I have installed Neverwinter Nights Diamond Edition yesterday, couldn't get it to work. First I had problems with "nwnmain.exe stopped working" but I figured that out.

The problem is whenever I start the game it goes through the intro sequence with the logos and when it has to load the main game it crashes with BSOD.

"Page fault in nonpaged area" blue screen viewer says it's from the ntoskrnl.exe. I understand that it's some kind of memory problem. I have 4*4gb sticks, tried to swap them all around, tried to use only 1 stick (different kinds) still not working, same BSOD every time, so I think my RAMs are good, also no other program produce this crash.

I tried to reallocate the pagefile for someone it's working but not me. Also I tried to upgrade the drivers of my vga, still nothing. Also I had my rams forced in Bios to be 1600mhz and cl9 timing, but I have set them back to auto.
Temperatures are good, no overclocking, ssd, hdds healthy condition no bad sectors.

My specs:

Asrock 970 extreme 3
Amd FX-8320
Xfx 280x DD edition (not the OC one)
2*4 Gb Corsair Vengeance 1600mhz, 2*4 Gb Klevv 1600mhz
Samsung 850 Evo 250Gb, 2*1 Tb Hdds
Be Quiet 630 pure power

My last dump file:
https://www.dropbox.com/s/uxkbh2j9enodlp0/010516-14071-01.dmp?dl=0

Please help if anyone can.

 

[johnbl]

note: the system timer indicates the machine was booted for 1 min 21 seconds before it bugchecked.

the device driver that crashed was
\C:\WINDOWS\system32\drivers\ddkmd.sys Mon Nov 02 21:18:18 2015
it is a driver from osbase i think. http://osbase.com/

mini memory dumps do not save USB info, only kernel memory dumps do.
(assuming it is a USB device, I really don't know)



machine:
BIOS_VERSION: P1.70

BIOS_DATE: 10/12/2012

BASEBOARD_MANUFACTURER: ASRock

BASEBOARD_PRODUCT: 970 Extreme3

if your device is a usb device put it on a usb 2.0 port not the usb3.0 port you have on your machine. most versions of usb 3 require drivers and a BIOS dated after about march of 2013 to work correctly with current usb devices. Your BIOS is old, and the USB 3 chip on your system also does not have a updated driver.

your motherboard ethernet driver is also very old
Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC
Rt64win7.sys Thu Apr 21 11:15:33 2011
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false

you might also want to update your bios to the last release p1.80
http://www.asrock.com/mb/AMD/970%20Extreme3/?cat=Download&os=BIOS

 

[dupla_X]

Update.
Whocrashed says:

On Wed 2016.01.06. 9:01:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010616-13119-01.dmp
This was probably caused by the following module: ddkmd.sys (0xFFFFF880127C98E5)
Bugcheck code: 0x50 (0xFFFFFA880E4876F0, 0x1, 0xFFFFF880127C98E5, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\ddkmd.sys
product: OSBASE iDisplay Software
company: OSBASE
description: OSBASE WDDM Kernel Mode Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ddkmd.sys (OSBASE WDDM Kernel Mode Driver, OSBASE).
Google query: OSBASE PAGE_FAULT_IN_NONPAGED_AREA

Now, I have an app for iPad called Duet Display (makes my device a secondary screen). I believe this thing uses this iDisplay software/driver. I turned off the app both on iPad (wasn't even on in the first place) and on my PC, still not working.

 

[dupla_X]

I have updated all drivers to the most recent ones I could find, also the BIOS to 1.80. Only using USB 2 ports now for the mouse and keyboard. Still nothing.

 

[dupla_X]

Ooooookay. Removing DuetDisplay solved the problem, nwn works like a charm. Last thing I ever believed. Never seen such BS before. Thanks anyways.

 

[dupla_X]

One more thing, if anyone has the same problem. You can keep both programs (Duet and Nwn) running if you force Nwn to start in windowed mode by adding/modifying these two lines under [Display Options] in the nwn.ini file:

FullScreen=0
AllowWindowedMode=1