Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\082811-33150-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
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0365d000 PsLoadedModuleList = 0xfffff800`038a2670
Debug session time: Sun Aug 28 17:20:58.084 2011 (UTC + 2:00)
System Uptime: 0 days 0:15:38.286
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
---------

3: 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: 
+6663386563656233
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

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff88002ffd3a8 -- (.exr 0xfffff88002ffd3a8)
ExceptionAddress: fffff800036e54e0 (nt!KiProcessExpiredTimerList+0x0000000000000110)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88002ffd450 -- (.trap 0xfffff88002ffd450)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffffa8007aea100
rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800036e54e0 rsp=fffff88002ffd5e0 rbp=fffffa8007aea168
 r8=fffff88002fd7301  r9=0000000000000002 r10=00000000000000f2
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po cy
nt!KiProcessExpiredTimerList+0x110:
fffff800`036e54e0 f00fba2f07      lock bts dword ptr [rdi],7 ds:d600:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800036d15fe to fffff800036d9c10

STACK_TEXT:  
fffff880`02ffc488 fffff800`036d15fe : 00000000`00000002 fffff880`01813200 fffff880`02ffcc00 fffff800`03705830 : nt!KeBugCheck
fffff880`02ffc490 fffff800`037054fd : fffff800`038e371c fffff800`03820c30 fffff800`0365d000 fffff880`02ffd3a8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ffc4c0 fffff800`037042d5 : fffff800`038240fc fffff880`02ffc538 fffff880`02ffd3a8 fffff800`0365d000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ffc4f0 fffff800`03715361 : fffff880`02ffd3a8 fffff880`02ffcc00 fffff880`00000000 f7fffa80`082c4360 : nt!RtlDispatchException+0x415
fffff880`02ffcbd0 fffff800`036d92c2 : fffff880`02ffd3a8 fffffa80`07aea168 fffff880`02ffd450 00000000`00000000 : nt!KiDispatchException+0x135
fffff880`02ffd270 fffff800`036d7bca : fffffa80`079fbc58 00000000`00016eb9 00000000`00000003 fffff880`0170e9e0 : nt!KiExceptionDispatch+0xc2
fffff880`02ffd450 fffff800`036e54e0 : fffffa80`07aea120 fffffa80`08eb5ba0 fffffa80`08eb5ba0 00000000`00000102 : nt!KiGeneralProtectionFault+0x10a
fffff880`02ffd5e0 fffff800`036e537e : 00000002`2f431a87 fffff880`02ffdc58 00000000`0000eaf2 fffff880`02fd93c8 : nt!KiProcessExpiredTimerList+0x110
fffff880`02ffdc30 fffff800`036e5167 : 00000000`99b5d2c1 00000000`0000eaf2 00000000`99b5d26e 00000000`000000f2 : nt!KiTimerExpiration+0x1be
fffff880`02ffdcd0 fffff800`036d196a : fffff880`02fd5180 fffff880`02fe0040 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff880`02ffdd80 00000000`00000000 : fffff880`02ffe000 fffff880`02ff8000 fffff880`02ffdd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`036d15fe 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
---------