If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

TNT2 Ultra and D3D=Crash to Desktop

I've recently installed a Xentor 32 TNT2 Ultra in my system (FIC VA503+, K6-2 400, SB Live Value, 64MB, IBM 8.4GB). I've got it stable in OGL (Q2, Q3) after some tweaking of the BIOS, but I'm still having troubles with D3D. Games (Motoracer2, Nascar3) that use D3D crash to the desktop after a few minutes, sometimes sooner. I've disables the prerequisite BIOS settings (read through cache, shadowing, etc.). Also, I've tried all different AGP aperture sizes. These do affect OGL stability, but seemingly nothing with D3D. Does anyone have the answer? Thanks for any help you can provide.
-Keith

Fat32:
I have recently got a TNTu and have had the same problems. Did you make sure your BIOS AGP options are enabled plus don't enanble the AGP 2X mode as that overclocks the card and will cause crashs. I have an email from tech support if ya want it you can email me

Oldcomputerfreak:
I do have AGP enabled in the BIOS, including the 2X option. I'll change that tonight and see what happens.
An aside...
You'd think it should all work, seeing as that's why I bought the card in the first place...the performance. If you have to dumb it down to a point where it's marginally faster than some other video card...well I'm sure you get my point.
Thanks for the suggestion.
-Keith

I had a similar problem on my K6-2 450, VA-503+, SB PCI-128, WD 4.3GB HD, Voodoo3 2000, 96MB PC-66. The damb thing would dump out of games to desk top all the time (the worst was Descent3 which took about 20 seconds after you start). I got disk errors and registry errors. I had resently upgraded the CPU (from a K6-2 350). After everthing else failed, I down clocked it to 400 Mhz and it ran fine. After about a week (and finding out I would be without a computer for at least 2 weeks if I returned it) I bumped up the voltage to 2.3 and it ran 100% stable at 450Mhz.

I tried giving it a little more voltage, and I (oops...forgot to mention this earlier) returned to the intended clock of 350MHz. Still crashing in D3D only. I'll try giving it more juice at 350MHz and see what happens. Thanks again for the suggestions.
-Keith
P.S. All worked fine with the Viper 330 I just took out. Go figure.