Here you go, I used "!analyze -v" and this the result:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: SRV*c:\symbols*
Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82a37000 PsLoadedModuleList = 0x82b7f810
Debug session time: Sat Dec 26 23:35:04.852 2009 (GMT-6)
System Uptime: 0 days 0:09:25.834
WARNING: Process directory table base AEB2E400 doesn't match CR3 00185000
WARNING: Process directory table base AEB2E400 doesn't match CR3 00185000
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffde00c). Type ".hh dbgerr001" for details
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 801de000, 0, 0}
PEB is paged out (Peb.Ldr = 7ffde00c). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffde00c). Type ".hh dbgerr001" for details
Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+5f )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 801de000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
PEB is paged out (Peb.Ldr = 7ffde00c). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffde00c). Type ".hh dbgerr001" for details
BUGCHECK_STR: 0x7f_8
TSS: 00000028 -- (.tss 0x28)
eax=ffff0023 ebx=00000000 ecx=875e3d08 edx=00000001 esi=875e3d08 edi=00000000
eip=82a7d57b esp=a154aff4 ebp=a154aff4 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!KiTrap0E+0x5f:
82a7d57b c74508000ddbba mov dword ptr [ebp+8],0BADB0D00h ss:0010:a154affc=????????
Resetting default scope
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: explorer.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 00000000 to 82a7d57b
STACK_TEXT:
a154aff4 00000000 00000000 00000000 00000000 nt!KiTrap0E+0x5f
STACK_COMMAND: .tss 0x28 ; kb
FOLLOWUP_IP:
nt!KiTrap0E+5f
82a7d57b c74508000ddbba mov dword ptr [ebp+8],0BADB0D00h
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiTrap0E+5f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc007
FAILURE_BUCKET_ID: 0x7f_8_nt!KiTrap0E+5f
BUCKET_ID: 0x7f_8_nt!KiTrap0E+5f
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 801de000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
PEB is paged out (Peb.Ldr = 7ffde00c). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffde00c). Type ".hh dbgerr001" for details
BUGCHECK_STR: 0x7f_8
TSS: 00000028 -- (.tss 0x28)
eax=ffff0023 ebx=00000000 ecx=875e3d08 edx=00000001 esi=875e3d08 edi=00000000
eip=82a7d57b esp=a154aff4 ebp=a154aff4 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!KiTrap0E+0x5f:
82a7d57b c74508000ddbba mov dword ptr [ebp+8],0BADB0D00h ss:0010:a154affc=????????
Resetting default scope
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: explorer.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 00000000 to 82a7d57b
STACK_TEXT:
a154aff4 00000000 00000000 00000000 00000000 nt!KiTrap0E+0x5f
STACK_COMMAND: .tss 0x28 ; kb
FOLLOWUP_IP:
nt!KiTrap0E+5f
82a7d57b c74508000ddbba mov dword ptr [ebp+8],0BADB0D00h
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiTrap0E+5f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc007
FAILURE_BUCKET_ID: 0x7f_8_nt!KiTrap0E+5f
BUCKET_ID: 0x7f_8_nt!KiTrap0E+5f
Followup: MachineOwner
---------
