NVOGLNT.dll Issues and Lock Ups with GF3 and WinXP

[jjkeefer]

I currently built a new machine, AthlonXP 1800XP+, Soyo K7V Dragon Plus, 768mb PC2100 DDR, Gainward GF3 Ti200 with 128mb and WinXP as my OS. Everything works fine, but when I play games, like Q3A and HalfLife, I'll get crashes and the source of the crash is NVOGLNT.dll. Looking at it I can see it's the Nvidia OpenGL drivers that I am using. Is there a way to prevent this?

The Current drivers that I am using are: 23.11 from their site
and my motherboard is currently has it's AGP configuration:
Aperature: 64mb
Mode: 2X
Driving: Auto
FastWrites: disabled
Master1 WS Writes: disabled
Master1 WS Read: disabled
Post Write: enabled

The only 2 things I can think of that could cause this are the drivers and possibly an IRQ issue. I'm not facing any conflicts but on IRQ11 I have my video card, on-board sound and NIC card.

If anyone has any suggestions I would be very grateful.

Thanks

 

[gunf1ghter]

well, I'm not sure about your NVOGLNT.dll problem... most folks have been having probs with NV4disp.dll locking up in those games.

I myself fought an isue with the NV4disp.dll locking up for several months... it turns out that my RAM could not handle running 2-2-2 timings (crucial ram) and when I lowered the timings to 3-2-2 the system completely stabilized.

It seems that any weakness will cause a lockup on WinXP with DX8

 

[FlamingPanther]

Format and Reinstall!

Seriously, Remove all traces of the 23.11's like the registry key, the inf's and the driver files,
The "Add/Remove Programs" control panel applet should have an option to remove the nvidia drivers,
then, install the latest VIA 4n1's from their web site, then install the 27.30 NED's
that should help some.

also, is 64Mb the lowest you can get your agp aperature?
go as low as you can.

It's true that this is a timing issue in the Nvidia drivers, so lowering any mem timings should also help a little.

 

[jjkeefer]

I thank you all for the suggestions..but I managed to fix it..I think. Out of a last measure attempt, I took out one of my 256MB Sticks of RAM and now everything seems to be working fine. No error messages nothing *knock on wood*

I've even been using AGP4x and Fastwrites.

 

[BFG10K]

It could be a problem with your motherboard - a lot of vendors making VIA chipsets have problems with stability when all 3 DIMM slots are filled.

 

[Mem]

<< thank you all for the suggestions..but I managed to fix it..I think. Out of a last measure attempt, I took out one of my 256MB Sticks of RAM and now everything seems to be working fine. No error messages nothing *knock on wood* >>



Make sure you`ve all video shadowing and system bios cacheable disabled in bios, this has been know to help sometimes when you`ve all 3 banks full.

 

[FlamingPanther]

Pokeing through the drivers I have come across what appears the be the reason,
for this massive bug thingy

tracking the drivers' steps it seems the error is in the AGP texturing.
Or when the GF sends textures to, or even accesses something stored in,
main memory, something happens.

I'm not sure if it has to do with fast writes or what,
I say that because fast writes bypasses the CPU when the card needs to access main Mem.

strange as it seems, i think the GF drivers are trying to make all the timing decicions themselves.
that would be rather bold, the northbridge would be able to time these things a whole lot better
than a piece of software, that is its job anyway.

This would not work very well(if at all) in high speed systems,
especially overclocked systems it seems.
(meaning where the AGP bus would be overclocked as a result of a FSB overclock)

the issue seems to be compounded when a second stick of ram is present,
not sure why just yet, maybe the drivers (if my theory is correct) aren't able to correctly account for
mutiple pieces of ram?

also, large sticks of RAM seem to make it worse as well,
A single 512Mb ECC registered stick would not work at all, but 2x256Mb sticks (NON ECC or REG)
would work for a longer period of time before crashing.

*please note all sticks are high quality Micron, with 7Ns chips capable of 2-2-2 timings,
timings were set to 3-3-3 for theses tests though...

strange, I am going to keep testing and looking though this stuff,
I will probably try to borrow a friends GF2 ultra and a GF3 TI200
(i have a GF3 that I am using for all these tests)

BTW, I used a hex editor, and basic knowledge of assembly language to make rough guesses about
when and where the drivers are failing, I can't be 100% sure about it though.

 

[Insidious]

<< I've even been using AGP4x and Fastwrites. >>




I had been led to the belief that Det. 23.11 will not enable fast writes on a GF3 even if you tell your MoBo BIOS to do so.

Are you sure you are actually using fast writes?


Have you been using a tweak utility? (If so, always back out of your tweaks if things don't seem to be acting just right)

 

[FlamingPanther]

Computers run on magic smoke,
I have let the magic smoke out of my computer.
blast it.
so, I won't be able to do anything for a few days
(besides this post)