K8T Neo-FIS2R Memory Problems

 Hello,
First can I say thanx in advance for any help that I might get, I'm new to this board and I appretiate the hard work you all put in to the comunity.
The problem originaly was that this board would only work with one memory stick. It did not matter how big it was 256 - 512 - 1GB, it would boot, but if I added another say 2X 512 the system would not boot, the screen would just stay black.  I upgraded the bios from the MSI site - the file name was 6702v22.zip.
The system now boots fine with 2X memory sticks is (that cured it), but now I find that I cant alter the memory timings. No matter what I set the CAS to it always defaults to 3, Its like its stuck on auto for some reason. I reset the bios after the flash, and tried different slots, different memory sticks, but the bios seems to ignore any manual settings I put in there.
Can anyone shed some light ?
Thanx
Umpa....

Duh. I read your post completely. The reason behind asking for specs is simply to investigate issues with older CPU's running the newer Bios's and vice versus. Yes there are known issues but as you are not going to supply specs then I am not going any further either. However you already have guessed my point and yes I have one of those MB's myself and can tell you firsthand what happened to me when I ran my older CPU with the newest Bios.
While that may or may not be the answer think about this;
This guys calls up a car mechanic and asks if he can help him with his car. The guys tells the mechanic that it makes a noise when the engine is turned on.
The Mechanic replies that he would like to know what type of car this is and if he can describe the noise.
The customer says, It's a red car and it growls.
The Mechanic replies that it would cost aboy $50,000 to fix.
The Customer is floored as he does not understand.
The Mechanic replies that without further info the best he can do is to replace the entire car.
Granted that is kind of a stupid story but rememer that we don't have a crystal ball. The symptoms you describe with out us knowing more could be a few different things but trying to give an appropriate answer is difficult to pinpoint better without good info. It could be the RAM, the PSU, the Bios or maybe a setting. It may even be something stupid like the RAM socket combo your using. LMAO Yes that can also lead to this kind of thing happening as it did for me when I first got mine setup. I also had stability issues until I changed from sockets 1 and 2 to 1 and 3.
Ao you can see there is no single answer that will fit. I could care less about what hardware you run nor can anyone else here other than to help you. So go ahead and be stubborn about helping us help you. It's your rig that needs help not ours.

