- Joined
- Jul 22, 2002
- Location
- USMC.. OoRah!!
Hey guys,
I've run into some issues here. My computer started BSODing the other day with the BSOD message saying iastor.sys caused it. It also has BSOD'ed with the stop error of:
I figured my RAID array was broken, so I went to reinstall Windows. I get through the DOS-based part, reboot, and begin the next part of the install (where you specify your language, name, CD-Key, etc). It installs for a couple minutes and then boom! BSOD- iastor.sys. I reboot and have to begin the install all over again. Same thing happens. I try again. I get the above stop error. So I figure its a bad/corrupt iastor.sys file or CD. I unplugged all my HD's except one of my Raptors and disabled RAID in my BIOS. I manage to get Windows 2000 installed so I can use nlite to make a new CD. I download the latest ICH9R Driver (dated 5/7/2008) and integrate it into my XP install CD. I reboot and re-enable my RAID and boot from my New, updated CD. SAME THING. I get to the second part of the install and I get a BSOD saying it was caused by iastor.sys!! I reboot and try again. Same thing, same stop error (0xF4).
I reboot, disable my RAID, and boot from my new XP CD. This time, I manage to install XP onto just one HD. Everything is going fine. I'm installing my apps, drivers, etc. And then the system hangs and guess what? I get the SAME FREAKING BSOD - iastor.sys!!! I reboot and start installing my apps again and I get another BSOD- 0xF4. : :
Ok so by this time, I'm thinking its just XP being stupid. I try installing Vista x86 and x64, both with the same result. They take forever to extract the install files, and hang upon reboot, saying that hal.dll was not installed correctly and Windows Setup cannot continue. Now I'm thinking its my HD's going south of the border or my motherboard is going south. I rolled back my BIOS to the previous one, hoping that would maybe help, but nope.
So my question to you guys is this: Is this my HD's going south? or is it my motherboard going south? I personally find it hard to believe that my Raptors would BOTH go south at the same time. Right before the BSOD's, the HD light is on solid. When I do manage to get XP installed, upon reboot it proceeds to scan my storage HD (250GB) for errors and starts to replace indexes, etc for a LONG time. Is it possible that these BSOD's are being caused by Windows trying to access my storage drive? I don't think so because when I installed XP to one raptor and have the other HD's disconnected, it still BSOD's.
Please help!!!
I've run into some issues here. My computer started BSODing the other day with the BSOD message saying iastor.sys caused it. It also has BSOD'ed with the stop error of:
0xF4 - Termination of system-critical process or thread If a system-critical program or object stops running, you get this blue screen of death. This is almost certainly a pure software problem. For what it's worth, the first parameter can tell you if the object that was killed was a process (0x03) or a thread (0x06). This is another "die immediately if this happens" error. Check your system file integrity (sfc /scannow), or back up the things that are really important to you and start fresh.
I figured my RAID array was broken, so I went to reinstall Windows. I get through the DOS-based part, reboot, and begin the next part of the install (where you specify your language, name, CD-Key, etc). It installs for a couple minutes and then boom! BSOD- iastor.sys. I reboot and have to begin the install all over again. Same thing happens. I try again. I get the above stop error. So I figure its a bad/corrupt iastor.sys file or CD. I unplugged all my HD's except one of my Raptors and disabled RAID in my BIOS. I manage to get Windows 2000 installed so I can use nlite to make a new CD. I download the latest ICH9R Driver (dated 5/7/2008) and integrate it into my XP install CD. I reboot and re-enable my RAID and boot from my New, updated CD. SAME THING. I get to the second part of the install and I get a BSOD saying it was caused by iastor.sys!! I reboot and try again. Same thing, same stop error (0xF4).
I reboot, disable my RAID, and boot from my new XP CD. This time, I manage to install XP onto just one HD. Everything is going fine. I'm installing my apps, drivers, etc. And then the system hangs and guess what? I get the SAME FREAKING BSOD - iastor.sys!!! I reboot and start installing my apps again and I get another BSOD- 0xF4. : :
Ok so by this time, I'm thinking its just XP being stupid. I try installing Vista x86 and x64, both with the same result. They take forever to extract the install files, and hang upon reboot, saying that hal.dll was not installed correctly and Windows Setup cannot continue. Now I'm thinking its my HD's going south of the border or my motherboard is going south. I rolled back my BIOS to the previous one, hoping that would maybe help, but nope.
So my question to you guys is this: Is this my HD's going south? or is it my motherboard going south? I personally find it hard to believe that my Raptors would BOTH go south at the same time. Right before the BSOD's, the HD light is on solid. When I do manage to get XP installed, upon reboot it proceeds to scan my storage HD (250GB) for errors and starts to replace indexes, etc for a LONG time. Is it possible that these BSOD's are being caused by Windows trying to access my storage drive? I don't think so because when I installed XP to one raptor and have the other HD's disconnected, it still BSOD's.
Please help!!!