We help IT Professionals succeed at work.

iastor.sys corrupt

andyberg
andyberg used Ask the Experts™
on
I have a Tyan Tempest i5000xl dual xeon board.  Wouldn't boot so I put in the
XP64 install disk.  During setup I get message iastor.sys corrupt.  I gather from reading solutions this means sata drivers not being loaded.  That makes sense since later error message says no hard disks

I've read that you download the sata driver to a floppy.  I can do that- I have another computer with a floppy and the computer in question has a floppy.  Can't find the download.  Also read something about Tyan having SATA built in to the board. I don't know what that means or how this all fits together.

One more fact.  Other error message I get is no mass storage device.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
dbruntonQuid, Me Anxius Sum?  Illegitimi non carborundum.

Commented:
First step is to test your memory.  Bad memory can cause this problem.

Get the UBCD http://www.ultimatebootcd.com/

Download links are the icons at the top of the page above Overview.  Browse the page and see what utils are there for you.  Check the memory utils especially.

Make the CD and boot from it.  Run the memory tester first - memtest -  and let it do two to three passes through your memory.  Memory could be the problem so get that test done first.

Quid, Me Anxius Sum?  Illegitimi non carborundum.
Commented:
If the memory tests OK look at using nLite http://www.nliteos.com/ to slipstream the iastor drivers into it.

And the drivers are

http://www.intel.com/support/chipsets/imst/sb/cs-020825.htm

http://downloadcenter.intel.com/Detail_Desc.aspx?ProductID=2101&DwnldID=18861&lang=eng&iid=dc_rss

>> Other error message I get is no mass storage device.

That will because it can't find the iastor.sys driver.
Top Expert 2013
Commented:
since it could not find the disks " since later error message says no hard disks", i would also test them - find all diags for it on the above mentioned UBCD.
note it can be a bad disk, cable, or controller (on mobo) !
post results