X58 Platinum Raid 1 Setup Problems

I am having difficulties installing and setting up Raid during my Windows 7 installation and wanted to see where I was going wrong. My setup is as follows:
Windows 7 Upgrade CD
MSI X58 Platinum motherboard
1 Seagate 250gb HDD (I intend to put the OS on this drive)
2 Seagate 1tb drives (Intended to be in Raid 1 configuration - moving all of my data files to the raid configuration)
Intel ICH10 8.5 drivers already installed. Attempting to install 8.9.0.1023 from both floppy and flash drive. Drivers downloaded from MSI site and Intel.
I can install Windows 7 without any issue if my Integrated Peripherals in the BIOS are set to IDE, but the second that I set it to Raid, things go downhill.
All three drives are visible in the BIOS. I have created a Raid 1 volume using the Intel Matrix Manager 8.5 and selected the 1TB drives.
I have the integrated peripherals setting set to Raid, but the second I do, Windows 7 installation indicates "Setup was unable to create a new system partition or locate an existing system partition". I have tried formating the HDD and using bootrec /fixmbr to correct the problem, but I have not had any luck.
1)I boot up the system with the Windows Installation CD in my drive, boot sequence is set to A:, Flash USB, CD/DVD drive, HDDs.
2)Windows installation starts. I select Custom Installation.
3)2 drives are visible - the drive I intend to install the OS and the Raid drive
4)I load the Intel Matrix Drivers using the load drivers command
5)I attempt to install Windows 7 upon successful installation of the Intel Driver and I get the error message stated above.
The three drives are all installed on the main board Sata slots: intended OS on Sata 1, intended raid drives on Sata 2 & 3.
Any assistance would be greatly appreciated.
Am I missing a step in the installation procedure or executing the installation procedures in the wrong order?

Quote
Windows 7
32 bit or 64 bit?
Quote
Attempting to install 8.9.0.1023
For Windows 7 32bit or Windows 7 64bit?

Similar Messages

K9N2 SLI Platinum raid setup after bios flash

Hi
I'm building a new system based on K9N2 SLI Platinum. Apart from a new 80 GB sys. HDD everything else is reuse from another MB (MSI K9N Platinum).
Here is what is puzling me: Before trying to install WinXP i flashed the bios to 3.2 because of the included updates to the raid bios. Flashing went well, however in my setup I want the 80 GB HDD to be non-raid and the two 320 GB HDD to be raid1. I've set this up in bios so that only channel 5 and 6 is enabled for raid and would expect that the 80 GB HDD (channel 1) would show up as a normal sata HDD when starting up. But it doesn't - it is listed as 0.0 xxxx after the "press F10 to enter raid setup" message?
This is strange because I had the same HDD setup on my old MSI K9N Platinum and there the 80 GB sata HDD was shown as a "normal" disk and not as a "appendix" to the raid list.
Because of this I have problems installing WinXP on the 80 GB HDD
Any suggestions?

Hi BOSSKILLER
Thanks for your quick response.
Quote from: BOSSKILLER on 12-August-08, 00:14:44
Well, leave the 80GB only and install XP over it.
Then connect other two HDD's and enable RAID for them.
Unfortunately this didn't help. As soon as I installed the Windows nVidia RAID SW it prompted med that it had registered the 80 GB disk as a new disk that wasn't a member of any RAID. This happened everytime Windows XP was started.
The trick was to add the 80 GB disk as a Spanned disk using the nVidia RAID BIOS setup utility. Install Windows XP (again) and the Windows nVidia RAID SW and setup RAID 1 on the other two sata disk.
I don't think this is a great setup but it works. I hope that MSI will fix this issue in a later BIOS upgrade. It would be nice if the enabled/disabled for sata RAID setting actually worked.

K9N SLI Platinum - RAID 0 problems

