Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\030111-19375-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\WINDOWS\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`03211000 PsLoadedModuleList = 0xfffff800`0344ee50
Debug session time: Tue Mar 1 16:45:11.634 2011 (UTC + 1:00)
System Uptime: 0 days 4:21:54.304
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) - The operation completed successfully.
FAULTING_IP:
+3039623165666439
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: fffff8000328ce39 (nt!KiProcessExpiredTimerList+0x0000000000000129)
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=fffffa8007169fe8 rbx=0000000000000000 rcx=f7fffa8007169fe8
rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000328ce39 rsp=fffff88002ffd5e0 rbp=fffffa8007751168
r8=fffff88002fd7301 r9=0000000000000004 r10=00000000000000d8
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KiProcessExpiredTimerList+0x129:
fffff800`0328ce39 48894108 mov qword ptr [rcx+8],rax ds:0002:f7fffa80`07169ff0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000327946e to fffff80003281710
STACK_TEXT:
fffff880`02ffc498 fffff800`0327946e : fffffa80`09fbea78 fffffa80`09fbea78 fffff880`02ffcc10 fffff800`032ae668 : nt!KeBugCheck
fffff880`02ffc4a0 fffff800`032a740d : fffff800`0348fb7c fffff800`033c9ea4 fffff800`03211000 fffff880`02ffd3a8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ffc4d0 fffff800`032aea90 : fffff800`033d0b34 fffff880`02ffc548 fffff880`02ffd3a8 fffff800`03211000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ffc500 fffff800`032bb9ef : fffff880`02ffd3a8 fffff880`02ffcc10 fffff880`00000000 fffffa80`07169fe0 : nt!RtlDispatchException+0x410
fffff880`02ffcbe0 fffff800`03280d82 : fffff880`02ffd3a8 fffffa80`07751168 fffff880`02ffd450 fffffa80`0a10ac00 : nt!KiDispatchException+0x16f
fffff880`02ffd270 fffff800`0327f68a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02ffd450 fffff800`0328ce39 : fffffa80`07751120 fffffa80`09faa010 fffffa80`09faa010 00000000`00000102 : nt!KiGeneralProtectionFault+0x10a
fffff880`02ffd5e0 fffff800`0328d4be : 00000024`9674a565 fffff880`02ffdc58 00000000`000f5ed8 fffff880`02fd9088 : nt!KiProcessExpiredTimerList+0x129
fffff880`02ffdc30 fffff800`0328ccb7 : 0000000c`33d746c3 0000000c`000f5ed8 0000000c`33d746ab 00000000`000000d8 : nt!KiTimerExpiration+0x1be
fffff880`02ffdcd0 fffff800`03289eea : fffff880`02fd5180 fffff880`02fdffc0 00000000`00000000 fffff880`06e6d588 : 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`0327946e 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: 4cc791bd
FAILURE_BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
BUCKET_ID: X64_0x1E_0_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) - The operation completed successfully.
FAULTING_IP:
+3039623165666439
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: fffff8000328ce39 (nt!KiProcessExpiredTimerList+0x0000000000000129)
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=fffffa8007169fe8 rbx=0000000000000000 rcx=f7fffa8007169fe8
rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000328ce39 rsp=fffff88002ffd5e0 rbp=fffffa8007751168
r8=fffff88002fd7301 r9=0000000000000004 r10=00000000000000d8
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KiProcessExpiredTimerList+0x129:
fffff800`0328ce39 48894108 mov qword ptr [rcx+8],rax ds:0002:f7fffa80`07169ff0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000327946e to fffff80003281710
STACK_TEXT:
fffff880`02ffc498 fffff800`0327946e : fffffa80`09fbea78 fffffa80`09fbea78 fffff880`02ffcc10 fffff800`032ae668 : nt!KeBugCheck
fffff880`02ffc4a0 fffff800`032a740d : fffff800`0348fb7c fffff800`033c9ea4 fffff800`03211000 fffff880`02ffd3a8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ffc4d0 fffff800`032aea90 : fffff800`033d0b34 fffff880`02ffc548 fffff880`02ffd3a8 fffff800`03211000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ffc500 fffff800`032bb9ef : fffff880`02ffd3a8 fffff880`02ffcc10 fffff880`00000000 fffffa80`07169fe0 : nt!RtlDispatchException+0x410
fffff880`02ffcbe0 fffff800`03280d82 : fffff880`02ffd3a8 fffffa80`07751168 fffff880`02ffd450 fffffa80`0a10ac00 : nt!KiDispatchException+0x16f
fffff880`02ffd270 fffff800`0327f68a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02ffd450 fffff800`0328ce39 : fffffa80`07751120 fffffa80`09faa010 fffffa80`09faa010 00000000`00000102 : nt!KiGeneralProtectionFault+0x10a
fffff880`02ffd5e0 fffff800`0328d4be : 00000024`9674a565 fffff880`02ffdc58 00000000`000f5ed8 fffff880`02fd9088 : nt!KiProcessExpiredTimerList+0x129
fffff880`02ffdc30 fffff800`0328ccb7 : 0000000c`33d746c3 0000000c`000f5ed8 0000000c`33d746ab 00000000`000000d8 : nt!KiTimerExpiration+0x1be
fffff880`02ffdcd0 fffff800`03289eea : fffff880`02fd5180 fffff880`02fdffc0 00000000`00000000 fffff880`06e6d588 : 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`0327946e 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: 4cc791bd
FAILURE_BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
BUCKET_ID: X64_0x1E_0_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) - The operation completed successfully.
FAULTING_IP:
+3039623165666439
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: fffff8000328ce39 (nt!KiProcessExpiredTimerList+0x0000000000000129)
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=fffffa8007169fe8 rbx=0000000000000000 rcx=f7fffa8007169fe8
rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000328ce39 rsp=fffff88002ffd5e0 rbp=fffffa8007751168
r8=fffff88002fd7301 r9=0000000000000004 r10=00000000000000d8
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KiProcessExpiredTimerList+0x129:
fffff800`0328ce39 48894108 mov qword ptr [rcx+8],rax ds:0002:f7fffa80`07169ff0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000327946e to fffff80003281710
STACK_TEXT:
fffff880`02ffc498 fffff800`0327946e : fffffa80`09fbea78 fffffa80`09fbea78 fffff880`02ffcc10 fffff800`032ae668 : nt!KeBugCheck
fffff880`02ffc4a0 fffff800`032a740d : fffff800`0348fb7c fffff800`033c9ea4 fffff800`03211000 fffff880`02ffd3a8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ffc4d0 fffff800`032aea90 : fffff800`033d0b34 fffff880`02ffc548 fffff880`02ffd3a8 fffff800`03211000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ffc500 fffff800`032bb9ef : fffff880`02ffd3a8 fffff880`02ffcc10 fffff880`00000000 fffffa80`07169fe0 : nt!RtlDispatchException+0x410
fffff880`02ffcbe0 fffff800`03280d82 : fffff880`02ffd3a8 fffffa80`07751168 fffff880`02ffd450 fffffa80`0a10ac00 : nt!KiDispatchException+0x16f
fffff880`02ffd270 fffff800`0327f68a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02ffd450 fffff800`0328ce39 : fffffa80`07751120 fffffa80`09faa010 fffffa80`09faa010 00000000`00000102 : nt!KiGeneralProtectionFault+0x10a
fffff880`02ffd5e0 fffff800`0328d4be : 00000024`9674a565 fffff880`02ffdc58 00000000`000f5ed8 fffff880`02fd9088 : nt!KiProcessExpiredTimerList+0x129
fffff880`02ffdc30 fffff800`0328ccb7 : 0000000c`33d746c3 0000000c`000f5ed8 0000000c`33d746ab 00000000`000000d8 : nt!KiTimerExpiration+0x1be
fffff880`02ffdcd0 fffff800`03289eea : fffff880`02fd5180 fffff880`02fdffc0 00000000`00000000 fffff880`06e6d588 : 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`0327946e 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: 4cc791bd
FAILURE_BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
BUCKET_ID: X64_0x1E_0_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) - The operation completed successfully.
FAULTING_IP:
+3039623165666439
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: fffff8000328ce39 (nt!KiProcessExpiredTimerList+0x0000000000000129)
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=fffffa8007169fe8 rbx=0000000000000000 rcx=f7fffa8007169fe8
rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000328ce39 rsp=fffff88002ffd5e0 rbp=fffffa8007751168
r8=fffff88002fd7301 r9=0000000000000004 r10=00000000000000d8
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KiProcessExpiredTimerList+0x129:
fffff800`0328ce39 48894108 mov qword ptr [rcx+8],rax ds:0002:f7fffa80`07169ff0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000327946e to fffff80003281710
STACK_TEXT:
fffff880`02ffc498 fffff800`0327946e : fffffa80`09fbea78 fffffa80`09fbea78 fffff880`02ffcc10 fffff800`032ae668 : nt!KeBugCheck
fffff880`02ffc4a0 fffff800`032a740d : fffff800`0348fb7c fffff800`033c9ea4 fffff800`03211000 fffff880`02ffd3a8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ffc4d0 fffff800`032aea90 : fffff800`033d0b34 fffff880`02ffc548 fffff880`02ffd3a8 fffff800`03211000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ffc500 fffff800`032bb9ef : fffff880`02ffd3a8 fffff880`02ffcc10 fffff880`00000000 fffffa80`07169fe0 : nt!RtlDispatchException+0x410
fffff880`02ffcbe0 fffff800`03280d82 : fffff880`02ffd3a8 fffffa80`07751168 fffff880`02ffd450 fffffa80`0a10ac00 : nt!KiDispatchException+0x16f
fffff880`02ffd270 fffff800`0327f68a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02ffd450 fffff800`0328ce39 : fffffa80`07751120 fffffa80`09faa010 fffffa80`09faa010 00000000`00000102 : nt!KiGeneralProtectionFault+0x10a
fffff880`02ffd5e0 fffff800`0328d4be : 00000024`9674a565 fffff880`02ffdc58 00000000`000f5ed8 fffff880`02fd9088 : nt!KiProcessExpiredTimerList+0x129
fffff880`02ffdc30 fffff800`0328ccb7 : 0000000c`33d746c3 0000000c`000f5ed8 0000000c`33d746ab 00000000`000000d8 : nt!KiTimerExpiration+0x1be
fffff880`02ffdcd0 fffff800`03289eea : fffff880`02fd5180 fffff880`02fdffc0 00000000`00000000 fffff880`06e6d588 : 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`0327946e 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: 4cc791bd
FAILURE_BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
BUCKET_ID: X64_0x1E_0_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) - The operation completed successfully.
FAULTING_IP:
+3039623165666439
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: fffff8000328ce39 (nt!KiProcessExpiredTimerList+0x0000000000000129)
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=fffffa8007169fe8 rbx=0000000000000000 rcx=f7fffa8007169fe8
rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000328ce39 rsp=fffff88002ffd5e0 rbp=fffffa8007751168
r8=fffff88002fd7301 r9=0000000000000004 r10=00000000000000d8
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KiProcessExpiredTimerList+0x129:
fffff800`0328ce39 48894108 mov qword ptr [rcx+8],rax ds:0002:f7fffa80`07169ff0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000327946e to fffff80003281710
STACK_TEXT:
fffff880`02ffc498 fffff800`0327946e : fffffa80`09fbea78 fffffa80`09fbea78 fffff880`02ffcc10 fffff800`032ae668 : nt!KeBugCheck
fffff880`02ffc4a0 fffff800`032a740d : fffff800`0348fb7c fffff800`033c9ea4 fffff800`03211000 fffff880`02ffd3a8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ffc4d0 fffff800`032aea90 : fffff800`033d0b34 fffff880`02ffc548 fffff880`02ffd3a8 fffff800`03211000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ffc500 fffff800`032bb9ef : fffff880`02ffd3a8 fffff880`02ffcc10 fffff880`00000000 fffffa80`07169fe0 : nt!RtlDispatchException+0x410
fffff880`02ffcbe0 fffff800`03280d82 : fffff880`02ffd3a8 fffffa80`07751168 fffff880`02ffd450 fffffa80`0a10ac00 : nt!KiDispatchException+0x16f
fffff880`02ffd270 fffff800`0327f68a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02ffd450 fffff800`0328ce39 : fffffa80`07751120 fffffa80`09faa010 fffffa80`09faa010 00000000`00000102 : nt!KiGeneralProtectionFault+0x10a
fffff880`02ffd5e0 fffff800`0328d4be : 00000024`9674a565 fffff880`02ffdc58 00000000`000f5ed8 fffff880`02fd9088 : nt!KiProcessExpiredTimerList+0x129
fffff880`02ffdc30 fffff800`0328ccb7 : 0000000c`33d746c3 0000000c`000f5ed8 0000000c`33d746ab 00000000`000000d8 : nt!KiTimerExpiration+0x1be
fffff880`02ffdcd0 fffff800`03289eea : fffff880`02fd5180 fffff880`02fdffc0 00000000`00000000 fffff880`06e6d588 : 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`0327946e 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: 4cc791bd
FAILURE_BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
BUCKET_ID: X64_0x1E_0_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) - The operation completed successfully.
FAULTING_IP:
+3039623165666439
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: fffff8000328ce39 (nt!KiProcessExpiredTimerList+0x0000000000000129)
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=fffffa8007169fe8 rbx=0000000000000000 rcx=f7fffa8007169fe8
rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000328ce39 rsp=fffff88002ffd5e0 rbp=fffffa8007751168
r8=fffff88002fd7301 r9=0000000000000004 r10=00000000000000d8
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KiProcessExpiredTimerList+0x129:
fffff800`0328ce39 48894108 mov qword ptr [rcx+8],rax ds:0002:f7fffa80`07169ff0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000327946e to fffff80003281710
STACK_TEXT:
fffff880`02ffc498 fffff800`0327946e : fffffa80`09fbea78 fffffa80`09fbea78 fffff880`02ffcc10 fffff800`032ae668 : nt!KeBugCheck
fffff880`02ffc4a0 fffff800`032a740d : fffff800`0348fb7c fffff800`033c9ea4 fffff800`03211000 fffff880`02ffd3a8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ffc4d0 fffff800`032aea90 : fffff800`033d0b34 fffff880`02ffc548 fffff880`02ffd3a8 fffff800`03211000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ffc500 fffff800`032bb9ef : fffff880`02ffd3a8 fffff880`02ffcc10 fffff880`00000000 fffffa80`07169fe0 : nt!RtlDispatchException+0x410
fffff880`02ffcbe0 fffff800`03280d82 : fffff880`02ffd3a8 fffffa80`07751168 fffff880`02ffd450 fffffa80`0a10ac00 : nt!KiDispatchException+0x16f
fffff880`02ffd270 fffff800`0327f68a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02ffd450 fffff800`0328ce39 : fffffa80`07751120 fffffa80`09faa010 fffffa80`09faa010 00000000`00000102 : nt!KiGeneralProtectionFault+0x10a
fffff880`02ffd5e0 fffff800`0328d4be : 00000024`9674a565 fffff880`02ffdc58 00000000`000f5ed8 fffff880`02fd9088 : nt!KiProcessExpiredTimerList+0x129
fffff880`02ffdc30 fffff800`0328ccb7 : 0000000c`33d746c3 0000000c`000f5ed8 0000000c`33d746ab 00000000`000000d8 : nt!KiTimerExpiration+0x1be
fffff880`02ffdcd0 fffff800`03289eea : fffff880`02fd5180 fffff880`02fdffc0 00000000`00000000 fffff880`06e6d588 : 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`0327946e 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: 4cc791bd
FAILURE_BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
Followup: MachineOwner
---------
Oprostite za otvaranje nove teme,ali nisam mogao postati u onu svoju staru.
Ako znate zaključiti u čemu je problem,molim pomozite!
