X3350 Arrival

Indeed... I couldn't believe that at first, but now someone else also confirms the same thing. But yeah... one PCI-E slot is truly... inconvenient.

I am going to revert this back to Maximus instead of Rampage and see if it gets any better:confused:

If not I will probably wait for P45 or buy a Rampage or DFI X48...

And... I'm uploading a video on YouTube. :)

P.S.: And creating a separate thread for ASUS P5E-VM HDMI in a few minutes. I think the board finally deserves some attention. ;)

BUMP! No thread yet... since I don't have enough information to post. But I have a video for you all. :)

http://www.youtube.com/watch?v=kZSocwaQntA

^= And THAT's the power of mATX! :up:

A guy from Gathering of Tweakers (A dutch forum) called to Asus and he talked to the BIOS Department fron Asus. He explained the problem to Asus and the will look what the problem is and he'll fix it! Next week we hear more from Asus and what we can do to fix the FSB limit on the X48/X38/P35 motherboards. Maybe they will come with a new bios with the fix in it.

Great support from Asus!
:up:

Quote:

---

Originally Posted by FiXeR

A guy from Gathering of Tweakers (A dutch forum) called to Asus and he talked to the BIOS Department fron Asus. He explained the problem to Asus and the will look what the problem is and he'll fix it! Next week we hear more from Asus and what we can do to fix the FSB limit on the X48/X38/P35 motherboards. Maybe they will come with a new bios with the fix in it.

Great support from Asus!
:up:

---

I hope this is the case and if it does, I would be willing to pay beer :ROTF:

In any case, I will probably buy a P5E-VM board for my HTPC box and if nothing change in the Q9450 side, I'll slap this on the board for a lovely 3.8 GHz.

Quote:

---

Originally Posted by ChaosMinionX

Well it seems we are getting somewhere.... Does anyone have older P5K's and things to test these chips on? I see almost everyone with *ironically* the board that wasnt supposed to OC 45nm well *cough* 780/790I *cough* all have theirs clocking flawlessly.

I wonder whats going on? And I wonder if Asus plans to do anything about the problems with X38/48 45nm clocking.

After all the info I have gathered over the past couple days, I think I will hold onto this chip and see if it pays off to ride it out.

---

I agree, this is most likely an issue with f***kin' X38 implementation - why the hell did it take so long to ship this board if they did not test it with then-available 45nm samples (they were out)? More importantly what's up with newer BIOS releases and when can we expect something that makes these board useful?

Apparently current ASUS X38 boards are USELESS for *ANY* 45nm QUAD CPU OC, period. UPDATE: it seems they will act fast which is good. :cool:

Man, I'm so pissed...

Quote:

---

Originally Posted by FiXeR

A guy from Gathering of Tweakers (A dutch forum) called to Asus and he talked to the BIOS Department fron Asus. He explained the problem to Asus and the will look what the problem is and he'll fix it! Next week we hear more from Asus and what we can do to fix the FSB limit on the X48/X38/P35 motherboards. Maybe they will come with a new bios with the fix in it.

Great support from Asus!
:up:

---

Great news, indeed! :clap:

Quote:

---

Originally Posted by T2k

Apparently current ASUS X38 boards are USELESS for *ANY* 45nm QUAD CPU, period. UPDATE: it seems they will act fast which is good. :cool:

Man, I'm so pissed...

---

My first two C0 QX9650s did 400x10 fine on Asus Maximus Formula.. The FSB wasn't high at all, but I was still able to get good clocks out of them.

You should reword it and say that they're uselses for high FSB overclocks.

Quote:

---

Originally Posted by zoob

My first two C0 QX9650s did 400x10 fine on Asus Maximus Formula.. The FSB wasn't high at all, but I was still able to get good clocks out of them.

---

Well, I meant that, high FSB, of course. My runs fine until 445 and then BANG, no boot afterwards.
Ridiculous and maddening.

Quote:

---

You should reword it and say that they're uselses for high FSB overclocks.

---

Just did it, added "OC", to be fair with ASUS. :)

Just as I thought after the extensive trial and error (mostly error) that I did trying to get this damn chip to clock worth a damn.

