3dmark2001 corrupt at 137fsb

[splateee]

Hello everyone, this is my first post in the forums. I am pretty new to overclocking and have a question with 3dmark2001.
It seems when i up my fsb to 137 i get an error in 3dmark saying that the texture is corrupt, this usually happens when it gets to the lobby test, but when i go back to 133fsb everything is fine. Besides that windows xp and everything else runs fine. my system temps are 27c on the cpu at idle and 25c on the mobo.
A little info on my system:
windows xp
xp 1800
soyo dragon plus
768megs 2100
geforce 3
could this be a memory related issue? it is cheap ram. should i maybe up the voltage a bit?

Any help will be greatly appreciated.

[funnyperson1]

how about games? could be the video card....is it overclocked?

Welcome to the Forums :)

[DarkArctic]

Well it's probably the RAM. All the other components should be able to handle that FSB easily. Just my $0.02

-DarkArctic

[splateee]

The video card is not overclocked. Games and everything else run fine. For some strange reason 3dmark will stop on the game lobby test and say there is a corrupt texture file.
Last night i left everyhting at stock settings but upped the video card a lttle bit, 220/485 and ran it again and it ran the whole test, got another 200 points or so. Then i bumped up the fsb just to 137 and thats when the error came up. so i backed the card back to stock and there was still error.

[deathstar13]

ive had the same problem myself and ive chatted with one other person with same probs.
to this day i dont know what starts the problem but only way ive found to remedy it was to uninstall 3dmark and reinstall it.
i would bet money its just the program and not a hardware issue!

[TruckChase!]

I have a differing opinion. I've had the same issues, and de/re-installing hasn't helped. I'm convinced it's too high a FSB for the memory. If I clock down a couple Mhz the prob goes away. I read on the Madonion boards that the texture corrupt message has nothing to do with vid card settings, aparently the error occurs when the textures are copied to/from main system memory.

[Violator]

The corrupt texture error is usually down to the memory being run too fast, resulting in memory errors and 'corrupt textures'. I get this myself if I try and run at 160FSB, but it's fine at 155.

[Rooski]

It's the memory speed. I've seen this many times while testing the limits of my ram. Play with your memory settings, and find a good compromise between ram timings and fsb. Remember, it's probably best to maintain the fastest timings possible, as opposed to highest fsb.

Also, a good thing to do is, try moving your memory around to different slots. Try every combination possible, and use 3dmark to test stability. If your using multiple dimms, try each slot with a single dimm. Sometimes using a particular slot can improve stability, or sometimes, in a multiple dimm configuration, you'll find that each dimm has a different limit.

[Kamikaze]

I would have to agree that memory speed is the problem, although I have had some heat issues that yeilded the same corrupt textures your getting in game 2 and 3, with a blorb on the top of my vid card everything settled down quite comfortably, though it didn't help me overclock the card anymore than it already was the 2 fans on the vid card stabilized the temps.