iaStor.sys BSOD

FrostWyrmWraith · Jan 31, 2013

I've been getting repeated BSODs related to iaStor recently. So far I have downloaded Malwarebytes, SuperAntiSpyWare, and TDSSKiller and none of them have turned up any malware, so a rootkit can presumably be ruled out. I did the scans both in and out of safe mode. I've also reinstalled the driver software and I'm still getting the BSOD. I've rooted through every iaStor BSOD related thread I could find on this forum and nothing I've tried has eliminated the problem.

Also, I don't seem to be able to attach files to my post. The attachment manager won't load.

Northernsoul55 · Jan 31, 2013

Hey FrostWyrmWraith and welcome to SF,

Firstly can you reconfigure windows to collect the correct info

You want "Mini-Dumps"

Dump Files - Configure Windows to Create on BSOD

Also here are the instructions for posting:

Blue Screen of Death (BSOD) Posting Instructions

Also can you please fill out your specs as this will be most helpful.

Cheers

Dave

FrostWyrmWraith · Jan 31, 2013

Yes, I saw that. And my computer is already collecting the dumps.

The problem was that when I made the thread the attachment manager refused to open, as I stated. It seems to be working now, so it's attached to this post.

Kaktussoft · Jan 31, 2013

run device manager. Open branch IDE ATA-ATAPI-controllers. What is listed there? right click->upgrade driver->on computer->pick from list->put checkmark at compatible devices. Select the Standard AHCI 1.0 Serial ATA controller. Press next a few times.

You have to reboot a few times but it tells you to. Check if drive letters and drive letters of dvd drive afterwards are still correct.

Post results

Britton30 · Jan 31, 2013

To better help us to help you would you please add your systems specs? Here's how:SystemInfo See Your System Specs Under System Manufacturer/Model Number add whether it is a desktop or laptop and whether self built. Very important

Log in to Seven Forums and you will be able to transfer the info directly to the specs page in your profile from within the System Info app.

After doing this your specs will be available in each of your posts.
Click on My system Specs in the lower left of this post to see how it should look.

Full instructions are in the tutorial.

Northernsoul55 · Jan 31, 2013

Hi,
Your last crash was caused by:
IMAGE_NAME: iaStor.sys

iaStor Intel RAID Controller Kernel 2/1/2012 7:15:24 PM

2: kd> lmvm iaStor
start end module name
fffff880`01008000 fffff880`013ac000 iaStor T (no symbols)
Loaded symbol image file: iaStor.sys
Image path: \SystemRoot\system32\drivers\iaStor.sys
Image name: iaStor.sys
Timestamp: Thu Feb 02 00:15:24 2012 (4F29D59C)
CheckSum: 0008B2F8
ImageSize: 003A4000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please update your Intel Storage drivers found here:

Intel Download Center

Please post back any progress.

Cheers

Dave

FrostWyrmWraith · Jan 31, 2013

System specs are up. As I stated in my first post, I knew what was causing it and already updated my drivers. It didn't work.

Northernsoul55 · Jan 31, 2013

Which driver did you update?

FrostWyrmWraith · Jan 31, 2013

The storage drivers. I did it through the site manually and attempted an update from the device manager just in case as well.

Britton30 · Jan 31, 2013

Try the Dell support for your model, some laptop drivers are specially made/written. also see if there is a BIOS update.

Northernsoul55 · Jan 31, 2013

Try this driver:

Drivers & Downloads | Dell United States

It is under Serial ATA and is newer than the one installed

cheers

Dave

FrostWyrmWraith · Jan 31, 2013

I installed the newer driver and now I'm getting a different BSOD error message.

Northernsoul55 · Jan 31, 2013

Please try the Intel auto detect.

Intel® Driver Update Utility

And see if it picks up the latest drivers for:

Intel Mobile Express Chipset SATA RAID Controller.

Cheers

Dave

FrostWyrmWraith · Jan 31, 2013

Everything was up to date except my WiFi driver.

Arc · Feb 1, 2013

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880010516b0, fffff88003be1868, fffff88003be10c0}

[COLOR=Red]Probably caused by : iaStor.sys [/COLOR]( iaStor+496b0 )

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

So it is Intel Rapid Storage Driver. Download and install this one.

Also there are some problems related to display driver.

Code:

fffff880`03be1008  fffff880`0f65c500Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0x257500[/COLOR]
fffff880`0f405000 fffff880`101cc000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
[COLOR=Red]    Image name: nvlddmkm.sys
    Timestamp:        Sun Mar 25 00:33:10 2012 [/COLOR](4F6E1A6E)
    CheckSum:         00DAC0F0
    ImageSize:        00DC7000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Download and install Driver Fusion.
Reboot the computer in Advanced Boot Options, safe mode. Search Driver Fusion in your start menu, and remove all components of your nVidia display driver.
If it says the the free version of Driver Fusion cannot remove all the elements, stop there and follow Drivers - Clean Left over Files after Uninstalling
Boot normally now. Go to Drivers - Download NVIDIA Drivers, Drivers > Beta and Legacy; search there with your cards particulars for GeForce 306.23 Driver, dated 13.9.2012 and install it.

Uninstall McAfee Using McAfee Removal Tool. Uninstall Super AntiSpyware, too. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

You have a lot of Dell factory stuff installed.

Code:

