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

[loafer87gt]

What the heck. I just fried another stick of Dominator 8500 with this board. This is the second set of modules now that I fried using this particular board. Previously I was running 4GB of C8500D memory, but was having some stability issues running everything at stock speeds. It turns out one of my sticks in slot 3 (second blue slot) was toast and was causing the problems. I pulled the one set of ram out and was planning on RMA'ing it to Corsair this weekend. This afternoon I started to have some more crashes, and ran mem test to find I have another dead stick.

Is this just bad luck, or do you guys think that maybe my board is killing ram modules?

[Severance]

What the heck. I just fried another stick of Dominator 8500 with this board. This is the second set of modules now that I fried using this particular board. Previously I was running 4GB of C8500D memory, but was having some stability issues running everything at stock speeds. It turns out one of my sticks in slot 3 (second blue slot) was toast and was causing the problems. I pulled the one set of ram out and was planning on RMA'ing it to Corsair this weekend. This afternoon I started to have some more crashes, and ran mem test to find I have another dead stick.

Is this just bad luck, or do you guys think that maybe my board is killing ram modules?

I had same issue. This board killed my OCZ aplha titanium sticks. It seems setts at fsb333, 533\200 divider kills the stick in slot3. Using stock 266 divider is safe but 200 is problem i think.

[loafer87gt]

I had same issue. This board killed my OCZ aplha titanium sticks. It seems setts at fsb333, 533\200 divider kills the stick in slot3. Using stock 266 divider is safe but 200 is problem i think.

Sorry, but can you please clarify? Are you saying using the reference frequency set at 333 or 200 can damage your ram? Both sticks that have gone bad have been in Slot 3 on my board as well. I was using the default reference frequency both times with my ram frequency set to 800 at 2.2V. Mem timings were set at a conservative setting of 5-5-5-18 while trying to troubleshoot stability probs.

[Severance]

Sorry, but can you please clarify? Are you saying using the reference frequency set at 333 or 200 can damage your ram? Both sticks that have gone bad have been in Slot 3 on my board as well. I was using the default reference frequency both times with my ram frequency set to 800 at 2.2V. Mem timings were set at a conservative setting of 5-5-5-18 while trying to troubleshoot stability probs.

I killed 2 sticks of memory using 200. I never had a problem with 266 and 333 but u say that u have had a problem. So i guess its not the 200 killing sticks. Both of us killed mem in slot 3 so thats a good place to start trying to figure this problem out i guess. my timings in both cases were set to 4.4.4.12

[Suge Knight]

Max FSB without mod with my 6600 step 5:

Strap 1066:


Strap 1333:

[Zucker2k]

how did you drop multiplier?

[Touchstone]

First off, a big 'thanks' to everyone contributing to this forum. It helped me a great deal when I replaced my P5W DH with the 'BX2.

I have a question, though ... I'm currently running a mild overclock, 9x333MHz FSB on an E6600 to hit 3GHz, and I'm trying to get the memory running with a 1:1 ratio. (BTW, the RAM is 2Gb Corsair XMS2 DDR800, the 'BX2 is a rev. 503, and I'm running 2507 BIOS.)

So, after reading 'BX2 calculator' and 'ratio formula' posts, I set reference frequency to 333 and the memory frequency to 667. IDCC shows what I'd expect - an FSB of 1336 and Memory at 667. But CPU-Z is reporting an actual memory frequency of 417.6MHz (4:5); not a 1:1 ratio?

Could someone educate me and point out the error of my ways?

Thanks in advance...

[jetjaguar]

First off, a big 'thanks' to everyone contributing to this forum. It helped me a great deal when I replaced my P5W DH with the 'BX2.

I have a question, though ... I'm currently running a mild overclock, 9x333MHz FSB on an E6600 to hit 3GHz, and I'm trying to get the memory running with a 1:1 ratio. (BTW, the RAM is 2Gb Corsair XMS2 DDR800, the 'BX2 is a rev. 503, and I'm running 2507 BIOS.)

So, after reading 'BX2 calculator' and 'ratio formula' posts, I set reference frequency to 333 and the memory frequency to 667. IDCC shows what I'd expect - an FSB of 1336 and Memory at 667. But CPU-Z is reporting an actual memory frequency of 417.6MHz (4:5); not a 1:1 ratio?

Could someone educate me and point out the error of my ways?

Thanks in advance...

from what i read .. cpuz is bugged and doesnt report the right mem ratio or speed when running the 1333 strap ... try IDCC that showed the proper one fo rme

[shogo_ca]

4x1gb of Teamgroup DDR800 4-4-4-12 CL4 were DOA or were killed with this board because the machine refused to boot when those sticks were installed, but it booted fine with other sticks with the same speed and timings...

