infinite loop...nv4_disp.dll errors

The above article seems to confirm that the problem associated with this is not known and inconclusive, which begs to question:

Do you think we are ready for space travel?

I had a daydream about travelling through space, on a futuristic shuttle, that has the capabilities of travelling close to the speed of light...only to be trapped in the center of our galaxy, where lies a black hole; sucking our ship into a "infinite loop". Where universal laws and time are intertwined for "infinity"

Just a thought from a frustrated PC owner

I post this thread, not only as a sarcastic commentary about my problem, but in hopes to read a miraculous set of tweaks, patches that you have done to resolve this issue without the use of voodoo dolls, witch craft or palm reading.

Thank you in advance

PS. I'll post what I have done to solve this as soon as I SOLVE IT...GRRRRRRRRRRRR!!!!

My motherboard is a Giga-byte GA7DXR and i'm actually working on it as we speak. It's a hybrid board that has on board audio, 20265 Raid chip, AMD761 Northbridge and Via686b southbridge. It's not the board but a combination.....

Originally posted by DarkArcher Please try to use a completely different stick of VERY HIGH QUALITY ram.

No generic or kingston.

I have solid evidence of Crucial shipped memory fixing this problem
in two epox instances with ddr geforce 2 a classic t bird and an xp amd.

just my 2 cents hope this helps

Click to expand...

It's not the memory but thank you for the input. Mushkin is by far the best memory I have been using for the past few years and have done sufficient memory test in dos to confirm that they are in order. If you want a copy of the membory test, you can get it here:

I´m new to this forum..and I think it seems very interesting and well worked out.
About this problem with the nvdisp and the infinte loop....have heard alot of people who also have this problem..and most of them only needed to pu the "agp aparautre size" in bios settings to 128 or 256 and that solved the problem.
I´ve never had this problem...I really don´t know why but I´ve always had that setting in bios and since I´ve installed XP I´m running my GF3 with the 22.50 drivers....they are giving me the best performance...have tried most of the drivers from nvidia.

I was experimenting with different memory values in bios without any success but finally removed one of the 512MB DDR 2100 from the board. It worked perfectly!

Mad Onion 2001 played in a continous loop for well over 2hours without a hitch, scoring 7989 without overclocking my CPU or my video card.

I proceeded to install a few games, Half Life and DeuceX without any problems!

I decided to switch DIMMS to see it the second one was defective, but it worked perfectly as well.

I decided to install the second DIMM in slot #3..AND IT WORKED TO MY SURPRISE:Q

Question

WHY?

Could it be that by playing Mad Onion on the 1 DIMM successfully for over 2hours, that WindowsXP may have adjusted itself to accomondate the task?

Could it be that the 1st and 2nd slot conflict? Which doesn't make sense because prior to re-installing WindowsXP on the exact same hardware conditions, I had both DIMMS in slot 1 and 2 without any problems.

Not "a" slot but a combination of 1 + 3 slot. 1+2 is unstable. I did a little research on this and found out that the reason for the problem with DIMM slots 1 and 2 could be that they
are mapped to the same controll arbiter, originally, the AMD 761
supported only 2 DIMM slots and depending on how the individual banks are mapped internally (either 1+2 / 3 or 1 / 2+3 depending on the manufacturer) there is more overlap which causes the problems.