K9A2 CF RAID / Driver Problems

Hi everyone, first of all here are my PC specifications:
Mobo: K9A2 CF (Bios v1.8 - RAID Firmware 2.5.1540.33-A)
CPU: AMD Phenom II 920 (no OC)
RAM: 2 x OCZ Platinum DDR2 1066MHz @ 800MHz (default @ 1.8v)
GPU: XFX GeForce 9600GT (no OC)
HDD: 2 x Wester Digital 7200.11 SATA II 500GB @ RAID 0 from ATI SB600
PSU: Satellite 600W
Windows XP Pro 32-bit SP3
The problem is the following, when i installed WinXP I insert RAID disk (downloaded from MSI website "miniport driver   2.5.1540.48"), select the RAID 0 drive (1000GB) and let it go...
First boot: fine... i can run every application without trouble. Then i proceed to install ATI SB driver from CD... all fine, ask me to reboot, i click yes.
Second boot: quick BSOD when WinXP logo shows... impossible to boot.
Then i boot with F8 and select "last known configuration" or something like that, it boots fine but ATI SB srivers are not installed. Every time i try to install them (i tryed version 8.54, 8.53 and the one that comes with the CD) i get BSOD during boot.
That leads to a posible wrong made driver by AMD, or am i missing something?
This problem happened in this thread also:
https://forum-en.msi.com/index.php?topic=124382.0
Please help, should i send motherboard to RMA ?

by reading this thread i could see what stop error the BSOD was showing.
https://forum-en.msi.com/index.php?topic=103936.0
and then i looked up the error here:
http://www.updatexp.com/stop-messages.html
My error was 0x0000007B and my 2nd parameter was 0xC000034.
Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE
The Stop 0x7B message indicates that Windows XP has lost access to the system partition or boot volume during the startup process. Installing incorrect device drivers when installing or upgrading storage adapter hardware typically causes stop 0x7B errors. Stop 0x7B errors could also indicate possible virus infection.
The second parameter is very important because it can indicate whether the 0x7B Stop message was caused by file system issues or problems with storage hardware and drivers. Values of 0xC000034 or 0xC000000E typically indicate:
# Disks or storage controllers that are failing, defective, or improperly configured.
# Storage-related drivers or programs (tape management software, for example) that are not fully compatible with Windows XP Professional.
I read the possible solutions on that page but there aren't solutions at all... ¬¬

