BSOD Occurs Randomly iaStorA.sys

[aqscithe]

Based on the BSOD I know that the iaStorA.sys file is the culprit and I've updated to the latest Intel Rapid Storage drivers. Unfortunately that hasn't helped. I also cant even do disk checks or a system restore becuz the BSOD always interrupts them. The BSOD also seems to occur randomly. Sometimes im playing a game and other times im just surfin the web but it usually occurs w/in 35 minutes of me turning the computer on.

I really appreciate your help.

 

[Arc]

Last time I have suggested you a particular version of RST. But later on that driver got removed from intel's download page. Probably they have found some issues with that one, too.

In such a situation, I would suggest you to get rid of intel rapid storage. First uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.

1. Right click on "my computer" icon and click "manage" on the context menu.
2. It will open the "computer management" window.
3. Select "Device Manager" in the left pane, It will list all the existing devices up.
4. Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
5. Select one Intel device item under it, right click, uninstall.
6. Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
7. Now restart the computer. At restart, windows will auto configure the appropriate native system driver.

Also Disable RAID in the BIOS.

Let us know the results.

Edit: (koolkat77 already added this point, too ) Make it sure that the Samsung SSD PM830 mSATA is running with the up to gate firmware. Also, I am wondering ... is it really 8 GB one?

Model    SSD PM830 mSATA SCSI Disk Device
Size    8.00 GB (8,587,192,320 bytes)
Partition Size    8.00 GB (8,587,837,440 bytes)

___________________________________________________________________________
BSOD ANALYSIS:

*** WARNING: Unable to verify timestamp for iaStorA.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880016925e8, fffff880045e57e8, fffff880045e5040}

Probably caused by : iaStorA.sys ( iaStorA+665e8 )

Followup: MachineOwner
---------

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880016925e8, The address that the exception occurred at
Arg3: fffff880045e57e8, Exception Record Address
Arg4: fffff880045e5040, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
iaStorA+665e8
fffff880`016925e8 488b4a38        mov     rcx,qword ptr [rdx+38h]

EXCEPTION_RECORD:  fffff880045e57e8 -- (.exr 0xfffff880045e57e8)
ExceptionAddress: fffff880016925e8 (iaStorA+0x00000000000665e8)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000038
Attempt to read from address 0000000000000038

CONTEXT:  fffff880045e5040 -- (.cxr 0xfffff880045e5040)
rax=00000000ffe7c49e rbx=fffffa800acb69a0 rcx=fffffa800acb69a0
rdx=0000000000000000 rsi=fffffa80119b04d4 rdi=fffffa800897f000
rip=fffff880016925e8 rsp=fffff880045e5a20 rbp=fffffa800897f750
 r8=fffffa80119b04d4  r9=0000000000000000 r10=fffffa800897f388
r11=fffffa800897f000 r12=fffffa8007745670 r13=fffff88001647520
r14=0000000000000000 r15=fffff880009b8040
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
iaStorA+0x665e8:
fffff880`016925e8 488b4a38        mov     rcx,qword ptr [rdx+38h] ds:002b:00000000`00000038=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000038

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003103100
GetUlongFromAddress: unable to read from fffff800031031c0
 0000000000000038 Nonpaged pool

FOLLOWUP_IP: 
iaStorA+665e8
fffff880`016925e8 488b4a38        mov     rcx,qword ptr [rdx+38h]

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from 0000000000000001 to fffff880016925e8

