Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\USER\Downloads\Compressed\HOME-Wed_12_24_2014_175135_71\122414-27268-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18526.amd64fre.win7sp1_gdr.140706-1506
Machine Name:
Kernel base = 0xfffff800`03019000 PsLoadedModuleList = 0xfffff800`0325c890
Debug session time: Thu Dec 25 04:21:54.863 2014 (UTC + 6:00)
System Uptime: 0 days 6:53:31.034
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 135, {ffffffffc0000005, fffff880082b05e0, fffff88002686b00, fffff8a00132b010}
*** WARNING: Unable to verify timestamp for bdfsfltr.sys
*** ERROR: Module load completed but symbols could not be loaded for bdfsfltr.sys
Probably caused by : bdfsfltr.sys ( bdfsfltr+41983 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
REGISTRY_FILTER_DRIVER_EXCEPTION (135)
This bugcheck is caused by an unhandled exception in a registry filtering driver.
This bugcheck indicates that a registry filtering driver didn't handle exception inside
its notification routine. One can identify the driver by the 3rd parameter.
Arguments:
Arg1: ffffffffc0000005, ExceptionCode
Arg2: fffff880082b05e0, Address of the context record for the exception that caused the bugcheck
Arg3: fffff88002686b00, The driver's callback routine address
Arg4: fffff8a00132b010, Internal
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x135
PROCESS_NAME: CP210xVCPInsta
CURRENT_IRQL: 0
EXCEPTION_RECORD: fffff880082b0d88 -- (.exr 0xfffff880082b0d88)
ExceptionAddress: fffff880026ba983 (bdfsfltr+0x0000000000041983)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 000000001234567b
Attempt to read from address 000000001234567b
TRAP_FRAME: fffff880082b0e30 -- (.trap 0xfffff880082b0e30)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000084 rbx=0000000000000000 rcx=fffffa8007c96b2d
rdx=000005800a6aeb4e rsi=0000000000000000 rdi=0000000000000000
rip=fffff880026ba983 rsp=fffff880082b0fc8 rbp=0000000000000001
r8=0000000000000004 r9=0000000000000000 r10=0052005400530049
r11=fffffa8007c96b2a r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
bdfsfltr+0x41983:
fffff880`026ba983 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800034057e4 to fffff8000308ebc0
STACK_TEXT:
fffff880`082afdb8 fffff800`034057e4 : 00000000`00000135 ffffffff`c0000005 fffff880`082b05e0 fffff880`02686b00 : nt!KeBugCheckEx
fffff880`082afdc0 fffff800`0343a4ed : 00000000`00000000 00000001`00000001 00000000`00000001 fffff880`082b01e0 : nt!CmpFatalFilter+0x24
fffff880`082afe00 fffff800`030b9cdc : 00000000`00000010 fffff960`000c7794 fffff960`00327170 fffff800`032c9ac0 : nt!CmpCallCallBacks+0x556
fffff880`082afe30 fffff800`030b975d : fffff800`031f9cc4 fffff880`082b1230 00000000`00000000 fffff800`03019000 : nt!_C_specific_handler+0x8c
fffff880`082afea0 fffff800`030b8535 : fffff800`031f9cc4 fffff880`082aff18 fffff880`082b0d88 fffff800`03019000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`082afed0 fffff800`030c94c1 : fffff880`082b0d88 fffff880`082b05e0 fffff880`00000000 fffffa80`07c969c0 : nt!RtlDispatchException+0x415
fffff880`082b05b0 fffff800`0308e242 : fffff880`082b0d88 00000000`00000000 fffff880`082b0e30 fffffa80`07c969c0 : nt!KiDispatchException+0x135
fffff880`082b0c50 fffff800`0308cdba : 00000000`00000000 00000000`1234567b fffff880`082b1100 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`082b0e30 fffff880`026ba983 : fffff880`026aaf94 00000000`00000000 00000000`00000001 fffffa80`07c969c0 : nt!KiPageFault+0x23a
fffff880`082b0fc8 fffff880`026aaf94 : 00000000`00000000 00000000`00000001 fffffa80`07c969c0 fffffa80`07c969c0 : bdfsfltr+0x41983
fffff880`082b0fd0 00000000`00000000 : 00000000`00000001 fffffa80`07c969c0 fffffa80`07c969c0 fffff8a0`056dd800 : bdfsfltr+0x31f94
STACK_COMMAND: kb
FOLLOWUP_IP:
bdfsfltr+41983
fffff880`026ba983 ?? ???
SYMBOL_STACK_INDEX: 9
SYMBOL_NAME: bdfsfltr+41983
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: bdfsfltr
IMAGE_NAME: bdfsfltr.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d89fb21
FAILURE_BUCKET_ID: X64_0x135_bdfsfltr+41983
BUCKET_ID: X64_0x135_bdfsfltr+41983
Followup: MachineOwner
---------
0: kd> lmvm bdfsfltr
start end module name
fffff880`02679000 fffff880`026e9000 bdfsfltr T (no symbols)
Loaded symbol image file: bdfsfltr.sys
Image path: \??\C:\Windows\system32\Drivers\bdfsfltr.sys
Image name: bdfsfltr.sys
Timestamp: Wed Mar 23 19:52:33 2011 (4D89FB21)
CheckSum: 0006B11C
ImageSize: 00070000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4