What should stock cpu volts be for quad 6700 ?? My BX2 board auto sets it to max 1.35V :confused:
Also in device mgr I have an unfound PCI device from fresh install, I use on board sound so no sound card involved, and I have no pci device??
What should stock cpu volts be for quad 6700 ?? My BX2 board auto sets it to max 1.35V :confused:
Also in device mgr I have an unfound PCI device from fresh install, I use on board sound so no sound card involved, and I have no pci device??
I thought I may share my results/issues with this board after a bit of testing.
For CPU stability, this motherboard is the best I've tested so far. (see sig)
Previously, my best Orthos results achieved were on the P5B deluxe @ 3820Mhz.
On the Bax Axe 2, Orthos is stable @ 3840Mhz :woot:
http://i10.tinypic.com/4c0iu5g.jpg
As for Ram stability, the results achieved were nearly the same as on my P5B Deluxe.
Results aside, I ran into a problem running with my 8800GTX.
My 3dMark and Aquamark scores are very low compared to similar setups as mine. They seem to be in the range of an 8800GTS :confused:
Here is a thread I started about this issue:
http://xtremesystems.org/forums/showthread.php?t=128365
Any help is appreciated :toast:
reference frequency in the memory settings screen. And yes, performance will be lower because it uses relaxed internal chipset timings. the plus side is by relaxing the timings you end up with a better high end in the FSB speed.Quote:
Originally Posted by badboy
I see your load temp is 83C. A few folks were saying that mine 6600 @ 72C load is too hot but I guess it is not that hot :rolleyes:Quote:
Originally Posted by rick_fx
I'm gonna buy some good digital thermometer for my projects anyway so will try to measure the die temp.
haha 3.84 83C :slobber:Quote:
Originally Posted by rick_fx
how hot is the T120 to the touch ?
btw, your pm box is full ;)
PM box is now empty :)Quote:
Originally Posted by Supertim0r
The TT120 isn't very hot, it only gets warm, even after 6 hours of Orthos.
I would be careful with those temps, whats your v-core???
You should check your contact.Quote:
Originally Posted by rick_fx
Contact isn't an issue, my CPU and Tuniq Tower 120 are lapped and have excellent contact. The point is that the temp sensors aren't right ;)Quote:
Originally Posted by EnJoY
Why are there so many people preoccupied with "safe temps"?Quote:
Originally Posted by chaotic646
If I limited myself to say 70C as a "safe temp", I would never have been able to overclock my CPU this much. As long as the CPU doesn't throttle (tjunction =85C in coretemp), I don't see the need to be "careful". ;)
Vcore is set at 1.5375V in bios, which is 1.47V under load in "Intel Desktop Utilities". :)
can't wait to see what it will do under SS ;)
I thought coretemp was using on die sensor that were the most reliable way to monitor your cpu temps. I limmit myself to the 70c barrier, i would like to know that i can go higher than that :PQuote:
Originally Posted by rick_fx
i'll try 2395 again then. with 1333 strap.Quote:
Originally Posted by Blauhung
we will see if 1333 performs better...
[fidget]
crap, I havn't been able to mess with my computer in 2 weeks due to having no unused video cards wandering about. Had a power supply fry a 7800GTX. My 8800GTX was sposed to get here last Friday but UPS somehow lost my apartment #. Then the driver didn't get back to the depot till after they closed so I couldn't pick it up and now it wont get delivered till tomorrow. Add on top of that the fact I now have the option of getting a QX6700 for $495.
[/fidget]
Any memory experts about?
I have one odd issue with this board. When I select a memory freq of 800 and boot into windows memset detects one stick set @ tRD 6 and the other @ tRD 7. I can change the one stick @7 stick down to 6 without issue. All other values match and this is the only time this happens. tRD isn't different @ 533 or 667. I've checked both sticks with CPU-Z and they have the same part number. They will pass any test I care to throw at them.
Are you sure that the sticks' SPD matches exactly? Perhaps the manufacturer changed the TRD value in SPD and now the board sets TRD according to the SPD value or something like that. Or did you set it to "6" in BIOS and it doesn't correctly set it for the one stick?Quote:
Originally Posted by malficar
They are matched according to CPU-Z and the stickers on them. There is no tRD setting in the BX2 BIOS. I am viewing the settings with memset after I boot and changing them then. I am thinking it's the board because I didn't have this happen with the same sticks on other motherboards.Quote:
Originally Posted by celemine1Gig
I am going to experiment with switching slots and using one stick @ a time and see what gets reported.
EDIT: It's definitely the mobo, or memset is reading things wrong. I tried one stick at a time @ a 800 freq and they boot with the same tRD in that case.
found a video card, did a few quick runs at stock FSB to test out how the strap settings play with timings
http://i18.photobucket.com/albums/b1...traptests1.jpg
these are all with 2395 BIOS
memory timings from Memset
benches from sandra
From what I understand of how the chipset works, there are lots more timings on the northbridge then what memset is reporting, but this gives you a good idea of how Intel sets the memory timings based on the chipset strap. Also shows how the bandwidth and latency scale with the strap at default FSB speeds. I'll start putting together graphs of performance as it scales with FSB speed on each strap
Quote:
Originally Posted by Blauhung
Please explain:slap:
How did you get those ram speeds with 1:1 ratios?Quote:
Originally Posted by Blauhung
:rolleyes: employee purchase programQuote:
Originally Posted by palese
266 1:1 =>266*2 (double data rate) = ddr2-533Quote:
Originally Posted by gtj
Sorry, I thought you were reporting the raw speed. :)Quote:
Originally Posted by Blauhung
hey,
anyone tried the last IDU_3.0.10.15 ?
monitor all the fans now, stable, no crash :)
works for me! the previous versions didnt work.
But... when i click on hardware monitor the first time it worked fine but now it seems to crash the program.... i will try to find out why
has vdroop gotten any better on newer bios versions
any chance the lower multiplier will be unlocked???