Sign in with
Sign up | Sign in
Your question

IaStor.sys BSOD - have tried everything

Last response: in Windows XP
Share
May 3, 2011 2:53:34 AM

2 days after the big windows April updates I started getting an iaStor.sys BSOD every few days. It only happens when I'm away from the computer (it's on 24/7), never while I'm using it. This is on a Dell desktop running XP.

Here's the relevant snippet from the dump file:

Quote:

Unable to load image iaStor.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys


I started with the basics. No malware or viruses. I ran memtest and checked the drives (RAID 1) using the disk check at startup. Everything checked out here.

But when I use chkdsk it gets weird...

chkdsk reports errors, so I run chkdsk /f and it says everything is fixed. Then I reboot and run chkdsk again and it reports the same problems again. Here's what chkdsk is saying:

Quote:

CHKDSK is verifying Usn Journal ...
Repairing Usn Journal file record segment.
Usn Journal verification completed.
Correcting errors in the Volume Bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.


I've tried re-installing Intel Matrix Storage Manager and re-doing all of the above, but still nothing. chkdsk still keeps reporting errors, and the computer keeps crashing every few days when I'm not actively using it.

Seems like a drive going bad no? I just replaced one of the drives about 2 months ago, and the other is about 2 years old. I'm just at a loss for what to do here.

Any ideas?

Here's the full minidump:

Quote:

Unknown bugcheck code (8086)
Unknown bugcheck description
Arguments:
Arg1: 00000000
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

Debugging Details:
------------------


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8086

PROCESS_NAME: services.exe

LAST_CONTROL_TRANSFER: from b7d92e55 to 804f9f1e

STACK_TEXT:
b84cfe60 b7d92e55 00008086 8afd8000 8abf3302 nt!KeBugCheck+0x14
WARNING: Stack unwind information not available. Following frames may be wrong.
b84cfe88 b7d5d7dc 8afd8000 8052b99c 8af8d000 iaStor+0x39e55
b84cff24 b7d5e3b5 8af8d000 ffdff000 8aff4008 iaStor+0x47dc
b84cffbc b7d98faf 8af8d000 00000000 ffdff980 iaStor+0x53b5
b84cffcc 80545eef 8afd8728 8afd8000 00000000 iaStor+0x3ffaf
b84cfff4 80545a5b ae39cd44 00000000 00000000 nt!KiRetireDpcList+0x61
b84cfff8 ae39cd44 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2b
80545a5b 00000000 00000009 0081850f bb830000 0xae39cd44


STACK_COMMAND: kb

FOLLOWUP_IP:
iaStor+39e55
b7d92e55 ?? ???

SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: iaStor

IMAGE_NAME: iaStor.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 46a947b4

SYMBOL_NAME: iaStor+39e55

FAILURE_BUCKET_ID: 0x8086_iaStor+39e55

BUCKET_ID: 0x8086_iaStor+39e55

Followup: MachineOwner

More about : iastor sys bsod

May 3, 2011 3:22:31 AM

I've done that, except using a more recent version of Intel Matrix Storage Manager. The one that came on the computer is 7.6.1 so that's the version I performed those steps with. The version they link to in that post is really old - it's like version 5 something. Installing that seemed like a bad idea to me. My computer has worked flawlessly until a few weeks ago... I can't imagine that reverting to an old outdated version of the driver would fix it...
m
0
l
!