Skip to main content

System Crash after disabling drive surveillance

Beginner
Posts: 1
Comments: 3

Hello together,

I had a severe system crash, including RAID degradation on my Win XP Professional Box after disabling internal drive monitoring.

Drive monitor could not read out S.M.A.R.T. Parameters of a iastor.sys controled HW(?)-RAID (SATA) on my ASUS Motherboard.

So I decided to disable monitoring of this drive and only monitor external eSATA drive, where the backups are stored (this drive crashed 2 weeks ago with sector write errors during Acronis-Backup).

After pressing "okay" in the drive-monitor window, the system crashed with a blue-screen and the described RAID degradation. The reconstruction of the RAID I lasted 7 hours (which is, I think normal).

So I uninstalled the drive-monitor. Now the system runns normal again (obviously).

I think that the windows-component "iastor.sys" is the problem.

Did anyone else have similar experience?

Best regards
Frank
Saarbrücken

Forum Hero
Posts: 613
Comments: 8747

Frank,

Do you by any chance recall either the message or error number on the Blue Screen?

Beginner
Posts: 1
Comments: 3

Hi Colin,

I took a picture with my mobile-phone:
(I will post it, next time I sync it with my desktop)

The error message was:

...
DRIVER_IRQL_NOT_LESS_OR_EQUAL
...
technical information:
*** STOP: 0x000000p1 ...
*** iastor.sys - Address F7859A06 base at F7B17000, DateStamp 46ff320c

Frank

Beginner
Posts: 1
Comments: 3

Hi Colin,

here's the "bluescreen-snapshot".

Regards
Frank

Attachment Size
58808-94288.jpg 227.08 KB
Forum Hero
Posts: 613
Comments: 8747

Frank,

OK the problem looks to be your RAID driver. IASTOR.sys belongs to the Intel Matrix Storage Driver.

How or why it became corrupted with ADM I don't know.

Hopefully Acronis might look in and let their development team know.

Beginner
Posts: 1
Comments: 3

Colin,

hope so too!

Thanks for your comments.

By

----------
Frank

Forum Star
Posts: 24
Comments: 3268

Hello FrankO and Colin!

Thank you for your comments! Colin, thank you for assistance!

I have checked our internal databases: there are no known issue matching your description, so we need Development attention here. I have just sent them the details of the problem, and the link to the thread. They will check it and either post the reply here, or send us the update regarding the situation.

In both cases we will update the thread with the latest information available.

Please accept our sincere apologies for the inconvenience faced. Rest assures we will do our best to speed up the process of resolution.

Should you need anything else or have any further questions - feel free to contact us at your earliest convenience, we will be happy to help you!

Thank you!

Forum Star
Posts: 24
Comments: 3268

Hi all!

Thank you for your patience.

FrankO, I've received a reply from the Development team, and they are working on reproducing the issue, but they will need additional information. Could you please specify us the following? 

  1. What is the version of the drive? 
  2. What is the level of the RAID? 
  3. Please go to Start => Run 0 => msinfo32 and hit Enter
    This will get you to the system information.
    Select File - > Save as
    and send us the file created

This information will help to shed the light onto the situation.

Please let us know if you have any questions or concerns.

Thank you!