StrikerMan780
10-08-2008, 03:12 PM
I've been getting this problem for a while now, and a Complete PC wipe and windows re-install hasn't resolved it. I think GOW has an issue with 8600 GT Cards or the recent NVidia Drivers... Anyhow, here are my relevant specs:
AMD Athlon 64 3200+ 2.1ghz
1.5 GB pc3200 RAM
nVidia NForce 4 Ultra AMD Chipset
NVidia GeForce 8600 GT
Windows XP Pro SP3
ForceWare 178.13
NVidia PhysX
Now, Here's the problem... I can play Gears for a varying amount of time, sometimes a few hours, sometime only 5 to 15 minutes, until which Gears of War's Graphics get Highly corrupted (Textures going white, Translucent Texture being plastered on the screen blocking all view, Text and other graphics turning into white squares, etc.), then a few seconds afterwards, the game will lock up and cause a BSOD, saying that nv4_disp.dll went into an infinte loop, and the system was shut down to protect from damage. IIRC, one of the Addresses in the dump was 0x000000EA, not sure what it's related to, but it may help.
If I can get it to crash again, I'll write down everything that is said on-screen. I'll also provide a kernel memory dump. I really really hope this gets fixed, as it's an extremely severe bug.
AMD Athlon 64 3200+ 2.1ghz
1.5 GB pc3200 RAM
nVidia NForce 4 Ultra AMD Chipset
NVidia GeForce 8600 GT
Windows XP Pro SP3
ForceWare 178.13
NVidia PhysX
Now, Here's the problem... I can play Gears for a varying amount of time, sometimes a few hours, sometime only 5 to 15 minutes, until which Gears of War's Graphics get Highly corrupted (Textures going white, Translucent Texture being plastered on the screen blocking all view, Text and other graphics turning into white squares, etc.), then a few seconds afterwards, the game will lock up and cause a BSOD, saying that nv4_disp.dll went into an infinte loop, and the system was shut down to protect from damage. IIRC, one of the Addresses in the dump was 0x000000EA, not sure what it's related to, but it may help.
If I can get it to crash again, I'll write down everything that is said on-screen. I'll also provide a kernel memory dump. I really really hope this gets fixed, as it's an extremely severe bug.