Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\YUSRA\Downloads\Compressed\Work-PC-SF_26-05-2015\SF_26-05-2015\052615-8814-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
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 x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18717.amd64fre.win7sp1_gdr.150113-1808
Machine Name:
Kernel base = 0xfffff800`0300e000 PsLoadedModuleList = 0xfffff800`03252890
Debug session time: Tue May 26 08:55:28.717 2015 (UTC + 6:00)
System Uptime: 1 days 3:22:21.001
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {ffffffffffffffa4, 2, 1, fffff880010f4227}
*** WARNING: Unable to verify timestamp for TeeDriverx64.sys
*** ERROR: Module load completed but symbols could not be loaded for TeeDriverx64.sys
Probably caused by : TeeDriverx64.sys ( TeeDriverx64+e7bb )
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: ffffffffffffffa4, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880010f4227, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032bc100
GetUlongFromAddress: unable to read from fffff800032bc1c0
ffffffffffffffa4
CURRENT_IRQL: 2
FAULTING_IP:
Wdf01000!FxRequest::PeekRequest+ab
fffff880`010f4227 f044014b0c lock add dword ptr [rbx+0Ch],r9d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
DPC_STACK_BASE: FFFFF80000BA2FB0
TRAP_FRAME: fffff80000b9c390 -- (.trap 0xfffff80000b9c390)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80000b9c5a8 rbx=0000000000000000 rcx=fffffa80094facf8
rdx=fffffa800ba81eb8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880010f4227 rsp=fffff80000b9c520 rbp=fffff80000b9c602
r8=0000000000000000 r9=0000000000000001 r10=fffff8800538c101
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
Wdf01000!FxRequest::PeekRequest+0xab:
fffff880`010f4227 f044014b0c lock add dword ptr [rbx+0Ch],r9d ds:00000000`0000000c=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80003082469 to fffff80003082ec0
STACK_TEXT:
fffff800`00b9c248 fffff800`03082469 : 00000000`0000000a ffffffff`ffffffa4 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`00b9c250 fffff800`030810e0 : 00000000`00000000 fffffa80`09475520 fffffa80`07a3c100 ffffffff`ffffff98 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c390 fffff880`010f4227 : fffffa80`094db290 fffff880`02e0da50 00000000`7849454d fffffa80`000007fa : nt!KiPageFault+0x260
fffff800`00b9c520 fffff880`010fc1d2 : fffffa80`094fac50 00000000`00000000 fffffa80`0949f250 fffffa80`094fac50 : Wdf01000!FxRequest::PeekRequest+0xab
fffff800`00b9c560 fffff880`010e9e43 : 00000000`00000002 fffffa80`094fac50 fffff800`00b9c640 fffff880`0108b408 : Wdf01000!FxIoQueue::PeekRequest+0x122
fffff800`00b9c5e0 fffff880`053857bb : 00000000`00000000 00000000`00000000 00000000`c0000010 0000057f`f6b00468 : Wdf01000!imp_WdfIoQueueFindRequest+0x2c3
fffff800`00b9c680 00000000`00000000 : 00000000`00000000 00000000`c0000010 0000057f`f6b00468 00000000`00000000 : TeeDriverx64+0xe7bb
STACK_COMMAND: kb
FOLLOWUP_IP:
TeeDriverx64+e7bb
fffff880`053857bb ?? ???
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: TeeDriverx64+e7bb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: TeeDriverx64
IMAGE_NAME: TeeDriverx64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 52125493
FAILURE_BUCKET_ID: X64_0xD1_TeeDriverx64+e7bb
BUCKET_ID: X64_0xD1_TeeDriverx64+e7bb
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0xd1_teedriverx64+e7bb
FAILURE_ID_HASH: {d0ec30b3-0563-338d-ef04-8c46cbd2dce9}
Followup: MachineOwner
---------
0: kd> lmvm TeeDriverx64
start end module name
fffff880`05377000 fffff880`05393000 TeeDriverx64 T (no symbols)
Loaded symbol image file: TeeDriverx64.sys
Image path: \SystemRoot\system32\DRIVERS\TeeDriverx64.sys
Image name: TeeDriverx64.sys
Timestamp: Mon Aug 19 23:23:31 2013 (52125493)
CheckSum: 000210A2
ImageSize: 0001C000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
