Lainaus:

---

*******************************************************************************
* *
* 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:
+3966306661383430
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: fffff88002f1b328 -- (.exr 0xfffff88002f1b328)
ExceptionAddress: fffff80002cdb6b2 (nt!KiTimerWaitTest+0x0000000000000212)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME: fffff88002f1b3d0 -- (.trap 0xfffff88002f1b3d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800507fc00 rbx=0000000000000000 rcx=effffa800526a800
rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cdb6b2 rsp=fffff88002f1b560 rbp=fffffa800507bc28
r8=fffff880009e9301 r9=0000000000000002 r10=0000000000000032
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!KiTimerWaitTest+0x212:
fffff800`02cdb6b2 48894108 mov qword ptr [rcx+8],rax ds:2a70:a808=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002cca5fe to fffff80002cd2c10

STACK_TEXT:
fffff880`02f1a408 fffff800`02cca5fe : 00000000`00000000 00000000`00000000 fffff880`02f1ab80 fffff800`02cfe830 : nt!KeBugCheck
fffff880`02f1a410 fffff800`02cfe4fd : fffff800`02edc71c fffff800`02e19c30 fffff800`02c56000 fffff880`02f1b328 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f1a440 fffff800`02cfd2d5 : fffff800`02e1d0fc fffff880`02f1a4b8 fffff880`02f1b328 fffff800`02c56000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f1a470 fffff800`02d0e361 : fffff880`02f1b328 fffff880`02f1ab80 fffff880`00000000 fffffa80`0507bc20 : nt!RtlDispatchException+0x415
fffff880`02f1ab50 fffff800`02cd22c2 : fffff880`02f1b328 fffffa80`0507bc28 fffff880`02f1b3d0 00000000`00000000 : nt!KiDispatchException+0x135
fffff880`02f1b1f0 fffff800`02cd0bca : fffffa80`05054000 fffffa80`05054000 00000000`00000000 fffff880`02f1b558 : nt!KiExceptionDispatch+0xc2
fffff880`02f1b3d0 fffff800`02cdb6b2 : 00000000`d8000000 fffffa80`05683dc0 00000000`00000001 fffffa80`056422a0 : nt!KiGeneralProtectionFault+0x10a
fffff880`02f1b560 fffff800`02cde43d : fffffa80`0507bc20 fffffa80`050cb920 fffffa80`050cb920 00000000`00000102 : nt!KiTimerWaitTest+0x212
fffff880`02f1b5e0 fffff800`02cde37e : 00000001`b1b41a07 fffff880`02f1bc58 00000000`0000b632 fffff880`009e9bc8 : nt!KiProcessExpiredTimerList+0x6d
fffff880`02f1bc30 fffff800`02cde167 : 00000002`6d2f13c1 00000002`0000b632 00000002`6d2f13e7 00000000`00000032 : nt!KiTimerExpiration+0x1be
fffff880`02f1bcd0 fffff800`02cca96a : fffff880`009e7180 fffff880`009f1f40 00000000`00000000 fffff880`049ac480 : nt!KiRetireDpcList+0x277
fffff880`02f1bd80 00000000`00000000 : fffff880`02f1c000 fffff880`02f16000 fffff880`02f1bd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

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

---

Lainaus, alkuperäisen viestin kirjoitti goljat:

---

Kaikki lähtee kyllä pyörimään ja valot syttyy emolle mutta näyttöön ei vain tule signaalia eikä kuulu POST piippausta. Ilmeisesti vika ei ole virtalähteessä? Miten rikkinäisen emon voi tunnistaa?

---