The following is the crash dump analysis provided by the Microsoft Windows Debugger.

I'm not expecting anyone to really look at this, but it is here so the search engines
will index it and someone searching for a similar term or memory address might hit it
and thus find the article, which can be found at:

http://dascomputerconsultants.com/BSOD-2.htm

Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\FederalScrew\Minidump\Mini033109-10.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 Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: LanManNt, suite: SmallBusiness TerminalServer SmallBusinessRestricted SingleUserTS
Built by: 3790.srv03_sp2_gdr.080813-1204
Kernel base = 0x80800000 PsLoadedModuleList = 0x808af9c8
Debug session time: Tue Mar 31 17:16:29.015 2009 (GMT-4)
System Uptime: 0 days 0:31:48.597
Loading Kernel Symbols
....................................................................................................................................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {170, d0000007, 1, f7352b83}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Unable to load image aarich.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aarich.sys
*** ERROR: Module load completed but symbols could not be loaded for aarich.sys
*** WARNING: Unable to verify timestamp for SCSIPORT.SYS
*** ERROR: Module load completed but symbols could not be loaded for SCSIPORT.SYS
Unable to load image intelppm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys


Probably caused by : aarich.sys ( aarich+9b83 )

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: 00000170, memory referenced
Arg2: d0000007, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: f7352b83, address which referenced memory

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




WRITE_ADDRESS:  00000170 

CURRENT_IRQL:  7

FAULTING_IP: 
aarich+9b83
f7352b83 ??              ???

CUSTOMER_CRASH_COUNT:  10

DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR:  0xD1

PROCESS_NAME:  Idle

TRAP_FRAME:  808a33cc -- (.trap 0xffffffff808a33cc)
ErrCode = 00000002
eax=00000000 ebx=89f0edc4 ecx=00000000 edx=00000000 esi=89ec1318 edi=89f0edc4
eip=f7352b83 esp=808a3440 ebp=808a344c iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
aarich+0x9b83:
f7352b83 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from f7352b83 to 80836df5

STACK_TEXT:  
808a33cc f7352b83 badb0d00 00000000 00000000 nt!KiTrap0E+0x2a7
WARNING: Stack unwind information not available. Following frames may be wrong.
808a343c 89eecd60 89eed874 89ef64a4 808a3488 aarich+0x9b83
808a344c f7359cd7 89ec1318 00000000 89eec9b0 0x89eecd60
808a3488 f735a502 00000000 89ee26f0 89ef64a4 aarich+0x10cd7
808a34a0 f7365ccc 00000001 00000000 89ee375c aarich+0x11502
808a34b8 f737a666 89ef0001 89ee307c 89ee375c aarich+0x1cccc
808a34cc f737520c 89ee3733 00000000 89ee26f0 aarich+0x31666
808a3520 f734b345 89ee307c 89fb1af8 808a3600 aarich+0x2c20c
808a3534 f732c673 89f61004 808a3600 89f29bb0 aarich+0x2345
808a354c 808395a5 89f29bb0 89fb1a40 00010007 SCSIPORT+0x2673
808a354c f75c9ca2 89f29bb0 89fb1a40 00010007 nt!KiInterruptDispatch+0x49
808a35e0 ffdffee0 8083fb57 ffdff000 87610a80 intelppm+0x2ca2
808a3600 80839b12 00000000 0000000e 00000000 0xffdffee0
808a3604 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
aarich+9b83
f7352b83 ??              ???

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  aarich+9b83

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: aarich

IMAGE_NAME:  aarich.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0xD1_W_aarich+9b83

BUCKET_ID:  0xD1_W_aarich+9b83

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