iaStor.sys BSOD

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 2,014
    Windows 7 Professional 64bit
       #11

    Try this driver:

    Drivers & Downloads | Dell United States

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

    cheers

    Dave
      My Computer


  2. Posts : 12
    Windows 7 64 bit
    Thread Starter
       #12

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


  3. Posts : 2,014
    Windows 7 Professional 64bit
       #13

    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
      My Computer


  4. Posts : 12
    Windows 7 64 bit
    Thread Starter
       #14

    Everything was up to date except my WiFi driver.
      My Computer


  5. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #15

    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}
    
    Probably caused by : iaStor.sys ( 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
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
     nvlddmkm+0x257500
    fffff880`0f405000 fffff880`101cc000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Sun Mar 25 00:33:10 2012 (4F6E1A6E)
        CheckSum:         00DAC0F0
        ImageSize:        00DC7000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

    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: Clean Up Factory Bloatware

    Let us know the results.
      My Computer


  6. Posts : 12
    Windows 7 64 bit
    Thread Starter
       #16

    Did all that and still got another BSOD.
      My Computer


  7. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #17

    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}
    
    Probably caused by : iaStor.sys ( 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
        Image name: iaStor.sys
        Timestamp:        Thu May 31 02:10:40 2012 (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:

    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 "Disc Drives" by clicking on the triangle in front of it.
    5. Select one item under it, right click, uninstall.
    6. Continue the process for all items under "Disc Drives"
    7. 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.
      My Computer


  8. Posts : 12
    Windows 7 64 bit
    Thread Starter
       #18

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


  9. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #19

    Now wait. Let us see what happens.

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


  10. Posts : 12
    Windows 7 64 bit
    Thread Starter
       #20

    Yeah it crashed again.
      My Computer


 
Page 2 of 3 FirstFirst 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 05:07.
Find Us