• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

3DMark2006 problem help!

Associate
Joined
4 Apr 2006
Posts
346
For some reason everytime it gets to the forest scene half way through it or just towards the end it crashs, locks up.
Now I don't know whats causing this, is it due to my overclocked cpu? my voltages or my ram timing?
I have no idea and its really frustrating because everything else I have ran has been stable.
Is my system unstable? It does the same on 2005, but only seems to be on the forest scene it just won't go no further, but then sometimes it will run with no problems.
 
If I were you, I'd revert to stock settings and try and gradually find a sweet spot. And yes, your system is unstable as is any system that malfunctions.
 
Thing is SP2004 runs fine longest I done it for is 4 hours decided that was enough and turned it off.
However come to turn it on today and 3DMark just keeps locking in the same places.
 
Different software / programs, stress differentt parts of the pc, likely why it crashes under 3dmark & not other times.


I really would try everything at stock settings & see if 3dmark is ok or not.
If yes then start overclocking & see when 3dmark fails, then lower the overclock slightly from there.
 
Well I had a couple of spare hours and decided to do another quick test, it was stable the whole time, but like I said on 3DMark it seems to become unstable, but then again other times its fine, I must be a noob clocker because I can't seem to figure it out, I did mess with the graphics cards mem and gpu clocks, I don't know if its just me or not but ever since then its seemed worse, less stable.
I have tried various things to try and sort it but nothing seems to work.

newss11qp4.jpg
 
Last edited:
Its becoming very frustrating, I clocked it right down to 2.66 and lowered the timings, messed about with all the voltages, and it still keeps crashing in 3DMark, sometimes it will run the scene for abit longer but all spikes and stuff will start to appear on screen or start to turn into large pixels.
Just don't know whats cauing it, thinking I broke my graphics card trying to clock it originally or something.
 
Last edited:
Well I put everything back to stock and it still does it, I must have fried my graphics card when I tried to clock it, I can't seem to figure it out.
I formatted today, tried different drivers and settings, all manner of things and still the same, locks up in 3DMark.
Any ideas would be much appreciated. :) Or could it be something to do with my memory timings?
 
Last edited:
Well its got to be the most anoying thing ever, it runs stable in everything else but 3DMarks now, like I said I must have damaged the card when I first tried to clock it, had nothing but problems since then, even after format, it could be something else though this is whats so frustrating!
 
Traducer said:
Its becoming very frustrating, I clocked it right down to 2.66 and lowered the timings, messed about with all the voltages, and it still keeps crashing in 3DMark, sometimes it will run the scene for abit longer but all spikes and stuff will start to appear on screen or start to turn into large pixels.
Just don't know whats cauing it, thinking I broke my graphics card trying to clock it originally or something.
It sounds like the graphics card memory to me. If the screen went blank it could have been the RAM, but artifacts Im certain is the graphics card. If it does it at stock it doesnt look good. Have u got any other components like spare pc or graphics card to test?
 
I think your right, I tried it all at stock, I clocked it down to 2.66 and 2.8 and it used to run perfect everytime on that, everytime.
I tried the RAM all at different timings and still everytime I get the same now, games are fine and everything else is fine, its just ever since i tried to clock my graphics card since the first time I unlocked it, I've had nothing but problems and artifacts and so on, but only in 3DMarks2005 and 2006 and mainly on the forest scenes, sometimes now it won't even run the full proxycon scene where as before it did everytime, I have tried numerous voltages and settings and still the same.

I've formatted, reinstalled drivers and tried different versions, I think I may have damaged my graphics card trying to clock to high the first time, I just raised the mem and the gpu right up and expected it to work, very nieve I guess.
I knew I should have left it alone, any ideas on what to do now? or is that a stupid question? :)
Or could it be something to do with the RAM? can that cause problems like this?
Basically gets to the same scenes everytime, it starts to become unstable and usually locks up or artifacts first then locks up totally. It does not usually go blank it just freezes totally, but you see it becoming unstable sometimes before it does, not all the time though.

Here are the results when it actually used to running at 3.22Ghz and 920Mhz 5-5-5-15.

3DMark Score 5511 3DMarks

SM 2.0 Score 2008 Marks

SM 3.0 Score 2234 Marks

CPU Score 2836 Marks

But I have It running at 3.325Ghz and 950Mhz 5-5-5-15.
Can't bench it because it crashs regardless if I default everything in the bios or not, running stable on Orthos though.

At the settings above, It ran and I changed my PCI Freq from 100 to AUTO and my Mipmap detail to high performance, this was ran on the 7.1s, but I am going to try again on the 7.4s as the score looks poor, however at least the CPU works lol.

3DMark Score 5490 3DMarks

SM 2.0 Score 1985 Marks

SM 3.0 Score 2221 Marks

CPU Score 2930 Marks

Well tried to run it again and it crashed in the forest typical.
 
Last edited:
I think you need to stop repeating yourself, you have explained the problem....

any clock speed on any settings your 3dmark crashes

this means two things:

1. you should overclock your computer gradually, testing its stable each way, not just wack everything up as high as you can and then wodner why it blew up

2. your graphics card is screwed, it may be ok in some things but since its is screwed and seems to be getting worse in 3dmark it will start doing this in other things and eventually die

so now...
go and put everything in your pc back to itsoriginal settings (which you did make a note of before changing them right?!?!
and go buy a new graphics card

then...

read lots of overclocking guides before ever touching your bios again
 
MuSsEr said:
I think you need to stop repeating yourself, you have explained the problem....

any clock speed on any settings your 3dmark crashes

this means two things:

1. you should overclock your computer gradually, testing its stable each way, not just wack everything up as high as you can and then wodner why it blew up

2. your graphics card is screwed, it may be ok in some things but since its is screwed and seems to be getting worse in 3dmark it will start doing this in other things and eventually die

so now...
go and put everything in your pc back to itsoriginal settings (which you did make a note of before changing them right?!?!
and go buy a new graphics card

then...

read lots of overclocking guides before ever touching your bios again

I don't mean to repeat myself I am just impatient and this is doing my head in, I have done all of the above and still the same, as I have already said.
As for clocking guides if I read anymore I will go blind, but always willing to learn, the guides I have read have all been cpu and memory based.
I made a stupid mistake dabbling with the graphics card when I did not really know what I was doing, and now I will pay the price it seems, if this is the case.
Anyway I managed to get 3DMark2006 to run, and got the best results so far. :rolleyes:


3DMark Score 5534 3DMarks

SM 2.0 Score 2014 Marks

SM 3.0 Score 2230 Marks

CPU Score 2933 Marks


The card does seem to be getting slightly worse, ie crashing earlier in 3DMark, but hopefully it is just the card and it will be a lesson learned.
 
Last edited:
Impatience and overclocking dont mix. It can be easier to just leave everything at stock if you just want to use it and dont care about benchmarks. ATM, I only have my cpu clocked. Ive not needed to overclock my x1900xt so far.
 
Back
Top Bottom