Asus P5B DX 56K WARNING

Printable View

Show 100 post(s) from this thread on one page

12-26-2006, 04:32 PM
palese

http://clubit.com/product_detail.cfm?itemno=CA4838942

229.00 and great customer service.
12-26-2006, 04:44 PM
Teratism

That is the bulk version which I am pretty sure means OEM which is about the same at newegg for the OEM version and other places. I needed to go retail because I own 0 cords and will need them etc. Thanks for the site though.
12-26-2006, 05:17 PM
situman

get the OEM version and order some nicer cables. OEM cables look like crap.
12-26-2006, 05:21 PM
Teratism

Already picked up the board through newegg so I am set. Hoping Ram works with the board now.
12-26-2006, 06:10 PM
xgman

Quote:

Originally Posted by situman

get the OEM version and order some nicer cables. OEM cables look like crap.

actually the cables that come with the BX2 don't look to bad. They look UV reactive. Even the sata ones.
12-26-2006, 06:14 PM
xgman

Quote:

Originally Posted by gtj

cpuz: No. Works OK.
Everest: Yes. As soon as you try to read the sensors it will hang.
Speedfan: I think it works OK but since Speedfan doesn't read the aSC7621 chip on this board, it's not of much use.
Memset. No. Works great.
Sandra: Yes: You can run the benchmarks but if you try to read MB info, instant hang.

To recover from a vcore reset, you MUST remove all power from the MB. I.E. unplug or power off the PSU and wait for the green light on the MB to go out.

Hmm, well not a biggie, but you would have thought that Intel could have easily fixed the voltage read/reset thing by now since it happened in the BX1 also. I don't think I have ever heard this on another chipset before. I called Intel and logged yet another case re: the Marvel disabled HDD light issue as well as the voltage thing. I guess if enough people call, they may fix it eventually.
12-26-2006, 06:15 PM
xgman

Quote:

Originally Posted by heikis

yup, jumped from 400 to 440 :P i will try to figure it out and tomorrow im probably gonna test if the vcore is raising or not after adjusting to higher in bios.
btw im using everest ultimate very easy to monitor temperatures :P

Does ultimate v3.5 reset the vcore or only everest basic?
12-26-2006, 06:15 PM
Blue078

Quote:

Originally Posted by xgman

Hmm, well not a biggie, but you would have thought that Intel could have easily fixed the voltage read/reset thing by now since it happened in the BX1 also. I don't think I have ever heard this on another chipset before. I called Intel and logged yet another case re: the Marvel disabled HDD light issue as well as the voltage thing. I guess if enough people call, they may fix it eventually.

So did you get your BX2 setup ?
12-26-2006, 06:26 PM
xgman

got it today but haven't even started. Going to do some pencil mods add a couple NB fans, rig a cmos config switch and then probably boot up a DOA board. (just kidding about that part) :)
12-26-2006, 06:28 PM
gtj

Quote:

Originally Posted by xgman

Does ultimate v3.5 reset the vcore or only everest basic?

Ultimate 3.5 beta 3.50.841 definitely does.
12-26-2006, 06:31 PM
xgman

Quote:

Originally Posted by gtj

Ultimate 3.5 beta 3.50.841 definitely does.

uggg . . . that's a real shame. I use the OSD monitor all the time.

So does it drop vcore while still in Windows or only while restarting?
12-26-2006, 06:41 PM
Teratism

Everest is up to 3.50.850 in beta if that may help.
12-26-2006, 06:43 PM
Supertim0r

Quote:

Originally Posted by heikis

yup, jumped from 400 to 440 :P i will try to figure it out and tomorrow im probably gonna test if the vcore is raising or not after adjusting to higher in bios.
btw im using everest ultimate very easy to monitor temperatures :P

try going back to bios 2333

I don't know why but with 2395, 400+fsb = no boot
back to 2333 and everything is fine :)
12-26-2006, 06:53 PM
gtj

Quote:

Originally Posted by xgman

uggg . . . that's a real shame. I use the OSD monitor all the time.

So does it drop vcore while still in Windows or only while restarting?

Go to Computer/Sensors and poof. Immediate hang.
12-26-2006, 06:56 PM
gtj

Quote:

Originally Posted by Supertim0r

try going back to bios 2333

I don't know why but with 2395, 400+fsb = no boot
back to 2333 and everything is fine :)

I had to go several rounds with the battery and jumper but it seems stable for me now.
12-26-2006, 07:05 PM
Tony

2395 has a tighter timing table on 1067 strap, so if you want to run 400+fsb you may need to try 1333 strap (333 reference) and tweak the timings down a little to gain back the bandwidth.

I also found some of the ram timings not working as they should on 2333 so flashing back may give you some issues also.
12-26-2006, 07:23 PM
Tony

If you have a 6800 you may want to try this.

Set 200 reference, set 533 for the ram (3:4) and 333fsb for the CPU. If you have good memory you should be able to set 4-4-3-8, TRAS dead low will actually hurt performance.

Now with the 6800 you will set a 12 multi for 4GHZ or 11 for 3.6+.

Access latency will be somewhere around 6ns faster in this config than running the ram 1:1 even if you are running well over 900 1:1 in 1067ref mode.

Im trying to source a 6800 to test here, im stuck with a 6700 so 10 multi is all i have but I have some data i can share.

Goldmem pro used for bandwidth, everest for latency.

Code:

