kmode exception error - nv4disp.dll

[kanonfodda]

Lo guys, need some help. I've got a new GFX card (geforce 4mx440) and I keep getting exception errors, it is also booting me back to windows when playing games. Any directX game wil lcause it to crash, but it is never the same time span from start of play to error.

Any help, or known problems. I am running the 30.82 dets at the moment, but have also tried the 40.72, with no luck. If I swap out the GFX for my old GF2GTS, it still gives me the same error

HELP!!

System specs:

AMD Athalon 1.4
512mb SDRAM
2*30gb Diamon Max 8 HDD (Raid 0)
SB Live
ISDN card (not in use)
Netgear 311 Network Card

Os = Win 2K

Any help would be greatly appreciated.

 

[Embattle]

What Motherboard do you have?
Did you reinstall W2K recently, like when you changed the GFX card?

 

[kanonfodda]

Knew I had forgotten something from the system list

Mobo is Abit KT7A-Raid (not 1.3)

Been running 2k for about 12-18 months, recently changed from GF4 to GF2. GF2 was stable, GF4 isn't with same drivers, and now the GF2 crashes as well

 

[Embattle]

Perhaps time to reinstall, it might clear the problem. I've heard of problems with nvdisp.dll and the loop of death but that blue screens the computer which doesn't happen in this case.

 

[Embattle]

Have you tried totally uninstalling the drivers and then starting up on VGA then installing them again?

 

[kanonfodda]

Erm, does rebuilding the whole system from scratch onto brand new, blank hard drives count

I'm running on a totally virgin system, no existing dets installed, clean OS, very little software.

Same error from intitial driver install

 

[(Shovel)]

I've got the same motherboard (also not 1.3) and running a GF4 Ti4200 on XP and I've got no driver problems at all - even with those 40.41 betas.

I don't know how helpful that is as I don't know how similar the Ti is to the MX. Since you've been quite drastic why not try reformatting and starting again with the GF2 card and check that that will work again. You might be able to narrow it down whether it's the card or driver - or something else.

 

[WPKenny]

There's a BIOS revision for the motherboard which makes it more compatible with the GeForce series of gfx cards. Go grab it here....


ftp://202.168.194.114/pub/download/fae/kt7a9.exe

 

[kanonfodda]

Thanks Kenny, I'll give it a try

I will probably re-format again, after this weekend (hosting a LAN ). See if I can make it more stable.

It seems to be more stable now.

/edit - def seems more stable, but still crashing

btw - GFX is a chaintech card.

 

[kanonfodda]

I Lied about it being more stable

I have looked at the resources, and all my cards (sound, GFX, network) are using IRQ 11 - any chance this could cause it??

Bios is set to allow OS to assign IRQ's. Anyone know any good troubleshooting websites??

Thanks for the help guys

 

[Testin da Cable]

no worries there. irq sharing is normal these days. iirc windows likes 11.

 

[kanonfodda]

Just been reading Guru3D forums, it says that if the sound card and GFX card are sharing an IRQ, it will create this error, any ideas on how to change the IRQ of one of them? Windows won't let me (greyed out)

 

[xane]

You can change IRQs using the BIOS, as long as there isn't a conflict Windows will not change it, however, you normally end up shuffling all the IRQs in BIOS to get it like this.

 

[Testin da Cable]

iirc windows won't even let you change it. iirc I bitched about this yonks ago

 

[kanonfodda]

Tdc is right Microshaft windows won't let me change the IRQ settings for anything

Just changed the BIOS, set the Sound Card to 5, didn't take.

so, basically I am shafted, what a great operating system. If Linux was easier to setup, I would be using that, I am really fed up with Windows

 

[Testin da Cable]

what you could try is this: put the soundcard in a different pci slot, drain the cmos and poweron. you may have to set stuff in the bios again and windows may bork on you. what the hay tbh. it's borking on you now anyhoo. good luck mate. tis the only thing I can think of.

 

[kanonfodda]

Just did that, Windows didn't bat an eyelid (or change an IRQ).

F*cking useless operating system

Ho hum, will have to see what else people can suggest.

Thanks for the help guys

 

[xane]

Changin just one slot is actually unlikely to help, as I was trying to say, you normally end up assigning IRQs manually to ALL the slots and then shuffling them until Windows doesn't fart with it.

I'm sure there is some registry entry that turns off IRQ steering.

Edit: just remembered I think the PCI bus properties in Device Manager may allow you to turn it off, not sure about W2K tho.

 

[PR.]

There is a registry hack to allow the altering of IRQ and stuff. Don't know were you can find it or what it was tho

Sorry

 

[kanonfodda]

Thanks for all the help peeps, I think I have got it sorted.

Basically I had to switch off ACPI in windows, this then used the IRQ's that I had set in the BIOS, and Ican now play games again

Thanks again all