BSOD error Iastor.sys

Hello,
Most of the crash were caused by iaStor.sys (Intel Storage driver) then you must update that driver.

It's also possible that your Windows infected by virus or rootkit.
https://www.sevenforums.com/crash-loc...ml#post1329064


Update these drivers:

Code:

RTKVHD64.sys Tue Jul 28 05:00:05 2009 → Realtek High Definition Audio
iaStor.sys   Thu Jun 04 17:53:40 2009  → Intel Storage Driver
igdkmd64.sys Wed Sep 02 10:54:15 2009 → Intel Graphic Driver

Log

Code:

Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a67000 PsLoadedModuleList = 0xfffff800`02ca4e50
Debug session time: Wed Apr  6 00:45:23.846 2011 (GMT-8)
System Uptime: 0 days 0:01:39.797
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {ffffffffffffffe1, 2, 1, fffff880010a24ff}

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+524ff )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffffffffffffe1, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880010a24ff, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0f0e0
 ffffffffffffffe1 

CURRENT_IRQL:  2

FAULTING_IP: 
iaStor+524ff
fffff880`010a24ff 48894620        mov     qword ptr [rsi+20h],rax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  grpconv.exe

TRAP_FRAME:  fffff80000ba2960 -- (.trap 0xfffff80000ba2960)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=7fffffffffffffff rbx=0000000000000000 rcx=fffffa80025b5000
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880010a24ff rsp=fffff80000ba2af0 rbp=0000000000000000
 r8=fffffa80025b5000  r9=0000000000000000 r10=fffff880010556b8
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
iaStor+0x524ff:
fffff880`010a24ff 48894620        mov     qword ptr [rsi+20h],rax ds:5d80:00000000`00000020=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ad8469 to fffff80002ad8f00

STACK_TEXT:  
fffff800`00ba2818 fffff800`02ad8469 : 00000000`0000000a ffffffff`ffffffe1 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`00ba2820 fffff800`02ad70e0 : fffff880`015d3110 fffff880`05956340 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba2960 fffff880`010a24ff : fffff880`05956660 fffffa80`045ca000 fffffa80`03496320 00000000`00000000 : nt!KiPageFault+0x260
fffff800`00ba2af0 fffff880`05956660 : fffffa80`045ca000 fffffa80`03496320 00000000`00000000 fffffa80`04062f48 : iaStor+0x524ff
fffff800`00ba2af8 fffffa80`045ca000 : fffffa80`03496320 00000000`00000000 fffffa80`04062f48 fffffa80`04062f58 : 0xfffff880`05956660
fffff800`00ba2b00 fffffa80`03496320 : 00000000`00000000 fffffa80`04062f48 fffffa80`04062f58 00000000`00000000 : 0xfffffa80`045ca000
fffff800`00ba2b08 00000000`00000000 : fffffa80`04062f48 fffffa80`04062f58 00000000`00000000 00000000`00000002 : 0xfffffa80`03496320


STACK_COMMAND:  kb

FOLLOWUP_IP: 
iaStor+524ff
fffff880`010a24ff 48894620        mov     qword ptr [rsi+20h],rax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  iaStor+524ff

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: iaStor

IMAGE_NAME:  iaStor.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a287aa4

FAILURE_BUCKET_ID:  X64_0xD1_iaStor+524ff

BUCKET_ID:  X64_0xD1_iaStor+524ff

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