Similar Messages

  • MSI K8T Neo FIS2R - Memory problem???

    I have bought myself a second stick of ram for my computer, being careful to make sure it was exactly the same brand and model.
    In spite of this I now get random bluescreen errors of varying types, the first was PFN_LIST_CORRUPT and the latest:
    PAGE_FAULT_IN_NON_PAGED_AREA
    STOP: 0x00000050 (0xC5AD0D7C, 0x0000000, 0x8050298A, 0x0000000)
    Is the new ram incompatible?? this makes no sense though.....   ???

    I have tried switching ram sticks around but no luck there
    Got three BSOD's yesterday, no specific error just STOP: blah blah blah when trying to burn a CD and then after that just when using IE.....
    ........and then I played call of duty 2 for 3hours without a single problem 
    Today when trying to run FS2 open I got two IRQL_NOT_LESS_OR_EQUAL errors (with no driver mentioned)
    Anyway, I have been doing some research on socket 754 athlon 64's, and I found some interesting info from AMD:
    Where MSI says that the board supports that config at DDR400. so the board supports it but the CPU doesn't! what is the point of that??
    I tried running at DDR333 but the CPU stuck at 1.8GHZ (150FSBx12) according to everest 
    Is it possible at all to run two sticks of Double sided ram at DDR400? surely someone has done it and has it working....
    Another thing, after the first IRQL error my computer hung at detecting the CD-RW drive and I had to turn off and on again  ???

  • MSI K8T NEO-FIS2R: RAM problems

    I have the motherboard K8T NEO-FIS2R with AMIBIOS 2VMS V2.0 010505.
    I tried these DDR-RAM:
    DDR-RAM 512MB PC400 CL3 Kingston KVR400X64C3A/512
    DDR-RAM 512MB PC400 CL3 Samsung
    but the motherboard recognizes only 256 MB for both. The RAM are good: I tried them in an other pc!
    Now I have installed an A-DATA ram 256 MB and the motherboard recognizes 256 MB!
    Do you think that my motherboard is defective?
    Thank you in advance.
    P.S. I'm sorry for my bad english.
     

    No the memory controller is onboard the CPU so in any case the MB is not defective. However the CPU revision may hold you back on some RAM especially if you mix make and model RAM on the same channel. A socket 754 CPU only has one channel so all RAM must be matched to work properly.
    If those Sticks can only be seen as a wrong value when used by themselves it is likely that either they have errors or the timings in Bios are improperly set to azllow them to work. In this case you can normally find out what is going on by running memtest86. If you get errors on test 5 or 7 then you have timgs timed improperly and any other errors would show bad RAM.
    Another case is not having enough power for everything to work properly together. Usually this happens when you don't have enough 12v amps for these newer rigs.
    Post complete specs and test results and maybe we can help you further.

  • K8t neo fis2r framerate problem

    i have an athlon 64 3400+, msi k8t neo fis2r, 120 gb seagate barracuda, corsair xms series pc3200 512MB ram(with black heatspreader), gainward geforce fx5700ultra, 500w allied power supply.  I'm having terrible framerate problems when i'm playing games.  It doesn't matter what game i'm playing...i've been playing unreal tournament as a tester game.  At first I thought i had a bad video card so i sent that back.  I'm still having the same problem.  I've flashed my bios, sp1a, all the newest chipset drivers, set my RAM timings, newest video card drivers (53.03), everything.  I don't know what is going on.  My games run at the same frame rate at 640x480 then when they are on 1024x768.  When I turn vsynch on, i'd say about half or maybe more of the time i'd have bad frame rate, when I turn vsynch off my games play reallllly fast.  It seems to jump in and out of normal rate of play.  I was talking to my friend and he thought it was the timing chip on my motherboard.  I'm on my last straw and i'm about to send this board back for a replacement.

    I dont know what you mean by am i letting windows install it...but i'm using live update to download it then it automatically installs itself.  I'll try that uninstall the agp thing on the 4 in 1 but I doubt it'll do anything seeing as how i've probably reinstalled windows 4 or 5 times and installed the 4 in 1 drivers each time to no avail.  I really think my mobo's agp slot is bad or something on my mobo is bad.  I was using a 300W psu for awhile, that might have done something to the board.

  • K8T Neo-FIS2R Old Problem, New Issue

    I made my system back in 2003 using a K8T Neo-FIS2R motherboard and a Barracuda 7200 SATA 160GB drive (ST3160023AS). If you don't remember, back then motherboards that supported SATA drives for main drives, sometimes needed extra drivers in order for the windows installation process to work. At first this threw me, but since then I have reformatted my drive a few times using the same disk with no issues.
    5 years of file sharing can do a number on your harddrives, and it seems my Barracuda has finally died. It came time to replace my drive with a Western Digital Caviar 320GB drive SE16 (WD3200AAKS). I did not predict there would be any issue with replacing my SATA drive. I have another 500GB drive connected to my system used for only storage and the computer recognized it at once.
    So I formatted my WD HD, to NTFS and made it active. Then I installed it in my computer disconnecting my other 500GB drive. I ran windows installation with my Windows CD (which I have used many times and I keep it in pristine condition).
    I found that after I hit F6, and it gave me a selection of SATA drivers to use (used xp), it did not not see that drive was there when asking which drive to format (I repeated this many times).  I set about making a new SATA boot disk thinking that my pre-used one had gone bad.
    http://global.msi.com.tw/index.php?func=downloaddetail&type=driver&maincat_no=1&prod_no=565
    VIA VT8237(R) SATA RAID Driver (For floppy driver)
    I followed the disk directions having already done it before. When I tried to install with my new drivers, I got this error.
    "File\I386\NT5\viamraid.sys caused an unexpected error (4096) at line 2108 in d:\xpclient\base\boot\setup\oemdisk.c."
    Now i KNOW my windows instillation CD is good, but just in case I used another windows CD and got the same error.
    The only idea I can come up with is that I upgraded the bios to much and now it is having issues. My bios version is:
    AMIBIOS A6702VMS V2.2 030405
    SATA378 TX2plus(tm) Bios Version 1.00.103026
    Does anyone have any ideas of what I can try? I have done all the easy stuff I could think off like try different cables, and plug in my SATA to the second sata port and not the first. I have run out of ideas.
    The only list thing I could try was connecting my sata drive to the computer using a SATA to USB adapter, and finding the partition in windows through that way. For some weird reason windows will see USBs in the computer but not installed Sata drives. I am thinking I will install windows using the USB device and then try plugging in the drive directly. I have no idea if it will work.
    Any help would be greatly appreciated.
    Sombrenote

    Quote from: sombernote on 11-July-08, 09:15:36
    Thank you so much for your help.
    I tried your two versions of your drivers, "VIA PIDE&SATA RAID.rar" "Promise 20378 S-ATA RAID.rar" neither of them worked well (I selected the "VIA RAID Controller(Windows XP"). I received a slightly different version of the last error "File\I386\NT5\viamraid.sys caused an unexpected error (4096) at line 2108 in d:\xpclient\base\boot\setup\oemdisk.c."
    The (4096) was a different number.
    I had used 4 different (yet old) disks, trying to get it to work. None of them did so until i tried it once more. This last time worked, it saw and used the drivers. I was able to get into the disk selection screen, and set to format the disk. As it started formatting (Quick), windows said that there was something wrong with the "Disk or CD". It then asked for me to install the SATA combo drivers. I let it detect the drivers I was using, and it kept saying something was wrong. I tried it 3 more times, and the last time it held and copied the files from the CD, to start windows.
    It is obvious to me that I have either a bad disk, CD, Disk drive, or CD drive. This is quite possiblly my last format before I make my new computer. Thank you very much for your help. I would have had to start my voodoo magic tricks to get it to work.
    Crappy floppy cause that
    Happend to me many times as well, when you receive the error take out diskette and re-insert it, then load drivers again until works.
    Of course simple solution is just replace the floppy drive to avoid "voodoo magic tricks"
    Or best solution do a slipstream XP installation and integrate the drivers which you need in XP installation.
    >>> Slipstreaming Windows XP Service Pack 2 and Create Bootable CD<<<
    >>> Slipstreamed Windows XP CD Using SP2<<<
    "Thank you very much for your help. I would have had to start my voodoo magic tricks to get it to work."
    You are done well

  • K8T800 K8T NEO-FSR Memory Problems

    Just a warning before I start in, this is a pretty long post. I'm going to try to include all the information I can.
    Here's my system right now. It's running Windows XP Professional with all the latest updates.
    Processor: AMD Athlon 64 3000, 512KB L2 Cache 64-bit Processor. Not overclocked at all.
    Motherboard: MSI K8T800 K8T NEO-FSR, latest BIOS updates from MSI
    Video Card: ATI RADEON 9800PRO Video Card, 128MB DDR, latest Catalyst drivers from ATI installed. Not overclocked at all.
    Memory: Mushkin 184 Pin 2x512MB DDR400 PC-3200, running at DDR400 with Auto selected for all the memory timings in the BIOS. Memory placed in DIMM#1 and DIMM#2. Not overclocked at all.
    Hard Drive: Western Digital 80 Gig
    I started experiencing random reboots and critical errors in game applications on Sunday. The computer would randomly reboot at random intervals from Windows. In addition, while running games like Warcraft 3, Asheron's Call, or World of Warcraft I would receive frequent critical errors that certain sections of the memory could not either be read or written to.
    I figured that there was some kind of problem with the memory, so I downloaded Memtest86 and ran it. The first stick of RAM was in DIMM#1 and the second stick in DIMM#2. This was the memory configuration during all the random reboots and critical errors.
    Memtest86 came up with several failures during the 5th phase of the test. The same failures came up upon repeated testing in the same phase of the test. I decided to try to isolate the failure and see if one stick or the other was defective. I yanked out the second stick from DIMM#2 and left the first stick in DIMM#1. The first stick (which I'll refer to as the "good RAM stick") passed the memtest repeatedly. I then stuck the second RAM stick into DIMM#1 alone and the computer would not even POST.
    I then moved the second RAM stick (which I'll refer to as the "bad RAM stick") over to DIMM#2 alone and managed to get it to POST. The bad stick failed the memtest with the exact same errors during the same phase of testing as the combined sticks had failed during the initial test. For the sake of completeness, I moved the bad stick over to DIMM#1 alone and finally managed to get it to POST. However, the bad stick passed the memtest repeatedly. Puzzled, I moved the bad stick over to DIMM#3 alone and tested it there, which it also passed repeatedly. I moved it back into DIMM#2 alone and it failed the test repeatedly again and again.
    Intrigued, I then moved the good RAM stick into DIMM#2 alone, to try to see if perhaps there was some kind of motherboard error occurring. The good stick passed the memtest repeatedly in DIMM#2. I then moved the good stick into DIMM#3 alone and it passed the test repeatedly in that slot.
    After checking the motherboard manual to make sure I could do it, I put the bad stick in DIMM#1 and the good stick in DIMM#3 and ran the memtest. The combined sticks passed the test where previously, while configured in DIMM#1 and DIMM#2, they had failed it. I moved the sticks back into DIMM#1 and DIMM#2 to test again. The combined sticks failed as they had during the initial test.
    I then reconfigured the sticks to DIMM#1 and DIMM#3 again and booted up the system. Although I only had limited testing time last night, I seemed to be totally stable. The system did not reboot at all and I actually managed to play WoW for an hour without a single crash.
    Any suggestions on what's occuring? I figured that maybe the mobo's memory seating in DIMM#2 was messed up, but I wanted to get some more guidance from others.

    Well if it's an Antec Sl-350, that one only has 16A @ 12V, way too little to handle your system.....
    I would get another PSU in any case, as even the TP-380 is bare minimum.....
    Go for the Enermax 465 it has 33A @ 12V and then you are sure it's not a power problem...
    Also, a good PSU is never a waiste of money

  • AMD64 3200 + MSI K8T Neo FISR2 memory problem

    I've had one KVR400X64C25/512 and it have worked like a charm. Now I've bought another one (total 1gb).
    When I've inserted it and start the computer I only get the CoreCell logo scren, it do not boot correctly.
    AMIBIOS is version 3.21a
    I've tried the following:
    * run only the new memory [works]
    * run only the old memory [works]
    * DIMM1 + DIMM3 [only CoreCell screen]
    * DIMM1 + DIMM2 [only CoreCell screen]
    * DIMM2 + DIMM3 [only a black screen]
    what should I do?

    Quote from: Tiresmoke on 22-August-05, 21:48:12
    A PSU is rated to run at +/-5% and that is well within it's rating. As for wether ists big enough there is no way we can say as you still did not give full system specs.
    If it won't run with the third stick of RAM then pull it out for the moment and see if the system will boot again. If it does then during post you will see a Bios version listed. That board only supports Bios versions to 2.2 at the moment so please also list what actuall Bios version you have.
    Ok, have booted with one instead of two sticks (one works, two don't, do not have three sticks)..
    AMIBIOS A6702VMS v2.2 released 030405. The autodetect settings (at startup): Clock = 400Mhz, CAS 2.5 which seems correct.
    More info:
    AMD64 3200
    MSI K8T Neo FISR2
    AMIBIOS A6702VMS v2.2
    Seagate 120GB SATA (no ides)
    CD rw + DVD-r combo drive
    floppy drive
    Saphire GF6800 (no GT or Ultra)
    Creative Audigy 2 Platinum Ex
    that's whats running in it

  • MSI K8T NEO-FIS2R Sound Problem

    Why does the sound cut out after a period of about 5 hrs or more it completely stops in windows XP havent tryed any other OS,  i keep having to restart the computer to bring the sound back!
    Any help on this would be greatly Appreciated

    Quote
    Originally posted by joshr45
    Why does the sound cut out after a period of about 5 hrs or more it completely stops in windows XP havent tryed any other OS,  i keep having to restart the computer to bring the sound back!
    Any help on this would be greatly Appreciated
    Do you have LiveUpdate installed (or whatever it is called)? When I was using the onboard sound (moved to an Audigy2 ZS) the sound would go once Live Update had searched the web for available BIOS/Driver updates.  I only had mine set weekly but sods law meant that I ended up with no sound for a Rugby World cup I had recorded on my AIW pro (aaaarrgghh). It would only come back with a reboot.
    Alex

  • K8T Neo-FIS2R - 3200+ - Mushkin Level 1 RAM: Optimal Memory Settings

    Just got a K8T Neo-FIS2R with a AMD Athlon 64 3200+ with 1g (512MB X
    2) Mushkin Level 1 PC3500 RAM as recommended by Anandtech on his High
    End System roundup:
    www.anandtech.com/guides/showdoc.html?i=2041
    I am having a HUGE problems with memory settings in the BIOS.
    On AUTO, the memory is only autodected at DDR200, which I found odd.
    I them took memory setting in my old hands and things don't seem much
    better:
    I made these changes:
    MEMCLOCK: DDR400
    BANK INTERVEAVING: AUTO
    BURST LENGTH: 8 BEAT
    CL: 2
    TRCD: 3
    TRAS: 5
    TRP: 2
    This was unstable at first and  bumped the DDR Voltage to 2.7, moved
    the sticks to DIMM1 and DIMM3 (instead of DIMM2), and it seems stable,
    but not very fast. according to Sandra Scores
    Any recommendations for Memory Settings?   Why would the MB not
    autodecte DDR400 RAM?  I am not looking to overlock...just maximize
    the CPU and memory I have.
    Maybe I just need to get new memory.  What is the best memory for this motherboard?
    Thanks,
    Steve

    I'm running the same mem (see my sig).  Since its PC3500 I attempted to tighten the settings to those you had listed (2,3,2,5).  It was not Prime95 torture test stable at even the stock 200 MHz FSB using these settings.  Upping the voltage to 2.7 did not increase the stability in my system at these settings.  The memory ran perfectly at AUTO settings, but was clocked at 2.5,3,3,8 I believe.
    Keep in mind that level 1 is advertised at 2,3,3.  My system is 100% stable at 2.7V for me up to 210 MHz FSB at these settings (I haven't tried any faster).  My TRAS is set to 6.
    Hope this helps a fellow Mushkin user  

  • Help! XP install problems with K8T Neo-FIS2R

    The other day I put together a new system for a friend.  I got the system to POST properly, the diagnostic lights on the D bracket are fine, and I can edit the BIOS, and the BIOS sees all the drives properly.  
    However, installing XP Pro has been impossible.  I set the system to boot first to the CD, then to the hard drive (from the BIOS).  After booting to the CD, I never see the message I am used to seeing ("Press any key to boot from CD...) when booting from the XP Pro install disk.  The system thinks about things for a long time with a blank screen, then later it finally begins to do the install.  Things appear normal at this point as in any other time I have installed XP Pro.  I reformat the hard drive to start clean and then the XP install files are copied over.  I get the standard message that the system will reboot and this is where things get flaky.  The system reboots, but I never get the message once again on whether or not to boot from the CD.  So after a while the system tries to install XP once again (it would repeat this process forever....trust me).  I've popped the CD out right after the system reboots so it will try to go to the hard drive.  I just get some kind of boot failure message and to insert the bootable media or whatever.  I've even gone into the BIOS right after the reboot to switch the BIOS loading to try and load the hard drive first.  This still doesn't give me the desired results.
    This is by far the weirdest thing I've ever experienced when doing an install.  I've installed XP Pro on at least 15-20 desktops/laptops of different configs and never ran into this before.
    The BIOS settings are stock.  I didn't see anything in there that was really needed tweaking or that hadn't "set itself".  I haven't messed with the SATA or RAID stuff since it's not really necessary in this situation.
    Here are the system specs:
    --Antec 430 True Power PSU
    --K8T Neo-FIS2R mobo
    --AMD 3000+ 64 bit CPU
    --40GB Maxtor HD (master on IDE1)
    --Lite-On DVD-ROM drive (slave on IDE1)
    --80GB Western Digital (8MB buffer) (master on IDE2)
    --Sony DRU510A DVD-RW (slave on IDE2)
    --(2) Kingmax 184 Pin 512MB DDR PC-3200 Model# MPXC22D-38  
    --ATI 9800 Pro
    --3.5 Floppy
    All the components except the mobo, CPU, and memory are from another AMD system that was running fine.  No problems with any of the HD's or the optical drives.  All new components were purchased from newegg.
    I thought that maybe I had a problem with the jumpering of the drives so I messed with those in about every possible combination.  I took IDE2 completely out of the system and just tried to get it running with the 40GB Maxtor and the Lite-On drive.  I tried about every master/slave/cable select combination but nothing was working.  In certain combinations the BIOS recognized everything as I intended.  I've pulled everything off that doesn't need to be connected.  Keyboard, monitor, and internal components are the only things connected.
    I don't consider myself to be a guru at this business, but I can get through most things with enough trial and error.  This really has me stumped.
    Any help is certainly appreciated.
    Thanks,
    Heath

    Quote
    Originally posted by chasmon
    Hi all,
    I have just setup up a brand new system but am having probelms getting it working. I want to install XP on a single Maxtor 160Gb drive.
    I have my HD on Promise Ser1 and all SATA stuff in BIOS enabled. When I get to the screen I press F6 and then when promted I insert the floppy with the promise drivers on. I then get this message:
    "File txtsetup.oem caused an unexpected error (4096) at line 1742 in d:\xpclient\base\boot\setup\oemdisk.c"
    I can't get past this screen I have tried:
    1.Drivers from the CD supplied.
    2.Drivers from the MSI website.
    Please help me this lot cost lots of hard earned I'm pretty gutted at the moment.
    System:
    Antec 380W PSU and Sonata Case
    LG DVDROM 8163B
    NEC DVDR/RW 2500B
    Panasonic Floppy
    Neo FIS2R mobo
    Maxtor Diamondmax Plus 9 160Gb SATA150
    Benq RF K/B & Mouse
    Download the drivers from MSI again, and when you copy the contents of the XP folder to floppy ADD the file txtsetup.oem from the directory above that folder. Worked for me..!
    Ian

  • Msi k8t neo fis2r problems part 3

    sometimes when the computer is turned on it just turns the fans and leds on but doesnt boot up...
    most of the time it loads up and i boot to the windows xp cd and i install the drivers for sata and then when it reaches the point of copying the files it will give me a bsod and say that there is a problem with the irql driver and then force me to shut the pc down..
    sometimes it makes it past that and will begin to copy files onto the hard drive, like somehow the data is becoming corrupted..however it will start to say that the files cant copy randomly and it will allow me to retry..they will copy the 2nd time usually..i can keep hitting retry and it will usually go by..it gets to 30 something % and then crashes to bsod just giving me some random error..for some reason the files keep screwing up that go on the sata drive....I just replaced the old power supply that wasnt working with an antec true watt 430 watt power supply, so i know it isnt that..
    i just cant figure out what the heck is going on..any help would be appreciated.my specs are
    "IRQ NOT EQUAL OR LESS"
    athlon 64 3000+ cpu
    msi k8t neo fis2r motherboard
    mushkin special cas 2.0 2-2-2-5 512 mb pc 3200
    western digital 8mb cache 80 gb sata hard drive
    sapphire radeon 9800 pro 128 mb 8x agp

    fyi look an your cd sticker ity will show power, consumption, but they are way lower than you would think, hard drives,can be only 10 watts, less then some case lights , and fans, cd are  similar.. your video, is the biggy somewhere between 90~150 watts..yikes .next to the cpu..and the mobo can use 50 or so (not sure about new mobos)  not to mention the ram 1024 is @40 watts or so., dont forget about 25watts per pci card, not counting the sound card which can be double....
    ergo the need for a big psu..
    the combined total ratting on a psu is not the max number that the psu is rated, that is surge value.. so a 500 may only hold 400 sustained , and that will drop as the machine heats up, so in the end your 500 may onlyy pull 366 @50'c...

  • Problems with OC in MSI K8T Neo FIS2R!!!

    Hi!
    I have faced problems when making OC in my Athlon 64 3400+. I do not obtain to increase the FSB for 213Mhz more than without that they occur stopped or reset. I am using 1Gb (2x512) of Ram (Corsair CMX 3200LL PRO).
    In the internet many stories exist that chip VIA K8T800 is not good for OC, because the AGP/PCI cannot be stopped with fixed values.
    Exists some form to obtain with stability in this Mobo one overclock descent, with FSB of at least 220Mhz? The lack of stability in overclock limits the processor very, what it finishes in forcing to who knows to abandon the K8T Neo, passing to a Mobo that uses Nforce3 250, for example.
    If somebody will be able to help with tips to try one overclock for FSB in 220mhz with stability would be very grateful, friends!
    my system
    Athlon 64 3400+ (cooler venus 12)
    MSI K8T Neo FIS2R
    1Gb Ram (512x2) Corsair CMX 3200LL PRO
    ATI Radeon 9800XT 256Mb
    120Gb SATA Maxtor 8mb buffer
    Audigy 2
    420W Thermaltalke
    Case Lanfire Thermaltalke
    Monitor LG Flatron 17 700P
    CD/RW+DVD
    LAN (adsl 400k) + Fax Moden (56k)

    Take your sata drive off and you can overclock higher. There is no PCI/AGP lock so the speeds are affecting your sata drive. 210 mhz. system clock is about the limit before the sata drives start to act up.
    The problem is with that particular VIA chipset. No way around it has been found to work in a practical manner.

  • Problem after CMOS reset K8T NEO FIS2R

    Hi,
    After messing around with my memory timings, I could no longer boot my system, so I decided to reset my CMOS using the jumper.  After doing so, my system gets stuck at the SATA drives not detected BIOS not installed screen, and I can no longer access the BIOS.  I'm fairly sure that the BIOS not installed message is in reerence to the SATA controller and not the main BIOS itself.  I have tried reseting the BIOS a couple of more times with no different results.  My D-Bracket reads red LED in location 1, green LEDS in 2, 3 and 4.  
    System:
    Athlon 64 3000+
    K8T NEO FIS2R
    Radeon 9700 pro
    Audigy 2 ZS
    400W PSU
    Any ideas would be welcome.
    Thanks

    Hi
    Try removing the Ram sticks when resetting Bios, remeber to earth yourself first, also remove power cable, and leave for a couple of minse, to allow all chips to discharge, then replace mem sticks, the cmos jumper and the power cable. Try to get into bios at start to reset the timings you have changed.  If still having a prob, use Ctrl + Home as you boot, holding them down will initialise the bios. You will have to reset the bios settings.
    Failing that you will need to use a recovery floppy.
    Good luck
    jocko

  • K8T Neo - FIS2R (model 6702) SATA and RAID Problems = Hair Loss

    Hi All,
    new to the forum, have searched but nothing like my problem exist.
    I have a K8T Neo FIS2R M/B and trying to get a single SATA HDD working for my secondary drive. primary is a IDE which works well and I want to leave it.
    I have plugged in the SATA HDD into the SER 1 port ( Promise 237 ?)  anyhow the bois at startup or post recognises the drive, but then says soemthing like you have set up raid before F1 for setup F2 to continue to boot.
    I have pressed both f1 and F2 at various time, but it appears that it want to turn the single drive into a RAID system, which is not possible with one drive !!....
    Anyhow windows XP then boots up and loads a RAID driver and also the promise RAID drivers.  the real problem is that XP sits and waits for the raid which never comes and during startup on XP. it is extremely slow.
    Does anyone have any ideas. I am not that computer techy as you can see by the description, but it appears that I cannot get into the RAID bios to turn it off.. I have zapped the bios to try and reset it. basically i am loosing my hair ove this.
    if anyone had some step by step instructions how to prevent raid from switching on at the bios and then in XP it would be greatly appreciated
    Jeff

    Hi All,
    Sorry for the slow reply, retrieving the box from the bottom of the swimming pool !!!
    I set it to SATA as you have indicated Hans, I did check that setting. Thankyou for checking.
    Spray, I have tried the P20378 setting as well. You indicate that you need to press F6 when installing the OS. I have WinXP running already on an IDE master and am trying to set the SATA up as a secondary disk drive.
    As I indicated above, the machine runs slowly to the point of it being a 486 when I use either promise or Via controllers.
    I have since removed the drive and are now having problems with XP on boot up/startup. The thing seems to hang or go slowly when the horizontal bar runs across under the Windows XP logo. I have turned everything off in the bios both Promise and Via.  I am at a loss as to why:
    1 it runs slowly with the SATA drive in ( also does not show all the auto loading icons near the clock)
    2. why it hangs when I remove it and turn both SATA controllers off in the bios.
    I have a feeling that I may have corrupted part of the registry playing around. Any thoughts... going bald :-)
    I really appreciate the feedback so far

  • K8T Neo-FIS2R and 2.2 bios problem

    I flashed the bios of my K8T Neo-FIS2R to version 2.2.
    Everytime I boot the system, I can just see the Windows XP logo appearing for a second, then the system reboots again.
    I reflashed from a floppy to version 2.1 again, but still the same problem.
    My HDD is a Western Digital SATA drive on the VIA controller.
    Can somebody please help me out?
    THX!
    Marco

    Thanks for your support!
    After reflashing to 2.0 I still had the same problem.
    The bios was not causing the problem. In some way, Windows couldn't load the SATA driver properly, I think.
    I removed the SATA HDD from the VIA controller and connected it to the Promise controller, and surprisingly, Windows started again.
    The HDD LED works on the Promise, but not on the VIA, so I left the HDD on the Promise controller. The LED problem is now solved as well.
    I still don't know exactly what was going on. Anyway, it wasn't MSI or the new bios, it was Microsoft...
    Marco

Maybe you are looking for

  • Can't download plug in for windows media player. Have used download site and it says it worked, but plug in is not showing up on my list of plug ins.

    I tried to hear a conference call on a website. Got a message, needed windows media plug in. Checked my plug ins, no windows media. Read tutorial on firefox support. Clicked on download. Got a window that asked for repair or change. Tried repair, the

  • Invalid signature so update to 11.01 wont load

    When I try to update to Itunes 11.01 Iget a reply "Files shared by these updates " has an invalid signature. It will not be installed. I am trying to update from 10.6.3.25 to 11.0 but the files refuses to go past initial download. Any one know what I

  • Position search event subscribe

    Hi all. Note 1112733 specifies the namespace and event of the employee search iView for subscription by custom iViews. Event namespace: urn:com.sap.mss.employeesearch Event name: selection_changed I am looking for something similar to subsribe to the

  • Merging data without MobileMe

    I have a MacBook, an iMac and a iPhone 3Gs. Currently, I use MobileMe to sync my calendars and contacts over all three devices, but it's time to renew and frankly, it's a bit above my budget. I know that if I want to merge things that I've entered in

  • Library window blanked out after V4

    "Library" window (previously "Organize favorites") is blanked out, although at least a folder "Imported from IE" is present in the Favorites menu. Also, in the "File" menu only "import" option is presented (and not import/export). This happened after