Hi everyone,
I've just assembled a new pc with a K9N SLI Platinum (PCB Ver: 1.1; BIOS Ver: 1.3), 1GB (2x512MB DIMM1 & 3) Kingston KVR667, 2 Maxtor SATA-II disks, GF 7300GS with 256MB DDR2.
I'm able to install windows with one disk but can't do it with both disks setup as raid 0.
I've tried both Sata Raid Driver from cd and from MSI website.
With the driver from the cd windows setup finds the raid and starts installation, but freezes somewhere (totally random) without finishing.
With the driver downloaded from the website windows setup can't find the raid.
Any hints?
Thanks

Quote from: manuelmont on 25-September-06, 07:13:09
I tried once again to install windows and this time setup finished successfully and the computer boots from the raid. So my first question: what is the relation between the bootable option at the raid setup and the fact that the system booted without it?
I doubt that the removal of the floppy from the bootable devices list has anything to do with the successful install...
Well if it is grayed out in the RAID setup is because it is already Bootable, as for the removal of the floppy from the bootable devices, there are things that only the gods of the computers know...
Quote from: manuelmont on 25-September-06, 07:13:09
Everything seemed to work ok but the computer started to freeze once again during installation of other software which made the system unstable.
Then I replace the graphics card with an ATI X300 (just for testing) and the system became stable. I installed software, played some games without problems. As the GF 7300GS I removed works on another pc this seems to be some compatibility problem between the MB and the GF (turbocache?).
I used Sisoft Sandra 2007 Lite to test/benchmark the system. All the tests were almost normal (except memory - benchmark showed values a bit lower than I expected!) but I could not run Physical Disks Benchmark module neither Physical Disks Hardware module (but could benchmark the file system). What does this mean?
The disks are in fact DiamonMax 17 (6G160E0) but I'll try another brand as well, these are the only disks. On the IDE channel I only have one dvd recorder.
Your PSU has way to low amperage for that system, the test is the change you made from a superior GFX to a lower end one, the NX7300GS eats alot of amps in comparison to the X300, and it does not have nothing to do with the TurboCache feature.
As for Sisoft Sandra I don't use that "I'm a potty mouth" (pardon my french ) I use Lavalys Everest or for disks HDtach, and others.
You could not test the physical disks because they are in RAID mode, but you can test or benchmark the logical disks because they are the partitions you created in the physical disks and are divided by the 2 disks, half in one half in the other...
I hope this will shed some light into the questions...
Be well....

Disk Utility RAID setup problem

I just formatted two 5TB drives in order to setup an internal RAID for an Intel Mac Pro (early 2009 OSX 10.10.1). I had no problem installing a RAID on 2TB drives a couple years back using Disk Utility. Now, the RAID option does not even appear for the new disks. I can see the RAID option when choosing the OS disk. The only other hint is Disk Utility says "this type of disk cannot be used as part of a RAID set". I have never seen this error. A disk is a disk (and a horse is a horse of coarse of coarse).
What do I do to make these drives eligible to be part of a RAID?
The disks are Seagate ST5000DM000. See image below for lack of RAID option.
Any and all assistance is greatly appreciated!!

Thses are normal but innocuous messages resulting from installing ARD and Java updates. If you now have Lion installed then these are left overs from the Snow Leopard system you upgraded. Don't worry about them. They will recur when you run repair permissions.

Marvell Raid Setup Problem

I have managed to install an onboard raid 0 using two 300Gb V'Raptors connected to an X70-UD5 board, and they are up and running.
I am trying to add second raid 0 using two WD 1Tb Blacks connected to the next pair of Marvell sockets on the MB. I have set that sata connection to raid, but after restarting and using Ctrl m to enter Marvell configuration, I can't see those WD blacks - only the 300Gb Raptors already set up and working.
If I go into Win7 Disk Management I can see the two WD Blacks as unallocated volumes.
Any ideas where I might be going wrong?

