Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\050911-32136-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`03210000 PsLoadedModuleList = 0xfffff800`0344de50
Debug session time: Mon May 9 13:39:00.206 2011 (GMT-4)
System Uptime: 0 days 0:53:53.299
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {fffffa98081b5040, 2, 0, fffff880046210e9}
Unable to load image \SystemRoot\system32\DRIVERS\FLxHCIc.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for FLxHCIc.sys
*** ERROR: Module load completed but symbols could not be loaded for FLxHCIc.sys
Probably caused by : FLxHCIc.sys ( FLxHCIc+210e9 )
Followup: MachineOwner
---------
3: 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: fffffa98081b5040, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880046210e9, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034b80e0
fffffa98081b5040
CURRENT_IRQL: 2
FAULTING_IP:
FLxHCIc+210e9
fffff880`046210e9 498b58f8 mov rbx,qword ptr [r8-8]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: WPControlPanel
TRAP_FRAME: fffff8800a9512c0 -- (.trap 0xfffff8800a9512c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000101000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880046210e9 rsp=fffff8800a951450 rbp=fffffa800a4b8749
r8=fffffa98081b5048 r9=fffffa80081b5030 r10=00000000000ff000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac pe cy
FLxHCIc+0x210e9:
fffff880`046210e9 498b58f8 mov rbx,qword ptr [r8-8] ds:5150:fffffa98`081b5040=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000327fca9 to fffff80003280740
STACK_TEXT:
fffff880`0a951178 fffff800`0327fca9 : 00000000`0000000a fffffa98`081b5040 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0a951180 fffff800`0327e920 : 00000000`00010000 00000000`00010000 fffff880`05c25150 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0a9512c0 fffff880`046210e9 : 00000000`00000000 fffffa80`0a4b8749 fffff880`05c25150 fffffa80`0a4b8731 : nt!KiPageFault+0x260
fffff880`0a951450 00000000`00000000 : fffffa80`0a4b8749 fffff880`05c25150 fffffa80`0a4b8731 fffffa80`00000000 : FLxHCIc+0x210e9
STACK_COMMAND: kb
FOLLOWUP_IP:
FLxHCIc+210e9
fffff880`046210e9 498b58f8 mov rbx,qword ptr [r8-8]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: FLxHCIc+210e9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: FLxHCIc
IMAGE_NAME: FLxHCIc.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c9c884c
FAILURE_BUCKET_ID: X64_0xD1_FLxHCIc+210e9
BUCKET_ID: X64_0xD1_FLxHCIc+210e9
Followup: MachineOwner
---------