i got me some spare chips just for this kinda problems lol
1 for my x38 n 1 for my p35 cost me 23$us for both shipped
It seems i have a problem with my UT..
So.. if i use wolfdale ( tied 3 x E8400 and 1 x E8500 ) and i set vcore 1.5 or more , then the boards shuts off and thats all.
This value depends on cpu, but in the past i dont got this kind of error/bug.
If i set 1.4 and the rest with % its ok, until a value ( higher than before ), but i got same thing with increasing the vcore..
Any suggestions?
brotha esau are selling bios chip :)
it's better if you could get from him :D
thanks ;)
Sorry to hear of your troubles, seems yet another had to learn the hard way NOT to flash in Windows. Quite a few have spoken about this issue. Flashing from a USB drive in DOS mode is the best bet, in fact I have not heard of a single board death when using this method.
Anyone using GSkill F2-8500CL5D-2GBHK on this board? Got a fresh set and want to see how well these play together.
I haven't had any time to clock them yet but I just put together my dads system with this exact board and that exact ram. So far it powers up and posts without issue. Timings are highly relaxed but recognized properly and at 1.9v the system has no problem doing anything. When the Velociraptors and new video card show up for the system I will finally be able to see what it is made of as a whole. One thing I am jealous of is the real low VID of 1.2450 for his Q6600. Wish I had that VID for my own.
@cantankerous: what's the vid on your Q6600?
Well that is stellar, even better than my dads VID, that chip should be a keeper for sure. I can do in the 3.1x range on stock volts with my VID, but anything higher needs a jump to 1.35+
So you still on 5/21? Find it better than 3/17?
I have had a similar thing happen with my 8400 around 1.47+ trying to boot at 4.5ghz with fsb > 500. This is on an e8400 that had degraded a bit (maybe.05v), but it used to boot up and run 32m at that speed with 1.37vcore. It also used to run at 550fsb with around 1.4vcore. I def think it's not the chip, but I want to do more testing.
I will try to just boot up at a low clock with 1.5v and let you know..
Huh, that's interesting. I assume you can go up to 2.0v + with special add? Must be so because I've seen some heavy benchmarks with this board.
I saw in another thread someone having similar issues around 1.45v and even with add could only get in at 1.53v max. A bios flash cure the issue.
http://www.xtremesystems.org/forums/...d.php?t=188307
i am in a dilemma
best overclockability with a q6600 or an e8400... dk p35 , lt p35 or , dk x38 ?
lt p35 and dk x38 are almost same price.. so i wonder...
all I know is, I want a DFI .. my x2 4200+ is running on my nf4 sli-d stable stable for like 3 yrs or so already...
please advice
thanks
@emon
Any benefit over the 3/17? I'm kinda lazy to flash these days. :D
HEy guys, can anyone give me indepth detail of how these all work....
Clock Setting Fine Delay Press Enter:
Tfine Item Value Degree............ - Auto
Ch1 Clock Crossing Setting......... - Auto
DIMM1 Clock Fine Delay............. - Auto
DIMM2 Clock Fine Delay............. - Auto
Ch1 ControlFine Delay.............. - Auto
Ch1 ControlFine Delay.............. - Auto
Ch2 Clock Crossing Setting......... - Auto
DIMM3 Clock Fine Delay............. - Auto
DIMM4 Clock Fine Delay............. - Auto
Ch2 ControlFine Delay.............. - Auto
Ch2 ControlFine Delay.............. - Auto
Ch1 Ch2 Common Clock Setting....... - Auto
Ch1 RDCAS GNT-Chip Delay........... - Auto
Ch1 WRCAS GNT-Chip Delay........... - Auto
Ch1 Command To CS Delay............ - Auto
Ch2 RDCAS GNT-Chip Delay........... - Auto
Ch2 WRCAS GNT-Chip Delay........... - Auto
Ch2 Command To CS Delay............ - Auto
CAS Latency Time (tCL).............. - Auto
RAS# to CAS# Delay (tRCD)........... - Auto
RAS# Precharge (tRP)................ - Auto
Precharge Delay (tRAS).............. - Auto
All Precharge to Act................ - Auto
REF to ACT Delay (tRFC)............. - Auto
Performance Level................... - Auto
[b]>Read delay phase adjust Press Enter:
Ch1 Read delay phase............... - Auto
Channel 1 Phase 0 Pull-In.......... - Auto
Channel 1 Phase 1 Pull-In.......... - Auto
Channel 1 Phase 2 Pull-In.......... - Auto
Channel 1 Phase 3 Pull-In.......... - Auto
Channel 1 Phase 4 Pull-In.......... - Auto
Ch2 Read delay phase............... - Auto
Channel 2 Phase 0 Pull-In.......... - Auto
Channel 2 Phase 1 Pull-In.......... - Auto
Channel 2 Phase 2 Pull-In.......... - Auto
Channel 2 Phase 3 Pull-In.......... - Auto
Channel 2 Phase 4 Pull-In.......... - Auto
MCH ODT Latency..................... - Auto
Write to PRE Delay (tWR)............ - Auto
Rank Write to Read (tWTR)........... - Auto
ACT to ACT Delay (tRRD)............. - Auto
Read to Write Delay (tRDWR)......... - Auto
Ranks Write to Write (tWRWR)........ - Auto
Ranks Read to Read (tRDRD).......... - Auto
Ranks Write to Read (tWRRD)......... - Auto
Read CAS# Precharge (tRTP).......... - Auto
ALL PRE to Refresh.................. - Auto
These things muddle me. Its not use just playing around with them hoping to see performance, its better to know what does what and what affects what.
If someone has the time to explain I would really appreciate it. Coz i like to learn more about my boards potential.
Thanks DoOb's
Anyone using GSkill F2-6400CL4D-4GBHK on this board???
Any idea to do with my config 500x8? or 445x9 to use 24/7, I need some help to achieve good stability....
Anyone getting Vdimm droop on this board? In my case it seems to have shown up over time. I have three different D9GMH kits, one of which is brand new as of yesterday so degradation of the ram itself is not an issue. I found that adding .1v got me back stable at clocks that were 8 hours stable months ago but had slipped.
In other words does this board show signs of wear and tear after months of high fsb usage? Maybe a break in phase? I need to measure this from the board sensors this weekend.
Board still rocks though.
let us know what you come up with after you have actually measured with some sort of tool as concrete numbers say a lot. Perhaps your board is exhibiting said issue, but that doesn't mean it will happen in general to this make and model. It also sounds exactly like what happens when ram degrades. I know you said one kit is brand new but hey.
Perhaps try another bios that you were familiar with working with in the past as changes may have been made in later bioses that exhibit this sort of behaviour. When you say high FSB over time, how high is high?