3D mark "problems"

13th October 2004, 01:09

Hey,

I sort off have problems running 3Dmark stable, any 3Dmark (01, 03, 05).

I can run Aquamark3 just fine @ 241 fsb and run the pc and games without a problem but the for the 3Dmarks to complete a run, I have to drop the fsb to 227 :grum:

Yesterday, I could get 03 to finish a run once on 236fsb realtime.

today, none of the 3dmarks would run at 241, 236, 231.

I just ran 01 at 227 and it finished it's run, 03 is running now but seems to be going wel...

So, is this normal? Personally I would think not.

Oh, I sort of ****ed up my driver installation. I forgot to install the mobo driver so it's been installed after the vidcard driver. Today I unistalled the vidcard drivers and ran drivercleaner 3.3 and then installed the latest omega's (beta).

13th October 2004, 13:39

lol and today, no changes made, 05 run completed @ 240 fsb :s

11th November 2004, 21:03

what combo?

piotke · 11th November 2004, 22:32

tst stability with prime 95

11th November 2004, 23:41

threaddigger!!

I think this was the setup although it was a little while ago already and it's currently dismanteld.

amd xp-m 2400+
abit nf7-s rev2
corsair xms pc3500 v1.1
asus x800pro vivo @ stock (pro) speeds 16 pipelines
antec true control 550
ocz ddr booster
ac-ryan sata raid pci card
... I think that about sums it up

but I believe the fsb overclock wasn't rock solid. In dispite of the fact that 3dmark 03 and 05 don't really take your cpu into account, they put much more stress on it then aquamark3.
lowering the fsb to 22* solved the problem.

I'm sorry for the inconvenience, I cried for help too soon and didn't update my findings here...

13th October 2004, 01:09	#1
kristos Posts: n/a	3D mark "problems" Hey, I sort off have problems running 3Dmark stable, any 3Dmark (01, 03, 05). I can run Aquamark3 just fine @ 241 fsb and run the pc and games without a problem but the for the 3Dmarks to complete a run, I have to drop the fsb to 227 :grum: Yesterday, I could get 03 to finish a run once on 236fsb realtime. today, none of the 3dmarks would run at 241, 236, 231. I just ran 01 at 227 and it finished it's run, 03 is running now but seems to be going wel... So, is this normal? Personally I would think not. Oh, I sort of ****ed up my driver installation. I forgot to install the mobo driver so it's been installed after the vidcard driver. Today I unistalled the vidcard drivers and ran drivercleaner 3.3 and then installed the latest omega's (beta).

11th November 2004, 22:32	#4
piotke [M] Reviewer Join Date: Jun 2002 Posts: 5,003	tst stability with prime 95 __________________ .

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
IRON MAN Mark 1 PC Case	jmke	WebNews	6	1st May 2008 08:39
Mark Rein promises UT3 beta demo soon	jmke	WebNews	0	9th October 2007 11:20
3D Mark 07 To Be Fully Quad Core Optimized	jmke	WebNews	0	8th December 2006 20:00
Epic Games Mark Rein Interview	jmke	WebNews	0	22nd March 2006 12:30
Good Work Systems R2 Mark II Gaming Mouse	jmke	WebNews	0	16th December 2005 17:39
AMD's server share leaps 10 percent mark	Sidney	WebNews	0	26th July 2005 00:53
First look at Futuremark 3D Mark 2005	Sidney	WebNews	2	5th October 2004 16:37
Intel's Hyper-Threading Technology Surpasses 50 Million Mark In Just Over Two Years	jmke	WebNews	3	2nd October 2004 02:15
3d mark 'hapert'	jakkerd	Hardware Overclocking and Case Modding	4	19th March 2003 00:45

13th October 2004, 13:39	#2
kristos Posts: n/a	lol and today, no changes made, 05 run completed @ 240 fsb :s

11th November 2004, 23:41	#5
kristos Posts: n/a	threaddigger!! I think this was the setup although it was a little while ago already and it's currently dismanteld. amd xp-m 2400+ abit nf7-s rev2 corsair xms pc3500 v1.1 asus x800pro vivo @ stock (pro) speeds 16 pipelines antec true control 550 ocz ddr booster ac-ryan sata raid pci card ... I think that about sums it up but I believe the fsb overclock wasn't rock solid. In dispite of the fact that 3dmark 03 and 05 don't really take your cpu into account, they put much more stress on it then aquamark3. lowering the fsb to 22* solved the problem. I'm sorry for the inconvenience, I cried for help too soon and didn't update my findings here...