Windows 2003 x64 crashing with “probably caused by: iaStor.sys”

bsodintelwindows-server-2003

My 2-year old mail server started crashing with BSOD about 2 months ago, and every time you check memorydump it says "Probably caused by : iaStor.sys ( iaStor+4b676 )".

Initially it ran with Intel Storage manager version 8.6, then I upgraded to 8.8, today it's at 8.9, still same problem.

Server is Tyan, out of warranty. Latest BIOS.

Windows Update is not working right now, but should be fairly up to date.

RAID is 1 (main data) and 0 (backup), 4 750GB drives total.

It runs Exchange 2007, Sharepoint v3 and Backup Exec V12.5.

As far as I know nothing changed – no drivers, no software, no hardware. I tried updating everything I could find (software-wise), no dice.

Everytime it crashes like that Intel starts rebuilding the Mirror. Data doesn't seem to be affected.

Server can go as little as 1.5 hours and as long as 1 week between crashes. Last data is 15 BSODs in a month.

Tried researching via google, via intel's site, tried disabling 1 USB which had same IRQ as Intel controller, updated BIOS, nothing.

Any ideas?

Thanks!

Best Answer

What OS are you running? 2003? 2008? SBS?

Just off the top of my head, it could be:

  • Driver issue: corrupt driver? Maybe rollback to a previous version?
  • BIOS setting: can you look at the storage controllers setting at boottime (assuming you have hardware RAID). Maybe there's a setting that needs adjustment.
  • Bad disk: I doubt that the hard drives are bad, but it wouldn't hurt to check or do some sort of disk scan offline and see what's what. Eliminate this option.
  • SATA/SAS wiring: I don't know which exact controller you use or bus type, but maybe (and it's highly unlikely) there's something wrong with the SATA/SAS wiring. Frayed maybe?
  • I/O port: try switching the physical cables/ports to see if it's a specific problem with the interface. Again, another uber-rare issue, but I've had this happen before.

Hope this helps. Please add more detailed information as that might help clue us in on what the problem may be.

Related Topic