Nforce 4 Sli Platinum motherboard nightmare

I bought an Nforce4 Sli platinum motherboard and have had some weird problems. This first to mention is the BIOS crashes i was recieving when searching for my hard drives to identify them in the bios this was cured by updating the bios. I am using x2 SATA Drives 80gig each with different manufacturers. The second then was i was not able to see the hard drives as 1, so i raided them or went into the screen created a sata array as stripe and so forth.
Second problem is Drivers for my motherboard on the Floppy were not on there totally blank. Now i have drivers installed i only just realised on the second day of having the motherboard that I only had Nforce 4tm raid class controller in there so i updated using another disk that says promise376 serial ata driver and seems to now have x2 sata drivers installed with the raid controller. Before this the 3rd problem was it wasn't shutting down the pc at all but now it is.
What my other problem is now, i used to have a k8n neo 2 and bought the neo 4 sli platinum as the neo2 was a cracking board. I have a winchester chip, 3500+ 1gig corsair memory low latect xms and when i used the optimal setting in the bios on the neo 2 the board would run sweet as a nut. Even if i took it to sergeant setting. But with the neo 4 forget it, it has to be set on manual and not optimal as if i do this the Operating system {windows home} will not boot up at all. Even if i alter anything in there to do with clocking.
why is this???

Optimal settings on a n4 sli board are tricky. It ups your overclock to sarge level which I think is a 5% overclock. Ok, so now your system is running at 210fsb or 420ddr. However, it does not know if your memory can run at the same default timings that gets set at default.
So now what is your ram timings set at - my crucial will run at 2,2,2,5 1T at 200fsb all the way up to 217fsb (400ddr-433ddr). Once I hit 218fsb/436ddr, my rig will crash. Also my system will crash if I dont have the vdimm set at 2.8v...at any timing level because crucial ballistix likes 2.8v.
I dont know anything about your ram to know if this is safe or not - plus, even if its rated to go higher, you have to test for stability using prime95 and/or memtest (see overclocking section of the forum). Just my 2 cents.

Similar Messages

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.

MSI P7N Diamond LGA 775 NVIDIA nForce 780i SLI Intel Motherboard

I Just got this board today.I dont see much output on this model!!!. I was running Evga 780 . I have 3 Evga 8800gtxs in sli.1x250 gig Western Digital with Vista/XP 3 x150 Raptors in Raid0.Galaxy 1000 PS. 2x2gig sticks of OCZ 6400. Ram. The CPU is a E6850, I switched to this board because the Evga780 did not have a space for External sound Card. The cooler iam putting on my CPU is aThermalright SI-128SE CPU Cooler with a 1 Scythe 120x25mm SlipStream SY1225SL12SH 1,900 rpm 37.00 dBA 110.31CFM DC12V 0.53 A With a Zalman 6 fan controller. All of this is going In a Cooler Master 830 Case. The monitor i run is A Viewsonic 245bw 24". So Anyways does any body have any comments on this board or suggestions or any problems. I would be interested in hearing Them.Thanks

In cell menu...change auto settings for FSB to "Manual" and then adjust CPU FSB in small increments until you get a stable overclock. Ie;..std FSB is 1333mhz...increase it to 1500 mhz and save and reboot. Small increases in CPU voltage may be necessary for a stable OC. If you want to see the full speed in CPU-Z you will have to disable C1E in Advanced bios....CPU...then hit "F4" to show the hidden C1E option. If you dont disable C1E, you will see the true OC fsb in bios when booting, but the C1E will "throttle" the multiplier back in Windows to a 6 or 7. At full load, the max FSB will kick in automatically. Hope this helps get you started in the right track.
Paul

K9N2 SLI Platinum Motherboard LED 8 On - Help!

I've got it barebones, and LED 8 is stuck on and I can't get any video to HDMI through the DVI adapter to HDMI.
I'm running an AMD Phenom X4 9950
4GB OCZ DRAM
700 W PSU
Any suggestions?

Yeah, I just dropped my GTX260 into it and hooked it to a regular monitor, now it is displaying fine...stupid onboard video.
I think I'll be okay from here..thanks!!

MOVED: Problems using Silicon Image Sil3132 on P6N SLI Platinum motherboard

This topic has been moved to Intel Core 2 Duo/Quad boards.
https://forum-en.msi.com/index.php?topic=143886.0

