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\060811-35583-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 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02e18000 PsLoadedModuleList = 0xfffff800`0305d650
Debug session time: Wed Jun 8 04:05:48.745 2011 (GMT-4)
System Uptime: 0 days 6:00:55.915
Loading Kernel Symbols
...............................................................
................................................................
.................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 35, {fffffa800c8519b0, 0, 0, 0}
Unable to load image \SystemRoot\system32\DRIVERS\kl1.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for kl1.sys
*** ERROR: Module load completed but symbols could not be loaded for kl1.sys
Probably caused by : kl1.sys ( kl1+83ff0 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
NO_MORE_IRP_STACK_LOCATIONS (35)
A higher level driver has attempted to call a lower level driver through
the IoCallDriver() interface, but there are no more stack locations in the
packet, hence, the lower level driver would not be able to access its
parameters, as there are no parameters for it. This is a disasterous
situation, since the higher level driver "thinks" it has filled in the
parameters for the lower level driver (something it MUST do before it calls
it), but since there is no stack location for the latter driver, the former
has written off of the end of the packet. This means that some other memory
has probably been trashed at this point.
Arguments:
Arg1: fffffa800c8519b0, Address of the IRP
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x35
PROCESS_NAME: avp.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002e97cf2 to fffff80002e97d00
STACK_TEXT:
fffff880`08de57a8 fffff800`02e97cf2 : 00000000`00000035 fffffa80`0c8519b0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`08de57b0 fffff800`02e407b7 : fffffa80`05c86930 fffffa80`0655a060 fffff880`08de58e0 00000000`c000000e : nt!KiBugCheck3+0x12
fffff880`08de57e0 fffff880`03efcff0 : 00000000`05a9f028 fffffa80`0c888b10 fffffa80`05c86a00 fffff880`03164180 : nt! ?? ::FNODOBFM::`string'+0x42a8b
fffff880`08de5810 00000000`05a9f028 : fffffa80`0c888b10 fffffa80`05c86a00 fffff880`03164180 fffffa80`06119050 : kl1+0x83ff0
fffff880`08de5818 fffffa80`0c888b10 : fffffa80`05c86a00 fffff880`03164180 fffffa80`06119050 00000000`00000000 : 0x5a9f028
fffff880`08de5820 fffffa80`05c86a00 : fffff880`03164180 fffffa80`06119050 00000000`00000000 00000000`00060001 : 0xfffffa80`0c888b10
fffff880`08de5828 fffff880`03164180 : fffffa80`06119050 00000000`00000000 00000000`00060001 fffff880`08de5848 : 0xfffffa80`05c86a00
fffff880`08de5830 fffffa80`06119050 : 00000000`00000000 00000000`00060001 fffff880`08de5848 fffff880`08de5848 : 0xfffff880`03164180
fffff880`08de5838 00000000`00000000 : 00000000`00060001 fffff880`08de5848 fffff880`08de5848 fffffa80`05c86930 : 0xfffffa80`06119050
STACK_COMMAND: kb
FOLLOWUP_IP:
kl1+83ff0
fffff880`03efcff0 ?? ???
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: kl1+83ff0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: kl1
IMAGE_NAME: kl1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a9d0591
FAILURE_BUCKET_ID: X64_0x35_kl1+83ff0
BUCKET_ID: X64_0x35_kl1+83ff0
Followup: MachineOwner
---------
