For Mr Icee and the others requesting some Sandra SS. First, my Mainboard Information screen.
Printable View
For Mr Icee and the others requesting some Sandra SS. First, my Mainboard Information screen.
And the System Summary screen - both with Sandra 2002, if that's important, haven't yet installed 2003.
I want to state that I really like the potential of this board. AGP doesn't start tearing until a higher FSB than any of my previous boards, a memory efficiency that was only equaled by my kr7a (on my first board lol), volts, 8x Vlink, etc. etc.
Just want more bandwidth :) Again, I'll give it a week of some gentle burnin and let you all know if the bandwidth improves.
You see my friend...your FSB and memory are in sync at 208Mhz:)
Lesson # 1: Don't believe the DDR333 on the post screen;)
The bottomline on bandwidth is to get all your memory timngs maxed out...then maybe a WPCrset tweak such as 6A=FF and you' be in business:)
Randi:D
Sorry - bzzt! - I lose. 6A=FF has been set all along. Kinda forgot about it, this is the same HD and install I was using on my original board.
And, on re-reading my post I *did* give the impression that my concern was the DDR reading on POST. It's the initial bandwidth that bothers me. My previous board topped 3k Sandra/200 FSB out of the box, so getting in the 2700 range with this one made me believe I was running async.
Hopefully I can make up the missing 10% bandwidth efficiency through some motherboard burnin.
Again, thanks for your attention Mr Icee!
Warmest regards :)
BTW, for KD7-E boards (perhaps for KD7's as well), setting the appropriate two registers at offset 60 from 00 to 10 will force Sandra to properly report DDR and to calculate DDR efficiencies. No performance gain, just that 00=SDRAM and 10=DDR.
So, if you've populated Banks 0/1 (the first DIMM slot), changing bit one of offset 60 will tell Sandra that you have DDR and not SDRAM.
Now that we have the sync vs async issue resolved I have another question about this mobo that I have yet to encounter with others.
Twice, within the past couple of weeks, my system goes into what I would call an "infinite loop mode".
Not benching or trying to run xtreme speeds, just my "normal" OC and settings. However, during a power up or restart, it boots into the "Choose Safe Mode or Start Windows Normally" screen.
Of course, I choose Start Windows Normally and it reboots and goes back to the same screen over and over. Then I'll try the different Safe options and same occurrence. It'll reboot and return to the same screen.
At this point the only cure has been to reinstall WinXP and my applications from scratch.
Thoughts? Bad memory? Mobo getting too hot? Anything I could check?
Sounds like HD corruption killing your OS.
This can be from too high of a FSB for the HDs you have. Ot too high of a FSB in general for the IDE to handle (but that is usually a bit above 200 at least).
Other times I've seen HD corruption occur when the memory is at the edge of stability...sometimes more DDR voltage can help.
Thanks Mike. At 190 I doubt it's affecting this WD 120mb 8mb HD so I think it's my memory. I'm convinced, although it runs at advertised speeds, it's right on the edge. I'll make sure I keep the volts up.
I need some help, it seems like I am not getting the bandwidth with this board that I was with the 8k3a+. Any advice on BIOS settings would be appreciated. I know Sandra is not reliable, but it can at least be used as a comparison and I am only getting about 2450 compared to the 2550 I was getting at 166MHz.
Sorry, had to mention how funny that was for me to see ;)Quote:
Originally posted by SPQQKY
I need some help, it seems like I am not getting the bandwidth with this board that I was with the 8k3a+.
What memory timings are you using?Quote:
Originally posted by SPQQKY
I need some help, it seems like I am not getting the bandwidth with this board that I was with the 8k3a+. Any advice on BIOS settings would be appreciated. I know Sandra is not reliable, but it can at least be used as a comparison and I am only getting about 2450 compared to the 2550 I was getting at 166MHz.
i feel like my KX7 is better :(
Cas 2Quote:
What memory timings are you using?
bank interleave 4
trp 2
tras 6
trcd 2
burst 4
queue 4
dqs drive strength high
auto
auto
auto
auto
dram access 2T
enhance enabled
command rate 1T
With these settings, I should get at least as high or higher bandwidth than my 8k3a+ with 2815 BIOS. The 8k3a+ was a great board, I know you Abit fanatics scoff at EPoX.
SPQQKY:
Well, you obviously have all the timings in the BIOS cranked all the way up, so I'm not sure what to make of it. Going back through my notes, I have the KX7, KD7 and KD7-E all bunched in a tight group when it comes to sandra mem benches. :confused:
The thing is, at this setting on the kd7-e, my cpu is running at 2.24GHz (166x13.5) and on the 8k3a+ is was only 2GHz (166x12 - the highest multi I could get with the unlock trick) and seeing as how Sandra kinda boosts things up the higher your cpu MHz is, it should be a little higher IMHO.
I think the true test will come when I get the time to install win2k and not run the tests on this winXP install. I did a clear memory and got 2491/2398 while F@H was running. Looks like I am going to have all day Monday to push this setup and do some serious benching. Gonna head out to the garage with it, it's only going to be -14c in the morning. :D
SPQQKY,
Let us know how you make out. Couple things...I have a KD7 here that I can't get to run 3D over 195FSB, & it doesn't appear to be any faster than the 8K3A to me @ that speed. So, I ordered better chipset cooling for it in hopes that it would help & while I'm waiting for shipment I stuck the 2400+ back in the 8K3A w/ the wire trick that you mentioned in another thread. Well, I max'd out @ 198FSB on the 2815, just can't get 3D stable any higher on that BIOS, so I thought I'd try the 2B01...the latest to my knowledge. Well, its scoring just as the 2815 did for me in 3D, yet I'm burning in right now @ 207FSB. Seems like a great BIOS so far and now this has made my hopes for the KD7 even lesser. If that KD7 won't run in excess of 200FSB for me I'm afraid I'll be going back to the 8K3A yet again. Not a good impression for me for my first Abit board, I'm sorry :(
Wanted to let you know that you have 12.5 available in that 8K3A, not just 12 :)
Set mult to 13 & the 8K3A gives you 12.5 :D
This is my kd7-e at 166. Same as my kx7. I love this board.This is on normal cpu decode.
well ive got mine today its my first abit and i must say im a bit dissapointed.. but not because of the oc options..its cause the board wont accept my soundcard..strange prob.. well i return it at monday and take another one :D
Bummer...have you tried reducing the overclock on the 9700 a little? What I did was remove the OC on the card altogether and find max stable FSB speed under 3DMark2001. Then I began applying the OC to the card....which does effect how high you can go with the FSB. Finding the best balance of card OC and FSB is the key. For 3DMark, having the core up more always seems better, but for the best balance acrossed all benches, lower the card OC just a tad for a few more mhz FSB wise is better.Quote:
Originally posted by bigdawginva
Latest benching with my KD7-E. Verified that 200 is a no go with my 9700.
The card wasn't even overclocked when I tried. Went into bios, set the fsb to 200, and the screen was full of different colored gibberish and distortion during the post sequence.
Well, I had some time yesterday to put the board to the test. I set up my system in the garage. First, the setup:
TBred 2400+ with Vantec AeroFlow HSF
Abit KD7-E (silver caps) with Vantec copper iceberg on NB
256 MB Corsair XMS pc3200 C2
Sapphire Radeon 9000 Pro
Antec sx-1030 server case w/Antec 430w TruePower
I loaded win2k w/ sp2 and then the Hyperion 4in1 4.45s and dx8.1 and the Cat 2.5s. The ambient temp in the garage was -2c and my cpu maxed out at 36c. I was able to get it stable finally at 2416MHz with a fsb of 201MHz. I had to hit the reset button a couple of times after 198MHz fsb to get it to boot. I was able to run PCMark and SuperPi and those speeds, but 3DMark became corrupted at anything above 190MHz and I don't believe it was the board but probably a bad copy of 3DMark because I would reinstall it and it just wouldn't run car chase low but ran other tests. I didn't have the time to find another copy on disk and try. I tried to boot at 2429MHz (202x13) but I got corrupted files and when I tried to reboot to fix them, the system would not boot at all. I simply ran out of time to do anymore. All in all I am pretty happy with the board and I'm sure with more time, I could get more out of it.
PCMark2002 I'm really happy with this. As you can see from my HDD score, I had UDMA disabled and set to PIO mode 4 so I know that was not my problem with corruption at high fsb.
Very nice SPQQKY!
I recently bought the KD7-E and slapped it in my prommie. Taking a look at your PCMark I noticed your MHZ wasn't being read properly. Mine is the same way, is that "misreading" a problem with the board or PCMark?
http://service.futuremark.com/compare?pcm=1009680
It's a problem with PCMark, it did the same with my 8K3A+. It's strange, when I save the project before I submit it, it shows it correctly, but once it's submitted, it doesn't show it the way it should be.
There is new BIOS for the KD-7E on Abit's site (CY). Anyone care to guinea pig these BIOS for us all? I rarely have time to bench so I'd like to know if it is any good so I can go straight to OCing next time I get a chance. Much appreciated.
I'm running a BIOS Savior. Will try it and post my observations later. Thanks for the heads up, I've been to Abit's site several times today and didn't notice that announcement.
(Edit) Running CY BIOS now. I was burning in a new stick of the TwinMOS/Winbond BH-5 before the flash and was up to 221/2.95Vdimm stable before the flash, now 220 is stable but I'll give the BIOS at least 24 hours before I make any conclusion about how it works for me. Same Sandra bandwidth as the C8, will check out my max 3dmark-able speed later - 216 was stable for 3dmark for this board under the C8 BIOS.
one question: how do i flash the bios under win2kprof???
I run Win2k Pro and boot DOS and flash from there. CD, floppy, your choice. http://www.bootdisk.com might be helpful to get some DOS boot images that can be placed on a floppy or CD.
well thx... damn here its 3 at the mornin i get some sleep now :D
hehe i dont even know how to create a boot disk :/
The bootdisk site has good (English, sorry!) directions. It's really very easy for a floppy and not too tough for a CD.
The CY BIOS is 3dmark stable to 216 on my rig, just as was the C8 BIOS - I get the same 1k drop-off in score at 216 with either BIOS. Above 216 it's iffy with either BIOS whether or not I complete a full run.
swissocer,
For your 8k3a+ it is way to easy to flash the BIOS. Just go to EPoX's site and get the latest BIOS .exe and then unzip it to a clean floppy disk. Then when you reboot, hit alt+F2 and it will do it for you. :D
You don't need to boot into DOS to do it, although you can take the hard route if you want to.
Created a bootable CD (don't use floppies) and flashed. Nothing remarkable to report...yet.
hehe i know spooky but i have the kd7e now...i must update my sig :D
well got it workin to flash the bios with the DrDOS 7.x Disk For BIOS Flashing Basic - No Drivers from bootdisk.com
thanx yall for the help :)
I will give this CY BIOS a try tonight. It doesn't look like much changed aside from adding "official" XP 2500, 2800, and 3000 support (which was already possible by manually selecting the mutliplier). Perhaps Barton tweaks?
We'll see.
I'm going to revert to the C8 BIOS. My initial impression that CY was less stable for me is being borne out by the steadily decreasing FSB at which I can continously bench Sandra memory and run Prime95 stably. 221 FSB Sandra/218 FSB Prime95 on C8 and 219 FSB Sandra/216 FSB Prime95 CY.
Im running an XP1600+, so perhaps those with tbred's will see better results.
hehe well ive had the c8 but it was very unstable i only could bench at 180mhz with my epox i was able to go till 197mhz fsb with the 3000xms and 3.0Vdimm
well must say this mobo kinda sucks,. i cant even run a 3dmark at 187mhz with the corsair xms3000
at my epox 8k3a+ i was able to run a 3dmark till 197with the same ram.. any suggestions why that is??
it always gives the same error :File \data\gs1\kf\objects\gasstation_l0.kf2 is corrupted
but the ram runs @ spd speeds.. and 3.0vdimm..
damn i thaught it was a good mobo.. well i try again when i got my stick of 3500xms..
oh and the PSU is a enermax 350watt
My opinion on that PSU of yours is that its a POS. Low +5v rails. I think you should try to reinstall 3dmark, if you already havent done that. Or try something else to verify stability. What fsb can you get into windows at?
well the +5V rail is always at 5.0+/-0.03
i can get into windows at 190mhz didnt try higher..
Well, that's too bad these BIOS aren't much better because I just cannot get 3DMark to run on this board.
well i putted back my good ol 8k3a+ runs till 199mhz fsb for now :D with my 3000er xms.. well very sad that the kd7e doesnt work for much people as me
Can you expand on this a little? What have you tried so far? Have you upped the memory voltage? (I find that the memory needs a good amount of voltage even though I might technically be running it less than advertised speeds).Quote:
Originally posted by SPQQKY
Well, that's too bad these BIOS aren't much better because I just cannot get 3DMark to run on this board.
PSU in good shape? Have you connected the ATX2 power connector?
Memory timings? 1T Dram Command is hit miss on the without great memory and some stiff voltages.
We should be able to work this issue out. Right now I've been through 2 KD7-Es that can loop 3DMark at 203mhz. That's 2 for 2. There must be an answer for those who are struggling.
well it always kikks me back to desktop even with the c8 bios.. man i luv this board with his oc options but damn sad it isnt stable as the old kt333.,.
Hi,
i have got a Problem with my KD7-E. I can't reach 200 FSB. Only 193 - 195. I have tried all dimm slots.If i set the FSB to 200 i got a blue sreen of win.
Please help.
Can you tell me your bios settings, please !
greetings from germany
I believe a few of us are having that same problem. I've given up trying to get above 195. It's still the highest I've been able to run a 24/7 system.Quote:
Originally posted by Redskin
Hi,
i have got a Problem with my KD7-E. I can't reach 200 FSB. Only 193 - 195. I have tried all dimm slots.If i set the FSB to 200 i got a blue sreen of win.
Please help.
Can you tell me your bios settings, please !
greetings from germany
My new Kd7-E will run up to and including 200MHz FSB! Haven't tried higher! Will do tonight though!
I love the way they unlock the T'Breds! Is it from 5x all the way to 20x or just some of them?
Voltages were maxed at 3.25v for the memory and timings were also maxed, was hoping to hit more than 201MHz but I may need to back down a bit. The system is stable at 201MHz for anything but 3DMark.Quote:
Can you expand on this a little? What have you tried so far? Have you upped the memory voltage? (I find that the memory needs a good amount of voltage even though I might technically be running it less than advertised speeds).
PSU is an Antec 430w TruePower, good to go and atx2 connector is firmly in place.
All pci devices are removed and power is disconnected from CD-RW and DVD ROM. HDD is Maxtor 20Gig ata100 5400rpm and can handle this no problem.
Win2k, sp2, via hyperion 4.45, dx8.1, cat 2.5's. Get corrupted 3dmark files. May give it another try in a day or two and see what I can do. May just back down the fsb and up the multi by .5 and then try lowering mem timings and see if those help.
:comp10:
Sounds like you have a good handle on things.Quote:
Originally posted by SPQQKY
Voltages were maxed at 3.25v for the memory and timings were also maxed, was hoping to hit more than 201MHz but I may need to back down a bit. The system is stable at 201MHz for anything but 3DMark.
PSU is an Antec 430w TruePower, good to go and atx2 connector is firmly in place.
All pci devices are removed and power is disconnected from CD-RW and DVD ROM. HDD is Maxtor 20Gig ata100 5400rpm and can handle this no problem.
Win2k, sp2, via hyperion 4.45, dx8.1, cat 2.5's. Get corrupted 3dmark files. May give it another try in a day or two and see what I can do. May just back down the fsb and up the multi by .5 and then try lowering mem timings and see if those help.
:comp10:
The first thing I would try is dropping the DRAM Command to 2T. Leave everything else cranked up (CAS 2 2,6,2). I found that I had trouble with the 1T command when running the XMS3200 above the mid 190s when the other settings were also cranked up. I also found more stability/performance by dropping the DRAM Command to 2T versus changing the other settings to 3,7,3.
SPQQKY - keep the mosfets cool as well. Maybe set a fan to blow air over them. My southbridge also runs hot, too hot to touch so I've put on a small heatsink and fan to cool it. Made my rig more stable - bootable at 220 FSB stable and 225 highly unstable. Still no bandwidth efficiency though...
Mosfets have cut up Thermaltake ramsinks on them and I have a 90mm fan blowing over the mobo (not to mention I was out in the garage when it was -2c outside), so I don;t hink keeping it cool is the problem. I can post some pics of my setup in the next few days. Gonna give it another go in a day or two.
You might also try lowering the mem voltage a tad. 3.25 might be too high for the RAM which is only running at spec at 200mhz. I found the sweet spot to be 2.95v at 205 with my XMS3500. You may indeed need more voltage than that...but 3.25 seems high.
Just a thought:)
It took 3.25v to keep it stable at that speed. I am disappointed in this RAM. Seemed like everyone was talking it up, but both my sticks have not reached as high as most.
My KD7-E have a cold boot problem :confused: , now i'm using a CY bios..
There's a bench:
http://cieskoz.supereva.it/other/220%20kd7.jpg
but the motherboard not can run over 220 fsb :rolleyes: :mad:.. and i don't undestand why..
For Mike or others with this mobo. Is a vcore fluctuation normal? According to MBM 5 my vcore ranges from 1.58 to 1.68 even though it's set at 1.625 in the bios. I don't recall my KX7-333R having that kind of spread. My 5 and 12 volt lines fluctuate just a tad 4.97-5.03 and 11.92-12.04, respectively. Vcore just seems a bit wide to me.
My vcore fluctuates between 1.86 and 1.9 when set to 1.85 volts. My 5v line is steady at 5.11v, and mem is steady at 3.04 when set to 3.05
My vcore fluctuates between 1.71 and 1.76v when set to 1.725.....I questioned this when I first got the board, but MrIcee assured me not to worry. It doesn't seem like it can be good for the cpu or even psu as throttling the voltage is worse than OCing a chip with steady volts.
Mine also fluctuates a lot, but I still love the board. I just traded for a Abit NF7 though. :)
enjoy the NF7 dude
I'm getting pretty stable volts on this board, 1.650 set, varies 1.63-1.67
Think I *might* have discovered the reason my kd7-e gets poor memory bandwidth in Sandra. Feeling stupid that I didn't see this before, but
In the thread "Newegg has Abit KD7-E in stock" ( http://www.xtremesystems.org/forums/...g&pagenumber=2 ), N8 adresses a possible tweak involving Fast CPU Command. His post is near the bottom of the second page. Part of my reply was
"My KD7E won't boot with Fast Command Decode above 166 FSB, so it's set to normal"
In that thread I was posting about my first kd7-e, RMA'd due to a failed IDE controller. I don't know why I've missed this next point, but
My current KD7-E has NO setting in the BIOS for Command Decode.
It isn't just grayed out, it's not there. C8 BIOS. I haven't yet tried to MODBIN the BIOS to see if it's still in there, but last night I flashed every KD7-E BIOS from ABIT's website and Command Decode was not present in any of them.
I also tried WPCREDIT and WPCRSET to enable Fast Address Out Decode at offset 97H without success.
Any thoughts? Do I have a fluke board or is Command Decode missing on other boards as well? I *know* it was enabled and selectable between "Normal" and "Fast" on my first board. What I don't know is why I've ignored the missing setting in BIOS :confused: D'oh!
check the manual you must short the crom jumper :)
go open up your mainboard manual and turn to page 3-12 and look for 'CROM1:S2K mode select Header' it will tell u how to enable the "CPU Fast Command Decode" option in the BIOs. You have to set a Jumper on the mobo manually to enable it.
lol, Guess I'd better sit down and read the manual thoroughly this time. Thanks, gents :stick: -->me
well i think its the ram limiting mee
i canboot in windows even at 198mhz but not runnin any sandra membench or somewhat and 3dmark either.. always desktop kikks well i purchase a stick of 3200xms next week well see :)
here the 3dmark link @ 187mhz http://service.futuremark.com/compare?2k1=5751782
I am such a dunce - setting the "S2K mode select Header" to "Strapping from Boot ROM" did the trick. Memory is now exactly where it was on my first board.
This KD7-E is GREAT, and I just suck ;)
how do i set that```??
Quote:
Originally posted by IversGarn
go open up your mainboard manual and turn to page 3-12 and look for 'CROM1:S2K mode select Header' it will tell u how to enable the "CPU Fast Command Decode" option in the BIOs. You have to set a Jumper on the mobo manually to enable it.
hehe me/lamer :D
To clarify this; is this forall bus speeds or only if you go above 166mhz?Quote:
go open up your mainboard manual and turn to page 3-12 and look for 'CROM1:S2K mode select Header' it will tell u how to enable the "CPU Fast Command Decode" option in the BIOs. You have to set a Jumper on the mobo manually to enable it.
All FSB. From the manual (I'm reading it thoroughly ;) ), "The system performance will increase." And, they don't lie :D
I guess I was lucky as I've had this option available in the Bios since installation and I've never touched a single jumper.
Well, not to excuse my stupidity, but my first board had this enabled as well. The manual lists it being enabled as the default. My second board had it disabled and I didn't notice the lack of the setting in the BIOS setup until last night :(
My bandwidth is up to par, but ill check it anyways. My board was one out of the first batch that came to Norway, and still performs great :)
My vcore fluctuates too,seems to get worse the higher i raise it.
It seems to be my IDE that won't let me run my fsb higher.I have tried 4 diff hdds:
WD =214fsb
Seagate =214fsb
IBM =212fsb
Maxtor 80g ata133 8mb=217
All drives 7200rpm, ata100, 40g except the Maxtor
I tried turning off dma and going pio on a couple of them but it didn't make a diff.
omg my board sucks, your lucky as heck with 214fsb and stuff. i cant even do 180! LOLZ
Sorry about late delays in replying here guys...I've been out of town for the last 4 days.
Anyway-
sjohnson: Glad you sorted out that bandwidth issue:)
bigdawginva:
As far as voltage fluctuations are concerned, I also experience mild fluctuations. When set at 1.90v the range is 1.89 to 1.95v. These are the same type of fluctuations I had also experienced with my KD7-RAID. However, per my discussions with Abit (while conducting my KD7-RAID Mobo Review for Liquid Ninjas), I was told it was more the result of voltage sensor readings and not so much actual voltage changes. It was further explained to me that due to the very high voltage choices available on the mobo, the voltage sensor had to be calibrated differently and resulted in a "very sensitive" sensor:) Although I cannot confirm or disprove this, I've had no ill effects while overclocking at all. So I assume it is not a serious problem.
Thanks Mike. Great expalanation.
:(
My new KD7-E wants to go like the wind but I think, from what I have read here, that my 256mb of Crucial Registered PC2100 can't make the grade.
I can get my XP1600 close to 1600 going into WinME, good temps from my HS/CPU but page changes and slow mouse lead me to believe my memory is not making the grade.
I tested it on "memtest86 v 3.0" and it passed all the tests.
Current mem settings:
2.5.
no
3
7
3
2T
Enhanced performance
I will be adding a T-bred later this year.
Your opionions are appreciated.
Memory recommendations also.
Thanks,
weetoots
KD7-E v1.0 CY
XP1600 AGKGA
Radeon 7000 (don't laugh)
:confused:
I would get some Corsair XMS 3200 or 3500. I've built a good number of systems on the KD7-E now, and all worked great with the Corsair. I also tried some Kingston and Samsung which worked good too, but the XMS stuff just went a bit higher with less voltage.
Once you get good memory, just drop the multiplier and up the FSB. Get at least 3200 memory to give yourself some headroom to work with.
My manual for the KD7-E rev 1.0 on page 3-12 shows the pin header incorrectly. The pins (as shown on the page) are show from top to bottom as 1-2-3. However if you look at page 3-8 and fig. 3-7 the pin arrangement for CROM1 is actually, form the top of the page 3-2-1.
Maybe this is why some people are not getting this set up correctly. :rolleyes:
weetoots
Mine came from the vendor set wrong. I was simply stupid for not reading the manual lol...
sjohnson,
You can't be stupid if the manual is wrong! :toast:
No bud, I *was* stuupud - if I had read the manual I would have know that the setting enabled my "missing" BIOS setting for CPU Decode. Then, even if the manual showed the wrong setting I would have tried it the other way around, just to check if I had a bum board or something.
ABIT has a history of small manual booboo's. In any case, I've beat myself up for the last time (on this problem anyway :D )
received my XMS3200 today.. and guess what.. the kd7e doesnt even BOOT at 190mhz...well done abit :( i tried evrey bios and the Pio mode and..and..and..
this "new" kt333 suxx
anyone have this board an a SB Live card? i wanna know if the SB Live card can handle 40mhz
I do. Im at 209 mhz FSB for benching and 200 for daily use. never experienced a hitch.
thanks. thats what i wanted, 200fsb for 24/7
What kind of CPU voltage do you need for stability @200fsbQuote:
Originally posted by DuraN
I do. Im at 209 mhz FSB for benching and 200 for daily use. never experienced a hitch.
aaaargh wish i was lucky with that mobo :/
do you use a raid controller??
I can't seem to get to any bus speeds over 175 with the 1/5 divider and the 1/6 doesn't work.
Are any of you using the non functioning 1/6 ? There is no pci/agp lock for this board is there? I'm using the spd dram clock and spd ram timings so the memory shouldn't be the prob. I'm using the ocz 3500 el.
have u tried lowering the command decode?
I was using the comand that is used by default after clearing CMOS, which I thought would be of relaxed timings. Let me check though.
Mike,
No one is using the 1/6 divisor. It does not exist in the KT400 (or new KT333) chipset.
In fact, if you are seeing that 1/6 divisor choice in the BIOS, then you have the orginal BIOS release. I strongly recommend that you flash to the most recent BIOS. I find that the C8 works best for me. You will find the original release BIOS generally sucks and that you need to flash to a newer BIOS for improved overclockability.
You definitely want to be running the CPU Command Decode at Normal.
swissocer:
I'm currently running a Rocket RAID ATA 133 card with RAID 0 on the KD7-E. Works great all the way up to my max FSB at 206mhz. After 206mhz, the Radeon starts to complain.
Keep in mind that with only a 1/5 divisor, and PCI card, graphics card, or HD that does not like to be run out of spec may be holding you back. I've done a good handful of systems now based the the KD7-E, and have not had one that will not go at least high 190s low 200s. If you are sure about your hardware, you may have a bum board.
Thanx Mike,
Flashed the bios to C8, definite improvement....is there a fix for the data corruption issue? I was fine with 190x14=2660 but next try was 198x14= windows toast. The chip (xp2700+) is not modified...ie: no L3 mod.
Have you ever run the chip at 2.77GHz? That seems like an awful big jump, 190 - 198 just like that.
It depends on what's causing the corruption.Quote:
Originally posted by mike.elmes
Flashed the bios to C8, definite improvement....is there a fix for the data corruption issue? I was fine with 190x14=2660 but next try was 198x14= windows toast. The chip (xp2700+) is not modified...ie: no L3 mod.
The KT400 and "new" KT333 both suffer from HD corruption at high FSB speeds. There is no real fix, although the problem can be lessoned.
First, make sure you have adequate core and memory voltages going on. Unstable cpu and memory can cause the corruption to come on much sooner. Particularly with the memory. So see if rasing the voltages help. If no relief there, try dropping the memory timings a tad.
If no joy from any of that, than you are faced with setting your HDs to PIO mode if you want more FSB. That will help but it is your choice if you want to do that.
If none of that helps, it may be that your HDs are sensitive to running out of spec with the 1/5 divisor.
BTW, SPQQKY has a good point about bumping your FSB up in smaller increments. That's the best approach.
Thanx for the help on this....
I am going to try ramping up a bit slower and I'll add more voltage to both cpu, and ram.
I am now running windows 2k and 3dmark is finicky on that os...so I don't know if I can clock a bit higher. I'll give it a go and see if I do better under 2k.
I am still pretty happy with 190x14=2660....it sure is fast, 10,000 mips in Sandra:)
Cant wait to get back at her...I'll post my results.
mike
I have a Morgan 1G ,KD7-E, OCZ RAM PC2700 256m, they work well on FSB166. Indeed, I do benefit from your recommendation about KD7-E.Quote:
Originally posted by mdzcpa
It depends on what's causing the corruption.
The KT400 and "new" KT333 both suffer from HD corruption at high FSB speeds. There is no real fix, although the problem can be lessoned.
First, make sure you have adequate core and memory voltages going on. Unstable cpu and memory can cause the corruption to come on much sooner. Particularly with the memory. So see if rasing the voltages help. If no relief there, try dropping the memory timings a tad.
If no joy from any of that, than you are faced with setting your HDs to PIO mode if you want more FSB. That will help but it is your choice if you want to do that.
If none of that helps, it may be that your HDs are sensitive to running out of spec with the 1/5 divisor.
BTW, SPQQKY has a good point about bumping your FSB up in smaller increments. That's the best approach.
Now what confuses me is the booting problem. After unlocking my Morgan, I enjoy changing the multiple (sometimes higher sometimes lower), therefore, very often I can¡¯t boot when I turn on or reset my system. So I looked through the manual of KD7-E¡_¡_.
the solution seems to be offered by ABIT in the manual (page 4-5 ¡°solution in case of booting problem due to invalid clock setup¡±):
¡°Normally, if the cpu clock setup is wrong, you will not be able to boot. In this case, turn the system off then on again. The cpu will automatically use its standard parameters to boot. You can then enter the bios setup again and set up the cpu clock. If you can¡¯t enter the bios setup, you must try turning the system on a few times(3-4times) or press ¡°INSERT¡± key when turning on and system will automatically use its standard parameters to boot. You can then enter bios setup again and set up the new parameters.¡±
I wonder whether other users are suffering the same or I am unlucky. Although this solution can work (sometimes not 3-4 times but more ), I don¡¯t think it is a perfect one. It seems to means the responsibility lies in the users¡¯ overclocking (not standard CPU parameters). But ABIT always encourage us to oc our CPUs.