UT has been crashing repeatedly while running BW with this error message:

---------------------------

UT2004 Build UT2004_Build_[2005-11-23_16.22]

OS: Windows XP 5.1 (Build: 2600)
CPU: GenuineIntel PentiumPro-class processor @ 1999 MHz with 1022MB RAM
Video: NVIDIA GeForce Go 7900 GS (8463)

IDirect3DIndexBuffer8::Lock failed(D3DERR_NOTAVAILABLE).

History: FD3DDynamicIndexBuffer::AddIndices <- FD3DRenderInterface::SetDynamicIndexBuffer <- FStaticMeshBatchList::Render <- RenderLevel <- DM-Icetomb.myLevel <- FLevelSceneNode::Render <- FPlayerSceneNode::Render <- UGameEngine::Draw <- UWindowsViewport::Repaint <- UWindowsClient::Tick <- ClientTick <- UGameEngine::Tick <- Level Ice Tomb <- UpdateWorld <- MainLoop <- FMallocWindows::Free <- FMallocWindows::Realloc <- 10910191 0 FArray <- FArray::Realloc <- 0*2 <- FMallocWindows::Free


Machine stats:

Intel Core 2 Duo @ 2.0 gHz
1GB RAM
NVIDIA GeForce Go 7900 GS, 256MB VRAM
Stock nVidia 84.whatever drivers, apparently they're made FOR this card. Other drivers have had issues.

------------------------------------

I've tried defragging my hard drive, doing a clean reinstall of UT (delete EVERYTHING), and using an ungodly number of drivers, cleaning after each one.

The game runs fine for quite a while, but it eventually just crashes instantly - no lag.

Any suggestions?

Does this only happen when running BW? If that's the case, are you using the zip or the umod to install? The umod has been reported as being faulty in quite a few cases.

Also Update your Direct X to the August Build.

My directX was up to date before the error appeared. Also, I'm using the UMOD install.

Now, I had been playing Icetomb for a while (CQC is fun), and decided to try other levels - no errors. Now it just pops up sporadically after a while, like just now on Adara (Bonus Pack ONS map). My GPU is NOT overheating, to get that out of the way. Temperatures are 70C at most.

70°C is not far from being too hot. My card never goes above 55 when working hard.

Since this error is related to a function within the local D3D module of the game, I'm suspecting BW may not be a direct cause of the problem. Does this happen in default UT, without running BW?

You're running on a laptop (since its a geforce go card) and you seem to be having the same problem as I did but with different games (UT2004 with mod, Elder Scrolls Oblivion, Bioshock, etc). Whats happening is that your card is overheating and as soon as the game encounters a single error it'll crap out. These 256mb cards run HOT as it is. Just look at the heat sinks on their desktop equivalents. When you condense it and pack it next to a processor with a similiar problem its no wonder things go wrong.

Take a can of compressed air and blow it through the air intake to clear out any dust (also blow through the other direction). Then try getting a $15 laptop chill mat.

Then nVidia's "Slowdown Threshold" is bull, since it's 102. >.>
I'll have to find some sort of cooling platform, then. Hopefully I can find one that works WITH the e1705's fan layout.



This issue happens ONLY when running BW. UT will run smoothly and happily for hours. BW has all sorts of loading hitches while cramming effects into RAM, runs smoothly thereafter for a while, and then dies on me.

That makes no sense at all. Why would he see a UEngine script error because of overheating?

I'm gonna guess this is related to a faulty/non-existent graphical feature that BW's code requests. So this can be anything from a DirectX error to a video driver related one, many possibilities.

Actually, it does make sense.

The error is always due to an inability to lock some buffer or another, likely because something isn't done writing to it yet. If it is overheating, the slowdown would eventually cause that. You said it was too hot, too.

70 is almost too hot I'd say, not really hot enough to cause stuff like this I'd say.

But it's worth a shot, try keep the computer as cool as possible.

Yeah, it has me wondering. This card/lappy has run at 75, even 80(!) before with few problems. (General lag, but no crashing.)

. . . 66C is nowhere near hot enough to be the issue. Nowhere near. (Crashed again. Peak GPU temp was 66C.)

I've done some minor GPU OCing in the past (something like 450/600, no voltage mod), but I don't think that was high enough to cause any damage. I'm in the process of freeing up some space on my HD (only 3.3GB out of 160 open, but the errors were occurring with 20), so I'll see if that helps. The only hardware I have my eye on is my memory; UT is quite RAM hungry, and BW only makes this worse. Peak RAM temp, btw, was 52C.

I've had some crashing issues as well, but only with one map. If we play it again I'll copy the message.

Btw I'm balling a quadcore with 2GB Ram and an Nvidia GEforce 8600GT 256MB vid card. No way I should be overheating.

Besides, I'm perfect.

HAHAHAHA....Perfect at missing me when im capping your flag.

This bug definitely looks well beyond the reach of BW. Fail to lock buffer, yes, thats in the D3D stuff... Solutions: make sure Directx is up to date. make sure ideo drivers are latest version. Cool down your machine, 70 seems way too hot, you could fry some bacon in there!

I don't know what to blame this on now. I just ran HL2 and Portal flawlessly (125fps+) at high settings - my card hit 80C. Heat is NOT the issue.

If it were the issue more games than just BW would be unstable.

Try this:
1) Open up UT2004.ini in C:\UT2004\System
2) Find this section of the INI file:



And make it look like this:


3) Save the changes and see if BW behaves better.

What is happening above is that you are forcing the game to ignore the D3D renderer, the line without the ; at the start, and force it to use the OpenGL renderer instead. Though keep in mind that the OpenGL renderer may not be as good in quality as the default Direct3D, but it might put an end to these crashes if my estimations are correct.

heat could be the issue in UT2k4.. it's graphics work diffirently to other games..

this is a Direct3D problem..

Heat is very unlikely the issue because BW is the only thing that crashes at all. And if D3D is in fact the issue, then my advice will fix it.