K8N SLI Platinum random boot behavior

Been almost 5 years since I've fooled around with my old Athlon sys which has been passed on to my younger bro to put it to a good use, and about 4 years since i last posted here 
Unfortunately I got a call yesterday to check the comp, since apparently it's not booting up.
I cannot for the life of me figure our what's the deal with it since I cannot reproduce the same issue and I have limited replacement hardware for testing each part.
Now onto the symptoms:
- when the system posts, at the part where the IDE devices are listed, the post stops after the last device is displayed. no irq/dmi table afterwards, no OS boot.
When I looked closely, the HDD names (or manufacturer codes) that are listed in the IDE device list, were wrong. The post lists them as WD140s while both of them are WD160s. Sometimes when the system hangs up, a different HDD name is displayed at post. Whenever the HDD names are displayed correctly, the system boots without any issues.
What I have tried till now:
- tested both HDDs in an external enclosure on another computer, they both work OK.
- I have changed the IDE cable, same results as before: sometimes works sometimes doesn't
- RAM is OK
- CPU is OK
- GPU is OK
- i have tried with different combinations of HDDs and DVD attached, same random post
- the only time the system post consistently is when no HDD, but only the DVD-writer is attached
Hit me with ideas guys.

Okey, down to basics, but I'm too lazy to type myself.
This is POST (Power On Self Test):
The first thing that the BIOS does when it boots the PC is to perform what is called the Power-On Self-Test, or POST for short. The POST is a built-in diagnostic program that checks your hardware to ensure that everything is present and functioning properly, before the BIOS begins the actual boot. It later continues with additional tests (such as the memory test that you see printed on the screen) as the boot process is proceeding.
The POST runs very quickly, and you will normally not even noticed that it is happening--unless it finds a problem (amazing how many things are like that, isn't it?) You may have encountered a PC that, when turned on, made beeping sounds and then stopped without booting up. That is the POST telling you something is wrong with the machine. The speaker is used because this test happens so early on, that the video isn't even activated yet! These beep patterns can be used to diagnose many hardware problems with your PC. The exact patterns depend on the maker of the BIOS; the most common are Award and AMI BIOSes. This part of the Troubleshooting Expert will help you figure out what the POST beep codes mean and what to do about them, if you are having this problem.
Note: Some POST errors are considered "fatal" while others are not. A fatal error means that it will halt the boot process immediately (an example would be if no system memory at all is found). In fact, most POST boot errors are fatal, since the POST is testing vital system components.
Many people don't realize that the POST also uses extended troubleshooting codes that you can use to get much more detail on what problem a troublesome PC is having. You can purchase a special debugging card that goes into an ISA slot and accepts the debugging codes that the BIOS sends to a special I/O address, usually 80h. The card displays these codes and this lets you see where the POST stops, if it finds a problem. These cards are obviously only for the serious PC repairperson or someone who does a lot of work on systems.
This is the complete Boot sequence, including POST:
The internal power supply turns on and initializes. The power supply takes some time until it can generate reliable power for the rest of the computer, and having it turn on prematurely could potentially lead to damage. Therefore, the chipset will generate a reset signal to the processor (the same as if you held the reset button down for a while on your case) until it receives the Power Good signal from the power supply.
When the reset button is released, the processor will be ready to start executing. When the processor first starts up, it is suffering from amnesia; there is nothing at all in the memory to execute. Of course processor makers know this will happen, so they pre-program the processor to always look at the same place in the system BIOS ROM for the start of the BIOS boot program. This is normally location FFFF0h, right at the end of the system memory. They put it there so that the size of the ROM can be changed without creating compatibility problems. Since there are only 16 bytes left from there to the end of conventional memory, this location just contains a "jump" instruction telling the processor where to go to find the real BIOS startup program.
The BIOS performs the power-on self test (POST). If there are any fatal errors, the boot process stops. POST beep codes can be found in this area of the Troubleshooting Expert.
The BIOS looks for the video card. In particular, it looks for the video card's built in BIOS program and runs it. This BIOS is normally found at location C000h in memory. The system BIOS executes the video card BIOS, which initializes the video card. Most modern cards will display information on the screen about the video card. (This is why on a modern PC you usually see something on the screen about the video card before you see the messages from the system BIOS itself).
The BIOS then looks for other devices' ROMs to see if any of them have BIOSes. Normally, the IDE/ATA hard disk BIOS will be found at C8000h and executed. If any other device BIOSes are found, they are executed as well.
The BIOS displays its startup screen.
The BIOS does more tests on the system, including the memory count-up test which you see on the screen. The BIOS will generally display a text error message on the screen if it encounters an error at this point; these error messages and their explanations can be found in this part of the Troubleshooting Expert.
The BIOS performs a "system inventory" of sorts, doing more tests to determine what sort of hardware is in the system. Modern BIOSes have many automatic settings and will determine memory timing (for example) based on what kind of memory it finds. Many BIOSes can also dynamically set hard drive parameters and access modes, and will determine these at roughly this time. Some will display a message on the screen for each drive they detect and configure this way. The BIOS will also now search for and label logical devices (COM and LPT ports).
If the BIOS supports the Plug and Play standard, it will detect and configure Plug and Play devices at this time and display a message on the screen for each one it finds. See here for more details on how PnP detects devices and assigns resources.
The BIOS will display a summary screen about your system's configuration. Checking this page of data can be helpful in diagnosing setup problems, although it can be hard to see because sometimes it flashes on the screen very quickly before scrolling off the top.
The BIOS begins the search for a drive to boot from. Most modern BIOSes contain a setting that controls if the system should first try to boot from the floppy disk (A:) or first try the hard disk (C:). Some BIOSes will even let you boot from your CD-ROM drive or other devices, depending on the boot sequence BIOS setting.
Having identified its target boot drive, the BIOS looks for boot information to start the operating system boot process. If it is searching a hard disk, it looks for a master boot record at cylinder 0, head 0, sector 1 (the first sector on the disk); if it is searching a floppy disk, it looks at the same address on the floppy disk for a volume boot sector.
If it finds what it is looking for, the BIOS starts the process of booting the operating system, using the information in the boot sector. At this point, the code in the boot sector takes over from the BIOS. The DOS boot process is described in detail here. If the first device that the system tries (floppy, hard disk, etc.) is not found, the BIOS will then try the next device in the boot sequence, and continue until it finds a bootable device.
If no boot device at all can be found, the system will normally display an error message and then freeze up the system. What the error message is depends entirely on the BIOS, and can be anything from the rather clear "No boot device available" to the very cryptic "NO ROM BASIC - SYSTEM HALTED". This will also happen if you have a bootable hard disk partition but forget to set it active.
This process is called a "cold boot" (since the machine was off, or cold, when it started). A "warm boot" is the same thing except it occurs when the machine is rebooted using {Ctrl}+{Alt}+{Delete} or similar. In this case the POST is skipped and the boot process continues roughly at step 8 above.
http://www.pcguide.com/ref/mbsys/bios/bootSequence-c.html

Similar Messages

  • MSI K8N SLI Platinum N4 Boot

    Hi all,
    I'm experiencing a strange problem sometimes.
    My system does not post and I get all 4 leds lit. Usually it means bad processor, but if I reset it, the ystem boots normally.
    I'm using BIOS 3.7 but It has happened with 3.6 as well.
    I let Memtest run for 8 hours and no problems were reported.
    What else can it be ?

    had same problem with 3.6. try 3.5 at the korean site, worked for me

  • K8N SLi Platinum USB keyboard boot issues

    Hello, I have a K8N SLi Platinum connected via an Aten US221 USB switch (http://www.aten-usa.com/?product&cat=804&Item=US221) and a Kensington USB hub to a Logitech MX518 mouse and a Logitech multimedia pro keyboard. I use this to connect the same two input devices to two computers and toggle. Previously I used a keyboard to each, with a Dell PS/2 used on the MSI motherboard.
    The problem is that the MSI motherboard fails to detect the keyboard every other boot or so. It doesn't matter if I unplug the Aten switch, the USB hub or even connect it directly to the USB root hub. The only thing that solves it to restart the MSI computer over and over until it decides to start working. And I need the keyboard since I have a bootloader (GRUB) that I select which OS to boot with. The switch and keyboard works without a hitch on an older Dell computer which is also connected in tandem.
    Since I need both mouse and keyboard on a single wire I cannot use a USB-to-PS/2 connector. I've found several posts here which suggests this motherboard is buggy, if that's the case shouldn't MSI issue some sort of BIOS patch?
    Sincerely, Martin "xarragon" Persson

    Might work.
    I don't like the inconsistency you describe: working sometimes and after a lot of reboots. Would you say your system parts, please. Troubleshooting this in your end must include finding a situation where it never works, and when it always work. For example, if you don't have the mouse connected at all, if you don't use the hub, etc.
    Not saying motherboards can't be damaged, specially port end, but the hub thing is a more likely culprit.

  • K8N SLI Platinum Won't boot...

    Hello!
    Yesterday i got my computer parts, i slowly assemblied it and read all the instructions.
    The parts was:
    MSI K8N SLI Platinum
    AMD Athlon 64 3500+ 2.2GHz Socket 939 (Boxed)
    Asus GeForce 7800GT 256MB GDDR3 2xDVI-I
    Corsair TWINX Xpert 3200C2 DDR 1024MBC
    Tagan 420W PSU(I didn't get any info from the reseller about me needing atleast 450W, but it booted so im happy)
    Samsung SpinPoint P120S 250GB SATA2.
    It booted and i was happy, i installed all drivers from the cds and installed a game and it ran smooth.
    I looked up on nvidia.com and saw that there was a newer driver for my graphics card so i downloaded them and got asked to reboot my computer and so i did.
    But it didnt get any further than the re, since it didn't boot up...
    All the fans are running in the computer, the memory display started and displayed info.
    The screen was dead and by pressing numlock repeatedly on my keyboard i noticed it didn't work either.
    I've tried to change spot on both the SATA disc and the Graphics Card. I've tried to reset cmos by holding the button.
    And now im out of ideas
    Thanks in advance /Hugge

    Quote from: SAB on 17-September-05, 19:44:06
    If you have your D-Bracket connected, what light pattern is it displaying!? Also, recheck your physical SATA connectors, as they have a tendency to back out.
    I had it at first, but when i moved my gfx-card i removed it.. Should i connect it again?
    Edit: Ok now i saw what use it has, i will connect it and i'll be back in a few..

  • K8n SLI Platinum can't get OS to boot

    Linked over from https://forum-en.msi.com/index.php?topic=97317.0
    Greetings - This is linked from the above thread and I was advised to come here to see if anyone could sheed some light on this...
    System is:-
    AMD64 3500+
    1gb of Corsair Low latency 2-2-2-5
    2 barracuda 300gb hard drives
    K8N SLI Platinum mo-bo (now sadly running in single card mode...)
    PSU - Hiper HPU-4S525
    NX6600GT TD128E (Newer version)
    Forceware - Nvidia Version: 84.21.
    Problem is - I have two versions of the 6600GT and the older one will work without a problem - either in SLI or in single card mode but the newer one causes the machine to hang at OS boot - I have tried booting with the card in slot two (running in SLI mode)  with the card in slot 1 (running in non-sli mode) and with the newer card in slot 1 (running in SLI) but still the same result - Is it the card, my PCU or a mo-bo problem?!?!
    Any advice/help Greatly appreciated!

    What motherboard BIOS version are you running? The original?
    A newer version might help: http://www.msi.com.tw/program/support/bios/bos/spt_bos_detail.php?UID=641&kind=1

  • [Resolved] No boot with K8N sli Platinum & AMD 64 X2 3800+

    Hye,
    I've received these new stuff last night (everything is good until here) :
    - Antec Sonata II 450W
    - MB MSI K8N SLI Platinum
    - Proc. AMD 64 X2 3800+
    - GC Sapphire X800 XL 256Mo
    I've assembled all and turned it on... No bip... but all the fans are turning... and the screen says "No signal" and becomes black ( and me    )
    Can someone help me? Please?
    On the MSI site, I also found this :
    http://www.msi.com.tw/program/products/mainboard/mbd/pro_mbd_cpu_support_detail.php?UID=641&kind=1
    Maybe the proc. and the Motherboard are not compatible? Has someone already tried this combinaison (MB+Proc.)?
    My Thanks in advance.

    Quote from: darinn on 12-November-05, 03:22:08
    I will ask the sellers if they can update the Mobo for me.
    But with the last version of the bios, will the mobo accept the dual-core with this proc. AMD 64 X2 3800+?
    And if it's not possible I'll change the mobo.
    Thanks .................................. again.
    Pretty much any SLI motherboard supports the X2 3800. MSI is just really pathetic sometimes. So, I had the Abit AN8 SLI before and their latest BIOS (17) supports all X2 CPUs. But Im sure most other brands support them too.

  • 2nd K8N SLi Platinum motherboard just died

    Hope somebody else has experienced this - now on my 3rd board. A bit about my system:
    Msi K8N SLi Platinum motherboard
    2 x Seagate Barracuda ST3200822AS 200Gb Hard disk
    Antec PSU True Blue 480w
    1 x AMD (Winchester) Athlon 64bit 3200+ CPU
    OCZ Dual Channel Kit 2x512MB DDR400 Ram
    128MB Gigabyte GV NX66T128VP Graphics Card
    Running MCE 2005
    I built my first system running Media Center 2005 a few months back. Very stable. Used to put it into S3 sleep mode each evening and wake up the next day. Never any problems. CPU temp ran about 47degC. Never did anything stressful on it, no games just watched tv with a tuner card and played mp3s.
    One day it wouldn't wake up, wouldn't post, no beeps nothing. cpu fan spun briefly (2 secs) and died. I stripped it down to bare essentials (1 stick ram, cpu). Tested PSU - fine. Tried out of case, again no joy, so I RMAed. Put it down to a bad board.
    So I installed the new board - it worked fine. Must have been a bad board. Great! It ran for another month and the same thing happened, it just would wake up one day! Now I'm worried, am I doing something wrong with these boards, are they getting too hot? How come they fail when they are switched off? Is it a bios thing? - I tried resetting the Cmos, no joy there.
    Any way that I can update the bios when they are in this state?
    Any ideas - cheers Richard

    richardwilshire...here is a list of many potential non-compliant APM features you may want to look at, and note that these are carry-overs from Windows 2000, the foundation of WinXP:
    Key APM Components and What They Do
    APM BIOS: Placed in ROM or flash by the OEM. Does most of the real work of powering the system on and off. The operating system can call the BIOS, and it either works or it doesn't; its operation is opaque to the operating system. The APM BIOS must be turned on using the BIOS setup utility for APM to work. If the APM BIOS is unstable, it may be necessary to turn the APM BIOS off using the BIOS setup utility, in addition to turning off Windows 2000 APM support. The APM BIOS should be configured such that timeouts are either turned off or set for the longest period possible, so that the operating system can control timeouts instead of the APM BIOS.
    Ntdetect.com: It detects whether the APM BIOS is present before booting the operating system, determines whether Windows 2000 can use it, and reports the results of detection in the registry.
    NtLdr: Restarts APM upon resume from hibernate, if APM was active before hibernation.
    Ntapm.sys: A Windows 2000 driver that hooks the system and the APM BIOS together. It includes certain system operations for dispatch to the APM BIOS, and it polls APM BIOS events and status. Note than when the APM BIOS presents an event (such as suspend or power off), Ntapm.sys catches this, and then issues an NtInitiatePowerAction call, which tells the operating system to respond appropriately. At the end, the Windows 2000 power manager calls into the HAL, which calls back into Ntapm.sys, which calls the APM BIOS. In this process, almost all operating system and driver power code is the same between APM and ACPI.
    Hal.dll: Windows 2000 APM support works only with Halx86, which is the only HAL to have the hooks needed to call into Ntapm.sys. It's also the only HAL relevant to important APM machines in the market.
    Apmbatt.sys: This emulates a battery unit so the system battery status code can work.
    Power Applet: The Control Panel applet that allows the user to enable or disable APM support on a computer. This is the only supported way to turn operating system APM support on or off.
    Biosinfo.inf: Windows 2000 file that lists machines on the Autoenable APM list and the Disable APM list, and also lists the BIOS detection sequences used to match them.
    Key Elements in the Registry
    Ntdetect Reporting. The data about APM that is discovered by Ntdetect.com is reported in the registry using a Multi-function adapter (MFA) entry in the system description of the hardware tree. To find this, look in HKEY_LOCAL_MACHINE\ hardware\ description\ system\ multifunctionadapter.
    There will be a set of keys there named 0, 1, 2, 3, etc. Each of them will have value entries named Component Information, Configuration Data, Identifier, and so on. Find the key whose Identifier entry == "APM". The "Configuration Data" entry of that key will contain the data on APM found and reported by Ntdetect.com. If the key is absent, then APM was not found. The contents of this value entry are reported in sdk\inc\ntapmsdk.h.
    Running Apmstat.exe -v will dump this structure, for machines where it's relevant. For machines where it's not relevant (multiprocessors, not x86, not halx86, ACPI is on, and so on), Apmstat.exe will report that.
    Biosinfo vs. Machine-Specific Info. The results of machine-specific detection versus Biosinfo.inf are stored in HKEY_LOCAL_MACHINE\ System\ CurrentControlSet\ Control\ BIOSInfo\ APM. If the "Attributes" value is 1, the machine's APM BIOS is "known good" and the machine is on the Autoenable APM list. If the value 2, the machine's APM BIOS is "known bad" and the machine is on the Disable APM list. Otherwise, the machine is neutral.
    Running apmstat will report whether the APM BIOS is known to be good, known to be bad, or is neutral.
    HAL Reporting. If the HAL is Halx86.dll, the registry key HKEY_LOCAL_MACHINE\ System\ CurrentControlSet\ Control\ ApmLegalHal will have a value entry present with data of 1.
    Running apmstat will report if this is not the case.
    ACPI Reporting. If the machine is an ACPI machine, there will be a services entry for ACPI under (HKLM\System\currentcontrolset\services\ACPI) with value Start == 0. This is telling the system to load and run Acpi.sys at phase 0. If this is not present, the machine is not being run as an ACPI machine, even if, perhaps, it should be.
    Running apmstat will report a machine as an ACPI machine if it sees Acpi.sys has Start == 0.
    UI Elements
    Power Applet APM Tab. The Control Panel includes a Power applet. If the APM is installed at all (enabled or disabled), there will be an APM tab in this applet. You can turn APM on and off by checking the box in this tab. This is the only recommended and supported way to do that. Turning APM on is an on-the-fly Plug and Play action; turning it off requires a reboot. If the tab is absent, it's an ACPI machine, an APM Disabled machine, or the machine simply doesn't have APM.
    Standby on Shutdown Menu. If APM is turned on, there will be a Standby entry under the Shutdown option when the user presses CTRL+ALT+DEL. There may also be a Hibernate entry, which is a separate function. (Hibernate can work even if neither APM nor ACPI are present.) Standby under APM has the same use as under ACPI.
    Battery Status Icon. If the battery display is turned on in the Control Panel Power applet, there will be a Battery Status icon on the system tray, which works about the same as for ACPI. Note that an APM machine always reports a single composite battery, regardless of how many are present or what the machine reports. (Windows 2000 uses the unified/composite number, because this is thought to be more reliable on a wide range of APM BIOSes, and is simpler.)
    Power Button. On most APM machines, the power button, a sleep button, or the like, can suspend the machine (place on standby). Most require the power button to resume, though at least one will come back with a keyboard touch. Windows 2000 APM does not support custom power buttons.
    Tools
    Apmstat.exe: As of Windows 2000 RC1, Apmstat.exe is included in the support directory on the Windows 2000 product CD. Support personnel and expert users can run this utility to determine status.
    BIOS Setup Utility. Essentially all APM machines will have some sort of machine setup/configuration screen, usually accessed at boot by pressing ESC, DEL, F1, F2, or F10. Support personnel and expert users may be able to improve system behavior by changing or disabling APM options.
    Note: Be warned that some APM BIOSes will turn themselves off if all timers are disabled. In this case, it's best to set all timers to some long timeout value.
    APM BIOS and Kernel Debugger. Some APM BIOSes will refuse to suspend if the kernel debugger is active on one of the system COM ports.
    Event log. If an APM_SETPOWER call fails (that is, a standby/suspend fails at the APM BIOS interface), then Ntapm.sys will write a record into the system event log, with data reporting that this happened and whatever error code the APM BIOS returned. This information is sometimes useful if a machine is refusing to suspend because of activity on some port that isn't obvious to the user.
    NOTES:
    • APM support is not allowed on server products. This means that the APM tab will not appear and that there is no APM support in Windows 2000 Advanced Server or in Windows 2000 Datacenter.
    • APM will not hook up the standby vector on machines that do not have batteries. This means that on machines that do not have batteries, standby will not appear as an option on the Shutdown list, and will not be available as an operation.
    • Hibernate is independent of APM or ACPI; hibernate can be used on machines that do not have either APM or ACPI.
    • To get the battery status icon, you must turn it on with the Power applet in the control panel.
    • To get hibernate, you must turn it on with the Power applet in the control panel.
    Suggestions for Problem Resolution
    The following provides guidelines for support personnel or expert users who are troubleshooting APM support on a system running Windows 2000.
    1.
     Make sure the user has APM turned on, hibernate turned on, and the battery icon turned on.
    2.
     Make sure that APM BIOS screen blanking is turned off. This will often make the system seem to behave badly when problem is only that the screen is black. (Use a screen saver of BLANK to get the right effect.)
    3.
     Run Apmstat.exe. Its output will often make the issue obvious (trying to run APM on a multiple-processor machine, for example).
    4.
    If the machine is a desktop, it will rarely run APM well, but you can get 90 percent of the value by using hibernate, which does not require either APM or ACPI to work.
    5. If Windows 2000 APM has been turned off, and the machine is still not stable, try turning off the APM BIOS itself in the machine's setup     screen.
    6.
     Some machines will work better with Windows 2000 APM turned on, because this puts the operating system more in sync with the system's APM BIOS.

  • Can't open BIOs Set-up, K8N SLI Platinum, after re-flash

    I used the USB Bio flash tool from the forum to re-flash the BIOs on my K8N SLI Platinum board to the latest BIOS from the MSI site, specs below.
    After the re-flash, which seemed to go okay, I cleared the CMOS (turned off and unplugged computer, pushed the clear cmos button for about a minute), and re-booted.
    I get a checksum error, no floppy found. I don't have a floppy drive in any case. But then I am unable to enter the bios. Pushing delete at boot gets me a screen that's blank, save for a cursor in the upper left corner. I can't enter anything from there, ESC key doesn't do anything. So I have to reboot.
    I can get to the POST screen and pressing F1 allows the system to start and get to Windows, which seems to run okay. System shows that the new BIOS is installed. I just can't get into it to re-set to default settings.
    If I turn off the computer, I get the checksum error again and in Windows clock and date have to be reset. But if I just reboot I just have to go through the no floppy found, then push f1 to get back to windows which has retained settings.
    I tried  doing the flash procedure again and got same result. I haven't tried flashing back to the old BIOs yet. MSI's site only lists the most recent BIOs, my preference would be to try a different one, but not as old as the 2005 version that was on there.
    Hopefully someone can tell me something obvious that I'm missing here.
    Rick
    Windows XP Professionnel
    Version   5.1.2600 Service Pack 3 Nu 2600
    Motherboard K8N SLI Platinum, with Nvidia nForce 4 SLI chipset
    Model   MS-7100
    Typ   X86-based PC
    AMD 64 3500+ ~2211 Mhz
    BIOS/Date   Phoenix Technologies, LTD V 3.12, 10/27/2008
    Version SMBIOS   2.3
    4,096.00 Mo RAM

    Quote
    I'd also like the RAM to run at at least 333, rather than the 200 something it runs at with this BIOS.
    Check this with CPU-Z at "memory tab" ==> http://www.cpuid.com/cpuz.php
    BIOS post screen info can be incorrect., or current older BIOS by 200MHz it may means 400DDR In all cases its cosmetics,
    the way of showing real of effective freq. can be changed in future version.
    Also with four sticks it should be shown as either 333 or 166, not 200 or 400
    Best check with CPU-Z how they are running
    Quote
    It may now be possible to put something faster in there, but I don't know that for sure. But the 4000+ should improve performance a bit.
    Such old CPU's can't be found easy in present days, also its not good investing to invest in old stuffs.
    You want W7 and such, changing to the best CPU wont improve much the performance in overall..
    Soon or later you have to change it, then this and eventually "newest" CPU which you gonna get will became useless.

  • MSI K8N SLI Platinum vs 1.5TB Western Digital

    Hi Everyone,
    I have recently been having some issues with my K8N SLI platinum and hoping I could get some help on resolving the issue.
    For the past 2 years i have been running the machine with multiple SATA drives (160GB{boot} and 300GB) and have now tried to add an additional 1.5TB WD and have encountered some problems. If i put my 1.5TB into a USB enclosure and then connect it to my machine it is recognized perfectly and I am able to write and read from the drive, However if i put it into my machine as a secondary HDD my computer fails to boot.
    First when i put the drive in my computer no longer boots to windows. It gets to post and loads the drives (including the new drive) and then wont go any further. PC seems to stall and wont allow me to get to the BIOS.
    I boot up the machine without the drive connected and go into the BIOS and then reconnect the drive. If i do a HDD Scan on SATA3 then the drive will be recognized (however capacity is only 136GB).
    My first thoughts were that it was a bios related issue so I have updated the Bios to the latest (3.C according to LiveUpdate) and am still having the same issue. Im not really sure where to go from now. 
    Any help would be greatly appreciated.
    Thanks for your time.
    Tim

    Hello! Please say what your system looks like. Include what PSU you are using.
    Try a different cable.
    Jumper the disk to SATA 1.
    Try the disk in a different system.

  • K8N-SLI Platinum strange behaviour

    Hi there
    Apart from the northbridge making a weird noise sometimes when the motherboard is on it's side (i.e. tower case standing upright), the motherboard started behaving strangely on saturday
    first the computer refused to find my network, always assigning a local ip, so i tried rebooting the router a few times, and then checked my other computer which is connected to the router fine
    then i tried to play a game and noticed the sound had gone, and then the game kept quitting barely after i started it so i gave that up
    then, after i had to move the mouse between this one and another computer, the usb ports (all of them, no matter whether through pci card or on motherboard, the mouse stopped working
    throughout all of this i rebooted many times.
    i finally gave up in the evening, and the next morning on a whim i turned the computer on and everything was fine, what's going on?!?! is this linked to the northbridge at all? i've monitored all the fans and temps and all are normal and running constantly ( cpu never above 40c)
    is the motherboard losing it, or maybe the power supply (all voltages seem normal too...)
    my spec
    Amd 64 3000+ venice
    MSI K8N-SLI Platinum
    2x512mb Geil Ram
    1xSata 250gig western digital hard disk drive
    1x Xfx 6600GT 256mb
    480w Tagen power supply (can't remember which off had, not the 2force one, the other cheap one, it's modular tho)
    i was going to take the motherboard back, but now it's working fine i'm sure they wont accept it
    please help
    thank you in advance
    Reaps

    Possible suggestions are as follows: Although the manual states that your power supply should be 450w or above i think that with your PSU your fairly border line. Remember that your psu will only draw the power that it requires and as soon as you start putting 256 Mb graphics cards and upgrading to more ram it is using even more resources and can cause your system to have all sorts of dramas and Re-boots.With your network connection problems this could be due to either network problems in your area which BT or your telephone provider can help you with or as i have recently found out.. too many net work connections that may conflict with each other.Go to your controll panel,Network and internet connections then network connections you should have your broadband or dial up connection listed. If you have more than one connection listed and for instance you dont use LAN (local area connection) Networking then you will have to uninstall this connection and disable all Lan options from the Bios i.e nVidia Mac LAN, nVidia Mac LAN ROM, Marvell Gigabit LAN, Marvell Gibyte rom.A possible other prob may be to disable your IEEE 1394 connection from the bios as i had similar problems to yours but am now okay. I am not saying any of these are related directly to your problems however they are possibilities which you may like to try. Please note also that your USB problems can be solved by using the latest Bios update (which i personally have never had any problems with) but may be risky if you have no idea how to flash your bios. My advice on this would be to read the moderators (Bas..i think) instructions as to how to do this or as he suggests unistall all your motherboards usb drivers that were installed from the disk provided by your Motherboard Manafacturer, Re-boot and let windows re-install its own USB drivers which certainly worked for me.
    Q-TEC 650W PSU
    AMD Athlon 64 3200+ CPU
    MSI K8N SLI Platinum N-Force4 MOB
    2x 512Mb Hynix DDR 400 RAM Modules(Single)
    Gainforce GeForce 7800 GT
    Samsung 120 GB SATA

  • MSI k8N SLI Platinum - dead??

    Hello,
    I have started the PC as per usual. Pushed the power button... nothing. Then again... nothing. Then I swithed off from the switch near the mains entry. and switched on... PC started however I get nothing on the screen. No beeps.
    I have an Antec Truecontrol 2.0 power supply, an MSI K8N SLI Platinum (socket 939) with AMD Athlon, 2 GB Corsair TWINX Ram, three HDDS SATA, Raptor 75GB as Primary (C:) and another two WDS. Video Card: BFG 7800GTX+ 256MB OC, PCI - Express.
    System has functioned Ok for three and a half years at least. I have replaced the Northbridge Fan from the beginning with a Blue heatsink - I believe Zalman. No temp issues. No overclocking, I am not using any commander modes etc etc.
    When I look at the D-Bracket I get Memory Init Error (RED-GReen-Red-Red). I am pretty sure it is not the RAM. I pulled the RAM, used only one stick... same error.
    I pulled the video card out. Then interestingly the system reaches the phase just before booting and the D_Bracket shows Floppy Init error (Green-Red-Green-Green). I tried moving the video card to the second PCI -ex - I also reach the Floppy Error point. I put in a crappy PIC-Ex video card - I reach the same Floppy init point - the floppy actually seeks but does not try to read. Unfort I forgot where I put the Monitor adapter thingy so I can;t check if I get anything on the screen with the crappy PCI-Ex video card. Will get it... soon...
    I have a hard time determining whether it is the Video card or the mainboard. I have pulled the battery out, left overnight, pushed the BIOS reset... nothing helped. With Video Card in PCI-Ex slot 1, I get the memory init error. With the card in PCI-Ex slot 2 or with no card or with crappy PCI-Ex, I get to the Floppy Init point.
    Could it be that at that point I would be getting a VGA error that I cannot see on the screen ? Why then NO BEEPS? Does this Mobo model not beep, just uses the D-Bracket?
    It is important - if it is the mobo I am done for, I have to buy Mobo, RAM, CPU... $1,000. If it is the Video card I may find something 1 slot wide and similar to the BFG ...
    Can anyone help narrow this please ?
    BTW on the screen I get NOTHING, if I pull out the cable the monitor says - check connection, if I plug it in the monitor goes to power saving.
    Thank you Heaps

    Quote from: Bas on 19-January-09, 00:17:28
    Put a stick of memory in there of el-cheapo brand.
    Those Corsairs you have need more voltage to start if I'm not mistaken.
    Found out what the prob was - the BFG 7800GTX was DEAD. RMA-ed the card. the MSI Mobo is Ok

  • MSI K8N SLI Platinum & Apacer PC3200 or PC4000 memory (Apacer chips)

    I have a situation here. My Athlon Venice 3000 is stable on 2520Mhz. So when i had Patriot PC3200 & Kingston PC3200 dual kit memory i set in bios 280x9 and a 166 memory divider or 315x8 and a 150 memory divider and got ~229Mhz on my RAM. And now Apacer dual kit modules don't want to work on this frequency in this conditions as i discribed earlier (computer isn't boot up and i have a black screen). But PC4000 modules are working on 280Mhz (280x9 and a 200 memory divider). Any suggestions? Is it incompatibility of my mobo and Apacer memory?   
    PS: Bios 3.9 or 3.A modded by Murdok.

    Quote from: kakarocht on 11-June-06, 16:14:30
    List down all your rig including PSU and bios revision and put it in your signature so others can help you. Gd luck.
    Mobo: MSI K8N SLI Platinum.
    CPU: Athlon 64 Venice 3000(1800Mhz) upto 2520Mhz(280x9 or 315x8)
    PSU: Delta 400W.
    Bios: 3.9 or 3.A
    With Apacer memory (PC3200 or PC4000) i have not working memory dividers (150, 166, 183) except 200. Computer is not boot up (black screen).

  • MSI K8N SLI Platinum and 4x512 DDR

    Hello everybody,
    My problem is with a 2nd kit of 2x512 MB DDR I bought recently. I had a pair of  Kingston KHX3200ULK2 512 MB and unfortunately this model was discontinued, so I got another 2x512 MB DDR, this time Geil UltraX which should work @ 5-2-2-2-1T.
    When leaving everything on auto, the motherboard sets the 4 modules at DDR333 with the tightest timing. I want to run them in DDR400, so I set them up manually @ 5-2-2-2-2T. In this config, everything is unstable. Sometimes the system doesn't boot, sometimes I get blue screens, etc.
    Can somebody help me with some ideas ? The system appears to run stable with timings setup at 6-4-4-2-2T, but I really paid a lot on those modules and I'd like to squeeze the most out of them.
    Thanks in advance
    System config following (not overclocked)
    MSI K8N SLI Platinum
    AMD64 4000+ Clawhammer
    2x512M DDR Kingston KHX3200ULK2
    2x512M Geil UltraX 5-2-2-2-1T (don't have the P/N)
    Gainward Ultra 3500 PCX

    Quote from: SIGSEGV on 10-November-06, 02:35:19
    Latest test I did: DDR400 with 5-2-3-2-2T. Ran Prime95 for more than 4 hours and no errors. Still have to check with some games, maybe a 3DMark in loop.
    Will come back with updates.
    Thanks.
    it's nice to be right 

  • MSI K8N SLI PLATINUM OC problem

    Hi
    This is my first topic.
    MSI K8N SLI PLATINUM
    Wincheaster 3200+ 90nm
    Aspire 520watt 35amp
    Point of view 6800ultra
    2*512 crusial BallistiX pc4000
    My problem is that the pc will not boot after 235 FSB. I have tried with 2*512 pc2700 memory with same result. I have tried diferent memory timing but it wont help, i have add more voltage to the memory and cpu but it wont work either. Im open for any idea.
    I hoped to at least overclock the cpu to 2,6 ghz watercoold
    Plz HELP

    Quote from: filleCarpet on 25-April-05, 09:36:05
    Maybe i need to add more electric power for my memorys. The spec says 2.80 volt on 250 mhz but i start to suspect that this is just an minimum requirment, maybe i need more than 3.0 v to operate the memorys on high performance(beyond 230 fsb), but the thing is that BIOS allows me only too add 2.85v maximum.
    Im trying to find a newer version of BIOS version 3.1 if there is any....
    Here: http://www.techpowerup.com/articles/other/111
    v5.0 Beta 4 allows to give 3.10V to the memory but i don´t think it´s going to help you, you probably have the CBBID issue.

  • MSI K8N SLI PLATINUM & Geil PC3200 400MHz CAS 2-5-2-2

    I'm thinking of buying a new pair of memory modules, particularly,
     Geil Ultra X  PC3200 400MHz CL2-2-2-5 DDR.
    Has anyone tested them with MSI K8N SLI PLATINUM?
    The specifications are:
    "PC3200 400MHz CAS 2-5-2-2
    GeIL Ultra-X TSOP 32x8 DDR Chips
    184pin, Non-ECC, Un-buffered DDR DIMM
    Platinum Copper Heatspreader
    6 Layers Ultra Low Noises Shielded PCB with Gold 30u" Plating
    Temperature thermometers
    Retail package
    2.55V-2.95V
    Lifetime warranty"

    I continued with the overclocking to see the limitations of the memory and not only.
    I managed to run the modules at 466MHz with 2-2-2-5-1T at 2.85v which was the upper limit.
    Unfortunately bios limitations didn't me allow to reach 500MHz as the memory chips could give.
    Max voltage at 2.85v.
    The ultra x series are out in the market with two chips: Samsung TCCD and Winbond BH-5.
    For that I searched and learned that the Windbond BH-5 can't work at CL 3, which I set at system bios.
    The system couldn't boot. So I suppose I'm having the coolest BH-5.
    It also needs over 3v in order to reach the 500MHz frequency and the necessity of an air cooler above rams.
    Maybe in the future with a more overclockable m/b like Stick proposed.

Maybe you are looking for

  • What's wrong with my macbook? It shuts down after 1 minute!

    Last night I updated my macbook with something, didn't see what it was, but it required a restart, so I did that. After that, when I was using my macbook it froze all the time, so I tried restarting it a couple of times, but the freezing kept getting

  • Does Crystal 2011 supports SAP R/3 4.6?

    Friends, I would like to know Does Crystal 2011 supports SAP R/3 4.6? Please help. Thanks, Tilak

  • Plug-in max heap space for IE on Windows Vista

    G'day, The organisation I work for will be moving from Windows 2000 to Windows Vista later this year. We'll be including JRE6 as part of the standard desktop installation :-) Ahead of that I'd like to know the default maximum heap-space configuration

  • Time Machine - "Can't Mount Device"

    Hi, recently my power went out and now my external HDD won't mount back to my Mac Mini! I have everything on here so any help would be great! My HDD was used as my "Time Machine" and did back ups every hour or so and now I tried restarting the comput

  • The status bar and search bar are black in safari

    Just in the last few days when I go to Safari on my IPad 2 the status and search bars are black with white print.  I want the silver and white color scheme back, can you help?