Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Richard\AppData\Local\Temp\Temp1_SF_17-02-2014.zip\SF_17-02-2014\021414-19593-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 (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0x8361a000 PsLoadedModuleList = 0x837634d0
Debug session time: Fri Feb 14 02:20:03.737 2014 (UTC - 5:00)
System Uptime: 0 days 0:03:02.814
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {440070, 2, 0, 8ca7ba1e}
Unable to load image \SystemRoot\system32\DRIVERS\TeeDriver.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for TeeDriver.sys
*** ERROR: Module load completed but symbols could not be loaded for TeeDriver.sys
Probably caused by : TeeDriver.sys ( TeeDriver+7384 )
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: 00440070, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8ca7ba1e, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 8378384c
Unable to read MiSystemVaType memory at 83762e20
00440070
CURRENT_IRQL: 2
FAULTING_IP:
Wdf01000!imp_WdfIoQueueRetrieveRequestByFileObject+ff
8ca7ba1e ff5014 call dword ptr [eax+14h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: 83741830 -- (.trap 0xffffffff83741830)
ErrCode = 00000000
eax=0044005c ebx=79b7c410 ecx=86483be8 edx=00000000 esi=00001018 edi=86483be8
eip=8ca7ba1e esp=837418a4 ebp=837418cc iopl=0 nv up ei ng nz ac pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010297
Wdf01000!imp_WdfIoQueueRetrieveRequestByFileObject+0xff:
8ca7ba1e ff5014 call dword ptr [eax+14h] ds:0023:00440070=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 8ca7ba1e to 8365ab7f
STACK_TEXT:
83741830 8ca7ba1e badb0d00 00000000 78ac4cf0 nt!KiTrap0E+0x1b3
837418cc 92e68384 860811d8 8753b790 79b7c410 Wdf01000!imp_WdfIoQueueRetrieveRequestByFileObject+0xff
WARNING: Stack unwind information not available. Following frames may be wrong.
83741b34 92e674b2 87523b48 860810f0 8753b108 TeeDriver+0x7384
83741b4c 8ca9438f 78ac4ef0 78adc630 8753b158 TeeDriver+0x64b2
83741b68 8ca94680 8374e404 83746608 83741bd4 Wdf01000!FxInterrupt:

pcHandler+0x84
83741b78 83691675 8753b158 8753b108 8753b108 Wdf01000!FxInterrupt::_InterruptDpcThunk+0x39
83741bd4 836914d8 83744d20 8374e380 00000000 nt!KiExecuteAllDpcs+0xf9
83741c20 836912f8 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
83741c24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_IP:
TeeDriver+7384
92e68384 ?? ???
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: TeeDriver+7384
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: TeeDriver
IMAGE_NAME: TeeDriver.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5228c726
FAILURE_BUCKET_ID: 0xD1_TeeDriver+7384
BUCKET_ID: 0xD1_TeeDriver+7384
Followup: MachineOwner
---------
Welcome
Usually the reports (as above) give conflicting information. All of your reports are consistent the cause is a driver: teedriver.sys. I am having difficulty in finding the software that uses this driver. So we will go another route. Run the computer in cleanboot mode. Follow instructions to determine the source of the questioned driver. If the computer does not BSOD in clean boot, follow the instruction relating to slowly restoring the deactivated services.
http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html
I am giving you a link to the best information that I could find on the driver. DO NOT DOWNLOAD ANYTHING FROM THE PAGE. It is for information only.
http://systemexplorer.net/file-database/file/teedriver-sys
To be sure that the driver is not a virus. Make a full anti virus scan. Download and make a full scan with Malwarebytes. Be sure that you update the software prior to making the scan. If a virus it can be fairly new.
Finally, if all the above does not lead to a solution, I will show you how to remove the driver after making a system restore point.