WinXP 'nv4_disp.dll' Infinite Loop Crash
Anyone else getting this BSOD in XP? Seems to be driver related. Anything other than the native Geforce (12. 40) drivers eventually will crash XP with WinXP 'nv4_disp. dll' Infinite Loop message. Any ideas would be appreciated It happens at stock speeds also, not just overclocking.
Anyone else getting this BSOD in XP?
Seems to be driver related. Anything other than the native Geforce (12.40) drivers eventually will crash XP with WinXP 'nv4_disp.dll' Infinite Loop message.
Any ideas would be appreciated
It happens at stock speeds also, not just overclocking. Have also tried raid and non raid with same results.
Have seen this in other threads, but have yet to find a solution
system specs are as follows:
A7V133A - OCZ Gladiator
512 PC 133 Mushkin (Cas 2)
Win XP Pro
1.4 @ 1575 (10.5 * 150)
Hercules Prophet Pro (230/460)
Raid 0 (2-WD 40 ATA 100's)
2 - WD 60 ATA 66 (mp3 drives)
Plexwriter 12/10/32A
Intel Phoneline Nic - Slot 2
Turtle Beach Santa Cruz - Slot 3
Linksys Ethernet - Slot 4
Altec ADA 305s (USB)
Cooler Guys Gamer Case
Seems to be driver related. Anything other than the native Geforce (12.40) drivers eventually will crash XP with WinXP 'nv4_disp.dll' Infinite Loop message.
Any ideas would be appreciated
It happens at stock speeds also, not just overclocking. Have also tried raid and non raid with same results.
Have seen this in other threads, but have yet to find a solution
system specs are as follows:
A7V133A - OCZ Gladiator
512 PC 133 Mushkin (Cas 2)
Win XP Pro
1.4 @ 1575 (10.5 * 150)
Hercules Prophet Pro (230/460)
Raid 0 (2-WD 40 ATA 100's)
2 - WD 60 ATA 66 (mp3 drives)
Plexwriter 12/10/32A
Intel Phoneline Nic - Slot 2
Turtle Beach Santa Cruz - Slot 3
Linksys Ethernet - Slot 4
Altec ADA 305s (USB)
Cooler Guys Gamer Case
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
Exactly, dosfreak.
This problem is getting WORSE instead of better!!!! I ONLY had this problem when playing Max Payne at first. In an effort to fix that, I started getting the BSODs in Windows when not playing games - just out of the blue. It was infrequent, but bothersome nonetheless. Now, I get them ALL the time when I play Madden NFL 2002. It is starting to piss me off.......WHY?!?!?!?! Don't tell me I'm gonna have to install Windows 98SE. This is bullshit. I just want it to work!!!!!!!
Brad
This problem is getting WORSE instead of better!!!! I ONLY had this problem when playing Max Payne at first. In an effort to fix that, I started getting the BSODs in Windows when not playing games - just out of the blue. It was infrequent, but bothersome nonetheless. Now, I get them ALL the time when I play Madden NFL 2002. It is starting to piss me off.......WHY?!?!?!?! Don't tell me I'm gonna have to install Windows 98SE. This is bullshit. I just want it to work!!!!!!!
Brad
Sorry for my english i'm french ;(
try this, i had this problem on WIn XP with Geforce 2 TI leadtek with MSI mainboard with VIA chipset.
I have install 21.83 detonator, via 4in1 and i have in BIOS VIA.
Put off the AGP *4, i have put *2 and i works but power decrease but i work (only 50img/s on Unreal tournament)...
But on win2K with 21.83 with AGP *4 it work (110 img/s)
it's AGP VIA/XP nividia incompatibility
try this, i had this problem on WIn XP with Geforce 2 TI leadtek with MSI mainboard with VIA chipset.
I have install 21.83 detonator, via 4in1 and i have in BIOS VIA.
Put off the AGP *4, i have put *2 and i works but power decrease but i work (only 50img/s on Unreal tournament)...
But on win2K with 21.83 with AGP *4 it work (110 img/s)
it's AGP VIA/XP nividia incompatibility
Actually I think you'll find it's just not CERTIFIED. They are official release drivers because they are on Nvidias own site!
The error in XP is just to tell you that microsoft haven't certified it (big whoop).
The error in XP is just to tell you that microsoft haven't certified it (big whoop).
Interesting. I've never seen this error on my machine. I'm having trouble telling by reading the thread... is it so far only NVidia boards that are having the problem? I've got a voodoo5, KT7 MB, AMD 750 processor and it seems rock steady. The only blue screens I've seen since installing have been from ejecting the CD too early after installing something (IE Please put CD-ROM vol # blahblahblah back in the drive)...
It seems to really only happen on FULL AGP cards, such as any nvidia agp card, or an ati agp card etc.
A 3dfx card is basically a fast PCI card, and so doesn't seem to be open to the same problem.
A 3dfx card is basically a fast PCI card, and so doesn't seem to be open to the same problem.
Yeah, I tried the new 23.11's too. No luck. I even tried this patch - http://forums.viaarena.com/messageview.cfm?catid=13&threadid=4123
Brad
Brad
Seems to be a problem that occured AFTER I used the automatic Windows Update. I have used XP a couple of months before (build 2600) with the 12.41 drivers (even 12.90): I had NO problems...
Yesterday I installed XP again, ran the Updater, installed some stuff and put the 23.11 on it. BAM: BSOD within 10 seconds after reboot.
I have a GF2-MX400 Asus, btw. I installed the 12.41 afterwards, the PC hanged, no BSOD but just froze at some point.
Yesterday I installed XP again, ran the Updater, installed some stuff and put the 23.11 on it. BAM: BSOD within 10 seconds after reboot.
I have a GF2-MX400 Asus, btw. I installed the 12.41 afterwards, the PC hanged, no BSOD but just froze at some point.
i remembered back when win2k had agp problems and amd/microsoft came out with a reg patch that fixed it...perhaps doing this again will solve the problem?? the only reason i thought of this is cause when i installed win2k with sp2 on my pops pc i still had the agp problems till i went and installed the reg patch. and also, i don't have that problem you guys have and thinking maybe cause i did a 2k->XP update instead of a clean install...anyways..just a thought tho maybe it doesn't matter...but something to try anyways
Yes, this has been tried, and unfortunately...doesn't work
