Publishing question.

[spaceman]

Hey guys, I know this is kinda old, but today's the first time I ever had probs publishing a score. Is there a common solution, that I've missed? My rig's plenty stable, and completes '01 fine, no artifacts or anything, I just can't publish. :( Thanx in advance for any tips. :)

[Kunaak]

can you post a score link?
that may help alittle to see where your last publishable score was.

then give us an idea where your scores stop being publishable.

I had the same time from my XP 1700 for awhile, it would finish 3dmark2001 all the way to like 2.9+ ghz, but never was publishable, and I heard that running cas 2-2-2-5 was the secret of publishing scores, but that didnn't work for me :(

so I backed down my OC just alittle, one FSB notch at a time, and then at 2.885 ghz, I was publishable 100% of the time.
so for me, it was stable to 2.9 but never publishable, I suspect that it wasn't as stable as it appeard, so backing down alittle, must have gave it that last little bit of stability it needed for publishable scores.

you may try that too.
just back down alittle, run a test, see if you can publish it.
if you can't, back down one more, and try again.
once you get to a point where it is publishable then run the test again to see if the next test is publishable too.
hopefully you dont have to back down too far.
I think if you have to back down your OC too far, then the problem would be other then stability...

but thats just my guess, I never found a explaination of NF2 scores being publishable and not publishable.

[spaceman]

It probly is a stability thing, cause I was playing with the FSB and timings. Here's a run I could publish, http://service.futuremark.com/compare?2k1=6753109 ,but I also had a few runs like 17,518 and 17,622 that I couldn't publish. :( Thanx for your input, I was hoping someone figured out a fix. That's all air-cooled, BTW, so not all THAT bad. :p: ;)

[spaceman]

This one published fine, my best score yet. :D http://service.futuremark.com/compare?2k1=6759757 I just had to back off the FSB a bit, then I realized I still had plenty of MHz. to add, with a higher multi. I also figured out for sure that my RAM doesn't care if it runs at CL2 or CL2.5. ;) I'm hopin' to clear that 18k soon. :cool:

[Kunaak]

Nice work, I too would think the lower FSB helped you with the extra speed. wanna break 18K.

give this a try, Use DX8.1 and the cat 2.5, the 3.5 is nice and fast but for the 95/9700 series the cat 2.5 is still the fastest, try that with you same settings in your 17,900 score.

I bet you break it then ;)

[spaceman]

Thanx for the tips, I've been thinking about trying that, but haven't really got around to it yet. I also want to put 2k Pro on my HDD, instead of XP Pro. I was going to last time I formatted, but didn't have the right driver for my U.S. Robotics modem. :rolleyes: Got it now tho, a tiny little file that I just put on a floppy. I also never dialed up the vr on my gpu mod, so I might be looking at 19 or 20k when it's all done. :D

[spaceman]

And here's 18k, plus a bit. :banana: :D http://service.futuremark.com/compare?2k1=6775694 There's something weird going on at the Orb tho, cause this showed up at the bottom of the first page, if I only specify 9700 Pro. :confused: If I also specify XP/MP/4, the closest score is 14k. We all know that's not exactly right. :rolleyes:

[zakelwe]

I believe Opp got a message ages ago from Futuremark that if there is too many fluctuations then the score can not be published. Futuremark said that it was because it was a bench for real users and not where the system is stable for only a short term ( paraphrasing them ).

Interestingly it mainly effects nforce2.

Also is the interesting fact that Futuremark obviously judge people pouring ln2 onto P4's as real users :)

So, it would seem that nforce2 goes mad at "on the limit" FSB and upsets Futuremarks checks.

Regards

Andy

[Kunaak]

I see you took all of my advice :)

nice score, always fun to break a new barrier.

[twiggy]

Try this, when you open 3dmarks check system info and make sure the CPU is reported at what it is supposed to be. If it is off then close 3dmarks and keep opening it till it reports the right CPU speed. That should take care of your probs. :)

[spaceman]

Thanx for your input guys. :) twiggy, your plan looks pretty sensible, I never woulda thought to look at that. It's all for fun, to me anyways, I'm not too worried about how they rate me. ;) I mostly look at it as a good stability tester. Next, I'll play around with the DMM, & figure out how to crank up my gpu core speed. That's only 400/348, so I know I can top it eventually. :D

[spaceman]

Got 1.8v on the gpu so far, runnin' stable @425/700. :cool: I did a run @ 430 core, but it was a lower score so I didn't bother publishing it. The HSF's warm to the touch now, so I'll need to be careful going up with the juice. Anyhoo, got 18,500 now. :D http://service.futuremark.com/compare?2k1=6779828 BTW, I'm using the Rage3D tweak, and I'm almost out of core options, so I might just call this good, till a newer version. :rolleyes:

[Kunaak]

you can get powerstrip and double click on the icons below the sliders and change the percentages from 133 to 150 or so, and then get even more overclocking headroom.

:)

[spaceman]

That crossed my mind. I was kinda wondering if I could uninstall just the ocing part of Rage3D (after resetting defaults), then install Powerstrip? That way I could still do the "tweaking" part of the Rage3D tweak. I might look into it. :)