Anyone good at decyrpting Dr. Watson logs?

[Xorcist]

I've asked this over at more game related forums, but no one is technical enough to give me an serious answer. I figured maybe someone here might have a clue. Neverwinter Nights (nwmain.exe) generates the following error at various times and then exits:

Error Message:
http://www.eden.rutgers.edu/~xorcist...s/ErrorMsg.png

mostly upon loading between modules, loading games, or dealing with inventories, but it has happened at other points. The corrosponding Dr. Waston log is as such:

Application Log:
http://www.eden.rutgers.edu/~xorcist...s/DrWatson.png

Dr. Watson Log:
http://www.eden.rutgers.edu/~xorcist/Images/dump.txt

This is always the Dr. Waston error generated. Same error, same memory range, always faults at same place. Just wanted some insight as the MS knowledge base gave me little to none. My system specs are listed below if needed.


Game Version: 1.30.7041
Game Language: English

Motherboard: Shuttle AV49N
Chipset: VIA P4X400 + VIA VT8235

Processor Manufacturer: Intel
Processor Type: Pentium
Processor Speed: 2.4Ghz (533FSM)

Operating System / Service Pack: Windows2000 with SP2
System RAM: 512MB DDR400 (Corsair)

Video Card Manufacturer: Sapphire
Video Card Model: "Atlantis" Radeon 9600 Pro
Video Card RAM: 128MB DDR
Video Card Driver Version: 7.90.7-030625a-009907E (wxp-w2k-radeon-7-90-ogl-hotfix.exe)

Sound Card Manufacturer: Turtle Beach
Sound Card Model: Santa Cruz
Sound Card Driver Version: 5.12.1.4193

Other important information:
DirectX 9.0a installed
OpenGL version is: 1.3.3803
AGP Bus set at 4x (Fast Writes OFF)
Error happens even with sound disabled


More: It seems to me the RtlSizeHeap function is the culprit, though I can't be completely sure. Anyone know what this function normally does or is called for?

[Steve R Jones]

Have you been to Neverwinter Nights web site support section?

[Siliconjunkie]

Mine has always done this from time to time. Maybe 1-3 times in a night. I have just learned to live with it.

[Xorcist]

Of course I've been to the NWN support site

I even e-mailed a detailed report to tech support, but have yet to hear anything back from them. I just wish I knew why it was happening. It took me two weeks just to get the game to run tweaking my AGP settings, Video card drivers, OpenGL versions, In-game settings and so forth. Finally now that I have it running (some-what) I have to put up with this crashing, which seems to be directly related to the allocation/deallocation of memory.

I've run SimmTester's DocMem v2.0, so it's not a problem with my memory as all the tests passed with flying colors. I guess I'm just going to have to live with it myself as well, but it sure would be nice to know why it's happening, I mean if it's an issue with Bioware's coding, at least I'd know it's not my system...

The thing that get's me is the fact it's the same error every single time:

FAULT ->77fcb9b1 8901 mov [ecx],eax

and although it's occurance in the game is random, that assembly command on that memory location is always constant when the error does rear it's ugly head.

[Siliconjunkie]

It's not your system. Mine has done it on 2 completely different boxes. Very frustrating indeed. Great game, but things like that can make it tedious to play.

[Xorcist]

What are the specs on those systems? Just so I can compare with my own.

I'm wondering if the fact I'm running a FSB of 133Mhz for my P4 2.4b clashes with the fact I'm running my memory at 200Mhz (Corsair 512MB DDR400). I know the VIA P4X400 chipset should be able to handle this fine... but maybe I should sync the two up to see if I get better results.

What do you think?

[Eraserhead]

mmm, yes, I'd try running your RAM at the same speed as your FSB. It's definitely NWN that's the problem rather than anything else on your machine. I suspect it's having trouble processing those register operations at your current memory speed.

[Xorcist]

well tried that, didn't help any though... I'm thinking it might be a DirectX issue... can't be completely sure though.