Start Menu\Programs\Dell    Public:Start Menu\Programs\Dell    Public
Start Menu\Programs\Dell\Dell Software & Utilities    Public:Start Menu\Programs\Dell\Dell Software & Utilities    Public
Start Menu\Programs\Dell\Service Agreements    Public:Start Menu\Programs\Dell\Service Agreements    Public
Start Menu\Programs\Dell DataSafe    Public:Start Menu\Programs\Dell DataSafe    Public
Start Menu\Programs\Dell DataSafe Online    Public:Start Menu\Programs\Dell DataSafe Online    Public
Start Menu\Programs\Dell Stage    Public:Start Menu\Programs\Dell Stage    Public
Start Menu\Programs\Dell Support Center    Public:Start Menu\Programs\Dell Support Center    Public
Start Menu\Programs\Dell Webcam    Public:Start Menu\Programs\Dell Webcam    Public

They often are problematic. Follow the guide: http://www.sevenforums.com/tutorials/219576-clean-up-factory-bloatware.html

Let us know the results.

FrostWyrmWraith · Feb 1, 2013

Did all that and still got another BSOD.

Arc · Feb 1, 2013

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8800104b6ec, fffff88003fee868, fffff88003fee0c0}

[COLOR=Red]Probably caused by : iaStor.sys [/COLOR]( iaStor+496ec )

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: fffff8800104b6ec, The address that the exception occurred at
Arg3: fffff88003fee868, Exception Record Address
Arg4: fffff88003fee0c0, 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: 
iaStor+496ec
fffff880`0104b6ec 488b4d40        mov     rcx,qword ptr [rbp+40h]

EXCEPTION_RECORD:  fffff88003fee868 -- (.exr 0xfffff88003fee868)
ExceptionAddress: fffff8800104b6ec (iaStor+0x00000000000496ec)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000040
Attempt to read from address 0000000000000040

CONTEXT:  fffff88003fee0c0 -- (.cxr 0xfffff88003fee0c0)
rax=00000000fff450fe rbx=fffffa8008937cc8 rcx=0000000000000000
rdx=fffff88003feeac0 rsi=fffffa800c7a7998 rdi=fffffa80082bdbc0
rip=fffff8800104b6ec rsp=fffff88003feeaa0 rbp=0000000000000000
 r8=fffffa8008953130  r9=00000000000000c0 r10=00000000000baf12
r11=fffff88003feeaf8 r12=fffffa8006c990a0 r13=fffff88001026dfc
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
iaStor+0x496ec:
fffff880`0104b6ec 488b4d40        mov     rcx,qword ptr [rbp+40h] ss:0018:00000000`00000040=????????????????
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:  0000000000000040

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000330c100
GetUlongFromAddress: unable to read from fffff8000330c1c0
 0000000000000040 Nonpaged pool

FOLLOWUP_IP: 
iaStor+496ec
fffff880`0104b6ec 488b4d40        mov     rcx,qword ptr [rbp+40h]

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from fffffa80082bdbc0 to fffff8800104b6ec

STACK_TEXT:  
fffff880`03feeaa0 fffffa80`082bdbc0 : fffffa80`0c7a7998 fffffa80`0c77f258 fffffa80`07c321c8 fffff880`0107fbc8 : iaStor+0x496ec
fffff880`03feeaa8 fffffa80`0c7a7998 : fffffa80`0c77f258 fffffa80`07c321c8 fffff880`0107fbc8 00000000`00000000 : 0xfffffa80`082bdbc0
fffff880`03feeab0 fffffa80`0c77f258 : fffffa80`07c321c8 fffff880`0107fbc8 00000000`00000000 00000000`00000000 : 0xfffffa80`0c7a7998
fffff880`03feeab8 fffffa80`07c321c8 : fffff880`0107fbc8 00000000`00000000 00000000`00000000 fffff880`03feeb50 : 0xfffffa80`0c77f258
fffff880`03feeac0 fffff880`0107fbc8 : 00000000`00000000 00000000`00000000 fffff880`03feeb50 fffffa80`fff450fe : 0xfffffa80`07c321c8
fffff880`03feeac8 00000000`00000000 : 00000000`00000000 fffff880`03feeb50 fffffa80`fff450fe 00000000`00000030 : iaStor+0x7dbc8


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  iaStor+496ec

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: iaStor

IMAGE_NAME:  iaStor.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4fc685c8

STACK_COMMAND:  .cxr 0xfffff88003fee0c0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_iaStor+496ec

BUCKET_ID:  X64_0x7E_iaStor+496ec

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

4: kd> lmvm iaStor
start             end                 module name
fffff880`01002000 fffff880`013a6000   iaStor   T (no symbols)           
    Loaded symbol image file: iaStor.sys
    Image path: \SystemRoot\system32\drivers\iaStor.sys
[COLOR=Red]    Image name: iaStor.sys
    Timestamp:        Thu May 31 02:10:40 2012[/COLOR] (4FC685C8)
    CheckSum:         00091790
    ImageSize:        003A4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Every version od RST is crashing here.

Go to Control Panel > Program anf Features. Uninstall Intel Rapid Storage. Then do it:

Right click on "my computer" icon and click "manage" on the context menu.
It will open the "computer management" window.
Select "Device Manager" in the left pane, It will list all the existing devices up.
Expand "Disc Drives" by clicking on the triangle in front of it.
Select one item under it, right click, uninstall.
Continue the process for all items under "Disc Drives"
Now restart the computer. At restart, windows will auto configure the appropriate system driver, msahci.sys.

And, scan the system for possible virus infection with these two programs. .

Let us know the results.

FrostWyrmWraith · Feb 1, 2013

I did the first list of things and the scans turned up nothing.

Arc · Feb 1, 2013

Now wait. Let us see what happens.

BTW, the WDO scan takes a bit time, IMO.

FrostWyrmWraith · Feb 1, 2013

Yeah it crashed again.

iaStor.sys BSOD

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

R.I.P. 7/09/2014

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

R.I.P. 7/09/2014

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer