Here is the babble from the debugging tool. This laptop powered itself of before creating this file. Not the first occurance.
*******************************************************************************
* *
* 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: 0000001c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: a71c9e71, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: 0000001c
CURRENT_IRQL: 2
FAULTING_IP:
USBRDXP+6e71
a71c9e71 c7421c04000000 mov dword ptr [edx+1Ch],4
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from a71c956c to a71c9e71
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a994ed7c a71c956c 83f72350 00000000 84ee41f8 USBRDXP+0x6e71
00000000 00000000 00000000 00000000 00000000 USBRDXP+0x656c
STACK_COMMAND: kb
FOLLOWUP_IP:
USBRDXP+6e71
a71c9e71 c7421c04000000 mov dword ptr [edx+1Ch],4
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: USBRDXP+6e71
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: USBRDXP
IMAGE_NAME: USBRDXP.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 46f71802
FAILURE_BUCKET_ID: 0xD1_USBRDXP+6e71
BUCKET_ID: 0xD1_USBRDXP+6e71
*********************************************************************
Any help/direction would be greatly appreciated.
Thanks
*******************************************************************************
* *
* 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: 0000001c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: a71c9e71, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: 0000001c
CURRENT_IRQL: 2
FAULTING_IP:
USBRDXP+6e71
a71c9e71 c7421c04000000 mov dword ptr [edx+1Ch],4
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from a71c956c to a71c9e71
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a994ed7c a71c956c 83f72350 00000000 84ee41f8 USBRDXP+0x6e71
00000000 00000000 00000000 00000000 00000000 USBRDXP+0x656c
STACK_COMMAND: kb
FOLLOWUP_IP:
USBRDXP+6e71
a71c9e71 c7421c04000000 mov dword ptr [edx+1Ch],4
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: USBRDXP+6e71
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: USBRDXP
IMAGE_NAME: USBRDXP.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 46f71802
FAILURE_BUCKET_ID: 0xD1_USBRDXP+6e71
BUCKET_ID: 0xD1_USBRDXP+6e71
*********************************************************************
Any help/direction would be greatly appreciated.
Thanks