KT3 ultra2bulk and fsb 166

   I want to know if this motherboard suport 166Mhz fsb ,with the pci at 33 and the agp at 66 ?????????????????? ?(  ;(  ?(

I have seen at a friend the KT3V motherbord at 166mhz fsb does not change cpupci ratio to 15 ,in sandra 2003 it is saing that the cpupci ratio is 14 the pci is 42 and the agp is 84.
   I have reach the fsb 166 from one 1700+ occ  b0 series to 2600+ .
   Do you know other program then Sndra 2003 that read the pci bus and the cpupci ratio ?

Similar Messages

  • KT333 and FSB 166

    I just finish reading an artcile at tomshardware about the the new XP2700+ and XP2800+, the article says that the VIA KT333 chipset supports the new cpu's... but when I check MSI's site on the KT3 ARU, it says no support for the new cpu's... Is that MSI is choosing not to support or does this board not have the capabilitites of supporting it.

    Yes that's right the all of the original KT3 do not support the new Athlon, due to design flaws(i would call them).
    Check this thread for more info:
    KT3-Ultra Thread

  • AMD says MSI KT3 Ultra2 will support 166 MHz FSB

    Here's the link:
    http://www.amd.com/us-en/Processors/ProductInformation/0,,30_182_869_4348^4378|123_1_XP,00.html
    What's really interesting to me here is that apparently bios version 5.7 , with an AMD-reported release date of 10/23/02, is what will actually allow the KT3 Ultra2 to support the 166MHz FSB.
    It looks very much to me as if the KT3 Ultra and the KT3 Ultra2's not only share the same model number but also the same bioses as well.
    What would prevent bios 5.7, when MSI releases it to the public, from supporting a 166MHz fsb in the KT3-U's as well as the the KT3-U2's?

    Quote
    Originally posted by wonkanoby
    http://www.msi.com.tw/program/e_service/forum/viewindex.php?threadid=6056&boardid=13&styleid=1
    Thanks for the link, Wonk...  I had actually read through that thread and kind of came away with the impression that although MSI said the KT3 U would not support a 166MHz FSB, nobody was really sure enough about that to place bets on it...
    Anyway, I only ran across this info on the AMD site last night--apparently it's new info, and runs in tandem with a rumor over on the Inquirer http://www.theinquirer.net/?article=6032
    which states that AMD is going to announce 166MHz FSB 2600's tomorrow--and if not tomorrow then shortly before Comdex.  I have to admit this info on the AMD site lends some credence to the idea.
    What's interesting to me as well is that on this same list the KT4 Ultra is not listed as supporting the 166MHz fsb 2600 +, at least with its present bios.  
    Hmmmm.....

  • AMD Athlon XP 2800 (Barton Core) will not post at FSB 166 MHz.

    Per top of the board “stickys” I have read a great number of the post on this board and done my homework to provide as much technical info to help you help me. This should explain some of it’s lengthy nature.
    Aside from Memory, HDD and Video card every thing else has been unplugged from board and power or stripped out of slots to isolate the problem.
    Presently running BIOS: A6712 V. 1B
    *As seen on face of MoBo: KT4V MS-6712   Ver:10A
    *The Original Box bar code label: KT4V-L (601-6712-050)
    K7, KT400. 5.1 chnl. S/W Audio, LAN, D-Bracket 2.
    CPU: AMD Athlon AXDL 2800 DLV4D 
    Q334763K40034  AQYHA 0447APMW
    Chip lable
    Athlon XP (Barton) Low Power Processor (Model 10) 2083 MHz
    OPGA Organic Pin Grid Array 1.50 Volt max. Temp. 85°C
    512 KB L2 Cache 333 MHz System bus (166 MHz FSB) x 12.5
    Memory: x3- PC 2700 512 mb DDR 333 Super Talent
      And shows at post as running 333MHz. MemTested to 1,000% with first 1 stick, then all 3 sticks presently on bios A6712vms.1B0. at fsb 100MHz (aprox. 24hr.) I even installed and ran other AMD utillitys while MemTest was running to “stress” the system memory with zero errors. During this period I checked Windows Task Manager > Performance, CPU usage at 100%, PF usage 1.35gb. No Probs.
    Video card: Removed: MSI AGP-8X Ti4200- VTD8X 128 MB DDR 533MHz
    Replace with: PCI card (to rule out AGP card prob.) Gilmont, nVidia 64mb
    (also tried Matrox AGP 32mb card with no different results then above cards)
    Power Supply: L&C Model: LC-B350 ATX = 350 watt
          115/130v      B/4a      60/50 hz
          +3.3v/+5v   1+12v   -12/-5v    +5vsb
          28a   35a    16a    0.8a    0.3a   2a
       +3.3v combined load 200w
    Cooler: Slim Volcano 10+,   P/N A1671,  rated for up to AMD Athlon CP 3400+ & fresh heat sink compound. Freshly re-seated.
    All PCI  slots empty as I attempt to run bare bones to eliminate problems. (except now running Vido card in 1 slot)
    Floppy Drive: ribbon unplugged from board
    HDD-0: Seagate 8 gb master, (HDD tested w/no errors)
    O/S: Win. XP w/sp2
    HDD-1: slave/  unplugged from ribbon and power
    Sony CD-Rom: Unplugged from PCI slot and power
    SATA/RAID-usb 2.0 card and other HDD’s, removed and not included till Sys. runs at full potential.
    Exterior HDD and Burner beyond the scope here and not attached.
    O/S Win. XP-sp2
    BIOS I have tried: The original; Ver:10A, ran fine on Athlon XP 1600 (1400 MP) 3 years.
    •   Then with MSI Live Update 3: Installed v. 1c which couldn’t run FSB 166MHz (MSI:” Fixes system reports incorrect message for AMD 3200+ CPU.
    - Supports Sempron L2 512K 3000+ CPU.)
    However, v. 1.c did not work and would not post at all with the newly installed Barton AMD-XP 2800. [frankly this attempt was months ago and I do not remember whether it would post at the slower 100 and 133 FSB speeds, and also to muddle my memory further I was upgrading an A7N8X-D with a Barton XP 3000 and having similar problems on the ASUS,,, which is now running fine at full potential. ; - p
    •   Then I selected and flashed A6712 V 1.7 122602, boots and runs Win.XP-sp2 at FSB 100MHz & 133MHZ.  (MSI:” Supports AMD Barton XP2800+ (FSB333) CPU
    -Fixes system sometimes will have IDE CRC error   -Fixes D-bracket2+USB keyboard, cannot use keyboard on DOS mode.)”    which couldn’t run FSB 166MHz.
    I checked with the Tech. at the local shop where I purchased the KT4V MoBo. He suggested I try a different BIOS but he didn’t specify which one. He is a personal friend and admits to some bad luck and dead boards due to flashing bios so reluctant to mess with it.
    •   Now running:  A6712vms.1B0 – MSI hid this BIOS V. found here:
    •   http://www.msi.com.tw/program/support/bios/bos/spt_bos_detail.php?UID=362&kind=1
    •    On a different page than the 2 versions mentioned above. http://www.msicomputer.com/support/bios_result.asp
    •    No wonder people are frustrated and confused about different MoBo versions there ID #’s and the BIOS versions them selves as seen on this news board. MSI’s fault, no fault of anyone here trying to help.
    A6712vms.1B0
    Runs fine at FSB 100 (shows as XP 1250+) and FSB 133 (shows as XP 2200+) Booting to Win. XP-sp2 on CMOS, default setup other than minor tweaks to accommodate MSI Ti 4200 AGP 8X 125mb graphics card or Gilmond PCI card. But which couldn’t run FSB 166MHz .
    No post at FSB 166 mhz (once, it did flash a post screen stating AMD Athlon XP 2800 for about 2 sec. before going blank) Manual power down. Just now I rebooted with FSB 166, and again saw the AMD Athlon XP 2800 at top of the post screen as I hit pause break,,,, then the machine power crashed to Off. Once it even loaded Win.XP-sp2 but crashed to power off with in 2 min.
    I must have booted this beast a dozen times or more after Clear CMOS jumper each time it went to blank screen with mach. still running. Start over; set Default settings and work up with FSB 100, 133, each time to read what POST says and see if it will boot to O/S.
    Btw: I have looked for clear evidence through the not so specific descriptions MSI uses to separate these board model #s and may be part of my current problem with correct board ID = correct BIOS ID.
    Found here:
    [VIA] unofficial FAQ for KT4 series motherboards
    https://forum-en.msi.com/index.php?topic=6090.0
    Eg: - KT4 Ultra (MS-6590), 6-channel hardware audio codec
       • KT4 Ultra (Pure Version)
       • KT4 Ultra-B (Bluetooth ready)
       • KT4 Ultra-BSR (Bluetooth ready + Serial ATA RAID)
       • KT4 Ultra-FISR (Bluetooth ready, Serial ATA RAID, Gigabit LAN, IEEE 1394)
    - KT4V (MS-6712), 6-channel software audio codec
       • KT4V-L, with onboard 10/100 LAN
    - KT4M (MS-6596) micro-ATX board
       • KT4M-L, with onboard 10/100 LAN
    - KT4A Ultra, (MS-6590) NEW!! based on KT400A chipset
       • KT4A Ultra (Standard Version)
       • KT4A Ultra-SR (Serial ATA RAID)
       • KT4A Ultra-FISR (Serial ATA RAID, Gigabit LAN, IEEE 1394)
    And a very similar version of this on Official MSI site. Both seem to try and make a difference between modles with on board Lan, and Blue Tooth ready.
    Take a look at my original box sticker:
    *As seen on face of MoBo: KT4V MS-6712   Ver:10A
    *The Original Box bar code label: KT4V-L (601-6712-050)
    K7, KT400. 5.1 chnl. S/W Audio, LAN, D-Bracket 2.
    Yup, it says all this on the sticker and the in the manual and verified on the MoBo. So I can only guess at all parts of the puzzle as they gave them to me which lead me to the afore mention BIOS versions I ran, or am running. The sticker points to nearly half of the boards above except for the MS-6712 and the Ver:10a which is what I based my BIOS choices on. If someone knows differently and can lead me to official Nfo with a better answer I’m all ears.
    Just saw this: Latest Official BIOS : KT4 MS-6590 (1.4), KT4V  MS-6712 (1.8 ) , KT4M MS-6596 (1.1)>>Here: [VIA] unofficial FAQ for KT4 series motherboards
    « on: 24 October 02, 05:14:04 »  But these links and all but one link in this ‘sticky’ are broken .
    So if  (1.8) is the Latest Official BIOS for KT4V MS-6712  then what is this at the Official MSI SITE ?
    KT4V
    BIOS Type
    AMI® BIOS      File Sizes
    485KB
    Version
    1.C      Update date
    Update Description   -Support Sempron L2 512K 3000+ CPU.
     BIOS Type
    AMI® BIOS      File Size
    Version
    1.B      Update date
    2004-8-9
    Update Description   Support Sempron 2200+/2300+/2400+/2500+/2600+/2800+ CPU.
        BIOS Type
    AMI® BIOS      File Sizes
    485Kb Version
    1.A      Update date
    2004-5-13
    Update Description   - System is unstable to run 3DMark03 with ATI 9600 PRO
    - Add "PS/2 Keyboard Detection" Function.
    - Support AMD 2400+ CPU.
    BIOS Type
    AMI® BIOS      File Sizes
    514KB
    Version
    1.9      Update date
    2003-7-29
    Update Description   -Fixed Adaptec 2100S SCSI card cannot be used
    -Modify CPU temperature detection
    -Support boot from Onboard LAN
    BIOS Type
    AMI® BIOS      File Sizes
    514KB
    Version
    1.8      Update date
    2003-2-12
    Update Description   -Support AMD Barton XP3000+ (FSB333) CPU
    -Add "CPU Halt Command Detection" item in the BIOS Setup
     Please also keep in mind I’m not trying to scuff anyone’s shoes…I just want to get what’s right for my board so that it and the CPU can live up to their full, "as advertised" potential and run with the other 3 big dogs under my desk.
    This seems descriptive enough and rather lengthy. Just doing my homework and reporting my findings so I won’t include actual CMOS settings unless requested. I have notes on all settings I currently use to boot with this problem.
    Other Dogs:
      ASUS A7N8X-D running Athlon XP 3000 barton core 10 (runs fsb 400..whoknew?), Mem:2.5gb Super Talent
       ASUS A7M266-D running Athlon XP 2800 (mp), Mem: 3gb Super Talent
                                                   Athlon XP 2800 (mp)
      I don’t want to boar you with the details.
    Yes, and the above have been upgraded w/new chips GFX cards and BIOS,,, NP.
      Cut to sound track: Down on the BIOS again,,, wasn’t that Creedance Clear Water Revival?
    Any suggestions or insights are much appreciated. 

    Welcome, and thank you for a thorough input! Hope I don't miss something you already said!
    Quick version: Try setting processor voltage to 1,5 volt.
    Long version:
    Posting at wrong FSB can be put down to two things:
    1 The processor isn't what you thought it is, but I think you eliminated that.
    2 The system cannot run the processor at the correct speed. Mainly this has to with overheating, and/or that memory and processor cannot cooperate. This must be it, as you noticed the processor is correctly recognised.
    You have little connected right? Then the best thing would be to pull power cable out. Take the motherboard and redo the seating of the processor, this is much better done with motherboard taken out.
    At the same time, I suggest you clear CMOS. Should always be done when changing processor, and I've noticed on the Internet there are a few 1,5V XP2800 around.
    http://64.233.183.104/search?q=cache:Q4eIa6OhudcJ:forums.amd.com/lofiversion/index.php/t47487.html+AXDL2800DLV4D+problem&hl=sv&gl=se&ct=clnk&cd=1

  • GTLREF and FSB VTT Voltage Tweaking

    *** This is all done at your own risk. I, any user on this forum, this forum, or MSI will NOT be held responsible for your actions! ***
    I'm sure you've heard about GTL reference voltages.
    I've decided to write a simple guide (it's not that simple any more... lol) so, people can understand how to tweak these voltages, and get those high FSB &/or CPU clock speeds.  I'll get right down to business...
    A quick breakdown of exactly what A/GTL+ [Advanced Gunning Transceiver Logic] does:
    Quote from: Intel Q9000 Datasheet
    Most processor Front Side Bus signals use Gunning Transceiver Logic (GTL+) signaling technology.  This technology provides improved noise margins and reduced ringing through low voltage swings and controlled edge rates.  Platforms implement a termination voltage level for GTL+ signals defined as VTT.  Because platforms implement separate power planes for each processor (and chipset), separate VCC and VTT supplies are necessary.  This configuration allows for improved noise tolerance as processor frequency increases.  Speed enhancements to data and address busses have caused signal integrity considerations and platform design methods to become even more critical than with previous processor families.
    Rather optional: read this article on how the values work: http://www.thetechrepository.com/showthread.php?t=87 |  It's a great explanation and shouldn't require you to do any more research into the matter.  However, if you still don't understand how GTLREF works, and how VTT effects it: Google is your friend.
    You can tweak the GTLREF and VTT (AKA FSB VTT voltage/FSB Terminator voltage) via the Cell Menu in the CMOS setup.
    There are many different GTLREF voltages.  There are GTLREF values all over mainboards.  The ones we want however, are for each CPU die (only P45 boards have the settings to signal each die (so far?)) or both CPU dies (every board excluding P45), and the ICH/NB.  You could guess the names.  They are pretty obvious, and sometimes named differently on each board, but they all do the same thing, generally speaking.
    The P45 boards have quite an edge.  You can sometimes get a flaky core that needs more voltage than the rest. You can fix that problem with the individual die settings.
    NOTE: You will NOT find these options present on a budget/low-end board.  Do not ask if it will have the options in a future BIOS release - it won't.
    According to Intel's datasheets: the nominal voltages for GTLREF are 2/3 of the VTT voltage.  However, I've found better results from setting ~63% on the CPU [Yorkfield and Kentsfield] and ~67% on the NB [780i, P35 and X48].
    You use a simple formula to calculate what each value will be:
    Code: [Select]
    a * b = c
    a = FSB VTT voltage
    b = percentage
    c = GTLREF setting
    For example:
    1.37v * 67% = 0.9179v - Note how precise my result is. The more precise you are, the better chance you will have of getting in the correct margin. Vnoise must also be taken into account. It's +/-10%.  However, I doubt noise is this high on high end boards.  Call it +/-3-5% if you have a high end board with a good power phase.
    NOTE: If upon tweaking, nothing is improved, you may need to go up/down a few notches.
    After further investigation to Intel's datasheets.  There is a maximum the GTLREF should be set to both in an above and below manner.  The minimum and maximum should be:
    Min:
    Code: [Select]
    0.550 * VTT = min
    Max:
    Code: [Select]
    0.725 * VTT = max
    [For those of you that are quick minded, that means don't go below 55% or over 72.5%]
    These GTLREF voltages are terminated on-die, going TOO HIGH will most likely mean the death of your CPU!  Going TOO LOW is guaranteed instability!
    Do not hesitate to tweak these values, but do not go beyond the limits!  They can sometimes give you great results.  On the other hand, they can also make your results worse (yes, worse).  That means you need to tweak the values more.  Please keep that in mind.
    Post your results in here - I'd like to see them.
    Good luck with your tweaking!
    If you have anything to add or change here, don't hesitate to contact me!
    A sidenote for P45 users:
    Quote
    MSI Tech.   11/03/2008   This is decision of our engineers which work directly with Intel.   
    End User   11/03/2008   They also recommend you don't go about 1.5 volts on the CPU, but this mobo will do it. Is there a technical reason why the GTL Ref voltage will not to 67%. All technical documents from Intel suggest 72% is the limit.   
    MSI Tech.   11/03/2008   No, since this is recommended by Intel.   
    End User   11/03/2008   I can not set the GTL Ref voltage to 67%, the highest it will go is 63%. This may be limiting my overclocking on my quad core. It there anyway to change this? Thanks
    james1701 contacted me via PM and shared this info with me.  It appears MSI refuses to put the GTLREF voltage over the limit of 63%.

    Hi AaronYuri and Autumnale,
    I'd like to pick your brains if you don't mind.  Both of you have made excellent posts here and on the extremesystems.org forum and have helped me very much with setting up my P7N Diamond.  I've learned a tremendous amount on the finer aspects of CPU OC'ing.
    This thread about GTLRef and FSB VTT tweaking is especially valuable.  But would either or both of you care to elaborate more on the relationship between Vcore and VTT?  I've seen references (from both of you and other posters) to http://edgeofstability.com/articles/dfi_p35/gtl/gtl3.html and statements declaring that VTT should not exceed Vcore.  From the link, I've come to understand that Intel processors have a safety mechanism to improve stability, but that raising VTT above Vcore will effectively disable the mechanism.
    Code: [Select]
    Another issue that most users are unaware of is the relationship between VCORE and VTT. To reduce the amount of ringing at the driver,
    Intel has added a weak pull-up device to the output buffer as mentioned above. This device turns on at the beginning of a low-to-high signal
    transition, substantially reducing the impedance mismatch between the output buffer and the transmission line. As a result, the amount of
    overshoot and ringback is significantly reduced. The source terminal of the pull-up device is connected to the core voltage supply. This causes
    the logic high voltage to rise above the GTL termination voltage for one cycle. After one bus cycle, the pull-up device is turned-off and the output
    will stabilize at VTT if the output remains in the logic high state. But when we raise VTT above VCORE we have effectively removed the pull-up
    device from the circuit.
    Therefore can anyone clarify how much of a threshhold exists between VTT and Vcore?  Also, does this rule refer to the absolute minimum Vcore during operation (net of Vdrip and Vdroop under full load), or just the average or max Vcore?
    On my P7N Diamond / Q6700 combination, I have VTT (FSB Term Volt) set at 1.293V.  My CPU VID is 1.2625V (per CoreTemp).  With cell menu Vcore set to +0.1250V, my idle Vcore varies between 1.344V and 1.352V as per CPU-Z (~0.04V Vdrip).  At load, Vcore varies between 1.296V and 1.304V as per CPU-Z (~0.05V Vdroop).  The voltages fluctuate frequently but mostly center around 1.352V idle and 1.304V load (Prime 95 Small FFTs).
    As such, my Vcore is typically well above my VTT.  But for brief periods, at it's absolute lowest point, my Vcore falls to 1.296V, just 0.003V above my VTT of 1.293V.  Assuming, the readings from CPU-Z are accurate, is this sufficient to not cause any conflicts with the safety mechanism?  I suppose I could lower VTT further but I've managed to run 12 hr+ Prime 95 Small FFTs under the current setup and am ready to FREEZE my cell menu tweaks.
    Should I consider my settings stable or continue experimenting with lower VTT (to avoid conflicting with the pull-up safety device)?  In any case (yes, you both do have lives and may not have time to respond), thanks for all your valuable explanations.

  • DDR500 and FSB Divider setting

    Hi,
    Been running my system as per signature and it's MemTest86+ and Prime95 stable.  However I have 2 problems.
    Firstly, if I try to raise the FSB to 251 the divider resets itself from 1:1 to 5:4 (both MemTest and CPU-Z verified) with the RAM dropping back to 200.  I have tried this with MAT settings of Slow, Fast, Turbo and UltraTurbo, Vcore from 1.575 - 1.7 and Vdimm from 2.7 - 3.3.
    None of it makes any difference.  It's like a switch.  As soon as I set 251MHz the system reboots with 5:4 divider.
    RAM appears OK.  Have run MemTest for 10 hours at 250 with no errors and this RAM should easily handle an overclock >270 .  Don't think heat is a problem as the highest stressed load CPU temp (by SpeedFan) I can get is 60 C.
    PSU shouldn't be an issue and I can run the CPU up to 260 with the 5:4 divider so still some headroom there.
    I've tried it with both the DRAM freq set to Auto and 400, no change.  It's almost as if it's a design feature or limitation of the BIOS.
    Also tried DRAM at 500 and FSB at 200 but the CMOS wouldn't even load at that setting.
    Any ideas?  Am I missing something obvious?  Anything else I can try?
    Second problem.  The RAM is spec'd by OCZ as Enhanced Latency 2.5-3-3-7 @ DDR500.  However the SPD is 2.5-4-4-8.  When I set the timings manually it accepts and displays 2.5-3-3-7 in the BIOS but both MemTest and CPU-Z report the clock speed as 2.5-4-4-8.
    The RAM does run stable at 2.5-3-3-7 at DDR500 as I have set this dynamically in the MemTest Advanced Options.  Unfortunately this does not get written into CMOS.
    Is this another BIOS problem?  With this rev bios and my previous HyperX I could easily set tighter timings.  

    @rc540
    Quote
    What stepping is your 2.8c and did you raise the vcore to acheive a 250 FSB?
    Stepping 9/Rev D1, Vcore @ 1.7V
    Quote
    I assume you set your FSB to DDR400 in BIOS?
    Yes, as mentioned in OP tried both 400 and Auto.

  • Random resets with a kt3 ultra and a MSI GF3 ti200 in 3d games

    Im having random resets with a kt3 ultra and a MSI GF3 ti200 in 3d games; namely Mafia and Bf1942. Ive tried new drivers for the video card, checked the cpu temp, and bios settings. Any ideas on how to fix it or is their a compatibility problem with the mobo and the video card?

    I found my 6380 v2.0 mobo liked 1 brand of ram more than other.I only run crucial,kingston or muskin(micron chips)ram.Put all bios settings to defaults & try only 1 stick(1 brand) of ram at a time.I also found my gf3 ti 200 & 500 liked certain versions of drivers over others.It would crash on some.Try original cd install drivers that came w/  vid :D  card.Try running 3d mark 2k1 bencmarks to test all drivers & ram.

  • KT6 Delta/KT3 Ultra2 and MegaRAID SCSI failure

    Greetings,
    Synopsis:
    I have several MSI motherboards and a MegaRAID SCSI 320-2 RAID controller made by LSI Logic. In the older boards (K7D Master and K7T Turbo2), the controller works normally. In the newer boards (KT3 Ultra2 and KT6 Delta), the controller is unable to display its DOS based or "Web" based BIOS.
    I have changed numerous settings in the BIOS of the newer boards but nothing seems to allow me to configure the RAID controller. I also found the following link (https://forum-en.msi.com/index.php?threadid=16821&sid=&hilight=SCSI+RAID) to be interesting. Unfortunately, the suggestions therein did not effect a positive change.
    Details:
    Working boards:
    K7D Master Award BIOS W6501MS V1.1 030502 with 2 AMD Athlon MP 2000+ processors, 1 Gig DDR memory.
    K7T Turbo2 Award BIOS W6330MS V3.3 121901 with 1 AMD Athlon 1200, 512 Meg of SDRAM.
    Non-working boards:
    KT3 Ultra2 AMI BIOS A6380VMS V5.5 071002 with 1 AMD Athlon XP 2100+, 1 Gig DDR 333 MHz memory. PS actual reading: +5=5.030, +12=12.228, -12=-12.071, -5=-5.026. Single 450Watt PS.
    KT6 Delta AMI BIOS A6590VMS V5.5 021004 with 1 AMD Athlon XP 2600+, 1.5 Gig DDR 400 MHz memory. PS actual reading: +5=5.278, +12=12.045, -12=-12.400, -5=-5.277. Dual 450Watt PS.
    The non-working boards work normally without the RAID controller. In fact, they seem to work normally with the RAID controller save that they do not allow the RAID controller to enter configuration mode. They report that - will be executed at the end of POST but they just go to a boot attempt off the floppy drive.
    These same systems (the last two) also do not work with an AMI Enterprise 1400 RAID controller BIOS ver. 1.48 (latest version) or an LSI Logic made Mylex controller.
    Any suggestions on configuration changes, etc. that would allow these RAID controllers to work in the aforementioned motherboards would be greatly appreciated. Further information available if needed.
    -Motherboard type and model: See above.
    -Bios type and revision: See above.
    -CPU type and model: See above.
    -Memory name, model and quantity: See above and seemingly irrelevant.
    -Video card: AGP based, but all different.
    -Power Supply: See above.
    -Hard Drives: Seemingly irrelevant as none are hooked up.
    -Operating system and service pack level: Seemingly irrelevant as no OS is installed.

    I feel your pain buddy !!! it's the same thing for me.  I just got a LSI-22320 and I going through the same troubles.  I was really looking forward to having this nice card in my system, only to find out it would not even let the system boot.  I took the card out and pluged it in my Mom's older than dirt computer and IT WORKS !!... This was a very disapointing experience to say the least....
    Well, if you do here something good, please let me know...
    P.S.  Your SCSI-brother in pain :
    Eli
    [email protected]

  • D3D crashing on KT3 Ultra 2 with 166 FSB

    I've just upgraded my CPU from a XP2000+ Palomino to a Barton 2500 with the idea of overclocking it but I'm having problems running it at stock speed. I'm using a KT3 Ultra 2 board with the latest 5.7 bios and a Radeon 9700 PRO. As soon as I run any 3d apps with a 166 Mhz FSB my PC crashes immediately.
    I've tested the CPU and memory with Sandra and as far as I can tell the system is 100% stable until my 3D card kicks in. If I underclock the Radeon core & memory then the system becomes stable again.
    If I go back to a 133 FSB then everything runs with the Radeon at full clock speed. I'm coming to the conclusion that the AGP divider isn't kicking in and I'm overclocking the bus - is there any way to test this?
    Is my motherboard knackered? Can anyone help?

    Thanks for the suggestion. I've had a go at 167FSB but its just the same. My PSU is a Thermaltake Xaser 480W.
    I've found the bit of Sisoftware Sandra that tells you the AGP multiplier and its still down as being 1/2 at FSB166 although the PCI has correctly gone to 1/5 so it looks like my first guess was right.  Is there any way to force it back down to 66MHz?

  • MSI KT3 Ultra ARU, FSB for Processor

    Help me!
    I have a KT3 Ultra ARU, which is lovely, however, I had an XP 1700+ with 512 DDR 266 Ram. The FSB was running at 133. However, i tried to change it, and it wouldn't boot.
    Fine, so I resetted Cmos and all was ok.
    I have now just installed an XP 2200+ with 512 DDR 333 Ram. My FSB, again, is 133, but i'm sure I read it can go up to 166 for these components. Is that right????
    Many thanks in advance,
    Jon

    I know that the 40.41 drivers were specifically targeted to the vertex shader performance, thus increasing the nature test, however, I don't know what else they did to get such a high performance increase. All I can say is amazing. You can get the drivers here , that is assuming you are running winxp or 2000 as this driver only supports those.
    Edit: It is a good idea to burn in your hardware before you go overclocking stuff. You may need to play with clock frequencies for your vid card as I can overclock alot higher then 305/605 but performance (and therefore score) drops significantly. Try different settings and run the test, when you feel comfortable overclocing. Be aware if you have never overclocked, that it can damage you components and void any warranty you have on your hardware.

  • WINXP won't boot on FSB 166

    I know that this kind of trouble has been here many times, but none of the posted info has been a solution to my problem.
    I've just upgraded to XP2500+ Barton. The system is running perfect on 133 FSB, with the RAM at 166 (333), Sandra 2003 Pro results.
    But!!!!!!!!!!!!!!!!!!!
    Whenever I try to get to 166, bios runs fine, but Winxp won't boot, claiming to either not find a crucial library ( I've received many various errors ).
    The farthest I've gotten, is the winxp boot screen, with the blue thingie moving, though the disk beeing dead. That was after setting a permanent AGP voltage and low driving comp.
    I have reinstalled the WinXP, that didn't work either. So underclocked to FSB 133 and I'm writing this thread.
    Could anyone help, please. There is so many positive comments about the KT3 Ultra 2 and Bartons, so why doesn't mine work.  

    Found some. Here goes a little of what I found on adress, but there are lots more, especially if you are upgrading from Windows 2000:
    http://search.microsoft.com/search/results.aspx?st=b&na=83&qu=crucial+library&View=en-us
    167354 - BUG: Error "Unexpected EOF" May Occur Under Dbmsrpc3.dll
    If it uses the 16-bit Multi-Protocol Net-Library, a DB-Library application may return the following errors when running queries through multiple concurrent connections: DB-Library: Unexpected EOF from SQL Server Net-Library error 81:...
    http://support.microsoft.com/default.aspx?scid=kb;en-us;167354
    321698 - PRB: Cannot Connect to MSDE 2000 by Using ADO.NET with SQL Authentication
    If you try to open a SqlConnection object to a new installation of Microsoft SQL Server 2000 Data Engine (MSDE 2000) under the following conditions, a SqlException exception may by thrown: You are using SQL Server Authentication. -and- You are using...
    http://support.microsoft.com/default.aspx?scid=kb;en-us;321698
    818779 - HOW TO: Populate a DataSet Object from a Database by Using Visual C++ .NET
    This step-by-step article describes how to fill a DataSet object with the results of one or more database queries and then how to access the data after the query is loaded in the DataSet object. DataSet objects are in-memory objects that can hold...
    http://support.microsoft.com/default.aspx?scid=kb;en-us;818779
    More Support & Troubleshooting results

  • KT3 Ultra2-C FSB support?

    About 13 months ago I purchased a prebuilt PC system and made the mistake of assuming (based on the name) that the KT3 Ultra2-C (MS-6593) was similar to the rest of the KT3 Ultra2 line, which I had heard good things about, and I expected similar future processor support.  In fact if you do a Google search you will dig up some old news releases that even state that MS-6593 supports Barton CPUs.  Flash forward in time, and I discover that despite the extremely similar name, the Ultra2-C apparently does not support the newer 333 FSB CPUs.  A search on this site comes up with some posts that say this is because the Ultra2-C  doesn't even have the 1/5 divider, so the PCI speeds at 166 will be far out of spec.
    Can anyone confirm if they have gotten Bartons to work with this motherboard?  Or otherwise confirm if this board is in fact lacking a 1/5 divider at 166 FSB?  Can this be fixed with a BIOS update?
    The BIOS allows one to set a CPU FSB up to 200 mhz, and the board came with overclocking utilities, etc.  Speaking as an engineer myself, it is completely illogical to make a product that supports high FSB but does not have a 1/5 DIVIDER at 166!  I also can't believe a company would release a product with such a similar name yet have such critical differences in features.
    Signed,
    Confused and Disappointed

    Yepp, it does not have the 1/5 divider, similar to the KT3 Ultra-ARU. But the Ultra-ARU is often reportet to run at FSB166, but it is not official
    CPU list:
    http://www.msi.com.tw/program/products/mainboard/mbd/pro_mbd_cpu_support_detail.php?UID=357
    misc page:
    http://www.msi.com.tw/program/products/mainboard/mbd/pro_mbd_detail.php?UID=357
    greetz sj

  • About FSB 166 with KT4 Ultra

    I use XP1700+, DDR 256MB PC2700, 11*133
    what if i increase fsb to 166Mhz and reduce mutiplier to 8.5 that will run at 1411 Mhz
    Do the PCI bus will automatically adjust to the original?
    (My friend told me that at 66,100,133,166 bus this MB wil adjust to the 33PCI and 66AGP)
    Thanks again

    Yes, on my KT4 I can up the FSB to 166, but the mutliplier needs to be reduced of course. Gives me a pretty good boost, and has been stable with good temps for almost a month.

  • K7N2 Delta-L and FSB

    I set my FSB via bios to 174x12.5...but as to my computer for some reason its showing the FSB at 173.... would anyone know why this happens and is there any way to get it to 174 like it should be. Thanks...

    1mhz up or down does it matter ?
    all frequencies is a bit off.
    take my cpy for instance.
    its working at 166*12=1996 mhz. but if i use a program in windows they all report around 2004.6mhz

  • KT3 Ultra2 and Win2k Bug

     ;(   I recently had to return my KT3 Ultra board.  Well, not too recently...it took a month.  But no biggie, they sent me another.  My reseller went bankrupt so I dealt directly with MSI, and they were very profesional.  
    They sent me a KT3Ultra2.  
    I just plugged all my hardware up as it was, and I was going.  But after a day I have started to notice a problem that is so fiercly aggravating that I am going to chew my arms off. here we go:
    *I am running windows 2000 pro.  SP3.
    *I have an Athlon 1800+,
    *1 Maxtor 40GB Hard drive
    *ATI 32MB DDR Graphics card(name escapes me, i'm an audio nerd)
    *M-Audio Audiophile 2496 soundcard
    *M-Audio Oxygen 8 Midi controller connected to onboard USB(not the bracket)
    *I am using a PS/2 mouse and kbd.
    *1 generic MAG monitor
    while running windows, under a load or not under a load, after about 15 minutes at the most, my mouse will lock.  the keyboard still works, and the CPU temperature and usage do not increase.  My Midi controller still works.  In short, everything runs great, but the mouse just won't last past a few minutes without gagging.   X( And yes, I know the mouse works because I've swapped it with others
    I have APIC turned off in the BIOS, quickboot disabled, and my FSB set at 133MHz, but no other changes have been made.
    I don't hae the manual for THIS board, only the last the Ultra, but the BIOS appears identical.  I have the optional D-Bracket connected at the point I connected it on the other board.   is this the problem?  The LED readout was so helpful....anyways, if anyone here has any advice or help, I would really appreciate it.  I'm at a loss.  I've done a clean install of windows 2000, and other than optimizing for background services and turning ACPI off(necessary for midi-latency reasons), no changes have been made to it.   My previous installation of Win2K did the same thing.  

    no, one is a generic logitech wheel mouse, the other is a microsoft intellimouse.  I had no problems with this on the last board.  how are these two boards different?

Maybe you are looking for

  • Insufficient space in Javaheap Error when installing BIEE 10.1.3.4 on linux

    Hi, I am trying to install OBIEE 10.1.3.4 on Linux Enterprise 4 on a VM machine. When the installer reaches 20% it shuts down with the following error. Can someone please tell me how to resolve this as I am not able to install BIEE. I have 4GB of RAM

  • Camera Raw 6.7 does not save XMP files

    I am running Camera Raw 6.7 on a Windows XP machine. In the Preferences under "General" I have the "Save image settings in" set to "Sidecar ".xmp" files. And in the DNG File Handling, I do NOT have the "Ignore sidecar ".xmp." file check-box checked i

  • Problem loading elements--AIR a problem, don't know where or what energy pane is

    Can anyone help?

  • AC305

    I have been working on the account determination and for the clearing account for revenue from asset sale I ma getting this message that account not allowed to be a balance sheet account. I am thinking the clearing account should be a B/S account. ca

  • Vanishing registration?

    About five weeks ago, I installed Adobe Photoshop Elements 13 and Adobe Premiere Elements 13 and registered the product serial numbers with no problems.  However, these registrations no longer show up when I query my account details.  If I attempt to