Ok some good news I guess. I downloaded the new debugging tools and it works much better. Have it set to download the sybols I need on demand. This is what I got when debugging the dmp file:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WORKER_THREAD_RETURNED_AT_BAD_IRQL (e1)
Arguments:
Arg1: 80421fb0, address of worker routine (do ln on this to find guilty driver)
Arg2: 00000002, IRQL returned at (should have been 0, but isn't).
Arg3: fcb40a68, workitem parameter
Arg4: fcb40a68, workitem address
Debugging Details:
------------------
FAULTING_IP:
nt+21fb0
80421fb0 8b442404 mov eax,[esp+0x4]
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xE1
LAST_CONTROL_TRANSFER: from 80455a16 to 804191fa
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f0833da8 80455a16 fcb40a68 00000000 00000000 nt+0x191fa
f0833ddc 80469bb2 804190f0 00000000 00000000 nt+0x55a16
00000000 00000000 00000000 00000000 00000000 nt+0x69bb2
FOLLOWUP_IP:
nt+21fb0
80421fb0 8b442404 mov eax,[esp+0x4]
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt+21fb0
MODULE_NAME: nt
IMAGE_NAME:
DEBUG_FLR_IMAGE_TIMESTAMP: 3ee6c002
STACK_COMMAND: kb
BUCKET_ID: 0xE1_nt+21fb0
Followup: MachineOwner
---------
kd> ln 80421fb0
As you can see it said to find the guilty driver do an "ln" command. Which I did and it came up with nothing. I don't know where to go from here...