Red "ERROR" in CSS Stress Test

[sharpturn]

I must have run the stress test about a dozen times over the past three months to identify my max settings. I had never had any problems in the past, but when I ran the test yesterday I noticed that the rotating square slabs in the first part of the test were all replaced with rotating red "ERROR" messages.

Does anyone know why this started happening? Is it software related or could my hardware be damaged?

Thanks

 

[WaryWolf]

try scanning your hard drive for errors (with scandisk) and running a defrag. also, if that doesn't show up anything, you might have to reinstall/re-download half-life 2.

 

[duffers20]

have you recently installed new gfx drivers? Also you could use the Steam utility to check the hl2 & cs:s files for errors, i forget the url for it, but someone on here is bound to know, if you do them please post a link. Thanks.

 

[willyd]

I have the exact same thing.
Ive never noticed it before.

 

[_Meitsi_]

Try validating the CS:S and HL2 files.

 

[sharpturn]

After doing a little investigating it appears to be a problem with the lastest update applied to CSS. That update forgot to include those textures; at least for Nvidia 6800 cards

 

[duffers20]

:S oh right, hope you get it sorted out. Also i really hope that no-one takes this as an opportunity to start a Ati is better then nVidia thread, as there really is no point.

 

[giant384]

i have it to now must be after that update or somethin

 

[rada]

I have an x800 and I get the same error ....

 

[furiousV]

hmm just installed windows XP and i got it now aswell.
9800 Pro for me.
il do a little googling and muck about, if im successful il let u all know.
i wonder, since the things being rendered, or are meant to be rendered, are now Error, its probably not using the same amount of processing power, therefore your Average FPS is not a valid outcome compared to what it should be if the windows and water effects are there.

 

[Lahire149]

I have the same problem...
(See Specs Below)

 

[Dumb Dude]

Everyone has this problem. It has nothing to do with drivers/video cards etc... Its just that the update messed it up. It happened a while back and when the models actually came back one of them was different (see pic).

 

[Barters]

So what is the solution? Do we just have to wait till the next update?

 

[Dumb Dude]

Yeah, the solution is to wait for an update to adress the problem.

 

[jimbo118]

i have this too due to a recent update,i also get the 'failed to lock directx8 vertex buffer' or watever it says when i change settings,so it just crashes after i change them,i also get the 'memory at referenceblbla couldnt be read' 1aswell when i change,once i load it back up though its fine,still annoying though