I would be surprised that the board is killing the sticks.

[Suge Knight]

how did you drop multiplier?

http://www.overclocking-masters.com/...coef,t3254.htm

[JZX100]

http://www.overclocking-masters.com/...coef,t3254.htm

Ahn... eeerrrr, can u translate it for us?

[Suge Knight]

- Open cristalcpuid
- function
- msr editor
- write 0x1A0 at MSR number
- clic to rdmsr
- copy EAX and EDX
- change at EDX the 2° number by 1 and 4° by 5:

exemple:
you have 0x62860089
change by 0x61850089

When the 2° number is 1, the C1E is disabled
When the 4° number is 5, you can change the multi with cristal cpu

[gtj]

First off, a big 'thanks' to everyone contributing to this forum. It helped me a great deal when I replaced my P5W DH with the 'BX2.

I have a question, though ... I'm currently running a mild overclock, 9x333MHz FSB on an E6600 to hit 3GHz, and I'm trying to get the memory running with a 1:1 ratio. (BTW, the RAM is 2Gb Corsair XMS2 DDR800, the 'BX2 is a rev. 503, and I'm running 2507 BIOS.)

So, after reading 'BX2 calculator' and 'ratio formula' posts, I set reference frequency to 333 and the memory frequency to 667. IDCC shows what I'd expect - an FSB of 1336 and Memory at 667. But CPU-Z is reporting an actual memory frequency of 417.6MHz (4:5); not a 1:1 ratio?

Could someone educate me and point out the error of my ways?

Thanks in advance...

You might also want to change to 266/533. This will still give you 1:1 but since this will be the 1066 strap, you'll get a little better performance.

[shimmishim]

- Open cristalcpuid
- function
- msr editor
- write 0x1A0 at MSR number
- clic to rdmsr
- copy EAX and EDX
- change at EDX the 2° number by 1 and 4° by 5:

exemple:
you have 0x62860089
change by 0x61850089

When the 2° number is 1, the C1E is disabled
When the 4° number is 5, you can change the multi with cristal cpu

what a pain!

are unlocked chips such as the qx6700 and x6800 have access to other mults through bios or are they locked at 10x and 11x, respectively?

[Suge Knight]

No the X serie (X6800 & QX6700) are unlocked in the bios but the other are locked also downwards on the XBX2

It is a pity really

[LazyBum]

I have never heard of any problems with the X-fi on this board, mine works flawlessly. I am in one of the upper slots, not sure that it matters, though.

[Supertim0r]

for me, it's not a problem with the board, only my X-Fi dying

[EtherealRemnant]

Okay so this is my first post here.

Long time lurker and I think its time.

