blue screen error in windows 7

os:windows 7 home premium 32 bit
processor: intel core i3
grphics : ati monility raedon 5145
memory : 4gb
hdd : 320 gb


now a days i have been facing some blue screen error
like:: IRQL_LESS_OR_NOT_EQUAL

BCCODE : D1
BCCODE : A
BCCODE : 70860002

BELOW IS PROBLEM REPORT
[SPOILER]
Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7600.2.0 - Pastebin.com
[/SPOILER]

ANOTHER ONE IS

[SPOILER]
Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7600.2.0 - Pastebin.com
[/SPOILER]

LAST ONE IS

[SPOILER]
Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7600.2.0 - Pastebin.com
[/SPOILER]


PLZ HELP ME......it also show blue screen error when wake up from hibernate......

BELOW IS DUMP FILES.....
Attachment 152760

Some TDSS malware may be the cause
How to remove malware belonging to the family Rootkit.Win32.TDSS (aka Tidserv, TDSServ, Alureon)?

iaStor.sys is the Intel® Rapid Storage Technology driver, update it Intel® Driver Update Utility
You have an old 1999 driver, Aspi32.SYS which is obsolete, it is used by programs made by Adaptec.

Code:

ASPI32.SYS        0x8f9fc000    0x8f9ffe40    0x00003e40    0x37d99842    11/09/1999 03:46:10

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 1, 83e54948}

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+43948 )

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

2: 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: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 83e54948, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 8356f718
Unable to read MiSystemVaType memory at 8354f160
 00000000 

CURRENT_IRQL:  2

FAULTING_IP: 
iaStor+43948
83e54948 8906            mov     dword ptr [esi],eax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  SAPISSVC.EXE

TRAP_FRAME:  8db20dac -- (.trap 0xffffffff8db20dac)
ErrCode = 00000002
eax=00000000 ebx=86d758d4 ecx=86d758d4 edx=00008700 esi=00000000 edi=86d75868
eip=83e54948 esp=8db20e20 ebp=8db20e38 iopl=0         nv up ei ng nz ac pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010296
iaStor+0x43948:
83e54948 8906            mov     dword ptr [esi],eax  ds:0023:00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 83e54948 to 8344d82b

STACK_TEXT:  
8db20dac 83e54948 badb0d00 00008700 83474587 nt!KiTrap0E+0x2cf
WARNING: Stack unwind information not available. Following frames may be wrong.
8db20e38 83e37fbb ac02f9d0 ac02f9d0 86d7cc18 iaStor+0x43948
8db20e50 83e196e6 fffffff5 fffffff5 ac02f9d0 iaStor+0x26fbb
8db20e68 83e1a30e 86d7cc18 ac02f9d0 83444f48 iaStor+0x86e6
8db20e84 83e1a360 01d7cc18 8db20eb4 86d7cc18 iaStor+0x930e
8db20e98 83e1a96e 86d7cc18 8db20eb4 86d75460 iaStor+0x9360
8db20f34 83e378e7 86d7cc18 00000000 89e990b4 iaStor+0x996e
8db20f48 8346f3b5 86d75460 86d73000 00000000 iaStor+0x268e7
8db20fa4 8346f218 8db00120 89e99030 00000000 nt!KiExecuteAllDpcs+0xf9
8db20ff4 8346e9dc 8f6ec940 00000000 00000000 nt!KiRetireDpcList+0xd5
8db20ff8 8f6ec940 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
8346e9dc 00000000 0000001a 00d6850f bb830000 0x8f6ec940


STACK_COMMAND:  kb

FOLLOWUP_IP: 
iaStor+43948
83e54948 8906            mov     dword ptr [esi],eax

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  iaStor+43948

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: iaStor

IMAGE_NAME:  iaStor.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ac656c5

FAILURE_BUCKET_ID:  0xD1_iaStor+43948

BUCKET_ID:  0xD1_iaStor+43948

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

after updating inter rapid storage......
ASPI32.SYS date still remain 10-9-1999

here is new dup file.........
Attachment 152868



and below is anti rootkit result............
Attachment 152869


thanx 4 reply.....

krunal5991 said:

after updating inter rapid storage......
ASPI32.SYS date still remain 10-9-1999

here is new dup file.........
Attachment 152868



and below is anti rootkit result............
Attachment 152869


thanx 4 reply.....

You may ignore the old 1999 driver, the logs show that your system was indeed infected and cured :)

ya.... now my lappy works great.........there is no more blue screen error.....hey thanx bro......i m greatful to you.......:)