If Asus pulls this one off, its just 1 more reason for me to continue to buy Asus products :)

And... update. :) I find the CPU score significantly lower than 3.90GHz on the X3350 for some reason.

http://i235.photobucket.com/albums/e...06CPUScore.jpg

Edit: No GPU score yet... unless you want me to bench the onboard X3500 GPU?

Yep... definitely lower than X3350. Then again, I haven't... changed any GPU settings yet. Maybe the onboard GPU is limiting me. :D

http://i235.photobucket.com/albums/e...PUScore490.jpg

Hi , is it worth me getting a X3350 chip to replace my 6600 go at the moment then or should i wait for better bios or a better board , got the maximus with rampage bios mod at the moment steady at 3.8 gig

Quote:

---

Originally Posted by andyr(uk)

Hi , is it worth me getting a X3350 chip to replace my 6600 go at the moment then or should i wait for better bios or a better board , got the maximus with rampage bios mod at the moment steady at 3.8 gig

---

Nope. Not worth it if you can get a Q6600 to such clock IMHO. Stick with the Q6600 for the time being.

@RunawayPrisoner, I dont think its the onboard GPU cuz I get around the same score @3.2GHz in 2D, 3D, Overclocked, Underclocked

51XX-52XX range even Underclocked got 5220 :shrug: 300-300 on the Gpu

http://www.picgarage.net/images/score_67919_453.jpeg

So far this is the best I've been able to get on air with decent temps. I doubt it is prime95 stable but It did get 20 minutes into OCCT before I got bored and closed it.

Quote:

---

Originally Posted by nezzari

http://www.picgarage.net/images/score_67919_453.jpeg

So far this is the best I've been able to get on air with decent temps. I doubt it is prime95 stable but It did get 20 minutes into OCCT before I got bored and closed it.

---

what about with the GPU will it do it in 3DMark06 ?

Quote:

---

Originally Posted by Dom7184

what about with the GPU will it do it in 3DMark06 ?

---

Didn't have a problem with my 9800GTX. I am back to 3.8Ghz for now.

Quote:

---

Originally Posted by FiXeR

A guy from Gathering of Tweakers (A dutch forum) called to Asus and he talked to the BIOS Department fron Asus. He explained the problem to Asus and the will look what the problem is and he'll fix it! Next week we hear more from Asus and what we can do to fix the FSB limit on the X48/X38/P35 motherboards. Maybe they will come with a new bios with the fix in it.

Great support from Asus!
:up:

---

Im glad to hear that. Yes.. great support from ASUS :clap:

Cant wait to be fix.. :cool:

Quote:

---

Originally Posted by Dom7184

@RunawayPrisoner, I dont think its the onboard GPU cuz I get around the same score @3.2GHz in 2D, 3D, Overclocked, Underclocked

51XX-52XX range even Underclocked got 5220 :shrug: 300-300 on the Gpu

---

Oh really???

http://i235.photobucket.com/albums/e...oretweaked.jpg


http://i235.photobucket.com/albums/e...reTweaked2.jpg

Slapped a brand new 9600GT that I ordered for some customers in there... and voila. :p: Anyway, card is back in box and I won't be benching that thing at all.

P5E-VM HDMI really needs to be droop modded. I set 1.525 V bios, and the droop bounces between 1.336 V and 1.344 load.

http://individual.utoronto.ca/bzhou/...mhdmi-3800.jpg

Well, you're lucky, at least. I need 1.36-1.38v for my Q9450 to be stable. Seems like the Xeon chips can clock higher at lower voltages.

But anyway, nice clocks!

@zoob

whats the NB volts set at?

is it still going or you stoped it ?

Still going! I dunno what happened but the vCore went up by itself! I'm not sure what NB is set at, I just kind of threw some voltages at it, bumped up vcore and clock overcharge and hoped for the best. Once I reboot I'll take a look.

http://individual.utoronto.ca/bzhou/...dmi-3800-2.jpg

your on water right ?

so now I have some one to compare temps to :D

edit: scythe ninja I guess thats a no :(