Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\051511-30139-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02e0e000 PsLoadedModuleList = 0xfffff800`03053650
Debug session time: Sun May 15 13:44:26.398 2011 (UTC - 4:00)
System Uptime: 0 days 1:19:34.707
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {48, 2, 1, fffff88006b05e83}
Unable to load image \SystemRoot\system32\DRIVERS\nvmf6264.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvmf6264.sys
*** ERROR: Module load completed but symbols could not be loaded for nvmf6264.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : nvmf6264.sys ( nvmf6264+13e83 )
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: 0000000000000048, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88006b05e83, address which referenced memory
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
FAULTING_MODULE: fffff80002e0e000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a723142
WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
0000000000000048
CURRENT_IRQL: 0
FAULTING_IP:
nvmf6264+13e83
fffff880`06b05e83 743b je nvmf6264+0x13ec0 (fffff880`06b05ec0)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from fffff80002e8d2a9 to fffff80002e8dd00
STACK_TEXT:
fffff800`00ba2428 fffff800`02e8d2a9 : 00000000`0000000a 00000000`00000048 00000000`00000002 00000000`00000001 : nt+0x7fd00
fffff800`00ba2430 00000000`0000000a : 00000000`00000048 00000000`00000002 00000000`00000001 fffff880`06b05e83 : nt+0x7f2a9
fffff800`00ba2438 00000000`00000048 : 00000000`00000002 00000000`00000001 fffff880`06b05e83 00000000`047b6601 : 0xa
fffff800`00ba2440 00000000`00000002 : 00000000`00000001 fffff880`06b05e83 00000000`047b6601 00000000`00000000 : 0x48
fffff800`00ba2448 00000000`00000001 : fffff880`06b05e83 00000000`047b6601 00000000`00000000 00000000`00000000 : 0x2
fffff800`00ba2450 fffff880`06b05e83 : 00000000`047b6601 00000000`00000000 00000000`00000000 00990022`002b0020 : 0x1
fffff800`00ba2458 00000000`047b6601 : 00000000`00000000 00000000`00000000 00990022`002b0020 002a0000`00050002 : nvmf6264+0x13e83
fffff800`00ba2460 00000000`00000000 : 00000000`00000000 00990022`002b0020 002a0000`00050002 00000000`00000000 : 0x47b6601
STACK_COMMAND: kb
FOLLOWUP_IP:
nvmf6264+13e83
fffff880`06b05e83 743b je nvmf6264+0x13ec0 (fffff880`06b05ec0)
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: nvmf6264+13e83
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvmf6264
IMAGE_NAME: nvmf6264.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\051511-28501-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02e4f000 PsLoadedModuleList = 0xfffff800`03094650
Debug session time: Sun May 15 14:01:33.213 2011 (UTC - 4:00)
System Uptime: 0 days 0:16:22.523
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {fa0, 2, 1, fffff88003b4fe83}
Unable to load image \SystemRoot\system32\DRIVERS\nvmf6264.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvmf6264.sys
*** ERROR: Module load completed but symbols could not be loaded for nvmf6264.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : nvmf6264.sys ( nvmf6264+13e83 )
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: 0000000000000fa0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88003b4fe83, address which referenced memory
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
FAULTING_MODULE: fffff80002e4f000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a723142
WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
0000000000000fa0
CURRENT_IRQL: 0
FAULTING_IP:
nvmf6264+13e83
fffff880`03b4fe83 743b je nvmf6264+0x13ec0 (fffff880`03b4fec0)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from fffff80002ece2a9 to fffff80002eced00
STACK_TEXT:
fffff800`00b9c1f8 fffff800`02ece2a9 : 00000000`0000000a 00000000`00000fa0 00000000`00000002 00000000`00000001 : nt+0x7fd00
fffff800`00b9c200 00000000`0000000a : 00000000`00000fa0 00000000`00000002 00000000`00000001 fffff880`03b4fe83 : nt+0x7f2a9
fffff800`00b9c208 00000000`00000fa0 : 00000000`00000002 00000000`00000001 fffff880`03b4fe83 fffff800`00b97000 : 0xa
fffff800`00b9c210 00000000`00000002 : 00000000`00000001 fffff880`03b4fe83 fffff800`00b97000 00000000`00000000 : 0xfa0
fffff800`00b9c218 00000000`00000001 : fffff880`03b4fe83 fffff800`00b97000 00000000`00000000 00000000`00000000 : 0x2
fffff800`00b9c220 fffff880`03b4fe83 : fffff800`00b97000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1
fffff800`00b9c228 fffff800`00b97000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvmf6264+0x13e83
fffff800`00b9c230 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff800`00b97000
STACK_COMMAND: kb
FOLLOWUP_IP:
nvmf6264+13e83
fffff880`03b4fe83 743b je nvmf6264+0x13ec0 (fffff880`03b4fec0)
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: nvmf6264+13e83
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvmf6264
IMAGE_NAME: nvmf6264.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\051511-38719-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02e0e000 PsLoadedModuleList = 0xfffff800`03053650
Debug session time: Sun May 15 15:02:03.702 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:06.012
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {fffffa8013b8230e, e, 1, fffff8800f55df3f}
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : nvlddmkm.sys ( nvlddmkm+4eef3f )
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\051511-29749-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02e16000 PsLoadedModuleList = 0xfffff800`0305b650
Debug session time: Sun May 15 15:48:44.090 2011 (UTC - 4:00)
System Uptime: 0 days 0:34:27.400
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+7fcd0 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: nt
FAULTING_MODULE: fffff80002e16000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd5b
EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
FAULTING_IP:
+3334333830373266
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
BUGCHECK_STR: 0x1E_0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002e8d6be to fffff80002e95cd0
STACK_TEXT:
fffff800`00b9b2f8 fffff800`02e8d6be : fffff880`01863ebc fffff880`01863ebc fffff800`00b9ba70 fffff800`02ec1890 : nt+0x7fcd0
fffff800`00b9b300 fffff880`01863ebc : fffff880`01863ebc fffff800`00b9ba70 fffff800`02ec1890 00000000`00000000 : nt+0x776be
fffff800`00b9b308 fffff880`01863ebc : fffff800`00b9ba70 fffff800`02ec1890 00000000`00000000 fffff800`02ec155d : tcpip!LowMemoryEvent <PERF> (tcpip+0x1abebc)
fffff800`00b9b310 fffff800`00b9ba70 : fffff800`02ec1890 00000000`00000000 fffff800`02ec155d fffff800`0309c968 : tcpip!LowMemoryEvent <PERF> (tcpip+0x1abebc)
fffff800`00b9b318 fffff800`02ec1890 : 00000000`00000000 fffff800`02ec155d fffff800`0309c968 fffff800`02fd9cbc : 0xfffff800`00b9ba70
fffff800`00b9b320 00000000`00000000 : fffff800`02ec155d fffff800`0309c968 fffff800`02fd9cbc fffff800`02e16000 : nt+0xab890
STACK_COMMAND: kb
FOLLOWUP_IP:
nt+7fcd0
fffff800`02e95cd0 4883ec28 sub rsp,28h
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt+7fcd0
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntoskrnl.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------