Anyway, I have a Core 2 Duo E6300 that can hit 3.2GHz on a DQ6 (and I didn't even get a chance to tweak it much before I returned that board for lack of compatibility with everything under the sun) but on this board, which I bought from reading a few pages in this thread, it will not overclock at all.

I can raise the bus to 276. That's it. I've played with different BIOSes, all the different settings, disabled Watch Dog, C1E, and EIST, and still.. nothing.

Any time I tweak the settings at all, I get the three beeps for memory failure and have to reset.

I have 2 gigs of OCZ Platinum Revision 2 (OCZ2P800R22GK) that worked perfectly in the DQ6.

I'm really bummed out right now... it was totally stable on the DQ6 but on the Bad Axe 2, it won't budge at all.

Any ideas? I'm completely new to Intel overclocking (the last Intel system I built was an old school Celeron back in 2000) and this is driving me insane.

Also, this board runs the processor at least 8 degrees hotter than the DQ6 did and yes, I cleaned the proc with isopropyl alcohol as well as the heatsink and applied brand new thermal compound both times (the same stuff, roughly the same amount).

Either the thermal readout on the DQ6 was wrong or the Bad Axe is wrong. It says that both cores are running 57C right now with totally vanilla stock settings and when I load them both to 100, they hit 74C before I get nervous and stop the experiment.

I hope I'm just doing something stupid and that I really didn't make a bad choice getting this board. I'll be really upset if I have a bad board since Microcenter won't let me return another one.

[Severance]

Okay so this is my first post here.

Long time lurker and I think its time.

Anyway, I have a Core 2 Duo E6300 that can hit 3.2GHz on a DQ6 (and I didn't even get a chance to tweak it much before I returned that board for lack of compatibility with everything under the sun) but on this board, which I bought from reading a few pages in this thread, it will not overclock at all.

I can raise the bus to 276. That's it. I've played with different BIOSes, all the different settings, disabled Watch Dog, C1E, and EIST, and still.. nothing.

Any time I tweak the settings at all, I get the three beeps for memory failure and have to reset.

I have 2 gigs of OCZ Platinum Revision 2 (OCZ2P800R22GK) that worked perfectly in the DQ6.

I'm really bummed out right now... it was totally stable on the DQ6 but on the Bad Axe 2, it won't budge at all.

Any ideas? I'm completely new to Intel overclocking (the last Intel system I built was an old school Celeron back in 2000) and this is driving me insane.

Also, this board runs the processor at least 8 degrees hotter than the DQ6 did and yes, I cleaned the proc with isopropyl alcohol as well as the heatsink and applied brand new thermal compound both times (the same stuff, roughly the same amount).

Either the thermal readout on the DQ6 was wrong or the Bad Axe is wrong. It says that both cores are running 57C right now with totally vanilla stock settings and when I load them both to 100, they hit 74C before I get nervous and stop the experiment.

I hope I'm just doing something stupid and that I really didn't make a bad choice getting this board. I'll be really upset if I have a bad board since Microcenter won't let me return another one.

In memory bios settings choose 266\533. then try to overclock. If u already have tried this then sorry.

[EtherealRemnant]

Well the weird thing is that it always resets my memory timings back to 5-5-5-15 too even though I manually set then at 4-4-4-15 so either way, I'm not accomplishing what I want.

Think I just have a faulty board? I'm not so sure that Microcenter will let me exchange a third time even for the same board.

[shogo_ca]

Either the thermal readout on the DQ6 was wrong or the Bad Axe is wrong. It says that both cores are running 57C right now with totally vanilla stock settings and when I load them both to 100, they hit 74C before I get nervous and stop the experiment.

monitor the temps with coretemp, its the most accurate one at the moment. If you still see 70c+ reseat the heatsink.

[EtherealRemnant]

monitor the temps with coretemp, its the most accurate one at the moment. If you still see 70c+ reseat the heatsink.

Thanks. I just discovered Core Temp through a Google search.

53C idle, 69C load (loaded both cores to 100% using TAT and monitored both programs - they're only about 1 degree C off of each other). Ouch. If I start kicking up some heat with the 8800GTS, it might catch on fire....

I'm going to grab some Arctic Silver tomorrow and see if I can find a decent cooler at CompUSA. Highly doubtful but I'm going to try.

Any recommendations? I had to toss out the CNPS9500LED I had on my old Athlon 64 system because it won't fit. I really liked that cooler. :/

[HeyNowDawg]

Thanks. I just discovered Core Temp through a Google search.

53C idle, 69C load (loaded both cores to 100% using TAT and monitored both programs - they're only about 1 degree C off of each other). Ouch. If I start kicking up some heat with the 8800GTS, it might catch on fire....

I'm going to grab some Arctic Silver tomorrow and see if I can find a decent cooler at CompUSA. Highly doubtful but I'm going to try.

Any recommendations? I had to toss out the CNPS9500LED I had on my old Athlon 64 system because it won't fit. I really liked that cooler. :/

Sho, so I've used 2 aftermarket coolers with my CD2's: on my E6600, I've got a Tuniq Tower and on an E4300 chip, I'm using an Arctic Freezer Pro7. while both do an excellent job, I am far and away more pleased with the Tuniq product. Pricewise, I think I paid around $35 for the Freezer and around $54 for the tuniq..both I think were reasonable in terms of value.

[EtherealRemnant]

Hmm... I thought I heard something about the Tuniq not fitting right on this particular board though.

I have a feeling I'm going to run into that problem regardless of what I choose. This board doesn't exactly have the best layout in the world for a large heatsink.

I'll see what they have locally tomorrow because I'm dying to get this system screaming...

I think I'll pick up an Antec Nine Hundred case too and dump my Thermaltake Xaser... its a bit outdated and I think its part of the problem.

[HeyNowDawg]

Hmm... I thought I heard something about the Tuniq not fitting right on this particular board though.

I have a feeling I'm going to run into that problem regardless of what I choose. This board doesn't exactly have the best layout in the world for a large heatsink.

I'll see what they have locally tomorrow because I'm dying to get this system screaming...

I think I'll pick up an Antec Nine Hundred case too and dump my Thermaltake Xaser... its a bit outdated and I think its part of the problem.

The only problem I ran into installing on the board was tightening down the sink to the backplate...fingertight has to be like superman finger tight so that it doesn't budge. I've got big paws so I finally settled on doing the whole install outside of the case and then I was fine.

It can be a bit of a tight squeeze depending on your case, but I'll tell ya, well worth the effort, this thing is amazing.