That's a good suggestion, and similar to what I was considering as a next step. The system hangs every time writing large data blocks to either raid0 array, and from different source drives. My next step was to start from the beginning keeping things as simple as possible to try and isolate the problem. I'll delete one of the hardware raid0 for instance, and if that works OK, keep adding drives until it fails.
As it happens, my second 300Gb v'raptor was obtained second hand from somebody who had upgraded to an SSD, so that's something to think about. But the v'raptor raid0 is only 600Gb so I was going to use it for captured video. It has a single 80Gb project on it at the moment, and it took two attempts to transfer that data to it.
The other raid0 is a pair of 1Tb WD Blacks, and I am trying to transfer My Documents to it, which is close to 600Gb. It hangs every time from anything from 200 to 500Gb moved.
I have a similar thread on an Oz gamers/overclockers forum. They sure seem to know their system tweaking stuff, but have not given me anything more helpful than that Marvell SATA sucks, and Marvell SATA 6G sucks big time. But I have eight drives (including the DVD burner – 10 with the USB3 externals), so have to use both Intel and Marvell ports.
I am just a hobbyist with video, and having spent close to NZ$5000 on the box so far, I would prefer not to invest upwards of another NZ$2000 for a raid controller. I mean I don’t know for sure that it’s the on-board raid controller that is causing the problem.
The place that built the box opens after the Christmas break this coming Monday, so I’ll get them involved, but I don’t think their experience and knowledge extends to this area. They are a Gigabyte main dealer though, and have good communications with the NZ Gigabyte technical people.
Just one thought, when I initially tried to set up using the Intel ports, it lost my boot drive and I reset the BIOS defaults while trying to fix it. Since then I have a display glitch when resizing some windows. Disk Management window is the worst affected. It looks for all the world like a GPU driver issue, but I have checked that. When I drag the corner to resize the window, it leaves these trails:

MSI 875P NEO-FIS2R RAID SETUP PROBLEM

hie everyone
with my hard disk now , how can i setup raid ?
detail plsee

Your signature shows 3 drives, all different sizes. If you are going to raid a pair, they should preferrably be the same size and preferrably the same type. If you raid a mismatched pair then your new raid "drive" will the the size of the smallest, losing the remaining space on the largest.

K9a platinum raid setup options?

few quick questions.
for raid 0 what do the following options mean?
gigabyte boundary? default is on. should it be?
next is fast write default is off but i turned it on?
stripe/block size? is smaller better or bigger better?
lastly, can i partition a raid 0 array? or is it a bad idea?
thanx.
p.s. i already set mine up but maybe when i upgrade to vista later i would like to have a better understanding of it.
i set my boundary to on, my fast write to on and my stripe/block size to 64k since it matches the block size for my NTFS. drives are 2 wd 150 gb raptors.

Quote from: msiguy on 26-September-07, 08:31:02
few quick questions.
for raid 0 what do the following options mean?
gigabyte boundary? default is on. should it be?
It means that the raid-size is in GB's only and not parts of them. Just leave it like it is. No reason to mess around with it.
Quote
next is fast write default is off but i turned it on?
I don't know what it does exactly, but I suppose it has to do with the way data is written to the array. I'd leave it at the default value for now.
Quote
stripe/block size? is smaller better or bigger better?
There is no good answer to that. You need to understand first how a striped array works. For example: if you have a raid 0 with two disks, the following situation exists. When the blocksize is set to 64kB and you write a 128kB file, the file is split in two 64kB parts. Those parts are written to both disks at the same time. So, disk A receives one part and disk B receives the other part at the same time. Now, the smaller the blocksize is set, the more files will be split. (You see, a 64kB file cannot be split in smaller pieces, since it is equal to the block size of the RAID-0).
So, the answer is something like this: if you use many small files, setting a small blocksize is better (for example, when you install Windows on the RAID). When you use it for data storage (many large files), larger blocksizes are better. If you are not sure, set it to 64 or Auto.
Quote
lastly, can i partition a raid 0 array? or is it a bad idea?
Yes, you can. No problem.
Quote
thanx.
You're welcome!
Quote
p.s. i already set mine up but maybe when i upgrade to vista later i would like to have a better understanding of it.
[/size]
I hope you will wait a bit with that ....
Quote
i set my boundary to on, my fast write to on and my stripe/block size to 64k since it matches the block size for my NTFS. drives are 2 wd 150 gb raptors.
If it is working fine now, just leave it alone.
Note this: if one of your disks gets damaged, or when data is lost from it, you will lose the whole RAID array and all the data on it. So, it is important to backup everything regularly.

