Sign in with
Sign up | Sign in
Your question

Scoring 10k's

Tags:
  • Graphics Cards
  • Graphics
Last response: in Graphics & Displays
Share
January 21, 2002 6:24:42 PM

P4T-E @ 2600Mhz and <A HREF="http://gamershq.madonion.com/compare2k1.shtml?2508258" target="_new">Radeon 8500</A>

P4T-E @ 2500Mhz and <A HREF="http://gamershq.madonion.com/compare2k1.shtml?2516811" target="_new">Gainward GF3 GS</A>

Figured I would update you girls, as you can see the GF3 is the stronger of my video cards. Also there is still problems with newest ATI drivers (fatburger).

More about : scoring 10k

January 21, 2002 6:39:36 PM

something has to be messed up somewhere looking at the scores the geforce 3 only wins in 3 of the scores nature, and both of the lobby test the r8500 scores are far supurior in nearly every catagory so i qusetion how 3dmark comes up with the scores if you included everybench mark in the final score the geforce 3 stands no chance but 3dmark isnt including all the test if you look at the scores

why does your p4 need to be overclocked to 2500 to get 10000 when you can do it at 1700 with a athlon?
<P ID="edit"><FONT SIZE=-1><EM>Edited by starwrs3 on 01/21/02 03:42 PM.</EM></FONT></P>
January 21, 2002 6:48:28 PM

Hmm, what are each clocked at? For all we know, you could have overclocked the GF3 and underclocked the Radeon 8500. The latest nVidia drivers, 21.83 and 23.11 have WinXP bugs but no one seems to be complaining. Plus, you're not using the latest ATI drivers.

AMD technology + Intel technology = Intel/AMD Pentathlon IV; the <b>ULTIMATE</b> PC processor
Related resources
January 21, 2002 9:20:15 PM

I'm using the 23.11 and they're cool.

My rice car will leave your R8500 in the dust!
January 22, 2002 1:15:29 AM

Hey man nice scores !!....I am a loyal Amd person but that new pentium core is nice and the 845d chipset is awesome with the way it clocks the pci agp etc when fsbs are raised....intel actually did a good job on this core!...now im just waiting on amd to return fire and maybe we will see more posts like yours =]...hehe...neways good job man
January 22, 2002 1:46:20 AM

*cough* suckup *cough*:)  Civilized must feel the equiv of what a man feels when he is next to someone who has a bigger willie than he;)

My rice car will leave your R8500 in the dust!<P ID="edit"><FONT SIZE=-1><EM>Edited by flamethrower205 on 01/21/02 10:56 PM.</EM></FONT></P>
January 22, 2002 11:31:52 AM

Quote:
Hmm, what are each clocked at? For all we know, you could have overclocked the GF3 and underclocked the Radeon 8500. The latest nVidia drivers, 21.83 and 23.11 have WinXP bugs but no one seems to be complaining. Plus, you're not using the latest ATI drivers.



A: the 21.83's dont have any xp bugs, dont spread fud amd_man ok.
B: the 23.11's are BETAS, NON WHQL.
C: the issue only affects certain via chipsets, when running xp/2k.
D: I believe the 23.12's are out, which supposedly resolve the issue, I however run the 21.83's till a new whql driver appears.

"The Cash Left In My Pocket,The BEST Benchmark"
No Overclock+stock hsf=GOOD!
January 22, 2002 11:32:59 AM

Part of me still things hes trying to live down his 3dmark2001 score thread humilation by posting all these insane scores lol.

"The Cash Left In My Pocket,The BEST Benchmark"
No Overclock+stock hsf=GOOD!
January 22, 2002 11:36:13 AM

Quote:

A: the 21.83's dont have any xp bugs, dont spread fud amd_man ok.

I'm not spreading fud!! It's a VIA/XP/nVidia//21.83/23.11 bug! You're looking at infinite loop errors and a non-fuctional ATI TV WONDER!

AMD technology + Intel technology = Intel/AMD Pentathlon IV; the <b>ULTIMATE</b> PC processor
January 22, 2002 4:28:25 PM

Firstly, the 8500 is still out-performing the Ti500 overall on MadOnion. Your results are atypical.

Secondly, why did you single me out? I haven't even installed my 8500 yet.

<font color=orange>Quarter</font color=orange> <font color=blue>Pounder</font color=blue> <font color=orange>Inside</font color=orange>
January 22, 2002 5:22:19 PM