STACK_TEXT:  
fffff880`045e5a20 00000000`00000001 : fffffa80`0ac28ae8 fffffa80`0ac28ae8 fffff880`01693a0a fffffa80`0897f000 : iaStorA+0x665e8
fffff880`045e5a28 fffffa80`0ac28ae8 : fffffa80`0ac28ae8 fffff880`01693a0a fffffa80`0897f000 fffff880`0167a3f1 : 0x1
fffff880`045e5a30 fffffa80`0ac28ae8 : fffff880`01693a0a fffffa80`0897f000 fffff880`0167a3f1 fffffa80`0acb69a0 : 0xfffffa80`0ac28ae8
fffff880`045e5a38 fffff880`01693a0a : fffffa80`0897f000 fffff880`0167a3f1 fffffa80`0acb69a0 fffffa80`119b04d4 : 0xfffffa80`0ac28ae8
fffff880`045e5a40 fffffa80`0897f000 : fffff880`0167a3f1 fffffa80`0acb69a0 fffffa80`119b04d4 fffffa80`08251278 : iaStorA+0x67a0a
fffff880`045e5a48 fffff880`0167a3f1 : fffffa80`0acb69a0 fffffa80`119b04d4 fffffa80`08251278 fffff880`0167a2a7 : 0xfffffa80`0897f000
fffff880`045e5a50 fffffa80`0acb69a0 : fffffa80`119b04d4 fffffa80`08251278 fffff880`0167a2a7 fffff880`016be218 : iaStorA+0x4e3f1
fffff880`045e5a58 fffffa80`119b04d4 : fffffa80`08251278 fffff880`0167a2a7 fffff880`016be218 00000000`00000000 : 0xfffffa80`0acb69a0
fffff880`045e5a60 fffffa80`08251278 : fffff880`0167a2a7 fffff880`016be218 00000000`00000000 00000000`00000000 : 0xfffffa80`119b04d4
fffff880`045e5a68 fffff880`0167a2a7 : fffff880`016be218 00000000`00000000 00000000`00000000 00000000`00000018 : 0xfffffa80`08251278
fffff880`045e5a70 fffff880`016be218 : 00000000`00000000 00000000`00000000 00000000`00000018 fffff880`ffe7c49e : iaStorA+0x4e2a7
fffff880`045e5a78 00000000`00000000 : 00000000`00000000 00000000`00000018 fffff880`ffe7c49e fffff880`0167a19d : iaStorA+0x92218


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  iaStorA+665e8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: iaStorA

IMAGE_NAME:  iaStorA.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5175919d

STACK_COMMAND:  .cxr 0xfffff880045e5040 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_iaStorA+665e8

BUCKET_ID:  X64_0x7E_iaStorA+665e8

Followup: MachineOwner
---------

4: kd> lmvm iaStorA
start             end                 module name
fffff880`0162c000 fffff880`018fd000   iaStorA  T (no symbols)           
    Loaded symbol image file: iaStorA.sys
    Image path: iaStorA.sys
    Image name: iaStorA.sys
    Timestamp:        Tue Apr 23 01:08:05 2013 (5175919D)
    CheckSum:         000B3756
    ImageSize:        002D1000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[koolkat77]

Is the firmware for your SSD up-to-date?

Check for one and see if the stability returns.

 

[aqscithe]

I appreciate the quick response.

I uninstalled the Intel Rapid Storage Tech program but IDE ATA/ATAPI controllers is not listed in the device manager.

Also I couldn't find RAID in the BIOS. I eventually figured out that it is sometimes listed under the SATA label but the only options were ATA, AHCI and Intel Smart Response Technology. Intel option is enabled. The other two would not allow windows to load.

My hard drive firmware seems to be up to date( used the 'check for drivers' option in device manager) but I will keep checking online becuase the check isn't always reliable.

And yes it is the 8GB one.

 

[Arc]

I uninstalled the Intel Rapid Storage Tech program but IDE ATA/ATAPI controllers is not listed in the device manager.

:sarc: Upload a screenshot of Computer management window with Device manager selected in the left pane.

 

[aqscithe]

Here is the screenshot.

Do you think restoring the computer to a point before I had this problem will help?

 

[Arc]

I would suggest a clean reinstall.
Boot into BIOS. Disable RAID. Set storage controllers to AHCI. Then follow http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html.

When installing the chipset drivers, dont install Intel Rapid Storage Technology.

 

[gregrocker]

Did you update the IRST driver from Windows Updates or Dell Support Downloads webpage for your tag number? This is where it should come from since it's likely modified by Dell and/or vetted by MS.

A Clean Reinstall always provides better performance, especially if you optimize it with the suggestions we've learned since before Win7 was released and compiled in Clean Reinstall - Factory OEM Windows 7.

In this case reinstalling in AHCI mode will give a comparison to IRST performance. If there is any appreciable performance hit then I would re-enable IRST and reinstall. Your IRST then lists as the SATA controller driver in BIOS and Device Manager.

 

[Samurai]

Same problem, Dell was really nice and replaced the hard drive, but problem persisted. The laptop had an mSATA drive and it wasn't until I turned off RAID for that drive (Ctrl-I options on reboot, that effectively reformatted it?) that the problem went away. A virus or corruption in there perhaps? TDSSKiller didn't find anything.