Similar Messages

  • D20 (4158-48G) RAID driver -problem / Win 7

    Hello,
    I've created an array (RAID1) using two identical 500GB hd's. Marvell's raid bios (?) gives me the long awaited info that the RAID1 is online and ready to be used. The problem is with Win 7.
    I've downloaded "drivers" that I need from here: http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-73716
    When I boot my system, Win 7  tells me that RAID driver is not installed correctly. When I go to the device manager and try to update the driver from specific location W7 doesn't find the drivers at all.
    No luck.
    Getting pissed off
    And as much as I have tried to use google and this forum to solve my problem - i'm starting to feel I'm all alone with this problem (
    Solved!
    Go to Solution.

    Thanks!
    the problem was that I followed too blindly Lenovos homepage and assumed that the right driver was located where I thought It should be.
    I went to Support -> ThinkBrand -> Quick Path
    Typed my model D20's model number (4158-48G)
    Chose a link "Downloads & drivers"
    From "Refine results" -box I chose "RAID" - and it only gave intel Matrix driver support..
    The correct one was found from here:
    http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=TSTN-MATRIX
    ->
    http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-72280

  • MOVED: K8N Neo2 - WinXP and Raid driver problem

    This topic has been moved to AMD64 nVidia Based board.
    K8N Neo2 - WinXP and Raid driver problem

    Quote from: SillySider03 on 18-June-05, 22:18:50
    Try This.
    Yes it worked... I did it a bunch of mins ago, ty a lot anyway 

  • K9A2 CF - RAID Drives for Server 2003

    Hi,
    I am trying to load Server 2k3 (standard) onto this board, I have 4 drives, 1 RAID0 array with 2 x 80G HDD's, 1 RAID1 Array, 2 x 500G drives.
    Problem is, I can't get any of the driver's supplied on MSI's website to be recognised by windows (at F6 stage). 
    I would greatly appreciate it if someone could point me in the right direction of a drivers / floppy image.
    Many thanks.
    Snakefood

    Ello guys, managed to get it sorted.  Problem was caused by my floppy drive; wasn't reading the disks properly.
    Resolved it by creating a new setup disk with the drivers slipstreamed into the process.
    XP drivers worked.
    Ta once again for the advice.
    Snakefood

  • K8N Neo2 - WinXP and Raid driver problem

    I've K8n Neo2 Platinum version.
    Tried to build up an array. But I cannot load the Nvidia storage controller (from floppy with F6 key) cause this file makes windows installer freeze after loaded all drivers (black screen with blinking underscore). What could I do? I've tried all solutions here with no luck at all

    Quote from: SillySider03 on 18-June-05, 22:18:50
    Try This.
    Yes it worked... I did it a bunch of mins ago, ty a lot anyway 

  • I have a MacPro that for some reason FCPX briefly "sees" my Raid drives then acts like the Events there don't exist. Seems like it wants to treat that drive like a "camera". Any ideas..help.. It sees the Main drive no problem.

    I am having a problem with FCPX seeing my Raid drive as a Drive and not as a Camera.. Don't know what I might have done to change things..it was working fine and other than backing things up to external harddrive..not sure what happened. I reinstalled FCPx, checked the disk permissions and verified it with the disk utilities. any suggestions?
    I am  using a MacPro mid 2010.

    TN22 wrote:
    As a follow up I found the DCIM culprit folder that you where referring me to! I feel better now that I understand what happened!
    Ted
    Great.
    That would definitely be an offender.
    Al

  • K9A2 Platinum Audio and Video Driver problems.

    I put together my new rig last night and am having a lot of problems with drivers.  The rig installed windows XP SP2 in about 10 minutes though   
    Rig:
    MSI K9A2 Platinum Bios 1.3
    Phenom 9850 BE
    G.SKILL 1066 5-5-5-15 2T
    MSI HD 3870 OC
    WD Raptor
    CoolerMaster 550watt
    Several fans to keep cool air flowing.
    My problem is that I can not find good audio or video drivers.  I started by trying the audio drivers included with the board, but they would not complete the install.  I ended up downloading audio drivers from the MSI site, however they also would not install with the "#-0001" error message.  I followed the instructions on the forum: https://forum-en.msi.com/index.php?topic=115396.msg866810#msg866810 including installing the MS HD Audio Driver Hotfix but still cannot get sound working.
    To further complicate my problem the 3870 has HD onboard, which makes a second instance of Microsoft UAA HD Audio driver in the device manager, and also tries to find drivers for bits of it's audio hardware.
    Currently I have disabled on-board audio completely through the bios, and now everytime I boot-up I get new hardware found for UAA HD Audio, and also some Media interface.  Clearly this is the HD on the 3870, however I can't seem to get drivers installed that will agree with the hardware thus the message continue to pop-up!
    Does anyone have suggestions or similar experiences?

    Quote from: AMDloyal on 24-April-08, 09:56:10
    Thanks for the links. 
    The standard AMD ATI Drivers + South Bridge chipset drivers worked flawlessly.  I've made a clean run through 3dmark06 so i feel good about them.
    As for the audio.
    I've worked through both of those suggestions but haven't gotten anywhere.  A few times I have been able to get the drivers to install without the "error code -0001" message, but that doesn't give me sound.  Under device manager I still end up with yellow exclamations.  It seems no matter what I disable or try to do nothing works.  I've tried updating drivers manually like was explained in the first link, but when the update is complete I get the messages lile: "There was a problem installing this device  MEDIA  An error occured...  The data is invalid"
    Does anyone know if this indicates a hardware of driver problem?
    "Thanks for the links. 
    The standard AMD ATI Drivers + South Bridge chipset drivers worked flawlessly.  I've made a clean run through 3dmark06 so i feel good about them."
    you are done well.
    As for the audio.
    I've worked through both of those suggestions but haven't gotten anywhere.  A few times I have been able to get the drivers to install without the "error code -0001" message, but that doesn't give me sound.  Under device manager I still end up with yellow exclamations.  It seems no matter what I disable or try to do nothing works.  I've tried updating drivers manually like was explained in the first link, but when the update is complete I get the messages lile: "There was a problem installing this device  MEDIA  An error occured...  The data is invalid"
    Provide screenshot from Device manager.

  • Problem with RAID drive purchased from Apple.

    A RAID drive I purchased from Apple is not functioning- something about the battery. Can anyone explain this to me?
    Thank you in advance!

    Tom,
    Some more information would help.  Make, model, etc.  Also, what exactly is the message?  Is it an Alert?  What does the console say?

  • Unable to capture to external RAID drive FCP 7

    Here are my specs:
    Model Identifier: MacPro1,1
    Processor Name: Dual-Core Intel Xeon
    Processor Speed: 2.66 GHz
    Number Of Processors: 2
    Total Number Of Cores: 4
    L2 Cache (per processor): 4 MB
    Memory: 4 GB
    Bus Speed: 1.33 GHz
    Boot ROM Version: MP11.005C.B08
    Running:
    OS X 10.5.8
    Final Cut Studio 3 (recently upgraded from Studio 1)
    At the end of last year I had a problem with capturing and upon research it seemed to be that the most recent update of QuickTime was not compatible with Final Cut Pro 5, which was causing my machine to not be able to capture at all. So we upgraded to Final Cut Studio 3 (FCP7) and part of the problem was solved but an issue still remains.
    For over 3 years we have been using an external Raid drive as a capture scratch and we still have over 5 TBs free. The Raid is connected by SCSI. Earlier last year I was able to capture to the Raid drive without any problems but now the capture will freeze whenever that is set as the capture scratch. If I set the internal drive as the capture scratch it captures without any issues.
    The problem is that using the internal as the capture scratch can only be a short term solution. The drive is only so large and I have a problem with finder if I try to move files from the internal drive to the external. Finder freezes up and I can't even force quit properly. So being able to once again use the external as the main capture scratch is the only real solution. The external is fully functionally and communicating with the Mac.
    Any help with resolving this would be appreciated!

    Off the top of my head, because I haven't worked with SCSI in years--
    "The problem is that using the internal as the capture scratch can only be a short term solution. The drive is only so large and I have a problem with finder if I try to move files from the internal drive to the external. Finder freezes up and I can't even force quit properly. So being able to once again use the external as the main capture scratch is the only real solution. The external is fully functionally and communicating with the Mac."
    Are you trying to move files while you have FCP open? The fact that simply moving files is giving you finder issues and freezing you up, says that all is not well with the scsi raid. You should not see that at all.
    You might try powering down the mac and the raid, unplugging and letting the machine sit for a while to discharge the capacitors. Then try reseating the scsi card. (pull it out carefully and plug it back in.)
    On another note, when you upgraded fcp, did you do a clean install?

  • Multiple users on single computer mounting same RAID drive

    Hi I'm a newbie:)
    I have multiple users on a single computer which need to mount the same RAID drive on a different networked computer. I have no problem making the mounts, the only thing is that when each user makes its mount the drive appears multiple times when doing an ls /Volumes. Ie, the first user mounts sparkle and it appears as sparkle. The second user mounts sparkle and it appears as sparkle-1. The third user mounts sparkle and it appears as sparkle-2. In the finder they all show up as just plain sparkle, but for running scripts, the hyphen-# screws things up. Does anyone know of a way to have the same drive mounted without the hyphen-#s?
    Many thanks!
    Megan

    What kind of scripts? I don't think there's any way around the naming problem, but you could use regular expressions. I don't see why sparkle* shouldn't do the trick, or add sparkle-[0-9$] to whatever constuct you have.

  • Using a expresscard FW800; G-Raid drive unmounts on it's own

    I'm using a NitroAV Fw800 dual expresscard to connect my 500gig G-Raid drive that i use for video editing. I have never had a problem with it using Tiger.
    Ever since I upgraded to leopard it is behaving strangely.
    I mount the drive and all is well, (this is an example of the problem I'm having with it) I used the drive to provide 3.8 gigs of info to burn a disk recently. It burned fine and when it was done the drive just sat there, turned on, mounted for a few minutes and then it unmounts itself.
    When it's doing something it behaves fine, when I leave it alone for a bit it unmounts itself and I get the error saying that it has been removed without ejecting it first.
    If I connect it via the built in FW400 port, it stays connected and I have no issues. other drive I have are FW400 and they behave perfectly.
    I have never had this problem before. what could it be?

    I spoke with the company that manufactures the expresscard (NitroAV) again and they said it is a foul up associated with upgrading to Leopard and not installing fresh and reformatting the hard-drive.
    Has anyone else had this problem?
    Is there anyway to have Apple address this problem?
    thanks for any help.
    Carlos

  • I cannot install windows 7 x64 with AMD/ASUS RAID driver

    Trying to install Windows 7 Ultimate x64 on an ASUS M5A97 mobo with AMD SB850 RAID, two WD 750GB drives configured as RAID 0. No drives are recognized by W7 install, so I choose Load Drivers. I put the drivers on a USB stick. Install finds the drivers there,
    starts loading them, then comes back with "Installing an unsigned 64 bit driver is not supported and may result in an unstable Windows installation." I downloaded the latest drivers from ASUS website which are WHQL certified (as are the one's on the motherboard
    disk). I saw other posts that recommend clicking Repair instead of Install, but I don't see where that option is. All I am given as options are Upgrade or Install. Choosing Upgrade tells me to boot Windows first. But this is a brand new install so...
    I tried pressing F8 as setup was booting and chose "Disable Signed Driver Requirement" but that had no effect at all. If I turn off the RAID W7 sees both disks and happily installs. I see related posts going back to 2009; surely someone has
    a solution for this issue?
    Da Bomb

    Hi guys,
    I have been struggling with the same issue.
    Win7 x64. Gigabyte GA-X79-UD3 Mobo with Intel core i7-3930K at 3.20 GHz
    Marvell 88SE9172 SATA RAID controller with two Hitachi 500 GB spinning disks configured as RAID1
    Windows would get to the point of asking for a mass storage drive. It would not see the RAID I had created.
    Tried every driver I could find. Tried drivers from the "Station Drivers" website. Tried Marvell drivers for the same chip from the ASUS website. No luck. Tried loading from CD as well as USB flash drive. Always the same result...  Windows would find
    the drivers appropriate for the hardware found, I would select the RAID version, and after a few seconds, would report that the drivers were unsigned, and the installation was not supported for 64-bit drivers. Clicking OK would take me back to the load drivers
    display with no new drives listed in the available drives window.
    I tried hitting F8 during startup, and selected the "allow install of unsigned drivers option". That didn't do ANYTHING. Still the same error.
    Someone suggested putting the drivers in the root directory. That didn't work.  I also disabled all other drives except one CD rom and a USB drive and made sure that my RAID array was the first drive in the boot list.
    Tried doing a windows repair, as someone else suggested. (This is an option that is available on the install disk I am using. It's enabled as part of EMS (emergency management services) in setup. Anyway, this was reported to be a workaround
    to the signed driver issue. It would allow me to browse to the individual files, but no matter which one I selected, the response was "cannot find hardware appropriate to the driver selected" or some such nonesense. So I gave up on that.
    Doing the install with the controller in IDE mode with just one drive connected, would result is Windows installing without a hitch. The problem was clearly when I presented 64-bit windows with a controller in RAID mode.
    Long story less long, here's what worked for me....
    Out of desperation, I began trying other subfolders in the driver lists. The Gigabyte manual indicated that the AMD64 subfolder was the correct one for the Marvell controller, when using RAID mode with 64-bit Windows. After trying every subfolder of
    every driver I could find, the driver in the i386 folder actually worked. It initially came back with the same error about unsigned drivers, but after clicking OK, my RAID drive showed up in the list. I have been able to partition and format
    the drive from within Windows setup, and am continuing with the install now. Hopefully won't be any problems booting from the drive post install, but so far it looks good, and I'm relieved that I was able to get it this far.
    The whole process has been one of the most frustrating computing experiences I've ever had. This is what it was like back in the 90's when building PCs from scratch.  I'm amazed that in this day and age the process is still so poorly documented
    and filled with potholes, traps and caveats. Shame on the entire PC industry for allowing this to continue. I'm not asking that they jump in and try to automate it and do all the thinking for me (their solution for everything lately)...all I'm asking for it
    clear, concise and accurate INFORMATION.
    With the right information, and software that provides accurate feedback, this would all be easy...and even fun.
    Hope this helps someone faced with the same problem.

  • Raid 0 problem 890gxm-G65

    Hello, I've been trying things with my pc for hours but I still don't know what is going wrong.
    -I've 2 identical hdd's in sata slots
    -I didn't get any option to ctrl + f, so i downloaded: (32 bit) ATI SB7xx/SB8xx RAID Driver from msi
    -I put the drivers on my USB stick, booted from it and it installed?? (to where?) a program: raid option rom version 3.2.1540.6 (i downloaded the 32 bit version... my guess now that my usb flashed the bios for raid drivers? but I flashed the wrong bit version, I want to use 64 bit. though it seems strange to me that drivers in Bios are 32 / 64 bit related? since bios flash downloads aren't.)
    -I put the 64 bit ATI SB7xx/SB8xx RAID Driver on my USB stick to see if it installed automatically, to bad... it didn't it says (find another boot device or something like that)
    -I made an LD works all fine, it says Functional 1.999 TB or something.
    -Booting windows installation, can't find the logical drive array, I think: ''no problem I have the drivers.''
    -Installed the driver (load driver option) that came with ATI SB7xx/SB8xx RAID Driver [AMD AHCI Compatible RAID Controller (D:\ahcix64s.inf) (x64), but still no recognition.
    Is all this going wrong due to a wrong bios update? Or whatever I did with the 32 bit?? Driver software that made the raid array?
    My option in the bios AHCI/RAID/IDE = Raid
    Raid chip = enabled
    While losing my mind hehe, I thought the software should be stored in the bios, with formatted harddisks where else could they be? So I
    -flashed the bios to version 1.9 with a fat32 flash function in the bios (n-flash i think)
    but I still have that stupid ''raid option rom version 3.2.1540.6'' (32 bit download) Which I expect is the problem here, but I'm raid noob lol.
    -Windows does recognize my harddrives when I do IDE instead of RAID in bios.
    Questions: Why doesn't Windows 7 recognize my raid array after installing 64 bit raid drivers? Is it due to wrong bios software [raid option rom version 3.2.1540.6]? How can I fix this?
    I'm totally lost please help me...
    Greetings,
    Sten

    Quote from: Sabbath on 20-July-11, 23:41:24
    Ok,
    So if the 64bit driver I linked is seen during your windows install and at that time correctly accepted, as w7 continues its install till its complete, I don't understand why there is a 32 bit pop up.
    That is why I suggested starting over being you did install at some point a 32 bit driver.
    Does your msi resource CD have a raid driver on it?
    When I did my msi raid, I installed my raid driver from msi's site during install and after I was in windows I needed to complete it by installing a raid driver off the CD.
    This removed all yellow flags in device manager concerning my raid.
    It is accepted, i suppose it's complete. But the 64 bit driver installs 4 times quicker than the 32 bit version. So maybe W7 doesn't install the 64 bit driver good enough? I can't install w7 at all since it can't find any harddrives to install on. I would like to start over, but I don't know how to delete the 32 bit driver... Formatting harddrives doesn't delete the driver, and bringing bios settings to default neither. I flashed the bios to 1.9 which didn't help aswell. If I mark the button  ''shows only hardware compatible drivers'' my original msi cd doesn't give any drivers. Though there are drivers on it, but they aren't compatible... Should I flash my bios back to 1.0? Hopefully it will delete all its extra features like raid array. And then I install it with the correct 64 bit driver. But it seems weird that the problem is there... Since it seems logical to me that the bios doesn't work on 32bit / 64 bit programms.
    Are there risks concerning flashing the bios back to version 1.0? Would it help? I would like to know where the driver is located... where does it get installed? Did I accidently indeed flashed my bios by booting with the driver usb, how can it be deleteD? And is that the problem? Meh! Thanks for your help Sabbath, appreciated ^^ Isn't there a moderator or technician from MSI on these forums that can help me?

  • Internal RAID Drives Disappeared from Desktop & Finder

    A few days ago, one of my two internal mirrored RAID sets no longer showed on the desktop or in the Finder Sidebar. A day later, the other internal RAID set disappeared from desktop and sidebar. The two remaining internal non-RAID drives show up as do two external drives. All internal and external hard drives still show under Disk Utility and Photoshop Bridge CS3.
    I checked Finder Preferences and boxes are checked to show internal and external drives on the desktop and sidebar. I looked at the drive detail under Disk Utility and nothing looks wrong with the two RAID sets ON-LINE. I unmounted one RAID set and re-mounted without any change. I tried unchecking the two preference boxes to not show the drives and rebooted, rechecking the boxes and rebooting and nothing changed on the desktop or sidebar.
    Does anyone have any suggestions to resolve this?

    Well our invisible drives problem is resolved but it's not the solution that I'd hoped for.
    We visited the Genius Bar at a local Apple store and they denied any knowledge of problems with invisible drives in Macs and discounted my reports from Mac forums.
    I went home and ordered a new 1tb Seagate drive. When it arrived, I installed it in bay 2, copied each invisible drive to the new drive one-at-a-time, broke my two sets of internal mirrored drives, erased all the affected drives and reloaded them. Now all drives are visible on the Desktop and Finder again.
    I'm hoping that the disappearing drive problem doesn't surface again but view this as an unresolved Apple issue. Now I can look at other mass storage options for future growth.

  • RAID DRIVE WON'T WORK IN LINK MEDIA BROWSER

    I have a RAID 5 drive connected to my MACPRO (MacPro5,1), OSX 10.9.2. Its working fine on OS. In Premiere Pro CC I can import files from it no problem, everything seems to be fine until I try to link media from it. The link media browser won't access it. I can see it, I can see the RAID drives icon, but it won't access the files.
    In the link media browser it won't show on the Local Drives list on the left pane. When I double click on local drives, on the right pane I can see the RAID HD icon, but when I click on it it won't open it. It knows its there but can't access it. I don't get it. I can import files from it, etc, but not link files. I would have to redo the whole sequence with files from that RAID drive and its days of work.
    I would appreciate enormously any help with this issue.

    Adobe CC 2014 v8.1
    iMac 27"  3.4GHz w/12GB Ram.
    OS 10.9.5
    OWC Mercutry ELite Pro Dual.
    RAID 0
    Thunderbolt.
    No adapters or daisy chaining going on.
    The RAID is new and only has about 700GB of data on it.
    I read on Creative Cow that alexojedav522 was able to figure out that the size of the drive was his issue:
    https://forums.creativecow.net/thread/3/954245
    After reading that I tried repartitioning my RAID into two sections of 2tb each (let's call them Partition1 and Partition2).
    So Partition1 is just the original partition (which was 4TB) shrunken down to 2TB.
    Partition2 is the brand new partition.
    Oddly enough, I can access Partition2 via Media Browser just fine.
    And when I move media onto it I can relink it as well).
    But Partition1 is still not accessible via Premiere at all.
    I am currently moving everything off of Partition1 and onto Partition2, so that I can at least relink my project and get to work.
    But obviously that isn't a permanent solution.

Maybe you are looking for