Quote from: NovJoe on 14-December-10, 22:37:59
Have you install the drivers for the add on controller card?
Yes, as I mentioned in my post the add on card is seen fine in Device Manager. It's listed under Storage Controllers, is listed as working properly and has the latest drivers for Windows 7.
Also, everything worked fine under Windows XP. Same add on card and all.

How to update a BIOS for a P6N SLI Platinum motherboard

I'm running Vista x64 with 4GB RAM. I'm having the same problem as everyone else that the OS runs slower with 4GB. I installed the Microsoft's hotfix and that didn't correct the problem. I downloaded the 1.5 BIOS drivers but I'm having trouble installing them. I created a boot disk by right clicking on the A: drive and selecting Format. Then I checked of System Disk or whatever it was called so I can boot off of it. It loads the A: prompt but it wont see any of my hard drives. I have two partitions; a C and a D. Since that didn't work I grabbed another floppy and installed the drivers on their.
Problem is that I don't understand how to Flash the BIOS. I run Afud408.exe from the command prompt and I get a list of options. I believe I selected the /p which did something, but then I rebooted and the BIOS is still v1.1 in the boot up screen. Can someone please help me? What do I need to type in the command prompt to get it to update?
Thanks.

Quote
Problem is that I don't understand how to Flash the BIOS. I run Afud408.exe from the command prompt and I get a list of options. I believe I selected the /p which did something, but then I rebooted and the BIOS is still v1.1 in the boot up screen. Can someone please help me? What do I need to type in the command prompt to get it to update?
In order to make this work you need to run the afud408.exe from a pure DOS command line (not a DOS box).
The correct command line needs to be:
afud408.exe BIOS-File name
Example:
afud408.exe A7350NMS.150
However, the best thing is to use the following tool, it will make the whole procedure a lot easier since it automatically prepares everything for you:
>>MSI Forum HQ USB flashing tool<<
It works with Vista 64bit as well. All you need is an USB Flash drive.
If you don't have an USB-Flash Drive you can also prepare a CD for flashing. Guides can be found here:
http://www.biosflash.com/e/bios-boot-cd.htm
http://www.biosflash.com/e/bios-boot-cd2.htm

MSI K9N2 SLI Platinum nForce 750a Problem

I bought this barebone kit a couple days ago http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=4692741&CatId=3508 and I had no troubles, I installed the 4GB Sli-READY 2GB RAM and thought that it wouldn't hurt to have another 4GB. So I bought the same RAM, and installed it, I started to get BSOD when I start programs, or games like "Lineage 2". I tried changing the voltage on DRAM but l can't change it to 1.8v, or 2.1v (2.1v says that the pc might be unstable) so l set it to auto. l also made it [AUTO] for SLI-READY DRAM. l still get BSOD.
Help would be greatly appreciated, the specs on the computer are:
MSI K9N2 SLI Platinum Motherboard
AMD Phenom X4 9850 Black Ed. 2.50GHz
OCZ SLI 4096MB PC6400 DDR2 / 8GB
Western Digital Caviar Green 500GB Hard Drive
Ultra LSP550 550-Watt Power Supply
(2) XFX nVidia 9800GT 512MB (1GB cause l have 2) SLI - Ready
Sound Blaster Audigy SE
My operating system is a Windows XP 64bit Edition.

Quote from: Younha on 04-July-09, 01:38:49
May you please explain how to use memtest and drop the mem. freq. to 667 and the 2T thing? :x
Memtest details ==> https://forum-en.msi.com/index.php?topic=103598.msg760534#msg760534
Quote
drop the mem. freq. to 667 and the 2T thing? :x
Apply "FSB/DRAM Ratio" in BIOS, 'Cell Menu' to 1:1.66
Quote
and the 2T thing? :x
By default it should be already 2T, verify that with CPU-Z memory tab{Command Rate} ==> http://www.cpuid.com/download/cpuz/cpuz_151_setup.exe

K9N2 SLI Platinum video won't initialize with monitor connected

