Screen goes black, Vid card fan runs beyond hyper speed, +

#1 well there is somthing wrong with the guns they seem to be useing way to much memory with there bullets. when i go to far T3d just closes on me. i did some tests on the burg level and the empty one both the same thing once you got like 5 bullets out there exploading. The fps can go from 60 down to 10 or less real easy now that will not make me crash but when i die wile i doing all this then it will go to far and crash T3d. takes about 2-3 deaths though but i still crash.

It should not be useing that many fps fireing a gun there got to be some memory being dumped. o and with the empty i have like 210 fps this is with AL on both but i can still get it to crash.

#2 Infrequent video related crashes or lockups are usually a sign of an overheating video card and/or computer.

#3 Has anyone else noticed increase fan use and general suspiciousness with the new 191.07(October) Nvidia driver?

#4 My experience is same with what Matt said. See if you can get the temperature of a) your GPU b)The inside of your case.

Run a bench mark to stress test your gpu and see if you can get it to lock up. You can try 3D Mark Vantage for this purpose. While running the benchmark, look out for artifacts and tearing as well. Try updating to the latest drivers if you haven't, sometimes nvidia does funny stuff to the drivers as noted by steve

#5 Sounds like your video card could be going into the 1st stages of failure right before its getting ready to go out for good.

#6 My old GeForce runs full tilt the moment any 3D starts, but I haven't had lockups like that. I also think yours might be faulty. Get 3D Mark to push it a bit, as suggested above. Or just look for a taxing (benchmarking) level in any other game you might have.

#7 Note: this post is not meant to be anti-fanboi at all..I like T3D alot and I would like to find the reason for this issue. If it is my hardware, then I say "excellent, case solved"...but if it is T3D on some level, I would like to know. So read this as genuinely as possible please.

Thanks for the posts but I think there is something lying under T3D or DirectX that is causing this and I would like to find it.
-Sorry for the harsh point of view here but I am running UT3 @ full settings & Fallout3 @ full settings without ANY issues, ever. Played for hours on days upon weeks. 3DMark Vantage score of approx: 32,000 and GPU score approx:7,000
- I ran the default install 3DMarkVantage tests 3 times in a row without any issues or lockups or artifacts or tears.

My video card is 3.5 months old and not overclocked, it's well cooled & temps/memory are monitored..at least when the screen is not blank from odd events! I can add temperature probes to the comp but I think that is getting a bit silly considering the information I have supplied.


Well, I guess this is a closed matter until someone else has the issue or until I can reproduce it OR unless my GPU/comp goes nuclear.

I am not trying to make T3D look bad at all..the engine is shaping up fantastically! I am enjoying the engine thus far. I am just seriously intrigued by this issue.

#8 Ran into something similiar as of late when the game kind of grinding for 4 seconds and online it goes completely green (I believe that has something to do with the level info as that is the background used if you cull out the terrain). You might not be going crazy. Decals seem to be causing us issues right now and is helping that some. Trying to debug the issue and for some reason it doesn't want to trigger right now *L*.

#9 I have recently been having issues like this only I get lockups and my screen starts flashing between some different diffuse maps and normal maps and sometimes it will start to look like there is a problem with the depth buffer.

This happens about 15 minutes of playing my game in T3D. I noticed this issue started in beta 5 and in almost every situation, projectiles have been shot and either right when they explode or before they explode, my pc will lock up.

I was playing Company of Heroes last night with a friend and ended up going for almost 2 and a half hours in a battle and there were no such problems.

Now my issue sounds to be pretty similar to yours eb and im using an Nvidia 8800 GTS 640mb card on the latest drivers. I have an image of whats happening and I will post it when my webhosting goes back online :(.

#10 ATI/AMD FTW ! =P I tried loading burg, turning AL, postfx all on, jumping and shooting "willy-nilly" and could not replicate the issue, i guess its as random as you say. On a side note, i was so lag on my 2400 pro that there were instances where i could see my character a few meters away from me, despite being in first person mode :P I guess the camera couldn't keep up :P

If you suspect its a direct x issue, are you on the Mar or Aug Directx ? Run T3D through Pix and see if you can detect anything ?

#11 Ok hosting is back up so heres my lockup image:

#12 I get those same lockups! ...lasts about 15 or 20 minutes and then it clears itself up.

Edit:
I have seen quite a bit of oddities in T3D and if the Dev staff has never seen things near that odd, they're simply lying about it. Not to call anyone a liar, but I have used T3D on 4 systems and all 4 have had your "lockup" issue.

#13 I havent had the patients to wait it out I just yell really loud and kick my pc's restart button. But it seems once it happens and I go back into T3D, as soon as I get into a mission it locks up again.

#14 All of my lockups like you're experiencing, have happened within the first few seconds of a mission. I spawn, then 1,2,FROZEN-screen with rendering issues.
- I have never had it happen after the first 10 seconds have passed.

BTW: everything I am talking about is STOCK T3D, NO CHANGES at all.

#15 @eb
Compile a debug version of the executable, then start it from the compiler (vs2008 etc) by pressing the little green arrow next to Debug. When T3D crashes, select break, trace the stack, and report the results.

#16 Thx Steve, I know how to do all of that shlamazzle.. I would prefer to not have to do this 200 times to find that 1 out of the 200 times it occurs.

//edit: I'll run tests this week when time permits, with my fingers crossed.

#17 I am getting it in stock T3D and in my game. Steve, the game isnt technically crashing so I dont think there will be any callstack or break points that can be looked at.

#18 I have this issue too,
gtx295 card,
check your log and see if you get shader warnings just before the game begins...

#19 You still should be able to halt/pause the execution and look into what could be going on. Tried that for awhile and couldn't for the life of me to get it to fire in debug. We started having this issue with 1.0.1 after we merged in the changes. Be easy to track down if we could get it in the debugger, but so far it is being elusive.

@Eb: Calling people liers does not help the problem. We all want to see issues resolved including the developers.

#20 I think he just finds it funny that not only did he experience it on all 4 of his systems, but others experienced it as well, yet non of the devs have experienced it :P

Anyway, please post the specs of all the systems which crashed. I'm running on ATI/XP and have not had this issue. Maybe its a vista/nvidia issue ? Just random guessing.