Cryodude
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
Gothmog88
Well, MS update drivers were worthless, but the 22.80 drivers seem to be the most stable for me. I still get a few BSODs, but not nearly as bad as before. Hopefully more stable drivers are in the works.
Vampy
Now only see bsod when changing between 3d screensavers with 22.88 drivers...mmmm. Better than it was though!
Dazultra2000
AHA!
people on the same subject.
I STRONGLY urge you to go here and read through, and if possible divert ALL efforts on this problem to THAT forum.
It has been going for AGES, and we have narrowed it down quite a long way. I only request that you read the WHOLE thing (7 pages so far) to get up the same level as we all are. Thanks.
http://www.icronticforums.com/showthread.php?threadid=14427
people on the same subject.
I STRONGLY urge you to go here and read through, and if possible divert ALL efforts on this problem to THAT forum.
It has been going for AGES, and we have narrowed it down quite a long way. I only request that you read the WHOLE thing (7 pages so far) to get up the same level as we all are. Thanks.
http://www.icronticforums.com/showthread.php?threadid=14427
DosFreak
Thanks for the link to that thread.
I've been EXTREMELY busy for the past 2 weeks and will continue to be for the next 2. So during this time I only have access to my home computer for about 2 days in the week. Due to all the catching up I have to do in Computer stuff during that time I haven't played around with XP for about 2 weeks. ALL of the fixes listed in that thread I tried when I installed the final of XP Pro sometime last month. None of it worked. I haven't bothered with XP since then (although I MIGHT tonight). Oh, It's most definetly not the VIA GART because I switched that out first thing with the 4-in-1's when I experienced the problem. It still happened. Never had this problem with any of the RC's. Also tried with ACP Multi/MPS Multi. (Only reason I list these 2 is because they are scarcely mentioned in the link you posted.)
This is an XP/NVIDIA problem that the 2 companies need to work together on. It's extremely doubtful that we will find a fix.
Well, I'm off to my home to consider on wether on not I should waste my time on the POS that is XP!
I've been EXTREMELY busy for the past 2 weeks and will continue to be for the next 2. So during this time I only have access to my home computer for about 2 days in the week. Due to all the catching up I have to do in Computer stuff during that time I haven't played around with XP for about 2 weeks. ALL of the fixes listed in that thread I tried when I installed the final of XP Pro sometime last month. None of it worked. I haven't bothered with XP since then (although I MIGHT tonight). Oh, It's most definetly not the VIA GART because I switched that out first thing with the 4-in-1's when I experienced the problem. It still happened. Never had this problem with any of the RC's. Also tried with ACP Multi/MPS Multi. (Only reason I list these 2 is because they are scarcely mentioned in the link you posted.)
This is an XP/NVIDIA problem that the 2 companies need to work together on. It's extremely doubtful that we will find a fix.
Well, I'm off to my home to consider on wether on not I should waste my time on the POS that is XP!
Dazultra2000
As we found in the thread, it's not just limited to nVidia either!
We have a user reporting the problem on a 3dabs Oxygen card, however, I am yet to hear of it on a PCI card (or AGP cards that act like PCI - meaning the 3dfx voodoo/velocity series).
So it is a XP/Full AGP card problem that we are faced with. As we have found, disabling fast writes seems to help, but will not dismiss the whole thing.
i wonder if microsoft check those error reports?
We have a user reporting the problem on a 3dabs Oxygen card, however, I am yet to hear of it on a PCI card (or AGP cards that act like PCI - meaning the 3dfx voodoo/velocity series).
So it is a XP/Full AGP card problem that we are faced with. As we have found, disabling fast writes seems to help, but will not dismiss the whole thing.
i wonder if microsoft check those error reports?
Vampy
Cheers Dazultra2000: Thanks for the link. Will go and look. Yeah have seen it on an Oxygen card also, which uses Nvidea chipset.
lammypie
yeah I've been getting this as well.
Each time it happens I send a bug report to Microsoft, and fill in my contact details so they can get back to me.
However most times their website packs up so I've only been able to give my contact details for 3.
If you have done this you can check the status of the problem by going to http://oca.microsoft.com/welcome.asp
If everybody always submits the report even if its anonymously then hopefully the pressure will be on to fix it!
Each time it happens I send a bug report to Microsoft, and fill in my contact details so they can get back to me.
However most times their website packs up so I've only been able to give my contact details for 3.
If you have done this you can check the status of the problem by going to http://oca.microsoft.com/welcome.asp
If everybody always submits the report even if its anonymously then hopefully the pressure will be on to fix it!
Udo Kammer
Quote:
yeah I've been getting this as well.
Each time it happens I send a bug report to Microsoft, and fill in my contact details so they can get back to me.
After only 8 weeks I have changed my first graphiccard with Nvidia-Chipset Geforce 2 MX400 to an ATI Radeon 7500 and all problems are gone.
yeah I've been getting this as well.
Each time it happens I send a bug report to Microsoft, and fill in my contact details so they can get back to me.
After only 8 weeks I have changed my first graphiccard with Nvidia-Chipset Geforce 2 MX400 to an ATI Radeon 7500 and all problems are gone.
auky
i'm a voodoo3 user and i'm getting the infinite loop problem. any solutions for this issue???
TomAL
Cryodude - yeah it also happens on gf3s i have a elsa 920 and i only get it with the 22.* series of drivers. the problem doesnt happen any other time.
Tom
Tom
Ronenn
I started having this after up[censored] the bios on my MB(Abit KT7-Raid.I Remembered having a similar problem with a Bios upgrade while running Win 98 and I fixed it by Changeing the AGP Driving Strength Signal in my Bios.I have Hercules 3 Prophett II Ultra 64.Set my AGP Driving Strength to E7 and havent had the error since.Hope this helps someone out there.
ahearnb
I just started a new post on this, but forgot to search.
One question: Has anyone asked about soundcard conflicts in all of this? You guys know a hell of a lot more than me, but I thought I had this problem ONLY in Max Payne. (Turned out to be wrong...) But, I could make it happen all the time when playing that game. I tried taking out my soundcard...NO BSOD. So I thought there was a soundcard/video card conflict only in this game. Do the people that don't have problems have a Soundblaster soundcard?
Maybe if you post the soundcard you use, we could narrow it down. I am using a SoundBlater Live! 5.1 X-Gamer.
Another idea, at least...
Brad
One question: Has anyone asked about soundcard conflicts in all of this? You guys know a hell of a lot more than me, but I thought I had this problem ONLY in Max Payne. (Turned out to be wrong...) But, I could make it happen all the time when playing that game. I tried taking out my soundcard...NO BSOD. So I thought there was a soundcard/video card conflict only in this game. Do the people that don't have problems have a Soundblaster soundcard?
Maybe if you post the soundcard you use, we could narrow it down. I am using a SoundBlater Live! 5.1 X-Gamer.
Another idea, at least...
Brad
DosFreak
Nope, Same error with Hercules Gametheater,SB Live!, SB Audigy.
Dazultra2000
I want you to try the 23.10 detonators (if you have an nvidia gfx card) as it seems to have fixed my problem, as well as quite a few others.
Also, VIA have reported that they have found a fix in the BIOS code, and are testing it extensively now to sort it out. If all goes well, we can expect BIOS updates with the fix shortly...but for now, try the 23.10s
Also, VIA have reported that they have found a fix in the BIOS code, and are testing it extensively now to sort it out. If all goes well, we can expect BIOS updates with the fix shortly...but for now, try the 23.10s
TomAL
yeah tried the 23.10's worked with no problems looks like i have bypassed the 22.X's
Tom
Tom
ahearnb
I just updated my SBLive drivers with the new ones that are now out. And switched to the 23.10 Dets. Now, I didn't get the BSOD in Max Payne, BUT it did freeze....just didn't get the error message....oh well.
Brad
Brad
Dazultra2000
Well, hopefully in conjunction with the new BIOSes to be released soon, it will disappear totally
lammypie
Hey Dazultra
I was just logging in here to tell everyone about the planned BIOS updates from VIA to fix this thing, and guess what, I found you beat me to it.
Its good to see some people from Icrontic here also.
I was just logging in here to tell everyone about the planned BIOS updates from VIA to fix this thing, and guess what, I found you beat me to it.
Its good to see some people from Icrontic here also.
Dazultra2000
hehe. Ner ner
DosFreak
Yep, with the 22.80's and 23.10's the computer locks but the cursor can still be moved. No blue screen but the computer is locked.