memspeed FSB REF Strap ratio bandwidth latency 833 333 267 4:5 4736 61.4ns 833 311 200 3:4 4639 55ns 888 333 200 3:4 4965 51.5ns 888 355 267 4:5 5041 57.6ns

CPU speed was manipulated with the strap to force given ram speeds, even though 4:5 267 REF at 888 had the highest bandwidth its access latency is no where near as good as 888 200REF, which will make the 200REF setting faster.Now I know the CPU would be faster at 355fsb but we are looking at the memory here not the final CPU speed.

Remember C2D does not need tons of bandwidth, it just needs to use the bandwidth more efficiently. Lower access latency = more performance.

Tony
12-26-2006, 08:04 PM
Supertim0r

No X6800 here :(

I'll try tomorow with Q6600 and see if its working with 9+ multi
12-26-2006, 08:12 PM
malachi1313

Quote:

Originally Posted by Tony

If you have a 6800 you may want to try this.

Set 200 reference, set 533 for the ram (3:4) and 333fsb for the CPU. If you have good memory you should be able to set 4-4-3-8, TRAS dead low will actually hurt performance.

Now with the 6800 you will set a 12 multi for 4GHZ or 11 for 3.6+.

Access latency will be somewhere around 6ns faster in this config than running the ram 1:1 even if you are running well over 900 1:1 in 1067ref mode.

Im trying to source a 6800 to test here, im stuck with a 6700 so 10 multi is all i have but I have some data i can share.

Goldmem pro used for bandwidth, everest for latency.

Code:

memspeed FSB REF Strap ratio bandwidth latency 833 333 267 4:5 4736 61.4ns 833 311 200 3:4 4639 55ns 888 333 200 3:4 4965 51.5ns 888 355 267 4:5 5041 57.6ns

CPU speed was manipulated with the strap to force given ram speeds, even though 4:5 267 REF at 888 had the highest bandwidth its access latency is no where near as good as 888 200REF, which will make the 200REF setting faster.Now I know the CPU would be faster at 355fsb but we are looking at the memory here not the final CPU speed.

Remember C2D does not need tons of bandwidth, it just needs to use the bandwidth more efficiently. Lower access latency = more performance.

Tony

Can you give us the best settings for the 6600??? Please?? Thanx!!
12-26-2006, 09:00 PM
mnemonik23

Quote:

Originally Posted by malachi1313

Can you give us the best settings for the 6600??? Please?? Thanx!!

I second that!

Just pulled the trigger and bought BX2!
Now wondering how to get the best from E6600 and G.Skill PC2-8000 HZ. I hope I won't need to go with slower RAM :(
12-26-2006, 10:55 PM
Blauhung

ah, so the reference frequency is actual control over the chipset strap. I was originally under the impression that it was just a way to force dividers on the memory controller.

for all you e6600 users this doesn't really help you out. At lower strap settings the ultimate stable FSB is significantly lower. It boils down to you having to test things out for yourselves (i know you despise this). With the ability to control the chipset strap, you have to make the trade off between memory latency and CPU speed (FSB speed). Basically you will have to bench at your max FSB on each of the strap settings (200/266/333) and go with the one that gives you the best stable numbers for the application you are most interested in. As with anything there is no "best setting" for any given CPU, each is different and it all depends on what you are most concerned with.

Tony, how does the chipset strap influence stability of a given speed on your memory? for instance if you were to run on the 133 strap with a 1:3 divider at 166 fsb. That would put your memory at 1000. All the stress would be on the memory controler, not the CPU or the actual FSB. I'm only asking without testing myself because I have no video card ATM.

edit: and i'm probably answering my own question, but I'm guessing that at this low a FSB you are killing your bandwidth to the point where any gains in lower latency are completely overshadowed. But i'll be testing for myself as soon as I get my video card.
<3 EVGA step-up
12-26-2006, 11:39 PM
palese

Quote:

Originally Posted by Teratism

That is the bulk version which I am pretty sure means OEM which is about the same at newegg for the OEM version and other places. I needed to go retail because I own 0 cords and will need them etc. Thanks for the site though.

Glad you found your board, but to set the record straight it is the boxed version, One way to tell besides the fact that they would have to list it as an OEM is the color of the sata connector at the bottom of the board, the boxed one the connector is red and not so on OEM.
12-27-2006, 01:17 AM
heikis

i was using the 1333 strap all along (333MHz referene frequency). but it wont even POST at 266MHz reference frequency. i tried playing with the voltages and so on. anybody have this problem with the lates bios (2395)?
12-27-2006, 03:52 AM
forumtroll

Quote:

Originally Posted by Supertim0r

everest reset the vcore to default (original bad axe had same issue when it came out)

I'm glad I stumbled across this thread... I was wondering why everest crashed my system! It did a hard reset and I had to toggle my bios configuration jumper to post. :)
12-27-2006, 04:41 AM
raj_kemp

Previous BIOS

Hi,

Recieving BX2 tomorrow and have downloaded 2395 BIOS from Intel site. Reading posts about not able to hit 400 FSB with this BIOS, can anyone post/link the previos BIOS 2333 or 2330 as I can't find them on Intel site.

Thanks

Edited: Found them on Intel site...

Show 100 post(s) from this thread on one page

Testing / comparing : Intel D975XBX2 / Asus P5B DX ***56K WARNING***

Testing / comparing : Intel D975XBX2 / Asus P5B DX 56K WARNING