~~NV4 loop bug <--- not a VIA only problem !Where was that website with the fix? LQQK @ my setup tell me what you think!

[EXman]

OK I got the Dreaded Bug NV4 loop like 30-120 seconds into any 3D game. But 3Dmark always runs AoK! I have read others but nobody has the same setup/exact probs I do so give this setup a whirl!

I am Running XP pro
XP333-R
11/29 Bios (I heard alot of whining about the newer ones)
Mem timings to normal/auto (trying to take this out of the equation) on 2X 256mb Crucial 2100 @ 2.8volts
1.4 bird @ 10X150 (I lowered it to get better results no luck)
Visiontek GF3 ti200 (Damn it!) 23.11 Det
ADS Firewire/capture card
3com NIC
WD100JB-SE on Raid 1
Lite-On 163 DVD IDE0
Lite-On 24X CD-RW IDE1


This is a pain in the Arse and I thought the XP333 would be more Immune to this having the ALi chipset I guess I was dead wrong.

Also I had Rivatuner installed to boost performance and all it did was F*%$ stuff up and make my 2d bleed the page. so I nixed that mofo! I do not reccomend rivatuner in the least! stay away

 

[nj]

"Where was that website with the fix?"

Did you mean THIS page? It helps *some* people out, sure didn't help me.

You might want to try the brand new 27.30 XP drivers HERE, or go find the 27.00, 27.10 or 27.20's and try those. I had excellent results with 27.00's (IE cured my infinite loop problems somewhat), but my setup is completely different then yours.

 

[EXman]

AHHHH

 

[AA0]

It never was a VIA problem, its a nvidia problem. Just the VIA haters will make you think its entirely VIAs fault.

 

[Rand]

It never was a VIA only problem, it happens on VIA/ALi/SiS/and Intel chipsets. It's more frequently an issue on VIA and ALi chipsets, but occasionally it's seen with intel and SiS also.

Suggestions: Drop memory timings.
Drop to AGP 2X, or 1X as a last resort.
Drop AGP aperture size to 8MB or lower as a last resort.
Try DetonatorXP 21.81, 21.83, or 27.10... I've found those to be the least likely to experience the dreaded infinite loop.

 

[moejr]

I have 2 x 256mb of Crucial ram and the default voltage is 2.5v. You have yours set at 2.8v! Having the voltage set on your ram that high will cause them to overheat and maybe cause some instability issues. Try installing the newest 4in1 VIA drivers and download the updated windows xp nvidia drivers 23.12 from Microsoft. Those drivers are rock solid.

 

[EXman]

Someone is not keeping up with Mobos! Iwill XP333-R is an ALi chipset Mobo no 4 n 1's required!

thanks for the help though... and Ram used to run it at 2.9 on my EPoX... Crucial can take alot

 

[FlamingPanther]

My suggestion?
Get a radeon.


But seriously, to fix this you need to format and reinstall unless you know where the nvidia registry key is,
and where the driver files are, (including any *.INF's) so you can delete them

then install latest mobo drivers, latest creative drivers (if you have a creative card)
check that the Geforce has it's own IRQ, and that it's not sharing it with the sound card or HDD especially,

then last but not least, install the 27.xx WHQL drivers from windowsupdate.microsoft.com

Lots more info Here and Here

 

[EXman]

FORMATTING oh no not goof rather buy a damn Radeon!

never should have installed rivatuner! it screwed everything up!

 

[EXman]

and the tricks I have done so far have made it worse!!!!!

 

[Bucksnort]

I had same problem with detonators 21.83-23.11 . I installed det 27.20 and have had no more nv4_dsp.dll errors.

 

[AmdInside]

Its not just a Via problem but it seems like 95% of the times, when it happens it happens on a Via/NVIDIA combo. It is also not just an NVIDIA problem since I have a friend who has a Radeon and it happens to him. I've seen posts by non-NVIDIA users that it happens to them but not as frequently as NVIDIA users. Been through every beta driver and never had it happen to me. I have an nForce system and had an Intel 850 chipset prior to that, both with Geforce 3 Ti500 cards on WinXP.

 

[EXman]

I guess I'll Use Detonator destoyer and then bump up to a 27.3 driver.... cannot do worse than it is now!

 

[FlamingPanther]

Take a look at this guy's setup
Thread Title: NVOGLNT.dll Issues and Lock Ups with GF3 and WinXP