BleepingComputer.com: BSOD - DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

Hello....this BSOD problem, DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) has happened at least 4 time this month and now I'm asking for help.
Make and Model of the computer having this problem...
Dell Dimension E310
Microsoft Windows XP Professional Version 2002 Service Pack 3

All of the minidump files have been generated early in the AM before the user gets to work.
Is there a quick way to fix this problem with out having to reinstall al of the drivers?

Below is the information extracte from WinDbg.
Thanks in advance -Craig


Microsoft ® Windows Debugger Version 6.12.0002.633 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini050810-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 XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.100216-1514
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sat May 8 04:47:18.687 2010 (UTC - 7:00)
System Uptime: 2 days 20:58:08.797
Loading Kernel Symbols
...............................................................
...............................................................
Loading User Symbols
Loading unloaded module list
..................................................
Unable to load image 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
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {34, 2, 0, ba649019}

Probably caused by : iaStor.sys ( iaStor+13019 )

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

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


READ_ADDRESS: 00000034

CURRENT_IRQL: 2

FAULTING_IP:
iaStor+13019
ba649019 0fb67034 movzx esi,byte ptr [eax+34h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from ba64964d to ba649019

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
bad43d88 ba64964d 00000000 8a62ada8 bad43ddc iaStor+0x13019
bad43da4 ba649a8c 8a681400 805cff62 8a681450 iaStor+0x1364d
bad43dac 805cff62 8a681450 00000000 00000000 iaStor+0x13a8c
bad43ddc 8054611e ba649a7c 8a681450 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
iaStor+13019
ba649019 0fb67034 movzx esi,byte ptr [eax+34h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: iaStor+13019

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: iaStor

IMAGE_NAME: iaStor.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 42b2df42

FAILURE_BUCKET_ID: 0xD1_iaStor+13019

BUCKET_ID: 0xD1_iaStor+13019

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

Dell Documentation on This Error

Louis

Louis -
Thank you....That seems to have worked.

Glad it worked for you...happy computing .

Louis