Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
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*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.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a59000 PsLoadedModuleList = 0xfffff800`02c9e670
Debug session time: Thu Sep  8 18:49:22.465 2011 (UTC + 2:00)
System Uptime: 0 days 6:56:02.293
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}

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

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:
------------------


EXCEPTION_CODE: (Win32) 0 (0) - Der Vorgang wurde erfolgreich beendet.

FAULTING_IP: 
+6664353532646666
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff8000414e268 -- (.exr 0xfffff8000414e268)
ExceptionAddress: fffff80002ae141a (nt!KiProcessExpiredTimerList+0x000000000000004a)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

TRAP_FRAME:  fffff8000414e310 -- (.trap 0xfffff8000414e310)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffffa8003b2dc00
rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ae141a rsp=fffff8000414e4a0 rbp=0000000000186a88
 r8=fffff80002c4e001  r9=0000000000000003 r10=0000000000000088
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!KiProcessExpiredTimerList+0x4a:
fffff800`02ae141a f00fba2b07      lock bts dword ptr [rbx],7 ds:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002acd5fe to fffff80002ad5c10

STACK_TEXT:  
fffff800`0414d348 fffff800`02acd5fe : fffff880`0199d128 fffffa80`09174080 fffff800`0414dac0 fffff800`02b01830 : nt!KeBugCheck
fffff800`0414d350 fffff800`02b014fd : fffff800`02cdf71c fffff800`02c1cc30 fffff800`02a59000 fffff800`0414e268 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`0414d380 fffff800`02b002d5 : fffff800`02c200fc fffff800`0414d3f8 fffff800`0414e268 fffff800`02a59000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`0414d3b0 fffff800`02b11361 : fffff800`0414e268 fffff800`0414dac0 fffff800`00000000 fffff800`0414e4c8 : nt!RtlDispatchException+0x415
fffff800`0414da90 fffff800`02ad52c2 : fffff800`0414e268 fffffa80`09c50c20 fffff800`0414e310 00000000`00000003 : nt!KiDispatchException+0x135
fffff800`0414e130 fffff800`02ad341f : fffff800`0414e310 00000000`00000002 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff800`0414e310 fffff800`02ae141a : fffffa80`03b2dc20 fffffa80`09c50c68 fffffa80`09c50c68 00000000`00000102 : nt!KiInvalidOpcodeFault+0x11f
fffff800`0414e4a0 fffff800`02ae137e : 0000003a`1eafa5ad fffff800`0414eb18 00000000`00186a88 fffff800`02c4f388 : nt!KiProcessExpiredTimerList+0x4a
fffff800`0414eaf0 fffff800`02ae1167 : 00000013`4c4ed9c2 00000013`00186a88 00000013`4c4ed97d 00000000`00000088 : nt!KiTimerExpiration+0x1be
fffff800`0414eb90 fffff800`02acd96a : fffff800`02c4be80 fffff800`02c59cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`0414ec40 00000000`00000000 : fffff800`0414f000 fffff800`04149000 fffff800`0414ec00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`02acd5fe 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

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:
------------------


EXCEPTION_CODE: (Win32) 0 (0) - Der Vorgang wurde erfolgreich beendet.

FAULTING_IP: 
+6664353532646666
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff8000414e268 -- (.exr 0xfffff8000414e268)
ExceptionAddress: fffff80002ae141a (nt!KiProcessExpiredTimerList+0x000000000000004a)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

TRAP_FRAME:  fffff8000414e310 -- (.trap 0xfffff8000414e310)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffffa8003b2dc00
rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ae141a rsp=fffff8000414e4a0 rbp=0000000000186a88
 r8=fffff80002c4e001  r9=0000000000000003 r10=0000000000000088
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!KiProcessExpiredTimerList+0x4a:
fffff800`02ae141a f00fba2b07      lock bts dword ptr [rbx],7 ds:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002acd5fe to fffff80002ad5c10

STACK_TEXT:  
fffff800`0414d348 fffff800`02acd5fe : fffff880`0199d128 fffffa80`09174080 fffff800`0414dac0 fffff800`02b01830 : nt!KeBugCheck
fffff800`0414d350 fffff800`02b014fd : fffff800`02cdf71c fffff800`02c1cc30 fffff800`02a59000 fffff800`0414e268 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`0414d380 fffff800`02b002d5 : fffff800`02c200fc fffff800`0414d3f8 fffff800`0414e268 fffff800`02a59000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`0414d3b0 fffff800`02b11361 : fffff800`0414e268 fffff800`0414dac0 fffff800`00000000 fffff800`0414e4c8 : nt!RtlDispatchException+0x415
fffff800`0414da90 fffff800`02ad52c2 : fffff800`0414e268 fffffa80`09c50c20 fffff800`0414e310 00000000`00000003 : nt!KiDispatchException+0x135
fffff800`0414e130 fffff800`02ad341f : fffff800`0414e310 00000000`00000002 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff800`0414e310 fffff800`02ae141a : fffffa80`03b2dc20 fffffa80`09c50c68 fffffa80`09c50c68 00000000`00000102 : nt!KiInvalidOpcodeFault+0x11f
fffff800`0414e4a0 fffff800`02ae137e : 0000003a`1eafa5ad fffff800`0414eb18 00000000`00186a88 fffff800`02c4f388 : nt!KiProcessExpiredTimerList+0x4a
fffff800`0414eaf0 fffff800`02ae1167 : 00000013`4c4ed9c2 00000013`00186a88 00000013`4c4ed97d 00000000`00000088 : nt!KiTimerExpiration+0x1be
fffff800`0414eb90 fffff800`02acd96a : fffff800`02c4be80 fffff800`02c59cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`0414ec40 00000000`00000000 : fffff800`0414f000 fffff800`04149000 fffff800`0414ec00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`02acd5fe 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

Followup: MachineOwner
---------