BSOD finally!

After 4 lockups I finally get a BSOD, I have already posted the previous lockups without reponses (except mine), so here I added the info requested to this BSOD.

Windows 7 x64
sample 30 day activate, today last day.
system is all new, about a 2 months old.

I have two 4 bay drive enclosures, Rosewill brand non raid all filled up, with an external USB 3.0 drive also

I have added the Windows_NT6_BSOD_jcgriff2 folder, the system health folder, and the dump file. I am going to re install the OS but I would like to find out if this is a hardware issue.

Thanks

I haven't had much time the last couple of weeks so I haven't been doing debugs, fortunately for you this looks like a simple one so I can help real quick.

Code:

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: 0000000000000000, memory referenced
Arg2: 000000000000000a, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880010cfae6, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034bf100
 0000000000000000 

CURRENT_IRQL:  a

FAULTING_IP: 
rr62x+16ae6
fffff880`010cfae6 4c8b10          mov     r10,qword ptr [rax]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff80000b9c0a0 -- (.trap 0xfffff80000b9c0a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800db55fd8
rdx=fffffa800db56a18 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880010cfae6 rsp=fffff80000b9c238 rbp=fffffa800db55d70
 r8=fffffa800db55fd8  r9=000000000000f005 r10=fffffa800db569d8
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
rr62x+0x16ae6:
fffff880`010cfae6 4c8b10          mov     r10,qword ptr [rax] ds:8b98:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000328f2a9 to fffff8000328fd00

STACK_TEXT:  
fffff800`00b9bf58 fffff800`0328f2a9 : 00000000`0000000a 00000000`00000000 00000000`0000000a 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9bf60 fffff800`0328df20 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0db56900 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c0a0 fffff880`010cfae6 : fffff880`010cf4d2 00000000`00000000 fffff880`010ba043 00000000`000003e8 : nt!KiPageFault+0x260
fffff800`00b9c238 fffff880`010cf4d2 : 00000000`00000000 fffff880`010ba043 00000000`000003e8 00001f80`005e0280 : rr62x+0x16ae6
fffff800`00b9c240 00000000`00000000 : fffff880`010ba043 00000000`000003e8 00001f80`005e0280 fffff800`00b9c350 : rr62x+0x164d2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
rr62x+16ae6
fffff880`010cfae6 4c8b10          mov     r10,qword ptr [rax]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  rr62x+16ae6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: rr62x

IMAGE_NAME:  rr62x.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b2f0d94

FAILURE_BUCKET_ID:  X64_0xD1_rr62x+16ae6

BUCKET_ID:  X64_0xD1_rr62x+16ae6

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

this points to rr62x.sys
as the culprit.
This is the rocket raid driver.
HighPoint Global Website
you should be able to track down updated drivers there.
62x appears to be the model/make.