P6N Platinum Raid 1 Problem

Doing a new build with P6n Sli Platinum 650i and Vista Ultimate. Raid 1 is set up in bios but when I try to load Vista it only sees one drive.Have two WD 10,000rpm Drives on sata 1 and 2.Loaded Nvidia divers after Os and Nvidia software says that drives are mirroring and healthybut Vista is only using and seeing one drive.Have tried to reinstall os but same thing.Tried loading drivers during Os install but Vista only saw one drive and would not except drivers.Any suggestions?

Firstly, do you know what RAID-1 does? It is mirroring both drives, that means both drives' data are exactly the same at all time. In OS, you can only see 1 visible drive for you to access. That is expected.

P6n sli platinum (raid setup "issues")

got 2# 320 gig seagates formated and ready (sata)
the system was up and running fine on 1 hard drive and windows xp-pro
reformated 1st hard drive and want to re-install XP but in raid O now...............
I am booting from my floppies, when instructed to hit F6 to install raid controllers off another floppy....
the damn system won't allow me...... I hit f6 quite a bit and can never get into the installation of the raid controllers?
any ideas?

I can remember having a similar issue when I installed a RAID system for the first time. It turned out to be the keyboard. I had a MS keyboad and it turns off the F-Keys on defult. There is a function key toggle button just to the right of the f-keys. you need to hit it as soon as the bios shows up on the screen. then you should be able to get the F6 key to work.
also, make sure you have the raid turned on for your drives in the system bios, then you need to activate the raid volume in the raid bios.
hope this helps.

SATA RAID setup problem - 845PE Max2 FISR

Hi,
I have tried to switch from XP made RAID 1 (striping) to BIOS (SATA) supported one.
1. Detached 2xIBM 80G disks from IDE1
2. Attached a ViPower VP-9041 SATA to Ultra ATA (33/66/100/133) converter to each.
3. Changed the jumper on the slave disk to master.
4. Attached the disks to the SATA ports.
5. At boot checked if SATA is enabled in the BIOS - OK. (Not too many or sophisticated options can be found in my bios, see below.)
Originally the a 40GB Maxtor on IDE3 (supported by the Promise 376 SATA chipset as well) used for XP SP2 boot - it remained this way.
At first boot FastTrak BIOS detected IDE3 (as before) and scanned for other IDE drives, but detected only one of the two 80 GB SATA converted disks.
At later boots, neither SATA disks detected, but I got the folowing message from FastTrak BIOS:
Warning- FastTrak does not detect proper interrupts. Please check your PCI IRQ settings, and make sure the PCI slot supports Bus Master operations.
IDE3 disk detected correctly and the system can boot from it.
If I remove ony one of the SATA disks, no warning from BIOS, but the other SATA disk is not detected either.
Any hint? (Changing PCI Bus Master state in the BIOS to either enable or disable does not matter.)
My BIOS is AMI 3.31a.

Now I got another 845PE-MAX2-FISR from the dealer, and this one works!!
So the conclusion is, the other 845PE-MAX2-FISR coursed the ram error...
>> Assaf
Ofcourse its a legal one!

Problem with MSI X58 Platinum SLI - IOH temperature !

