however everest says its at 1066?
im relatively new to this stuff obviously
Printable View
however everest says its at 1066?
im relatively new to this stuff obviously
Folks, don't worry about "memory frequency" or any other displays other than an actual benchmark and some simple math.
Actual memory frequency is simple math based on the BIOS FSB, Reference Frequency, and Memory Frequency settings. Use the spreadsheet in my sig. It's NOT variable. It is what it is.
What many programs report as "Memory Frequency" or "Memory Speed" is actually read from the memory's SPD table and that's a static table programmed at the factory. The SPD is there for 1 main reason: to allow the motherboard to boot successfully without intervention. My OCZ3-1800 sticks show up as DDR3-1333 because that's the highest entry in the SPD. Why? Because there's no motherboard or processor on the planet that can use an 1800 SPD entry and 1333 will pretty much guarantee a successful boot.
If you want to see actual memory frequency, look at Everest's "Motherboard" page. The "Memory Bus Properties" shows your actual settings.
I did that after many reboots.
I think the host clock is wrong or it's not reported right.
Quote:
Originally Posted by down8
Hey DOWN8,
Can you do me a favor and see if you can lock your multi on your Q6700 to something lower than 10 and have that reflected in Windows somewhere other than IDCC?
Would appreciate it
sean
I'll try to give that a shot today.Quote:
Originally Posted by Sean-E-Boy
EDIT: Tried disabling C1E, and lowering to 8x. It still dropped to 6x occasionally.
-bZj
Hi Pontius
Like gtj said, don't worry about that, it's only the SPD safe settings for initial booting purposes.
Sometimes manufacturers even use the same chips but higher binned to make modules of a higher speed grade, like 1066 rated chips to make 1333 modules, or enhanced latencies modules.
mpeg3s
Check that you're using the correct BIOS and IDCC versions, the latest v4.1.0.169 only works with BIOS 1554, same for earlier versions 1521 with 128 and so on. Maybe that's the problem. If you had voltage or regulator problems probably your system wouldn't work.
I'm still getting BSODs. And, I've even given up on 1600 for the RAM. It won't stable up at 1333MHz. I'm at 325.
I'm not sure whether it's the RAM or the BT, however.
-bZj
sure it will drop, but if you go under load, does it stay at 8 or jump back to 10?Quote:
Originally Posted by down8
Ah, it does stay at 8x - by "lock your multi," I thought you meant "lock your multi."
-bZj
Well finally got my board setup, and I don't get anything. No beeps, nada, just a blank screen. It was late last night, and I didn't get a chance to fully troubleshoot it - but I'm guessing my problem is one of these things....
- Stock bios revision does not recognize an E8300.
- Memory
- Try Maintence/Recovery mode jumper
if it still does not work with one stick of memory in any of the slots, or the recovery mode jumper , ill have to try using my E4300 and see if it boots it up. Did anyone need to flash before getting one of the newer wolfdales to boot up besides the e8400 ? (e7200,e7300,e8300,e8500, etc)
ok so I was looking at the temps, I have a Q9300, and from past experience the heatsink for dual cores is a perfectly fine heat sink, but man do these chips just run super hot? is that ok, it doesnt seem like it is. I guess its got me a bit worried cause I'm intending to put some more stuff and probably OC somewhat when i get a new heat sink for it. heres a page, let me know what you guys are experiencing please.
uh yeah i just read a little bit more, theres definetly something wrong... uh maybe i put the heat sink in facing the wrong direction???? would that make a difference?:shrug:
isnt the fan speed supposed to go up ?
well I got my board up and running. A few memory pulls, switched slots, configuration jumper, and battery pulls later, it finally boots :). Got Vista 32 Ultimate installed, RAID Setup, Bios flashed to 1554.
Pain in the ass, but not too bad coming from an XBX2 :)
Now to see how high I can ramp my E8300...
Hmm, doing pretty well with my DX38BT. :) :). Some little quirks initially, but I am liking it as well as my previous XBX2!
Here are some initial benches. I have not tweaked memory at all yet aside from setting the top 3 timings in the bios. I'm going to try and Orthos this overnight...
http://www.fileden.com/files/2006/6/20/80195/4GHz.jpg
I am using the
Ref: 400MHz
Mem: 1333MHz
vMem: 1.86
vMCH: 1.475
vFSB: 1.375
First off, my latency sucks, no doubt because of my timings as well as the 400MHz strap. I doubt I can hit this FSB using the 333MHz strap, but I might try it out tomorrow. Need to work on tweaking the voltages, memory, and making sure this is 24/7 stable at 471FSB / 4GHz. I think my vFSB/vMCH is a tad high? Using an Enzotech RNB-R1 NB Cooler with a 40x28mm Delta on the Northbridge
you definitely won't be able to hit a 470 FSB with the 333 strap. my 333 strap hits a wall somewhere around 440 FSB. and your hard drive speed is through the roof. nice setup.
yeah, i tried hitting 470 on 333 and was presented by a nice black blank screen :)
Still trying to get this stable and find the right blend in voltage settings. Memory is giving me very strange results. Anything above 1.78 vMem causes Orthos Blend to fail instantly even though I have active cooling over my sticks. Happens with any timings too. HD speed is using Matrix Raid with a 40GB Slice on each of my three drives on the OS Array
Ok so I got a new Heat sink and I idle about 39c, and 50 under load, which is fine, Im just curious did you guys turn off the system managed fan control setting so it runs at full all the time?
A fan controller is a great $20 investment where you will have much better control of your fans over system managed settings.
my 1.78v problem might be related to Orthos only, sincle Prime95(latest beta version) Blend seems to run fine as well as MemTest for anything over 1.78v. Very strange. Also, what is a good way to test out vFSB? Stressing the hell out of the Northbridge? vFSB should not have any effect on memory stability (vMCH moreso), but rather just to get your board booting at a higher FSB, correct?
vFSB will have a direct impact on what appears to be memory stability since the path from the processor to the memory passes over the FSB. If the vFSB is off, Prime95 will still pass the small FFTs (because they're done in the processor cache with minimal traffic over the FSB) but will fail the other tests.Quote:
Originally Posted by Miwo
ahh ok, gotcha.
I'll just stick with Prime95 Blend + HCI Memtest for Memory/System/FSB testing and Small FFTs for CPU as usual then.
How high is a safe voltage for vMCH and vFSB using Air Cooling? Running at 1.5v vMCH currently and its passing Memtest + Blend from what I can tell (passed a 6 hr overnight run). If I hit 480FSB, it makes for an even DDR1600 on the 400Ref/1333MHz Mem setting, which I feel confident my sticks can do with decent timings.
Looking pretty stable at 471FSB.....
http://www.fileden.com/files/2006/6/...#37;204ghz.jpg
Time to push the FSB more :P
So I have a question, with everything at default, at idle there is almost always a 10degree difference between cores, like 35,45,36,45,
I overclocked just to mess around and try some of this stuff out and set the multiplier so that it wont change, and upped the voltage a litte bit, and those temps became within 3-5 degrees of each other like 43, 46,44,46.
anyone have somehting similar?
anyone get the stuck sensor message from real temp if you test the sensors?
No stuck sensors but I see the same 10deg difference on my Q9300.Quote:
Originally Posted by Pontius
is it ok to just go ahead and bump my pci express freq up to 109.24?
oh and thank you!