Fairly frequent BSOD

[dreborn]

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!

 

[richc46]

Your Dump Report

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64

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

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.
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

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

Virus Scan
SFC /scannow

www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

If the BSOD continue, after uninstalling the above driver, replace your AntiVirus with Microsoft Security Essentials, and Malwarebytes, use the Windows Firewall

 

[dreborn]

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?

 

[richc46]

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.

 

[dreborn]

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

thanks for the help!

 

[richc46]

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.