beetof Posted October 18, 2009 Report Share Posted October 18, 2009 Configuration: XPpro in RAID0, 2GB DDR2, GA-P35-DS3R, hardware firewall, PCtools firewall, Avast free.Few days ago, I got suddenly a flash of a blue screen and the PC rebooted. The boot stopped with the mesage: Disk boot failure, insert system disk. I tried several times to reboot, no success.Next day, the computer booted normally. I worked for several hours, then crash. At a certain time I saw a blue screen with STOPcode 0x0000007B (0xF78D2524, 0xC0000034, 0x00000000, 0x00000000). Impossible to reboot afterwards.Yesterday morning it started up but crashed after a minute. Few hours later I could boot again, but only for a very short time.It went like this:Boot to desktop screen, then blue screen in a flash and reboot. Very slow in first lines (Controller Post00 HD, Post01 no device, Post02 cdrom, Post03 HD, etc.).Volume0 Raid0 (stripe) failed.Disk boot failure, insert system disk and press enter.Entering an installation disk starts Windows setup - loading files for several minutes - Setup is starting Windows - STOP 0x0000007B. The same sequence happens every time.0x0000007B points to masterbootrecordvirus, conflicts in devices or controllers or bad disk.The fact that 'working time' became shorter everytime points to bad disk, I think. But I can't run chkdsk, and, as it is raid0, I think I can't take out one disk to run chkdsk on another computer. Right?Someone who can help? Quote Link to comment Share on other sites More sharing options...
-pops- Posted October 18, 2009 Report Share Posted October 18, 2009 Intermittent or variate faults are the most difficult to diagnose but the behaviour of working/not working and the stop error code suggests to me a failing hard drive (=bad disk).I've always avoided RAID setups but isn't this the kind of thing that RAID is designed to avoid?I think you should be able to test the drive in another machine - there is no harm in trying but I think you ought to be prepared to shell out for a new drive.What you may find is that the drive can be resurrected as a subsidiary or scratch drive when you have installed a new main drive in its place and then reformatted/repaired that one.Have you seen this, BTW? http://support.microsoft.com/kb/324103 Quote Link to comment Share on other sites More sharing options...
Irene Posted October 18, 2009 Report Share Posted October 18, 2009 Might be some help HERE. :) Quote Link to comment Share on other sites More sharing options...
beetof Posted October 18, 2009 Author Report Share Posted October 18, 2009 I've always avoided RAID setups but isn't this the kind of thing that RAID is designed to avoid?Raid0 gives higher speed of writing. Half is written to one disk, the other half to a second. Raid1 is designed for safety. Data are written to both disks.I think you should be able to test the drive in another machineI'm not sure of that, because one disk contains only half of the data. Can chkdsk handle that?Have you seen this, BTW? http://support.microsoft.com/kb/324103Yes, from this article I concluded the possible causes of the error. But thanks anyway.Thaks to you too, Irene. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.