Hi guys.
I have this PC configuration:
- MSI X58 Platinum SLI ( Bios Version 3.8 - http://img822.imageshack.us/img822/6707/161020101249.jpg )
- Intel Core i7 930 2.80 GHz box ( with Intel Turbo Boost running sometimes at 3.06 Ghz )
- MSI GeForce GT240 1GB DDR5 128-bit HDMI
- Corsair 6GB DDR3 1333MHz CL9 XMS3 Triple Channel Kit ( sets to AUTO and running at 1066 Mhz )
- Corsair CMPSU-750TXEU
- Ordinary case ( http://img828.imageshack.us/img828/4200/161020101246.jpg & http://img29.imageshack.us/img29/8480/161020101247.jpg ).
- Windows 7 Ultimate 64 bit.
I bought my PC components 2 months ago, so they are new.
Now, guys I think that is a problem with my motherboard. When I turn on the computer in Bios I have this temps: CPU – 30 C (86 F); IOH – 71 C (159 F); System 30 C (86 F) - http://img687.imageshack.us/img687/394/161020101242.jpg. After 2 minutes the temperatures are: CPU – 34 C (93 F); IOH – 82 C (179 F); System 41 C (105 F) and 2 more minutes later the temperatures are: CPU – 34 C (93 F); IOH – 84 C (183 F); System 43 C (109 F). After 30 minutes of doing nothing I have this temps: CPU – 35 C (95 F); IOH – 85 C (185 F); System 42 C (107 F) -
Guys it is normal with IOH temperature ? I am a little worried about it ( to be honest I am more than “a little” … I am worried a lot ).
Ok, I know I don’t have a good case but in 3 weeks I should receive this Thermaltake Spedo Advance Case (http://www.thermaltakeusa.com/Product.aspx?C=1121&ID=1829) and I will buy a new CPU cooler ( I don’t know yet wich one – maybe Corsair CWCH70 or Noctua NH-D14 but I have to see the case first … to be sure there is a plenty of space for those coolers ).
Pls help me with that IOH temperature. It is normal ? What if I intend to make a little OC ( lets say CPU to 3652 Mhz and RAM to 1333 Mhz … but also I will ask for your support ! ) my motherboard will burn ?
If it is necessary I will contact my retailer and send him back the motherboard but … I like MSI a lot.
Thx guys for your support !

Hey guys,
Here is a nice cheap alternative.
Here is my story about the same issue. I found it after looking at why my computer freezes sometimes. Not very often but enough for me to do some investigation. I noticed my IOH temp was a whopping 117 degrees Celsius. lol. Surprised my mobo didn't burn out by now. I wanted to evaluate the situation with the heat sink and decided to take it off. After taking it off I found extremely crusty purple compound on board the chipset and the heatsink. I took me FOREVER to scrape it off. it was almost like a cement which I found odd. After scraping and cleaning the surfaces with alcohol, I placed some silver compound on and proceeded to put it back on.
Well, upon hooking everything back up I was still at 95 to 103 degs. Now I started to really look at the options to replace this. I had SLI config which means I had to do something clever with the southbridge as well. A nice thermaltake chipset solution w/fan and a low profile copper southbridge with shipping was about 45 bucks. Hmm ... This is a sure fix from the threads I have read and its really kid of expensive to fix a simple defect. the problem is not necessarily with the heatsink not being sufficient. Its the combo of the compound used vs the amount of pressure applied between the heatsink and chipset. It was completely unacceptable. I knew this right away when I was watching the temp and then I would press on the top of the IOH heatsink and I would watch it drop another 15 degrees in less then 10 seconds. The springs are extremely weak and not effective at all in transferring the heat from the NB.
Here if my fix. Cost me less than a dollar at the hardware store and it works ideal thus far. Do this at your own risk. Doing this will probably void any warranty too. All my problems are solved and I am running at 57 degrees, YES, 57 degrees with the stock heatsink and no additional cooling.
For one scrape all that old crap off like I did. Apply your new compound. But when you go to replace your heatsink, use the following method. The trick is to use metal screws with a mobo washer, original springs from the plastic studs and a nylon locknut. Use screws that are the same diameter and length (maybe a tad bit longer) as the plastic retainer studs. Also grab a few of those red nylon mobo washers too, were gonna need them as well.
After scraping and applying compound, reassemble as follows. Screw with washer inserted into the back of the mobo so the threads are out front. The plastic/nylon washer is betweeen the screwhead and the back of the mobo as a insulator. Put the heatsink on. With the threads thru the heatsink already, put the springs on and start spinning on the locknut. I torqued the nut down on the spring until the spring almost became fully compressed. The purpose of the spring here is really to prevent you breaking something and at the same time using the max force of the spring since it weak to begin with. Thats why we need to compress it down pretty much all the way. There will be little to no room in the spring at this point. The heatsink at this point should be pretty solid to the board as well. I noticed with the plastic studs before the heatsink would wobble if you gave it a little rocking back and forth before. Not this time. Shouldn't move much if at all. Remember not to torque down too much. You don't want to go beyond the springs compression. Even if you did by accident, its better then not using a spring at all. If you feel that it starts to feel tight when torquing, you torqued too far. Stop an backup a 1/4 turn or so. It is also very important to make sure both torques are equal on both sides as well. Alternate sides when torquing down. I could tell by how much thread I had left on both sides and by looking for any uneven sides.
To summarize, the compound is a problem no doubt. After you resolve the compound issue, its all about the adequate pressure between the heatsink and the IOH. Much like the amount of pressure needed between your CPU and your heatsink give or take. And the pressure that would be as an aftermarket solution like the thermaltake chipset cooler. You dont see cheesy springs on that. Wake up MSI. Simpy using a more effective spring could save MSI some cash in the long run. I envision a leafsprin design like the thermaltake chipset one. The heatsink design could be better, sure, but the design itself is not the problem. Replace the heatsinks if you would like to, if your overclocking and stuff. Funny, this board I have is a refurb too and only had it for a few weeks. Figured they would have done something about it.
Sorry the pics are not the best. Here is about as close as I could get to the finished product

K9A2 Platinum Raid problem

Hi i have 4 days trying to install my new system. And the mobo do not want to recognize the drives in sata 5 and 6, those controlled by promise.
My system specs:
Phenom 9600
MSI k9a2 platinum
6 samsung hard drives SATAII 7200 rpm
8gb ram Corsair Dominator 1066 MHZ
2 x Diamond ati HD3870 512 mb GDDR4
Thermal take toughpower 850W PSU
I want to run:
RAID 1+0 With 4 drives of 320GB each using sb600 controller
and two 320 GB single drives, NON RAID on the promise controller.
How can i run this config on my mobo? it is possible? i need detailed bios settings for this please.
Second alternative config:
Raid 0 on sb600 using 4 disk
Raid 1 on promise using 2 disks
I have 6 drives in total and want to use them all.
Right now if I enable additional raid config on BIOS my sb600 controller only detect disks on the 1 and 3 ports, but doesnt see the 2 and 4 ports. Also i cant see the 5 and 6 ports anywhere in the bios or in the ctrl-f raid utility.
My bios version is 1.3
Any help?

hi, you could use the promise controller for your raid array using the rear esata connectors (with a esata to sata cable) and in side ports 5-6, use the sb600 not in raid for the other drives, like bas was saying each controller has it own bios, so what that means is if promise raid is on (sb600 off) the drives would show up in the promise raid setup and the other way around (drives in the SB600 RAID set up) and also if both raid controllers are off the drives show up in the main board bios. once i did have both controllers run through their setup at the same time but i got "some memory ran out of room" message after post,..
anyway so you should be able to do what you want, but use the promise for raid and sb600 for not, that way only one raid controller is on.

K9A2 Platinum Raid 0 Setup

Setup:
K9A2 Platinum
Phenom 9850 BE
4 GB GSkill 1066 4 x 1GB
2 WD caviar SATA HD (in RAID 0 - I think??)
LITEON BD Player
Rosewill 850W PSU
Sapphire 3870 HD x2 in Crossfire
I connected the 2 HDD to the 5&6 SATA ports, set them on Promise controller both to RAID 0 and reloaded Windows Vista 64 bit. I manually loaded the RAID driver during the Windows load from the MSI disk that came with MBO. Everything seems ok. Windows only sees a C drive, but on Device Manager sees both drives as a 1+0 RAID device in Raid 0 - this also shows up on Fast Build Utility as LD1 and 2 and both 1+0 RAID device RAID 0. Don't really notice any improvement in load times. Is the RAID setup correctly? Is there a way to improve the speed? When I run the Windows Vista performance test - HDD speed rating is only 5.7.
Thanks for any help

Why are you starting a scond topic about all this?
Please stick to the one you already started... this makes no sense at all.
I'm locking this one.
>> Here << is the other topic.

K8N neo Platinum - Possible RAID & ATI problem?

Shortly after installing XP onto my new RAID 0 setup, I installed Direct X9, nVidia nForce3 drivers and the Radeon drivers. This combination worked fine before I set up RAID 0 so it should work fine this time, right?
Wrong.
After I install the Radeon drivers, it asks for a reboot. Now normaly, it would reboot, windows XP would load and then the screen would go black for a second, then the desktop would appear. I guess this is the new driver kicking in and after that, I can reboot how many times I like and the screen woulden't go black because the drivers have already initialised. Right? With me so far?
This time, however, there is a huge delay before the screen goes black and the driver initialises. Even after it does, and windows is graphicaly alot faster, 3D apps take an age to load... like the 3DMark2003 logo will just sit there for ages, then finally load... the test itself isn't giving me the score I had before, it's a couple of hundred short, and there is nothing different about my system other than using RAID 0. Every reboot I get the same thing, a delay in driver initialisation... once there was even an area of the screen which was corrupted but it went away when I refreshed the desktop.
Can anyone shed some light on this? I can't believe RAID would cause this problem but I have no idea what else it could be... I doubt it's the K8N either, despite the numberous problems people have had.
One thing worth mentioning, it is a 9800pro flashed to XT (has the R360 core) and it's running at 9800XT speeds. It's run fine like this before, with the Artic Cooler installed, I hope it hasn't decided to start dying on me
Also, when I was trying to setup RAID 0, I had to use SATA ports 1 and 3?! I could not use 1&2 or 3&4 without problems with XP RAID setup during installation.
I am not overclocking either...

Yea, I'm really mad because not only will this board not recognize my slave driver properly, it may have also killed my X800 Pro video card
I moved my working X800 Pro video card from my old MB to my new one and when I turned it on, the X800 Pro was dead.
I then reinstalled my old MB, hoping it was merely a faulty MB that was the problem, however, my X800 Pro is quite dead now
I'm not sure if it was me who damaged the X800 Pro or it was the MSI K8N motherboard - either way it's dead
My experence so far with my new MSI MB has been horrible !!

MSI x58 platinum Problems???

To start off, I am a newb. I have...
msi x58 platinum MB
I7 920
Corsair 6gb ddr3 1333
CoolerMaster Cosmos case
Asetek liquid cpu cooler
800w PSU
ati 4850 GPU
Vista x64
I have read alot of the overclocking threads for this board.
Kinda seems like I chose the wrong one!! LOL!
I cannot get anything over 3.0GHZ
The max base clock the Mobo will let me do is 151???
I have even tried to manually change the switches on the board to 166 instead of 133..
Can somebody please help??
I tried doing everything in the BIOS.
BTW how do you add pictures here??

Images need to be hosted on a website, such as www.photobucket.com or your own webpage.

X58 Platinum Raid 1 Setup Problems

Similar Messages

Maybe you are looking for