WINDOWS XP PROBLEMS

Hello people.

I have an AMD 1.2 gig athlon machine running over 756 meg ram. Attached to this I have installed a Geforce 2 MX400 64 meg video card.

I have installed the latest Nvidia Detonator drivers. I believe it is version 23.1.2 from memory.

Everything runs fine however when I go into CS the machine commences to load the game and then locks up. A screen tells me the NV4.dsp has a problem with eiter the device or driver.

I have tried all drivers from the Nvidia range and all are the same.

I have tried a geforce 2 mx200 32 meg video card. Same thing happens

If I select software mode in cs it crashes. If I select Open GL it crashes. It did run for a short time in 3d mode but 10 minues later...it crashed.

I have tried everything I can think of including resolution etc to no avail.

Has anybody any ideas or perhaps may have had the same problem. The os XP version 2600 Corporate.

My hair is turning gray and I have aged over the last 3 days trying to resolve this issue.

Everything else runs fine and its damn fast but cs.

Thanks

try winding back the screen resolution before opening cs and see if that helps - also a good idea to end task any wierd apps that may be self starting on bootup - mind you, i've never had this sort of problem, but i might try and install cs on my workstation here to see if it does anything similar..

It seems like it's just an nVidia thing. No offence. I had a tnt2 running and got nv4_disp.dll blue screens every ten minutes. Literally. I just got rid of it and now have a friends voodoo5. Works fine now. But this prolly isn't the best thing for you to do, coz your cards worth a fair bit more than a tnt2. [Blocked image]

Well still have the problem and have decided to do something real radical. My mobo doesnt appear to like XP according to Gigabyte so I bought a late model flash arsed mobo.

I now have a spare for my 1.6 gig athlon server.

Well see how we go

i have a similar problem to you bob i have a geforce 2 MX 400 with a pentium 3 733mHz and when ever i play games (doesnt matter which one it is) it locks up then crashes (on XP as well)

when i was running windoos ME i never got a reason for this but with XP i get a reason which says

Nv4_disp.dll was caught in a infinite loop

to me sounds like the dll is on a merry go round but i aint getting any fun from it and im pissed

can anyone tell me why ???

google has plenty to say on the subject, mostly along the lines of people saying 'hey i changed this and it works'

bob old chap i share your pain heh it horrible aint it ? damn nVidia [Blocked image]

legendary paladin. trying some now. thanx mate

theres no way im taking my computer apart and swaping stuff =\

Whoa thats it.

Exactly the same problem. Exactley. Who wants to earn a nice big fat bottle of bourbon.

All you need do is fix it for me

Okay problem is the Nvidia card shares an IRQ with other devices notabley on my machine the sound card. According to seveal sources they suggest having the cards on their own irq.

Apparently this then fixes the problem.

Im going to try it

hmm.. Try this site
http://www.viaarena.com/?PageID=64
And read below the "What can be done?" part...

also give the viaarena forums a look over.. solutions MAY be found there...

TSUNAMI

Fantastic thanks Tsunami its the first time I have located a page where they show a possible step by step fix. Will give it a go

presumably you have a motherboard with a via chipset.. try a few different versions of the via 4in1 drivers.. another thing to try is to turn off ACPI in the motherboard bios.. cant think of anything else just now.

when i comes to bios and irq im lost i need someone to do it for me [Blocked image] *is dumb* and how the hell do i find out what a via chipset is ?

[ 21 February 2002: Message edited by: bLaCk kNiGhT ]</p>

my motherboard has a intel chipset

Bugga I say. There are 7 items sharing the same IRQ of 9.

Black Knight what operating system you running. I know how to do that bit with finding out the IRQ on your devices.

Might have to get soemone to show me how to seperate the IRQ as I have no F..ck..ng Idea.

I note that according to info I have recieved the VIA mobos are the ones most effected.

i remember some years ago having the irq conflict problem with realtek network cards, they tried to be PnP, but were shit at it, and ended up trying to hijack the IRQ's generally associated with com ports.

Best way i found to fix that was to enter system bios and disable PnP for the PCI slot in question, and manually assign an IRQ to the slot.

Its been years since i've had to do anything like that, but you may want to try it.

XP assigns all devices to one IRQ by default.. that where ACPI comes in.. it lets the operating system manage stuff like IRQ's.. disabling ACPI gives the IRQ control back to the BIOS. Often fixes problems like the one you describe :/

Hmm, disabling ACPI is the first thing I do setting up a new machine.

Second is I manually assign IRQ's in the BIOS.

That is do not share IRQ's for things like Gf2's SBlive's and the like. (These guys prefer their own separate accommodation, but they pay for it!)

Some device doesn't like IRQ sharing specially SB live-series.

Asus has "pre-set" IRQ sharing among its PCI slot, that you can't do anything about it. (except assign it to different number but NOT independently).

It has AGP1 sharing w/ PCI 1
PCI 3 sharing PCI 6.
PCI 4 sharing PCI 5.
PCI 2 seems to be the only "true" independent slot.

Using the info above and you should install your PCI device accordingly for better performance.
For example, if you have your SB on PCI 3, then try not to have other device on PCI 6.

Or if you have your SB on PCI 4 or PCI 5, then it will sharing IRQ w/ your USB device.

Excerpt above from Asus mobo's!

http://www.viaarena.com/?PageID=64
go here sponge should help you out