Windows 7: Multiple random BSODs

 icrosoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp4_Windows_NT6_BSOD_jcgriff2.zip\Windows_NT6_BSOD_jcgriff2\060611-26910-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 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`03460000 PsLoadedModuleList = 0xfffff800`036a5650
Debug session time: Mon Jun  6 16:15:39.411 2011 (GMT-4)
System Uptime: 0 days 0:31:41.253
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {368, b, 1, fffff88001108a8f}
*** WARNING: Unable to verify timestamp for ulsata2.sys
*** ERROR: Module load completed but symbols could not be loaded for ulsata2.sys
Probably caused by : ulsata2.sys ( ulsata2+375d )
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: 0000000000000368, memory referenced
Arg2: 000000000000000b, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88001108a8f, address which referenced memory
Debugging Details:
------------------
 
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000370f100
 0000000000000368 
CURRENT_IRQL:  b
FAULTING_IP: 
SCSIPORT!ScsiPortNotification+597
fffff880`01108a8f 0fbaab6803000012 bts     dword ptr [rbx+368h],12h
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
TRAP_FRAME:  fffff80000ba26a0 -- (.trap 0xfffff80000ba26a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88001111110 rbx=0000000000000000 rcx=fffff880011112c0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001108a8f rsp=fffff80000ba2830 rbp=fffffa800afec008
 r8=0000000000000000  r9=0000000000000000 r10=fffff88006473200
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
SCSIPORT!ScsiPortNotification+0x597:
fffff880`01108a8f 0fbaab6803000012 bts     dword ptr [rbx+368h],12h ds:00000000`00000368=????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff800034df2a9 to fffff800034dfd00
STACK_TEXT:  
fffff800`00ba2558 fffff800`034df2a9 : 00000000`0000000a 00000000`00000368 00000000`0000000b 00000000`00000001 : nt!KeBugCheckEx
fffff800`00ba2560 fffff800`034ddf20 : 00000000`40820288 fffff800`03652e80 fffffa80`0d6a7250 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba26a0 fffff880`01108a8f : fffffa80`0c663ed0 fffff880`04c68a64 fffffa80`0c663c80 fffffa80`0c652250 : nt!KiPageFault+0x260
fffff800`00ba2830 fffff880`010bf75d : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0afec008 : SCSIPORT!ScsiPortNotification+0x597
fffff800`00ba28d0 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`0afec008 fffff880`035e7c90 : ulsata2+0x375d
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
ulsata2+375d
fffff880`010bf75d ??              ???
SYMBOL_STACK_INDEX:  4
SYMBOL_NAME:  ulsata2+375d
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: ulsata2
IMAGE_NAME:  ulsata2.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  464a69eb
FAILURE_BUCKET_ID:  X64_0xD1_ulsata2+375d
BUCKET_ID:  X64_0xD1_ulsata2+375d
Followup: MachineOwner
---------