190 fsb
So far this is the highest fsb I have ever had a system. I'm please so far but concerned with the temp readings of this mobo/WCing system.
Printable View
190 fsb
So far this is the highest fsb I have ever had a system. I'm please so far but concerned with the temp readings of this mobo/WCing system.
Yes...they do. I've experienced the same temp reporting with the KD7-E as I have with the KD7-RAID. System temps always read kinda high on both . Based on the sys temp research I did on the KD7 a few months ago, I don't worry much about the sys temps reading higher than we've seen on other Abit boards. Once i baseline the sys temp under normal operating conditions, I watch the changes in temp more than the actual value when overclocking. My original KD7-RAID has been running loaded sys temps around 43-45c for months under 24/7 load (folding) now without incident. The case it is in has exceptional airflow to boot. I don't sweat it any more:)Quote:
Originally posted by bigdawginva
Anyone know if they used the same method for all KD7s?
That is true Mike :)
My sys temp is always 6-8 degrees celsius higher than my CPU temp. Dont bother me as long as it doesnt rise much under load.
If you look at the motherboard pics you'll see that the location of the motherboard temp sensor is right up against the NB heatsink.
Does your KD7-E NB run a bit hot? Mine sure does and the air coming off that HSF blows right onto the system sensor.
I believe that OPP mentioned sensor placement as one of the things he'd change on the KD7, looks like it's one I'd want changed on the KD7-E.
How should I set up MBM5 to monitor the system properly? My system temp also reads quite high on the board, about 41c. My new Vantec AeroFlow HSF has knocked 13c off of my CPU temp over that P.O.S. AOC model I was using. I am very happy about that!
SPQQKY, look at your manual - the "system" sensor is next to the northbridge heatsink. All the warm air coming off that northbridge heatsink is flowing over the system sensor and heating it. You won't be able to get true ambient case temps on this board without an external sensor or without unsoldering that system sensor and moving it somewhere else.
SPQQKY,
What you want to do is take note of what your system temp is about 15 minutes after boot up when you're not overclocked. Consider that your baseline sys temp. From there just keep an eye on what change from baseline you see as you overclock and run for extended periods to get a feel of how things are sys temp wise. Remember your temps are relative measurements. It's really the fluctuations that matter.
To be honest, sys temp has always been one of the lesser important temps for me to watch anyway. I'm very careful about having very good case cooling, so there is not much more i would do regardless of what the sys temp sensor reports anyhow. Far more important is the CPU temp.
I went through the same thoughts you did when I got my first KD7-RAID which reported the same high sys temps. sjohnson is correct about why they read so high...tucked right under the NB hsf about an inch from the mosfets. I think abit did this on purpose to be honest. The KD7 series offers some crazy high voltage options, and i think the high sys temps keep the noobs from doing something stupid. Just my guess though.
Bottom line...don't sweat the sys temps. But keep an eagle eye on the CPU temp:)
I agree. I've gotten so aggravated looking at it reading 45-50c that I took it off MBM readings and just read my CPU temp.
I am not worried about the system temps, just saying it reads higher than I am used to. I know my case has good cooling. I was fully aware of the temps reading higher on this board than I am used to before I got it. It doesn't bother me, I know it will be any large fluctuations or spikes that I will worry about. I put a Vantec Iceberg on the northbridge, so I know it is cooled good enough. I just wanted to know which sensors I should use for the board. I have a secondary temp sensor from my Enermax multifunction transfer panel that I can read case temps from, in fact, I kinda like the sensor being close to the northbridge.
Okay:) Sorry if my post sounded like a lecture...didn't mean to make it come off that way:) It looks like you have a very good grip on the aspects of the board and what to expect.
I'm unfamiliar with your Enermax multifunction transfer panel, so I can only tell you that I use the Winbond 1 sensor to monitor sys temp in MBM 5.
I think you have it pretty much sorted now anyway:D
Bad luck for me, my Radeon 8500 died on me and now I believe my psu is going bad. I am getting low voltage readings, which is what may have been wrong with my 8k9a2+. I am back to a Radeon 9000 Pro and a new psu is on the way.
Sorry to report that my primary IDE channel went bad. Thought it was the disk, then the cable but the disk checks good on another system and several different new 80-conductor cables were tried without helping.
The disk was a Maxtor and the current MaxDiag couldn't even identify the drive for testing. Installed in my kx7, the disk tested completely recertified without error under MaxDiag. My KD7-E is already boxed and going back to Newegg.
Symptoms were increasing length of shutdown and frequent re-cal clicks and buzzes. Just before I tried to test it, the shutdown from Win2k took over 10 minutes. Again, the drive itself checks out perfectly.
This question is for MrIcee, mdzcpa, SlimHitman, Duran and others who are having high FSB success with this mobo.
So far the highest FSB I can reach with my combo listed in my sig is 190. If I bump it to 195 I get lockups and freezes in games and benches. I make sure my multi is turned down to 10 just to eliminate the CPU so that's not the issue. My memory setting is at Turbo, Enhanced for Benchmark, and all others are default.
I'm thinking it's the memory timings I need to play with to get 195+ but not sure which. Also, I'm not sure which Corsair stick I have since the person I purchased it from removed the white sticker. Sandra says it 2700 but I'm not sure if Sandra is that accurate anymore.
Of course, it could be the 9700, but I would think it should run 78mhz.
Any suggestions to try for 195+? TIA!
Sandra says i have SDRAM, so dont bother :)
My suggestion is to set your RAM timings to lowest possible to eliminate that, try disable UDMA(shouldnt be necessary though) to eliminate the HDD, try with another GFX card. That is what i think is most likely, even though Mike is running his Radeon at 200mhz fsb.
Gl m8
SPQQKY:
Sorry to hear of the demise of your 8500. keep us posted when things are back in order. I am curious as to your results with the KD7-E.
sjohnson:
Wow...an IDE going out sucks. Sorry to hear it. Are you going to get another KD7-E or go for something else?
bigdawginva:
It could be a number of things, but I think you have keyed on on two better possibilities...the memory and the 9700.
I run my memory timings set to Manual, CAS 2, 4 Bank, 2,6,2. I have also raised the memory voltage to 2.85v. These settings work great with my Corsair XMS3500.
Now depending on which memory you have makes a big difference. If it is reading as PC 2700, my guess is that you have either Corsair XMS2700 or XMS3000. XMS3200 and XMS3500 usually read as PC3200 memory under Sandra. If this is the case, you will need to work much harder to achieve higher FSB speeds as you'll be pushing the memory harder.
There are two things you should do. First, relax the memory timings to CAS 2.5, no bank interleave, 3,7,3 and see how high you can go FSB wise. If you find an improvement in how high you can go, we'll know it is the memory holding you back. If you have no luck with relaxed settings, make sure you've tried upping the memory voltages too.
If relaxed memory timings do not get you any further, I'd suspect the R9700 or another component is holding you back. So the next thing to do is try another Vcard.
My R9700 has no problems running high FSB speeds on this mobo, but that's not to say everyone will have the same success. The R9700 is a finicky card for sure.
This should get you started in your investigation I hope:)
Looks like DuraN has you covered already...sheeze I type slow:)
BTW, hard freezes do sound more like video card trouble. Memory instabilities usually lead to BSODs or CTDs (crashes to dekstop) when benching/gaming.
But...let's take it one step at a time.
Thanks so much for the help. This is the most advice I've gotten in awhile so it's very beneficial.
I ran Sandra and again it reads my memory as Corsair CMX512-3200 512MB 16x(32Mx8) DDR-SDRAM PC2700U-233-700 (CL2.5 upto 167mhz) (CL2 upto 167mhz).
I checked the Cosair pdf for this stick and the SPD is probably programmed to read the PC2700 piece but I'm confident it's reading the CMX512-3200 correctly.
I have the vdimm set at 2.85v currently. I will try to eliminate the memory by trying the suggestions.
Currently, I am running the CPU at 190*12 @ 1.85v
Thanks again!
I think you are right about your memory...it definitley sounds like a 512 stick of XMS 3200. This is good.
Try relaxing those memory settings and let's see what happens:)
Have you tried raising the vcore bigdawg?
I am still stuck at 213fsb at fastest settings.If i lower the timings and try 214 it messes up windows,one time it messed windows at 211fsb. Still waiting to find a good deal on a used Seagate Barracuda IV, i heard they are good for high fsb.
Check out these voltages. I think this has to be a failing PSU, this was happening on my old board as well. The fluctuations and lows are to extreme for my liking, even if they are within 5%.
BTW, the vcore is set to 1.725v and another note is my vagp is only 1.53v instead of 1.57v.
SPQQKY:)
Your AGP is about right for the KD7....I've run 3 and all 3 ran at 1.52v. Also, the Vcore flucuation is also not unusual on an ABIT board..or at least mine, your 3.3v line looks good. My concern would be to strengthen your 12v and 5v lines, they are both under what I would like to see. Strengthening those lines will also aid in keeping your Vcore strong under load. Not sure if you can tweak the +5v and +12v lines on that Antec, but if you can I'd start there.:)
Randi:D
MrIcee never sleeps either;]. I was thinking basically what you said above. The KD7 loves to chug on that 12v rail even with the extra connector as many have seen and may be tough to bring up. I honestly don't think the power supply is failing though. At least not from these readings alone.
Tiribulus:D
There are no adjustable pots on the Antec TruePowers. And after puting in the Radeon 9000 I haven't had a single lock up or reboot, which seems obvious that the 8500 was what gave me all the grief with my system and not the psu. So far the system has run for 72 hours straight without a hiccup.
Good news SPQQKY:)
I've also noticed the same kind of voltages on my KD7-RAID and KD7-E....but they have caused me no troubles whatsoever. I think Randi has once again hit the nail on the head with this KD7 issue:)
My +12v is hovering around 11.80 all the time, although my +5v is stronger, like 5.08-5.11. Im currently using my Antec 340W, but its the same with my Chieftec 340W. On the other half, my brothers 350W Enermax would not cut it with this board.
Btw, my AGP is 1.55v steady, not moving at all :)
Hey SPQQKY:
Up to 200 fsb for you it seems:)
Hey mdzcpa what is the highest FSB that you've achieved 3DMark proofed? So far I am burning in a second 256Meg Corsair 3200 platinum for my Nforce board and I am up to 195 max timings at 1.85 volts.
I have got this 3DMark high fsb:
http://service.futuremark.com/compare?2k1=5348582
But this is my ram stopping me,can do 215 mhz windows (prolly 210 3DMark) but the bandwidth is bad due to slow timings
i believe SlimHitman has achieved a 212mhz fsb and even ran the full test
What were his voltages and timings? Also do you know if he was using a 333 or a 266 processor?
As it sits now with the R9700 Pro in there, it will loop 3DMark2001 at 202mhz indefinitely, and make solid bansi runs that can get through the bench once or twice up to 205mhz. Unfortunately the Radeon is FSB sensitive so that's where the fun stops.Quote:
Originally posted by Nohto
Hey mdzcpa what is the highest FSB that you've achieved 3DMark proofed? So far I am burning in a second 256Meg Corsair 3200 platinum for my Nforce board and I am up to 195 max timings at 1.85 volts.
Memory timings at that speed are at CAS 2, 4 way, 2,6,2 @1.85v with 2 256 sticks of XMS 3500C2.
If I stay out of 3D apps the system will boot and run Windows just fine up to 218....Prime stable. I am contemplating putting my Ti 4600 back in there just to see how high things will go FSB wise in 3Dmark. But I know my overall 3DMark score would drop so I haven't been eager to do that just yet.
What about the last set of timings :
Dram Access
Enhance Dram Perf.
Dram Command Rate
Write Recovery Time
Dram tWTR
What processor are you running? 333 or 266?
Dram Access: 3T (default)
Enhance Dram Perf: Enabled
Dram Command Rate: 2T with 1.85v, 1T with 2.95v up to 205
2T above 205 with 1.95v
Write Recovery Time: 3T (default)
Dram tWTR: 3T (default)
Processor is a 333mhz XP 2700.
Thank you good sir I appreciate it.
Nate
Anytime M8:)
So far rock solid at 190*11.5 @1.85v but 195*11 won't boot into windows even with the most relaxed memory settings. I'm guessing it's the 9700 but I'll try this old GF3 to make sure.
Sorry for the delay in reply, just got back from a trip.
Newegg p*ssed me off, they won't give me a full refund - I have to pay 15% restocking fee on a broken board.
I don't know why, but they don't want to cross-ship on a "repair' RMA - and I don't trust them on a "repair" - I want a new board not a refurb and they don't seem to want to assure me I'll get a new board from them.
So, I'm taking a 15% plus shipping loss and getting my money.
Don't get me wrong, Newegg is great for stuff that works but I've had zero satisfaction with them on RMA stuff. The last RMA I got from them was on a refurb and the received replacement was DOA. Sent it to ABIT, cross-shipped and was ultimately happy.
Another KD7-E sounds appealing but I may just chicken out and get a KX7. Has anyone yet gotten to 220 FSB on the KD7-E, at least stable enough for a WCPUID and Sandra SS?
I'm still stuck at 214fsb if i try 215 with udma on it scrambles my OS.I just tried setting it to pio4 and it just reboots instead of scrambles.
Wish they would hurry with the kt400a.
That sux about Newegg shafting you with the 15%.
Ow! Before my kd7-e started going south on me, I had it up to 218. No screenies, I was pushing for higher FSB and after a 12-hour sandra mem burnin at 218 I tried for 219 and my problems began :( It *was* sweet while it lasted tho :)
I'm not sure whether my KD7-E could get there or not. My R9700 Pro begins holding me back above 205mhz:(
Still, though, this is the most silky smooth 200+mhz board I've ever had. It has yet to bsod, freeze, or bomb out in Prime/3DMark...and it runs 24/7.
Man...I hate sounding like a cheerleader about this board. But it's just worked so well...for me anyway:)
Agree with mdzcpa. A nice, smooth board.
I don't know why mine went bad but think that the NB went sour since both memory performance and Max FSB went way down prior to the controller failure. In fact, it seems likely that the NB either influenced or caused the IDE failure.
I was aggressive in working it up to high FSB (less than a week from receipt to 218 FSB), perhaps a long, gentle burnin would have been more productive.
OK, I liked the board so much that I bought another. Newegg was OOS plus the RMA left a bad taste in my mouth, so
$84.99 *shipped* at googlegear: http://www.googlegear.com/jsp/Produc...uctCode=240095 - almost recoups my lost newegg $$, at least makes it less painful :)
Since I'm still struggling to get over 190 fsb even with removing the PCI cards, I thought I'd try a different approach.
I realize Sandra is unreliable but it indicates my AGP and PCI buses are running 96 and 48mhz, respectively.
Clearly, this would indicate it's seeing a 1/4 divider and not 1/5. Can I assume the 1/5 divider is indeed operating?
I haven't tried Sandra 2003, but 2002 has problems reporting correctly on the KD7-E.
I got the same relative AGP and PCI speeds on mine that you're getting, plus the added bonus of Sandra "seeing" SDRAM instead of DDR, so my memory bandwidth efficiency was typically 192% - don't trust Sandra's reports on this board until they put out a version that supports it.
Indeed you can. Sandra hasn't reported the KT333 divider properly for some time now :)Quote:
Originally posted by bigdawginva
Can I assume the 1/5 divider is indeed operating?
Thanks. I never had a need to check with my KX7-333R so I didn't realize this had been an ongoing Sandra issue. I verified by switching to 1/4 and it wouldn't even boot so that's when I confirmed the 1/5 was indeed working.
I can boot 195*10 and 200*10 all day long but will never get into WinXP where it just hangs. That's even with the PCI cards out. My only other thought is the NB, caps and/or mofsets are too warm to get past 190. I'm not going to add more fans just to cool the mobo as I'm quite pleased with this new, almost silent running rig as it is.
Again, thanks for everyone's input. My overclocking buzzard's luck continues. At least it can run 15k without any video card overclocks.
I'll going to sell this new rig and move back to Intel in the coming weeks.
I have been dying to give this board a run for it's money but have yet had the time. I probably could have yesterday, but the Corona's and Rumple Minze the night before took it's toll. Hopefully this weekend I can give some results. So far it has been rock stable for my everyday use. My 2400+ has been running as a 2800+ for 4 days now (166x13.5). Not sure what this Radeon 9000 will do either, my last one did 331/300 before it died.
Here are my two benches 17014 16618
The second bench (KD7-E), although run with different mobos, has the CPU clocked higher (190 fsb) than the first (KX7-333R) but with the same video card settings (380/340).
I realize everyone's more interested in Oppainter's 21k efforts but I could use some advice.
1. Would the mobos cause the 400+ mark difference?
2. What drove the lobby scores so low?
3. What components and/or settings affect Lobby FPS?
Hmmm...that is strange.
When I was considering doing a KD7-E mobo review, I compared the KX7, KD7, and KD7-E bench scores (using identical configurations). And I pretty much had all the scores clustered together. None of them lead the pack by any significant margin. Based on that, I beleive there is something else definitely going on with your systems...something set up between them differently.
I am no 3DMark expert, but I can throw out a few ideas to consider as to why you have materially different scores. You would need to make sure these items are identical between the test systems.
Memory timings. These can really effect the score at higher fsb speeds too.
AGP settings such as APG aperture and Fastwrites.
Video card overclock, core and memory, if any.
Vid driver tweaks such a Vsync, refresh rate fix, and all the performance vs. quality settings.
A fresh install of the same OS with the appropriate service packs, 4in1 drivers, and vid card drivers.
Video card driver version.
These are the biggies anyway. It's very hard to have an apples to apples comparison unless you run these boards together, one right after the other, with the exact same hardware (except the mobo), BIOS set up and OS/driver install routine. they must all be exactly the same. Easier said then done sometimes.
Hope this helps:) I'm sure a real 3DMark expert might be able to help you more.
Thanks for the awesome feedback and advice. First, although I can't run it as high as some, I can run it higher than any other mobo I've ever owned. It's a great mobo. I've included my comments below.
Quote:
Originally posted by mdzcpa
Hmmm...that is strange.
When I was considering doing a KD7-E mobo review, I compared the KX7, KD7, and KD7-E bench scores (using identical configurations). And I pretty much had all the scores clustered together. None of them lead the pack by any significant margin. Based on that, I beleive there is something else definitely going on with your systems...something set up between them differently.
I am no 3DMark expert, but I can throw out a few ideas to consider as to why you have materially different scores. You would need to make sure these items are identical between the test systems.
Memory timings. These can really effect the score at higher fsb speeds too.
I think this is a biggie as I have it set on TURBO so I need to go to MANUAL and set them more aggressively.
AGP settings such as APG aperture and Fastwrites.
They were the same between mobos according to my notes.
Video card overclock, core and memory, if any.
They were the same between mobos according to my notes
Vid driver tweaks such a Vsync, refresh rate fix, and all the performance vs. quality settings.
They were the same between mobos according to my notes.
A fresh install of the same OS with the appropriate service packs, 4in1 drivers, and vid card drivers.
They were the same between mobos according to my notes.
Video card driver version.
The video card drivers (6193 vs 6218) and I believe this may have something to do with it as well.
These are the biggies anyway. It's very hard to have an apples to apples comparison unless you run these boards together, one right after the other, with the exact same hardware (except the mobo), BIOS set up and OS/driver install routine. they must all be exactly the same. Easier said then done sometimes.
Hope this helps:) I'm sure a real 3DMark expert might be able to help you more.
A little hard to tell without the full tests on 3DMark. The fill rates would help determine if the card is somehow suffering. I had a problem with decreasing scores on a rig that was exactly the same, only difference was the card was getting tired and couldn't perform at the same clocks, that was right before it died. :( But then Lobby is more cpu dependant, so I can't say that is your problem.
how is everyone with a KD7 or KD7-E hitting 200mhz fsb and higher stable? i tried the Pio hd mode and that didnt help. what to do. :confused:
taco,Quote:
Originally posted by taco
how is everyone with a KD7 or KD7-E hitting 200mhz fsb and higher stable? i tried the Pio hd mode and that didnt help. what to do. :confused:
Which board do you have? Full system specs?
What troubles are you having when you up the fsb? HD corruption? Crashes or freezes?
To be honest I'm not really doing anything special to hit 205mhz here. For me the board just seems to not mind it. I know that a lot of it has to do with having components that can handle higher bus frequencies. Even with the 1/5 divisor, the AGP and PCI bus does run a bit out of spec. Another thing is high quality memory and great cooling.
Give us some details and maybe we can help.
well i got a 2400+ week 46, its stable at 2.56 with aircooling (mcx-462+ w/ panaflo 40cfm). motherboard is a KD7R, Corsair 3500 256mb, 9700 pro, 80 gig maxtor and power supply is kingwin 450w..
it would always do a bsod then restart or id have to turn it off, the other day the hd just had enough, and decided to corrupt for real.
save me sir. :smileysex
What vcore are you using?
I'm in the same boat kinda.My hdd always fails above 214fsb even in pio4. With the 1/5 divider it shouldn't be out of spec too far i would think. My XMS 3200 lets me use fastest timing at 214fsb too.
KD7-E sounds good.... because of high voltages are allowed with this board.
I just don't see how KD7-E or KX7-333 is gonna beat KR7A. The KR7A's FSB overclocking ability is superb, with the FastCPU decode, and its reign-champ 1/2AGP, 1/4PCI divider. No other board beat this, ever, if the user special pick the components and plan out for mid 190's FSB, this board will nuke all other boards including the NF2 boards as well. Only problem is that cards like the GF4 series and especially the R9000/9500/9700 series cards go poo poo.... at those AGP/FSB speeds.
If you are planning to use the GF1, GF2, GF3 series, Kyro, R7000/7500/8500 series, the KR7A will nuke all boards out there in 3D games and 3Dmark as well as the overal performance due to exotic AGP/PCI bizarre speeds. eh eh... I thought I should mention that. :banana:
I've owned all 3 mobos this year and that is not an accurate assessment at all.
I've got news for ya:)
My KX7333R smoked my KR7A and my KD7-Raid smoked both of them....I'm now working on smoking all 3 with the NF7-S:D
And BTW, Welcome to XtremeSystems !!
Randi:D
Quote:
Originally posted by IamAnoobieCheez
KD7-E sounds good.... because of high voltages are allowed with this board.
I just don't see how KD7-E or KX7-333 is gonna beat KR7A. The KR7A's FSB overclocking ability is superb, with the FastCPU decode, and its reign-champ 1/2AGP, 1/4PCI divider. No other board beat this, ever, if the user special pick the components and plan out for mid 190's FSB, this board will nuke all other boards including the NF2 boards as well. Only problem is that cards like the GF4 series and especially the R9000/9500/9700 series cards go poo poo.... at those AGP/FSB speeds.
If you are planning to use the GF1, GF2, GF3 series, Kyro, R7000/7500/8500 series, the KR7A will nuke all boards out there in 3D games and 3Dmark as well as the overal performance due to exotic AGP/PCI bizarre speeds. eh eh... I thought I should mention that. :banana:
Now that is an accurate assessment:) ...not to mention I experienced the same results!Quote:
Originally posted by MrIcee
I've got news for ya:)
My KX7333R smoked my KR7A and my KD7-Raid smoked both of them....
Never owned a KX7, but as good as my KR7's were (are) and as much as I still love em, my KD7 with all it's quirks does indeed stomp mercilessly upon them.
Tiribulus:D
Says it all. Welcome to the madness of Xtreme.Quote:
IamAnoobieCheez
PS:D
My NF7-S WITH its quirks smokes ALL my previous boards hands down;)
Randi:D
Your trying to tempt me, aren't you Randi;)Quote:
Originally posted by MrIcee
PS:D
My NF7-S WITH its quirks smokes ALL my previous boards hands down;)
I am struggling trying to identify which of the 3 of 5 KD7-E sensors go with each temp. I think the HD temp is straight forward since it's listed in the sensor listings. I think the system one is a given as well. However, I've had to take a stab at the others.
Anyone care to take a stab based on the information provided?
does anyone know what im doing wrong, to not hit 200 or higher on the fsb? i picked up a maxtor 80gig with 8mb of cache, any suggestions before i install windows?
Can't help either Taco. I can't get past 190 even at the lowest memory settings.
I'm not sure which MBM sensor choices you used and how you chose to label them, but I can tell you this.Quote:
Originally posted by bigdawginva
I am struggling trying to identify which of the 3 of 5 KD7-E sensors go with each temp. I think the HD temp is straight forward since it's listed in the sensor listings. I think the system one is a given as well. However, I've had to take a stab at the others.
Anyone care to take a stab based on the information provided?
LM90 Remote is the CPU Diode temp
LM90 Local is the in socket temp
Winbond1 is the system temp
Still need more info.Quote:
Originally posted by taco
does anyone know what im doing wrong, to not hit 200 or higher on the fsb? i picked up a maxtor 80gig with 8mb of cache, any suggestions before i install windows?
How far have you got to on the FSB with stability?
What mutliplier and FSB were you using at that point?
Core and DDR voltages at that speed?
Temps at that speed?
Any PCI cards?
HD connected the Highpoint or regular IDE?
Every system is different, and I need more info, so it is hard to say. But I'll make a few suggestions.
Make sure your HD is on the Highpoint Controller.
Disable all unused mobo devices such as serial ports, parallel port, USB, on board sound, on board LAN, etc. If you use them fine, but if not, shut em down.
Keep the memory and core plenty volted. Low DDR voltage can result in HD corruption (as can low core voltage, but not as often).
Other things to consider:
Although I have not experienced HD corruption with the KD7-E, I did have the problem on my KD7. I beleive this is a well known issue with the KT400 chipsets and is reported to occure in the 198 to 208 range. Some people have gotten around it by setting the HDs to PIO mode (turning off DMA mode).
One other thought is the Radeon. I swapped to the KD7-E from my KD7-RAID becuase my Radeon 9700 Pro would not play nice in the KD7-RAID. It "forces" AGP x 8 in the BIOS when it recognizes the AGP x 8 card in there. The KD7-E is an AGP x 4 mobo. The max I could go in the KD7-RAID with the Radeon was about 188, but now I can get to 205 in the KD7-E.
Mike:)Quote:
Originally posted by mdzcpa
Your trying to tempt me, aren't you Randi;)
wait until the end of the month..then buy rev 2 to evaluate. You'll be a much happier camper all the way around ;)
Randi:D
Not to disrupt the flow of the thread right now, but /me is a happy camper, my replacement KD7-E came in today. Not only do I get to try it again, this one has Nichicon caps instead of the Rubycons in my original board :) Still a Rev 1.0 board.
isnt rev 2.0 suppose to have the 4 holes?
That sounds like a plan my friend:)Quote:
Originally posted by MrIcee
Mike:)
wait until the end of the month..then buy rev 2 to evaluate. You'll be a much happier camper all the way around ;)
Oooo...nice. Keep us posted on how it does please:)Quote:
Originally posted by sjohnson
Not to disrupt the flow of the thread right now, but /me is a happy camper, my replacement KD7-E came in today. Not only do I get to try it again, this one has Nichicon caps instead of the Rubycons in my original board :) Still a Rev 1.0 board.
Yes, Rev 2.0 will have the 4 holes plus some other additional fixes and niceties:)Quote:
Originally posted by taco
isnt rev 2.0 suppose to have the 4 holes?
Randi:D
Mike, that's exactly how I have those 3 plus the HD monitoring setup on this KD7-E. Good to know I was on the right track. I just can't figure out what Winbond 2 monitors.
BTW,
Can I tell which ones just from looking at the caps?Quote:
Nichicon caps instead of the Rubycons in my original board
Nichicon caps are silver...Rubycon dark blue/black:)
Randi:D
Quote:
Originally posted by MrIcee
Yes, Rev 2.0 will have some other additional fixes and niceties:)
ehm..
RANDI!!
i'm :slobber: for these!
tell us more :toast:
I'm under NDA on any specific changes outside of the 4 holes, but I can say there will be some changes:)
Randi:D
when is this NDA gonna fall? :D
i hope these changes will be in the xtreme enthusiast-mobo way!
Randi, thanks. I see 3 tall caps just on the south edge of the ziff and a couple between the ziff and power connector. They are all dark blue/black with a stripe of gray. Can I assume these are the ones we are talking about? Could this explain why my mobo struggles above 190 fsb?Quote:
Originally posted by MrIcee
Nichicon caps are silver...Rubycon dark blue/black:)
Randi:D
Also, there are 3 more further south of the ziff that are silver.
Quote:
Originally posted by bigdawginva
Randi, thanks. I see 3 tall caps just on the south edge of the ziff and a couple between the ziff and power connector. They are all dark blue/black with a stripe of gray. Can I assume these are the ones we are talking about? Could this explain why my mobo struggles above 190 fsb?
Also, there are 3 more further south of the ziff that are silver.
check out the 2 big ones between mosfets and agp ports!(in between there's the HIP voltage regulator )
mine's are the silver ones and the mobo oc like a champ
Ok, thanks. If you're referring to those then all 3 of those are silver so I suppose that's not the porblem.
I'm giving up for the night. I've tried a 256M stick of TwinMOS/Winbond BH-5 and a 256M stick of Samsung CTL-TCB3.
No matter what I do, my new KD7-E won't run DDR400, only DDR333.
I've done the following, and always started out resetting CMOS for 5 minutes followed by setting "Optimized settings" per Mr Icee's recommendation, and the first post after setting optimized shows DDR400, but I've done the following without success:
Set 200 FSB and change NOTHING on the first post from Optimized, TwinMOS and Samsung.
Set SPD on the TwinMOS/Samsung, and 200 FSB.
Set SPD on the TwinMOS/Samsung and walked up in 10's from 133 to 208.
Set 200 on the TwinMOS/Samsung, and 200 FSB.
Set 133 on the TwinMOS/Samsung, and walked up in 10's from 133 to 208.
Set 166 on the TwinMOS/Samsung, and walked up in 10's from 166 to 208.
Repeated the above after a new flash of the C8 BIOS. Twice.
No matter, it always posts showing DDR333 at 200 FSB, and gives PC2700 bandwidth in Sandra (2700 MB/S Float). :(
The Samsung is the same stick that gave me 3200 at 208 with my original KD7-E.
Can you guys help out here? If this board won't do DDR400 I'm afraid it's the last straw for me and ABIT, this board acts like it's been purposefully crippled from the factory. Yah, I know, I'm paranoid - but I was so very impressed by the potential of my first board that this is REALLY getting to me.
sjohnson:
Your first board must have been a glitch or something. I've had a number of these KD7-Es pass through here now, and none of them would run DDR 400 at any speeds above 165mhz fsb. Starting with a FSB of 166mhz, the memory and FSB are automotically run synchronously.
This is really no different than the original KD7 (KT400) and is limitation of the chipset.
Are you sure that your memory was running asynchronously at speeds above 166mhz on your first board? Could it be differences in your basic memory timing settings that account for the difference in Sandra scores.
For comparison purposes my Sandra float is about 2760 at 195mhz, 2832 at 200, and 2903 at 205. This is at CAS 2, 2,6,2 2T.
You're missing my point, musta been my lack of sleep and frustration when I tried to explain. My board won't run synchronous above 166 FSB. At 200 FSB, I'm still running asynchronously. Sucks to have the ability to run well in excess of 200 FSB but your memory is stuck at 166.
(Edit) - rereading your post, I'm confused about what you're trying to say - if the KD7-E won't run DDR400 at any speed above 165, how can it run synchronously at 200?
I never run asynchronous by choice.
This is from my original 7-e. I think it shows that I was running synchronously on the first board. My examples above were to show how I tried to force synchronous behavior above 166 FSB, without success, on my new board.
If you run the board at speeds below 166mhz FSB, you can select the memory to run asnychronoulsy at DDR 400.
A good example is for the avererage joe who just pops in his 133mhz processor (133 double pumped), and sets the memory to run at either DDR333, or DDR 400. In this instance, the mobo will run the FSB at 133mhz and the memory asynchronoulsy at 166 or 200mhz.
Performance gains are just about nil when doing this, though, as memory latency penalties for running in asynchronous mode kill the gains...not to mention the CPU bus bottleneck at 266mhz (133 x 2).
You say that at 200mhz fsb your memory is still running aynchronously. What speed is the memory running at when your FSB is at 200mhz? What does Sandra say about the memory bus speed stated in mhz?
sjohnson:)
When you set FSB AND memory to 166Mhz...you are in Sync. It will post from then on as DDR333....no matter where you set the FSB. Even if you set the FSB to 200...the memory will post DDR333. The only time I've ever seen it post DDR400 is when you run ASYNCH and FSB is 133 or 166...and the memory is at 200Mhz.
You cannot pay attention to the posted DDR333 speed(or the 166 speed in the memory section of the bios). Go into Sandra after you've done as I've explained above. For giggles, set your multi to 10....FSB to 166 and in the memory section the memory to 166Mhz. Mind you from here on it will show the memory at 166 in the memory section and DDR333 at post. Reboot and go into the bios...set the FSB to 200Mhz and reboot. Boot into Windows and run Sisoft Sandra's Mainboard configuration. You will first see FSB listed, then scroll down, then memory and it's speed. They should both be showing 200Mhz.
Give it a shot and let us know how you make out:)
Randi:D
PS. The reason it shows DDR400 after setting optimized defaults is that optimized it's running async 133/200 or 166FSB/200Mem. You WILL NOT see DDR400 at post EVER running in sync mode...it always shows DDR333 even when you are running 200/200.
BOTTOMLINE: Set Memory to 166Mhz and leave it. Set FSB to 166Mhz.From there raising your FSB ALWAYS raises FSB and MEM
syncronously all the way to your hardwares limit. Use Sandra's mainboard configuration module to confirm
Looking at that Pic, you need to scroll the Sandra box down to see the memory speed in mhz. What you can see there is only the FSB speed.
I'm quite sure that the pic above was running synchronously based on the scores you have.
On the new system, run the same bench and scroll down and check the memory speed.
BINGO! Thanks for helping explain that Randi! I wasn't sure why he was thinking he was running at DDR333 when he was at 200mhz FSB. I didn't even think about the post screen....I'm so used to ignoring it now:)Quote:
Originally posted by MrIcee
sjohnson:)
When you set FSB AND memory to 166Mhz...you are in Sync. It will post from then on as DDR333....no matter where you set the FSB. Even if you set the FSB to 200...the memory will post DDR333. The only time I've ever seen it post DDR400 is when you run ASYNCH and FSB is 133 or 166...and the memory is at 200Mhz.
BOTTOMLINE: Set Memory to 166Mhz and leave it. Set FSB to 166Mhz.From there raising your FSB ALWAYS raises FSB and MEM
syncronously all the way to your hardwares limit. Use Sandra's mainboard configuration module to confirm
Yeah...the initial post screen at DDR333 confuses alot of people. It's because you locked the memory in sync at DDR333 by setting it at 166Mhz. It's a shame it doesn't change and adjust to reflect it's ACTUAL speed as you scale the FSB upwards. This anomaly has been the frustration of many setting up KD's since their introduction. Using the mainboard configuration module in Sandra is the easist way to confirm you in fact are sync and running the speeds you've set in the bios:)
Randi:D
Same CPU, same memory (Samsung CTL-TCB3), same memory timings, same voltages, same HD and peripherals. The only change is the the board and it's the same make and model, KD7-E.
From my list, sorry it was so long:
"Set 166 on the TwinMOS/Samsung, and walked up in 10's from 166 to 208." So, I did set 166 and then ran it up. Still showing scores indicative of running at PC2700 instead of PC3200. What gives?
(Appreciate the really quick responses guys. Sorry, but I have to head out to work. Will pick this up tonight. Again, thanks - this is such a nice board that I'm really frustrated that I can't seem to run anywhere near this Sammy or this TwinMOS bandwidth on my new KD7-E).
Quote:
Originally posted by sjohnson
Same CPU, same memory (Samsung CTL-TCB3), same memory timings, same voltages, same HD and peripherals. The only change is the the board and it's the same make and model, KD7-E.
http://www.xtremesystems.org/forums/...=&postid=85726
What FSB speed is this at?
I'm out the door, will repost tonight. (You'd have to take my word for it at this point), it's identical to the SS showing 3200 on the original, 2.5-2-2 1CMD, Enhance/Enhance/full aggressive/208 FSB.
Your first SS shows the CAS setting at 2 in Sandra, not 2.5. That's going to be your major difference:)Quote:
Originally posted by sjohnson
I'm out the door, will repost tonight. (You'd have to take my word for it at this point), it's identical to the SS showing 3200 on the original, 2.5-2-2 1CMD, Enhance/Enhance/full aggressive/208 FSB.
You also didn't run the mainboard configuration screen as I asked and checked the FSB and memory Mhz settings...that will confirm its running in sync and at whatever you have the FSB/Mem set at. Bandwidth tests are not conclusive at all, especially as Mike pointed out you are running at cas 2.5 as opposed to cas 2 in your first post
Please run the Sandra mainboard configuration module later today and give us the lowdown on the FSB amnd memory speeds from it.:)
Randi:D
I would not trust Sandra, look at these screenies(first one is CAS2,second one CAS2.5):
http://home.tiscali.no/kartoffel/sandra180cas2.jpg
http://home.tiscali.no/kartoffel/sandra180cas25.jpg
CPU-Z also mistakes CAS2.5 for CAS3. Maybe its a mobo problem? Anywas, you can also notice that the performance hit from running CAS2.5 opposed to CAS2 is not big. Are you using the same BIOS? I think its strange that Abit has replaced the caps but not changed revision. Also, from my experience with Nichicon vs Rubycon on the KX7-333, the Nichicon board smoked the Rubycon board in stability, OC ability and voltage stability. Strange problem sjohnson :(
damn thats a mess, wonder why :confused:
I would think if he could post these two shots for us that could confirm either way.
OK gents, just got home from work, long day and no 'net access. I'll fire up the 7-E and see if I can't respond to each request.
Sorry Mr Icee, I was incredibly rushed this AM, that's why I haven't yet responded to your requests for more info. I will, though! :) Spoiler, Sandra will show the memory running at 208X2 at 208 FSB.
So much else is fubar with sandra's reporting that I assumed it was wrong as well. My memory bandwidth on this board is currently well below what I know the memory can run at the same FSB on both of my KR7A and KX7. However, I trust Mr Icee and mdzcpa'sknowledge on this board - if they say it's running 200 I did NOT intend to argue the point and apologize if my posts seemed to do so. Perhaps the bandwidth experienced with my first 7-E was a fluke, one of a board destined to be RMA'd.
My plans, after this ardent help and time taken to explain will be to gently burnin this new board and see what might happen.
Got to help my son with homework now, will post the requested infos later tonight. Again, thanks to all!
sjohnson:
No need to apologize:) Post the info when you can and we'll see if we can come up with some ideas to help.
I would have to agree now with you guys about Sandra being all borked up on this memory reporting. I guess I nevered looked hard enough at it before.
Not only does it refer to regular "SDRAM" and the wrong efficiency % as mentioned somewhere earlier in this thread, all the settings are off. More like mislabled maybe.
I think it's a Sandra issue based on my experiences benching it and the close similarities to my KD7-RAID memory benches. The benches I'm getting are almost exactly what I could get from my KD7. Which makes sense to me as both boards use the same memory controller.
Although...sjohnson's problem does puts a wrinkle into the mix until it can be fixed/explained.