I'm with AMD man on this.
I got Via, i got nvidia and i got xp.
both the 21.83 and 23.11 cause restarts in games. I just got my hands on the 23.12 which seem to have fixed this prob for some people. I'll keep you posted.

<A HREF="http://fileforum.betanews.com/detail.php3?fid=950852325" target="_new">23.12</A>

-- There are no answers to find in the bottom of a glass. But you can have fun looking for them.
January 22, 2002 5:39:51 PM

My GF3 is an exceptional card overclocking, capable of hitting 300/630. My Radeon is a poor overclocker only capable of 290/600 (For ATI this is low/average but ATI is a very strong card at stock compared to the GF3).

Im not running any voltage mods.

Im pushing both cards hard. The GF3 is a stronger card at lower Mhz.

My drivers are currently what everyone else uses at the 10k level on each board for best performance.
January 23, 2002 5:33:03 AM

"C: the issue only affects certain via chipsets, when running xp/2k"

Negative, it has been found to affect Intel 815 and other chipsets as well. Thats how we know its a Nvidia error not a Via error.

Crap, all the good ones are already taken.
January 23, 2002 7:01:22 AM

From the thread on it in viaarena the VAST majority of the problems occur on the 23.11's with a via chipset, there are a few isolated incidents of intel chipsets but one out of 100 does not mean that the issue actually affects the intel chipsets(more like someone has found a cause to believe in for his unstable system).


The same for the 21.83's the number of poeple who have the issue on the 21.83's is very small compared to the people with the 23.11's also many people have reported the issue dissapears when they went from the 23.11's>the 21.83's.

"The Cash Left In My Pocket,The BEST Benchmark"
No Overclock+stock hsf=GOOD!
January 23, 2002 7:02:57 AM

Quote:
Negative, it has been found to affect Intel 815 and other chipsets as well. Thats how we know its a Nvidia error not a Via error.



See my post above, but even if my counterpoint was invalid, this would remove via from the equasion, but that would leave both nvidia AND microsoft as possible causal factors.

"The Cash Left In My Pocket,The BEST Benchmark"
No Overclock+stock hsf=GOOD!
January 23, 2002 12:59:06 PM

In response to the FLAMER that just responded to my post.....I do believe that the athlon usually performs better on 3dmark than that of the p4....but still yet I thought his scores were impressive.....and I was just simply saying that I would like to see how the new hammer line performs to that of the p4 northwood.....but until then just stop whining and stop and take a glance down at your own shriveled penis =]....because when i walk down the beach I leave three tracks
January 23, 2002 2:08:27 PM

Lol, was joking:)  Ur legs are that short :eek:  :) 

Only if you let me see the Umpa Lumpa- Homer Simpson.
January 23, 2002 3:27:04 PM

Running 23.11 under Windows ME/nForce is guaranteed to crash 3DMarks 2001 (and games too IIRC). But when I drop it back down to 21.81 (didn't try 21.83) it works fine. Funny thing is 23.11 and Windows XP/nForce is ok. I'm pretty sure my system is stable as a rock.

Here's a link from a web site documenting the problem (I don't know how reliable the source): <A HREF="http://www.theddrzone.com/news.asp?id=404" target="_new">http://www.theddrzone.com/news.asp?id=404&lt;/A>

Quote:

So in summary, is it a VIA problem as some people have said? Definitely not. <b>It covers ALL chipsets from all the major manufacturers and Video cards using both nVidia's chips and those from ATI</b>. Personally it looks more like a combination of Video drivers and the NT kernel with a good does of DirectX 8.1 thrown in. Can it be fixed? Yes but at this stage only VIA have stood up and made an effort.

Here's another link: <A HREF="http://www.tech-report.com/news_reply.x/3219/1/" target="_new">http://www.tech-report.com/news_reply.x/3219/1/&lt;/A>

Quote:

I've been doing some reading up on people's difficulty with the 23.11 NVIDIA drivers. In those travels, I've also managed to run across others with non-NVIDIA hardware who are facing the same issue. If I understand correctly, this kind of error can occur across <b>all operating systems</b>. The sudden increase of the problem by name of "infinite loop" or "thread stuck in driver" is just a by-product of a new bugcheck code in Windows XP.


Pretty confusing state of affairs.
January 23, 2002 3:57:53 PM

maybe I was wishfully thinking at the time =]...
!