- Feb 8, 2012
- 74
- 0
- 18,630
Well I need to start at the beginning of this whole fiasco.
Firstly I have a Asus P9X79 WS. I'm running a Samsung 256GB 840 Pro SSD on an intel SATA port and two WD Caviar Black 500GB drives in RAID0. They have been working fine together for about 4 months.
Just yesterday I was having issues with the RAID0 drive (considered one accessible drive in windows) kept disconnecting when used. This happened in a relatively short period of time. I was playing a game off of the RAID0 and it would crash. Every consecutive time trying to run the RAID array again it would crash quicker and quicker. It came to the point where it would disconnect just by browsing the file contents of the array.
I assumed at this point that one of the drives of the array had gone bad. I was fine with this and was just going to take the drives out of RAID0 in the Marvell Raid Utility by clicking CTRL+M at boot. When I shutting off my computer to do this my installation of Windows 7 hung at the "shutting down" screen. It was very peculiar since I had an SSD, shut down times should not have taken as long as they did. So as a result of this hanging at the shut down I manually held down the power button on my computer case.
When booting up after manually shutting down my motherboard could not POST. It got stuck at the Q-Code 67. I intuitively disconnected the RAID0 drives and all of a sudden I could POST again. Problem was this time is that when I went to boot into Windows I would then get a BSOD on the boot screen. The BSOD's BCC code was 7E. I tried to reboot again. This time I was given the option to use startup repair. I chose this option and it tried repairing my installation of Windows 7. Unfortunately it came to no avail.
My thoughts at this time believed that the motherboard was dying in some sort of way, but with the ability to use startup repair without crashing I thought maybe it was just that Windows was corrupted. So I decided to go out on a limb and try to reinstall Windows. I installed Windows 8.1 Pro but this may be irrelevant. Anyways I got Windows 8.1 Pro to install fine on my SSD and this is what I'm using now to type this message.
Now at this point I thought, "it must have been Windows 7 that couldn't detect my RAID array. It must have been a corruption or maybe a Trojan. Oh well!".
After stabilizing my computer to at least get Windows to boot again I decided to reconnect the hard drives. What I have found at this point is that if I connect any one of the two hard drives used in the RAID0 array to the Marvell ports that it will not post. When it refuses to post it always gives me the same Q-Code of 67.
So at this point I'm thinking that the Marvell SATA chip died on my board. When I first installed my hard drives to enable RAID0 I was prompted to hit CTRL+M (when booting) to configure my RAID0 array. During every boot (as far as I remember at least) I was given this prompt every time. However I only had this prompt when both drives were connected to the Marvell ports.
I haven't tested another hard drive in the Marvell ports as of yet. Basically I just want to regain control of my Marvell SATA ports. I need to be able to POST with my drives connected and I also need to view the Marvell RAID Utility (CTRL+M). I'm assuming methods for fixing this may be forcefully updating the firmware on the Marvell chip? Any ideas or ways to fix this? Does anyone know what is going on?
PS. I believe that the corrupted Windows installation may be unrelated to my issue. I think I corrupted it when shutting down manually.
Firstly I have a Asus P9X79 WS. I'm running a Samsung 256GB 840 Pro SSD on an intel SATA port and two WD Caviar Black 500GB drives in RAID0. They have been working fine together for about 4 months.
Just yesterday I was having issues with the RAID0 drive (considered one accessible drive in windows) kept disconnecting when used. This happened in a relatively short period of time. I was playing a game off of the RAID0 and it would crash. Every consecutive time trying to run the RAID array again it would crash quicker and quicker. It came to the point where it would disconnect just by browsing the file contents of the array.
I assumed at this point that one of the drives of the array had gone bad. I was fine with this and was just going to take the drives out of RAID0 in the Marvell Raid Utility by clicking CTRL+M at boot. When I shutting off my computer to do this my installation of Windows 7 hung at the "shutting down" screen. It was very peculiar since I had an SSD, shut down times should not have taken as long as they did. So as a result of this hanging at the shut down I manually held down the power button on my computer case.
When booting up after manually shutting down my motherboard could not POST. It got stuck at the Q-Code 67. I intuitively disconnected the RAID0 drives and all of a sudden I could POST again. Problem was this time is that when I went to boot into Windows I would then get a BSOD on the boot screen. The BSOD's BCC code was 7E. I tried to reboot again. This time I was given the option to use startup repair. I chose this option and it tried repairing my installation of Windows 7. Unfortunately it came to no avail.
My thoughts at this time believed that the motherboard was dying in some sort of way, but with the ability to use startup repair without crashing I thought maybe it was just that Windows was corrupted. So I decided to go out on a limb and try to reinstall Windows. I installed Windows 8.1 Pro but this may be irrelevant. Anyways I got Windows 8.1 Pro to install fine on my SSD and this is what I'm using now to type this message.
Now at this point I thought, "it must have been Windows 7 that couldn't detect my RAID array. It must have been a corruption or maybe a Trojan. Oh well!".
After stabilizing my computer to at least get Windows to boot again I decided to reconnect the hard drives. What I have found at this point is that if I connect any one of the two hard drives used in the RAID0 array to the Marvell ports that it will not post. When it refuses to post it always gives me the same Q-Code of 67.
So at this point I'm thinking that the Marvell SATA chip died on my board. When I first installed my hard drives to enable RAID0 I was prompted to hit CTRL+M (when booting) to configure my RAID0 array. During every boot (as far as I remember at least) I was given this prompt every time. However I only had this prompt when both drives were connected to the Marvell ports.
I haven't tested another hard drive in the Marvell ports as of yet. Basically I just want to regain control of my Marvell SATA ports. I need to be able to POST with my drives connected and I also need to view the Marvell RAID Utility (CTRL+M). I'm assuming methods for fixing this may be forcefully updating the firmware on the Marvell chip? Any ideas or ways to fix this? Does anyone know what is going on?
PS. I believe that the corrupted Windows installation may be unrelated to my issue. I think I corrupted it when shutting down manually.
Facebook
Twitter
Instagram