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


Loading Dump File [C:\Users\Preben\Desktop\Feil med PC\Mini101208-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/downloads/symbols
Executable search path is: 
Windows Server 2008 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18063.amd64fre.vistasp1_gdr.080425-1930
Kernel base = 0xfffff800`01e19000 PsLoadedModuleList = 0xfffff800`01fdedb0
Debug session time: Sun Oct 12 21:43:08.345 2008 (GMT+2)
System Uptime: 0 days 5:16:44.500
Loading Kernel Symbols
..........................................................................................................................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {2c3f8e2972, 2, 1, fffff80001e770f7}

Probably caused by : ntkrnlmp.exe ( nt!KiTimerExpiration+97 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000002c3f8e2972, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80001e770f7, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002042080
 0000002c3f8e2972 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiTimerExpiration+97
fffff800`01e770f7 0f83e187fdff    jae     nt! ?? ::FNODOBFM::`string'+0x39810 (fffff800`01e4f8de)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff8000310cb10 -- (.trap 0xfffff8000310cb10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=fffff80001f8d680
rip=fffff80001e770f7 rsp=fffff8000310cca0 rbp=0000000000000000
 r8=00000000001296b5  r9=0000000000000000 r10=fffffa80044a89f0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
nt!KiTimerExpiration+0x97:
fffff800`01e770f7 0f83e187fdff    jae     nt! ?? ::FNODOBFM::`string'+0x39810 (fffff800`01e4f8de) [br=0]
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80001e6e12e to fffff80001e6e390

STACK_TEXT:  
fffff800`0310c9c8 fffff800`01e6e12e : 00000000`0000000a 0000002c`3f8e2972 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`0310c9d0 fffff800`01e6d00b : 00000000`00000001 fffff800`0310cbc0 00000000`00000400 0000002c`3f90a191 : nt!KiBugCheckDispatch+0x6e
fffff800`0310cb10 fffff800`01e770f7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x20b
fffff800`0310cca0 fffff800`01e77a9f : 000008e8`04308e23 00000000`00000000 fffffa80`00000010 fffff800`01f90a80 : nt!KiTimerExpiration+0x97
fffff800`0310cd10 fffff800`01e78b72 : fffff800`01f8d680 fffff800`01f8d680 00000000`00000000 fffff800`01f92b80 : nt!KiRetireDpcList+0x1df
fffff800`0310cd80 fffff800`020465c0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x62
fffff800`0310cdb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!zzz_AsmCodeRange_End+0x4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiTimerExpiration+97
fffff800`01e770f7 0f83e187fdff    jae     nt! ?? ::FNODOBFM::`string'+0x39810 (fffff800`01e4f8de)

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiTimerExpiration+97

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4812c3f7

FAILURE_BUCKET_ID:  X64_0xA_W_nt!KiTimerExpiration+97

BUCKET_ID:  X64_0xA_W_nt!KiTimerExpiration+97

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