PDA

View Full Version : Issue involving Ti4200 and nForce2 with OpenGL


Stu137
04-22-03, 05:36 PM
I have an MSI K7N2 motherboard with an nForce2 SPP chipset, in this I have a Chaintek Geforce4 Ti4200. The combination works very well in any D3D applications, but any OpenGL applications run for a short period, then begin stuttering (images pausing then skipping ahead) until it crashes (always under 2 minutes). I have tried using the most recent drivers from MSI, Chaintek, and Nvidia, all have the same result. This issue shows itself in both windows and linux. I have a friend with a MSI motherboard (also has a nForce2 chipset, but not sure if it is an SPP of an IGP), and an Mx440 video card. His card works find in my PC with both D3D and OpenGL. My card works fine with his system as well. The drivers for my system are the same as his. I don't think it is a driver issue since it is occuring in more than one operating system.
Is anyone aware of a BIOS version conflict with the Ti4200 card, or some other issue that might be specifically related to OpenGL? I am also positive that neither device is not working poperly as the video card has been replaced and both cards do this.
Thank you for any help.

Corben9
05-20-03, 07:27 PM
I have the exact same issue with the same motherboard only my config is the following..

Athlon XP 1700+
MSI K7N2G (nforce2 MCP2) - lates bios
( i didnīt install nvidias crappy SW IDE controler drivers just the ragular one coz it keeps chrashing my ahead InCDpacket write software and freezes MMC and any WDM!)
512MB DDR Ram
Ati AIW Radeon 9700PRO PAL + DX9a + Catalyst 3.4
Multimedia Center 8.5
Maxtor ATA133 60GB
SB Audigy2
windows XP +SP1
Creative DTT 2500 sound system
Ati Remote Wonder
Terajon TJ 100 Cable modem (running at 1.5Mbit)

I tryed everything (really everything and its definetly the mobo 1000000% I contacted MSI today and am waiting for a responce I advise u to contact them to so that they become aware of the issue it also affects the K7N2 ILRS (the 219$ version ) So keep hoging there thech support to so that they realize that it is not an isolated cas : I also found some people at Rage3D to have the prob and there is also mention of it in MSIs own forum but there are no solutions for the problem yet. Creative said that it could be related to problems with IRQ steering ( I first blamed ATI , then creative and in the end itīs a mobo issue wow took only 3 whole days of reconfigureng testing and trubbleshooting to findout :(