Fairly frequent BSOD

  1. Posts : 9
    Windows 7

    Fairly frequent BSOD

    Win 7 64, fully updated. Rest of specs you can see in my signature.

    about a week ago my computer has been BSOD'ing. It's been running perfectly for more than a year. Haven't installed any new hardware or new drivers that i can think of. Tried to analyze the dmp file myself and the only culprit I noticed was tcpip so i went ahead and updated my ethernet drivers via windows update (probably not the smartest but the easiest). =)

    I attached all the crash info as per the sticky

    thanks for any help!
      My Computer

  2. Posts : 17,796
    Windows 10, Home Clean Install

    Your Dump Report

    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_BSOD%20analyze[1].zip\Windows7_BSOD_jcgriff2\071310-10250-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Machine Name:
    Kernel base = 0xfffff800`02c11000 PsLoadedModuleList = 0xfffff800`02e4ee50
    Debug session time: Tue Jul 13 21:57:50.355 2010 (GMT-4)
    System Uptime: 11 days 9:00:04.000
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    Use !analyze -v to get detailed debugging information.
    BugCheck A, {88, 2, 1, fffff80002c60ea2}
    Unable to load image \SystemRoot\system32\DRIVERS\iaStor.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for iaStor.sys
    *** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
    Probably caused by : iaStor.sys ( iaStor+2d990 )
    Followup: MachineOwner
    0: kd> !analyze -v
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arg1: 0000000000000088, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80002c60ea2, address which referenced memory
    Debugging Details:
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb90e0
    fffff800`02c60ea2 f0480fbaab8800000000 lock bts qword ptr [rbx+88h],0
    PROCESS_NAME:  System
    TRAP_FRAME:  fffff800041f7790 -- (.trap 0xfffff800041f7790)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000002 rbx=0000000000000000 rcx=fffffa8008c80208
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002c60ea2 rsp=fffff800041f7920 rbp=0000000000000002
    r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
    r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe nc
    fffff800`02c60ea2 f0480fbaab8800000000 lock bts qword ptr [rbx+88h],0 ds:43a8:00000000`00000088=????????????????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff80002c80b69 to fffff80002c81600
    fffff800`041f7648 fffff800`02c80b69 : 00000000`0000000a 00000000`00000088 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff800`041f7650 fffff800`02c7f7e0 : 00000000`0000c000 00000000`00000000 00000000`00011031 fffff880`05a56000 : nt!KiBugCheckDispatch+0x69
    fffff800`041f7790 fffff800`02c60ea2 : fffffa80`08d94340 fffffa80`07252000 fffffa80`0780f001 00000000`00000000 : nt!KiPageFault+0x260
    fffff800`041f7920 fffff800`02c8445b : 00000000`00000000 00000000`a000000c 00000000`00000000 00000000`00000000 : nt!KeInsertQueueApc+0x42
    fffff800`041f7980 fffff880`0110a990 : fffffa80`09164280 fffffa80`08c80100 fffffa80`08369b70 00000000`00000000 : nt!IopfCompleteRequest+0xbdb
    fffff800`041f7a60 fffffa80`09164280 : fffffa80`08c80100 fffffa80`08369b70 00000000`00000000 00000000`00000000 : iaStor+0x2d990
    fffff800`041f7a68 fffffa80`08c80100 : fffffa80`08369b70 00000000`00000000 00000000`00000000 fffff880`010e6e7d : 0xfffffa80`09164280
    fffff800`041f7a70 fffffa80`08369b70 : 00000000`00000000 00000000`00000000 fffff880`010e6e7d fffffa80`04b84458 : 0xfffffa80`08c80100
    fffff800`041f7a78 00000000`00000000 : 00000000`00000000 fffff880`010e6e7d fffffa80`04b84458 fffff800`041f7b40 : 0xfffffa80`08369b70
    fffff880`0110a990 ??              ???
    SYMBOL_NAME:  iaStor+2d990
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: iaStor
    IMAGE_NAME:  iaStor.sys
    FAILURE_BUCKET_ID:  X64_0xA_iaStor+2d990
    BUCKET_ID:  X64_0xA_iaStor+2d990
    Followup: MachineOwner
    You have given us two reports, both indicate the same problem.

    STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

    Probably Caused by iastor.sys.

    Intel Matrix Storage Manager driver - Intel Matrix Storage Manager driver - Intel Corporation

    Iastor.sys file description
    Productname: Intel Matrix Storage manager Driver
    Description: Intel Matrix Storage Manager driver
    Company: Intel Corporation

    Uninstall and replace iastor.sys, with an updated driver. Update from Intel Website.

    Virus Scan
    SFC /scannow


    If the BSOD continue, after uninstalling the above driver, replace your AntiVirus with Microsoft Security Essentials, and Malwarebytes, use the Windows Firewall
    Last edited by richc46; 18 Jul 2010 at 18:13.
      My Computer

  3. Posts : 9
    Windows 7
    Thread Starter

    hmm...ok, so I believe I have intel's updated RST driver package for my intel SSD drive. Should I still uninstall and replace iastor/Intel Matrix Storage Manager?
      My Computer

  4. Posts : 17,796
    Windows 10, Home Clean Install

    Yes, I would uninstall and then install again. You have two reports with the same indication. This BC report, usually points toward a driver. We have to be able to rule out the driver as the cause. If replacement does not work, install the new AntiVirus as suggested. If new BSOD reports are made post, and they will be analyzed.

    These reports are not definitive, but merely point the way. We have to follow the trail until we reach our destination.
      My Computer

  5. Posts : 9
    Windows 7
    Thread Starter

    ok, well i uninstalled and reinstalled lastest RST drivers...we'll see

    thanks for the help!
      My Computer

  6. Posts : 17,796
    Windows 10, Home Clean Install

    Enjoy the computer.

    If it happens again, change your antivirus as indicated in my post, above.

    If it still continues, just post and the new BSOD will be analyzed. Based upon the reports submitted, it was caused by the Driver, but it could been caused by the interaction of the driver and memory. If it does happen again, and the report is the same, I will give you an easy memory diagnositic to check the memory.
      My Computer


  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 07:29.
Find Us