Hi,
I've gone through the RMA process with my vendor and I am on my third motherboard right now and I am still having an issue (so, basically, nightmare scenario here ). The first and second motherboard failures seemed slightly different but the failure seems to be the same for the second and third and it is making me think that another factor may be at play other than the motherboard. All of the failures have been with the integrated video (which is all I plan to use at the moment --I don't even own a PCI-E video card right now nor have any plans to get one in the near future).
In the first motherboard, everything seemed to work (as far as I could tell --4 green diagnostic LED's and all that) but no video signal was produced. Testing with an antediluvian Virge DX based PCI card (some of you kiddies may be too young to remember such things) did show normal booting with that video card (as far as I allowed it to go) and I suspect, from the pattern of hard drive activity, that with the integrated video the boot process was also normal (I just couldn't see it because of no video signal being produced). But that is past and has been RMA'd.
The replacement motherboard and the motherboard replacing the replacement motherboard, on the other hand, have seemed unable to initialize video whenever my monitor is connected but if the monitor is not connected, they work fine (but then video defaults to a 1028x768 mode and I cannot run my monitor at native resolution). Curiously enough, my second motherboard worked correctly twice before exhibiting the described behavior making me think, at the time, that I just got really unlucky and simply had had it fail shortly after testing it those two initial times.
Not being able to initialize video while the monitor is plugged in means that if I try to start it while the monitor is attached, the motherboard will not even POST and that the diagnostic LED's will be stuck at the video initialization stage (three reds, and one green at group 4).
Furthermore, if I start it with no monitor attached and plug the monitor in after I get 4 green LED's, it will start booting the OS (Windows XP) but the screen will go black when the Windows XP logo should be appearing. I can also leave it unplugged until it should be at the Windows XP logo stage (or plug it after the 4 green LED's and unplug it again before the video mode switch happens) and when I plug it back in I can see the Windows XP logo. However, as soon as it switches to the Windows XP desktop, I get a black screen.
And again, if I leave the monitor unplugged until the Desktop should be showing up and I plug it in at that point (or go through the process of plugging and unplugging the monitor while avoiding having video mode switches happen with the monitor plugged in) I do get a Windows desktop at the 1024x768 resolution. Once in the desktop, as far as I can tell, I can do anything there that I normally would be able to do (so I mostly have a working system, as far as I can tell). I have even installed drivers, verified that the sound works, etc.. I will still do a repair install at some point because I am not doing this the "right way" and I probably needed to do it anyway (though I think it's using the right kernel and everything --showing 3 CPU's, etc.) but I am not looking for answers with that as my issue shows up before the system even goes through POST. Again, note that I cannot even take advantage of my monitor's native resolution with the current kludge.
Curiously enough, if I try to switch to my native resolution of 1920x1200 it will do it but only by switching me to a virtual 1920x1200 desktop on a 1024x768 display (so there's no actual video mode switch involved and the desktop becomes bigger than what my monitor can show). It's as if part of the subsystem is reading the monitor and "knows" that it supports 1920x1200 but another part of the subsystem is just assuming some sort of 1024x768 default common lowest denominator for digital displays. I attribute this to the fact that video has been initialized with no monitor connected.
I originally had a 350W Enermax power supply (which worked as long as the monitor was not plugged in) supplying 32A on the +3.3V rail, 32A on the +5V rail and 26A on the +12V rail but I replaced it with the power supply shown on my profile (which was probably totally unnecessary as I'm only using the integrated video --but hey, I now have a blue light coming from my power supply so that makes it all worth it ). I suppose both power supplies could work badly with this motherboard model but it seems exceedingly unlikely that that would be the case (specially since everything works as long as there is no monitor plugged in during video mode switches).
I currently am running it, on cardboard, with a single stick of RAM (on the slot next to the CPU) and nothing else connected to it except the power supply (including JPW3 & JPW4), the CPU, a hard disk with a working Windows XP install, a mouse on the mouse port and a keyboard on the keyboard port (specification as on my profile minus one RAM module). I did play with RAM timings at the request of tech support but I can't imagine how it could be a RAM problem when everything works as long as a monitor isn't plugged in during video mode switches.
I did update the BIOS from 3.4 to 3.5. 3.5 did not seem to be available at the time of my previous motherboard and I knew it was a real long shot for this to be a BIOS issue that would be fixed with the 3.5 update (specially since the update mentions only CPU support stuff and nothing about video) but I am desperate. Yes, I have done the whole resetting the CMOS thing.
I am even considering the possibility that there may be some weird incompatibility between the video on this board and my monitor (under the assumption that, quoting Holmes, once you have eliminated the impossible, whatever remains, however improbable, must be the truth). I don't even know how that would work. Note that my monitor worked in my previous system with the digital input (my previous system is no longer available to me for testing --but I did get a chance to test it, after having problems with my first K9N2 SLI Platinum motherboard which I returned, and it worked). Note that my monitor works with the system in question (I simply cannot have it connected while there's a video mode switch under way). Note that the lack of a picture seems to be related to the motherboard as evidenced by it being stuck at the video initialization stage if I attempt to start it with the monitor connected.
Any wild ideas? I do not want to return this motherboard a third time and I specially do not want to return this motherboard a third time if it's something that can be easily fixed.

Quote from: Svet on 25-May-09, 02:21:06
Have you tried with just memory stick in 1st DIMM near to CPU socket and mainboard out of PC case?
Yes, I currently am running it, on cardboard outside the case, with a single DIMM (on the slot next to the CPU) and nothing else connected to it except for the power supply (including JPW3 & JPW4), the CPU, a hard disk with a working Windows XP install, a mouse on the mouse port and a keyboard on the keyboard port (specification as on my profile minus one RAM module). And it works,... as long as the monitor is not ever connected while video mode switches occur (including power on). And this is exactly how the previous motherboard which I returned also behaved.
Addendum: As an additional note, I have tried the other DIMM on the same socket by the CPU with the same results (everything works as long as there's no monitor connected during a video mode switch). I also managed to make a bootable Memtest86+ (is that what people use to test memory these days?) USB stick and I am running it right now. It has shown no errors right so far but it has only been running a few minutes. I do not really expect any memory errors to be at fault since they would have to be magical memory errors which only cause problems when there is a monitor connected while a video mode switch is happening but I'm desperate to try anything to find out what the issue is.

Can K8N sli Platinum be upgraded for PCIE 2.1?

Hi. Quick question as per the subject. Can the K8N sli Platinum motherboard BIOS be updated to recognise a PCIE 2.1 MSI R5570 graphics card.
We did one BIOS update using the Live Update online thing but when we try and check to see if another newer update is now due the PC shuts down and says that we have got to undo an overclocking thing!!! The BIOS update was dated something like July 08 and I don't know if PCIE 2.1 was around then.
I now assuming that there isn't a BIOS update for this motherboard to allow PCIE 2.1. Bit worried that the BIOS update that we did has done something bad although everything other than checking for the updates again seems to be working? Just putting Windows 7 on and that seems to be going fine.
Do I send the graphics card back, or can I upgrade the motherboard and still use all or a lot of the rest of the existing items like the CPU and the memory, or will a new motherboard which accepts PCIE 2.1 pretty much force an upgrade to the whole lot? CPU = AMD Athlon 64 3500+ and memory = Corsair (TWINX1024-3200XLPT) 1024MB (2x512M Matched Pair). Things like wireless and disk drive etc shouldn't need changing would they?
Thanks

Quote from: Svet on 04-December-10, 21:26:07
No, the board is too old
Based on posts on this forum, i bought Radeon HD 4770, so not to get 5xxx series, i was eager to get. But nevertheless MSI K8N Diamond won't boot with 4770. Error code says it halts on "Testing VGA Bios".
And when searching for possible fixes i came upon AMD forum where people were complaining about the 5xxx series not working with nForce 4 chipset, but most of them got an easy fix - email the support of the mainboard company and recieve new BIOS - so all the Gigabyte users got their machines running by just sending 1 email and waiting for few hours.
I do hope MSI will respond and be as generous as the rivals, otherwise it will look bad for future buyers.

K9N2 SLI Platinum Blue Screen of Death when installing Windows XP

My hardware includes:
•   MSI K9N2 SLI Platinum Motherboard
•   Corsair XMS2 TWIN2X4096-6400C5
•   GeForce 9800 GT 512MB GDDR3
•   AMD Phenom X4 9850 Quad Core Processor, Black Edition 2.5GHz
4MB Cache 2000MHz [4000 MT/s] FSB
•   Thermaltake Ruby Orb Aluminum Core CPU Cooler
•   UltraX3 850 Watt ATX Modular Power Supply
•   [1] Western Digital 200MB7200 ATA133 [Not connected yet]
•   [1] Maxtor 80MB ATA133 Drive [Not connected yet]
•   [1] Western Digital 500GB 7200RPM 16MB SATA II HARD DRIVE
•   [2] Seagate 7200.11 ST3500320AS 500GB SATA Hard Drives With 32 MB Cache
[Not connected yet]
•   LG DVD-RW
•   Toshiba DVD-ROM [Not connected yet]
•   AMI Bios v02.61
•   Antec Full Tower case
After partitioning my drive with Fdisk I tried to install Win Xp. My plan was to format the drive with XP. XP starts up and runs through the initial system check then when it prepares to install I get the blue screen that says [my words] "Windows has shut down to prevent damage to your system. If drivers are mentioned try disabling them in the BIOS or get the latest bios update from the equipment manufacturer..." The error is:
Stop 0x0000007E on the next line
pci.sys - address f7480BFbase at f7487000 Datestamp 3b7d855c
Just never had these problems setting up a system and soon I will be able to say it took me 2 years to get this running. Hope someone can help. Thanks

Use XP Installation disk with SP2 or SP3 included to fix the BSOD.
Simple your XP installation disk is outdated and cause troubles with latest hardware.

Need help with drive installation for K9N2 SLI Platinum

Hi
I am new to the forum and to MSI
This is my 6th computer build and first time using SATA and PCIe
My hardware includes:
•   MSI K9N2 SLI Platinum Motherboard
•   Corsair XMS2 TWIN2X4096-6400C5
•   GeForce 9800 GT 512MB GDDR3
•   AMD Phenom X4 9850 Quad Core Processor, Black Edition 2.5GHz
4MB Cache 2000MHz [4000 MT/s] FSB
•   Thermaltake Ruby Orb Aluminum Core CPU Cooler
•   UltraX3 850 Watt ATX Modular Power Supply
•   [1] Western Digital 200MB7200 ATA133
•   [1] Maxtor 80MB ATA133 Drive [Not connected yet]
•   [1] Western Digital 500GB 7200RPM 16MB SATA II HARD DRIVE
•   [2] Seagate 7200.11 ST3500320AS 500GB SATA Hard Drives With 32 MB Cache
[Not connected]
•   LG DVD-RW
•   Toshiba DVD-ROM
•   AMI Bios
•   Antec Full Tower case
The board set up fine, but I can’t figure out how to install my drives. The MSI directions are the worse I’ve ever seen, or should I say non-existent. They don’t even describe the bios entries… I am familiar with the bios, but don’t know all the settings for the board. I set the time and date and had to rearrange my drive placement on the board to have my 2 DVD drives show up on the secondary IDE Channel instead of the primary IDE. The Western Digital 200MB7200 ATA133 is on the primary master IDE. I’m old fashioned so I still use FDISK to erase the old OS and partition the drive… I couldn’t see my SATA drive in FDISK even though I could see it in the bios. Now I want my Western Digital 500GB 7200RPM 16MB SATA II HARD DRIVE to be the system drive and the Western Digital 200MB7200 ATA133 to be a slave drive. My previous boards had raid but I just used them as additional slave drives.
My goals: I want to have redundancy for my personal audio/video and my work. I will use the 2 Seagate 7200.11 ST3500320AS 500GB SATA drives for that.
I also want 2 additional drives not purchased yet for my other data storage needs and for games
My questions are:
Can I use the SATA drive as the system drive if a drive is connected to the primary IDE?
How do I set up Raid on this board? I actually want to use its capabilities this time.
Does this board present any special problems with dual booting XP sp2 and Vista 64bit.
If I put another set of Corsair XMS2 TWIN2X4096-6400C5 in anticipation of installing Vista 64bit will this cause a problem other than windows XP not seeing the additional memory.
Is there additional documentation for this board somewhere?
Please help…I have been working on this thing for 4 days straight. My last build took 2 hours not including software installation. Hope I stated everything you need to know. Thanks in advance

Hello!
Advice no. 1 will be not to have everything connected at once. Have the chosen SATA and one of the DVD:s connected and install Windows. (Windows can only boot from bootable devices. It "jumps" all un-bootable.) Once you have a successful boot and happy with it, remove other things from the boot-sequence.
Eh, some of your questions suggest you don't have the full manual, but a multi-lingual one. Check this out, bottom of the list:
http://global.msi.com.tw/index.php?func=downloadfile&dno=6745&type=manual

P6N SLI Platinum not booting after CPU change

I just upgraded the CPU in my machine with a P6N SLI Platinum motherboard from a E6700 to an E8500. I first upgraded the BIOS to 1.7 as the MSI page seemed to indicate that was a pre-req for this CPU. The machine was working fine for a day with the new CPU.
I changed the CPU in the machine and when I tried to boot, the lights on the motherboard came on as well as the fan, but no video or sound. In addition none of the diagnostic LEDs on the D Bracket light up. They had been previously working. Neither do the lights on my memory sticks light up.
I tried clearing the CMOS by hitting the switch but nothing. I am now going to try switching back CPUs but I don't have much hope that that is the problem given the diagnostic LEDs don't light. Does anyone have any suggestions as to a fix or is this motherboard fried?
P.S. Do you hit hte CMOS clear switch when the computer is off but the motherboard is charged? Or do you unplug the computer and wait for the internal orange light to go out as well too?

Quote from: Henry on 24-January-10, 11:41:19
What is the QC number (by the cpu socket) is 01, 02, or 03?
See this thread for more:
https://forum-en.msi.com/index.php/topic,123486.msg932471.html#msg932471
Ah. Given I bought my P6N SLI Platinum 3.5 years ago when they first came out I imagine mine is one of the older versions that doesn't support 45nm CPUs by default. Is there a photo somewhere showing where the QC number is located exactly on this MB? It's probably located under my huge CPU heatsink and I'm not going to remove that for a third time just to check.
I really wish the MSI CPU compatibility page mentioned that. It would save me a lot of time. It's not worth my time and effort to dismantle my PC, send them the MB and wait for them to send me back a compatible one.
I verified the BIOS upgrade by looking at the version number at startup and using CPUZ.

Will k8n sli platinum support 3TB hard drives

Folks,
will the k8n sli platinum motherboard support 3TB hard drives? I have a 3TB hard drive that displays as 746GB. Latest bios is on board and running win7 64bit.
Many thanks
Dave

in the BIOS it states 3TB under the hard drive section, however that might just mean it's reading the drives properties and not it's capabilities if you know what I mean.
In the motherboards raid setup only 746GB on each drive is available and within Windows only 746GB is available.
I've read somewhere that's it's got something to do with 32bit "storage" hardware systems only being able to address 2.2GB or close to that. I think I'm gonna have to upgrade.
cheers
Dave

Difference between K8N Neo4 Platinum/SLI and K8N-SLI Platinum

Hey guys.... I have one question and i hope you can help me.
I'm about to get an MSI SLI Platinum motherboard, but it seems that there are two versions, the K8N Neo4 Platinum/SLI and the K8N-SLI Platinum.
What is the real difference between them? As i can see in the manual, the Neo4 version has the additional SATA2 and Gbit LAN controller.
Anyone: Does your K8N-SLI board have 4 or 6 SATA2 ports? and 1 or 2 LANs?
At this picture http://www.midtdata.dk/asp/index.asp?varernr=K8N-SLI-PLAT&goto=productinfo&mainfunc=link I can see that there are 6 blue SATA connectors (lower right corner), and 2 LAN ports left to the LPT port... But the description says 4 SATA and 1 LAN, and so says the manual.
To all owners of this mobo: Does this picture look like your K8N-SLI Platinum or does it look like your K8N Neo4 Platinum/SLI ?

https://forum-en.msi.com/index.php?board=36.0
d/l a raid manual and all should be clear

Is there a big difference between MSI K8N SLI and MSI K8N SLI Platinum motherboa

i am a bit tight on budget, so I was wondering if I should get the MSI K8N SLI motherboard instead of the MSI K8N SLI Platinum motherboard (my previous choice),.......what do u guys say ?

Hi,
Note that he is not talking about the Neo4 versions, looks like in the US MSI has different products:
Here is the K8N SLI:
http://www.msi.com.tw/program/products/mainboard/mbd/pro_mbd_detail.php?UID=681
And here is the K8N NEO4 SLI:
http://www.msicomputer.com/product/p_spec.asp?model=K8N_Neo4/SLI&class=mb
One has Sound blaster, the other does not.
Besides, K8N SLI Platinum has only one LAN.
http://www.msi.com.tw/program/products/mainboard/mbd/pro_mbd_detail.php?UID=641
While the Neo4 Platinum has two.
http://www.msicomputer.com/product/p_spec.asp?model=K8N_Neo4_Platinum/SLI&class=mb
A bit confusing right !? Remember that this forum is accessed by people all over the world.
The thing is that the Neo4 and the related non-Neo are using the same BIOS AFAIK.
wpr

Nforce 4 Sli Platinum motherboard nightmare

Similar Messages

Maybe you are looking for