Nov thinkpad w510 se ruši. Mučim se z !analyze -v ....

Bi bil zelo vesel, če bi mi kdo znal razvozlati rezultat Windbg in povedati kaj v moji čisto novi mašini je treba zamenjat. Tole napiše:

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt! ?? ::FNODOBFM::`string'+c1f1
fffff800`03017ee4 8a01 mov al,byte ptr [rcx]

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 000007ffffff0000

READ_ADDRESS: 000007ffffff0000

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR: 0x1E_c0000005

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: devenv.exe

CURRENT_IRQL: 1

TRAP_FRAME: fffff8801d86ae70 -- (.trap 0xfffff8801d86ae70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000007ffffff0000 rbx=0000000000000000 rcx=000007ffffff0000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003017ee4 rsp=fffff8801d86b000 rbp=000000007343ac00
r8=0000000000000000 r9=0000000073473528 r10=fffff8801d86bba8
r11=0000000073420000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt! ?? ::FNODOBFM::`string'+0xc1f1:
fffff800`03017ee4 8a01 mov al,byte ptr [rcx] ds:000007ff`ffff0000=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800030da5d8 to fffff8000308ed00

STACK_TEXT:
fffff880`1d86a5e8 fffff800`030da5d8 : 00000000`0000001e ffffffff`c0000005 fffff800`03017ee4 00000000`00000000 : nt!KeBugCheckEx
fffff880`1d86a5f0 fffff800`0308e382 : fffff880`1d86adc8 fffff880`1d86b120 fffff880`1d86ae70 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x4987d
fffff880`1d86ac90 fffff800`0308cefa : 00000000`00000000 000007ff`ffff0000 fffff880`1d86af00 fffff880`1d86b120 : nt!KiExceptionDispatch+0xc2
fffff880`1d86ae70 fffff800`03017ee4 : 00000000`00004204 00000000`00010206 fffff880`1d86b020 00000000`00000018 : nt!KiPageFault+0x23a
fffff880`1d86b000 fffff800`0337f8ad : fffff880`00000000 00000000`73420000 fffff880`00000000 fffff880`00000000 : nt! ?? ::FNODOBFM::`string'+0xc1f1
fffff880`1d86b090 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PspGetSetContextInternal+0x265


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+c1f1
fffff800`03017ee4 8a01 mov al,byte ptr [rcx]

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+c1f1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd5b

FAILURE_BUCKET_ID: X64_0x1E_c0000005_nt!_??_::FNODOBFM::_string_+c1f1

BUCKET_ID: X64_0x1E_c0000005_nt!_??_::FNODOBFM::_string_+c1f1

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

5: 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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80003017ee4, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 000007ffffff0000, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt! ?? ::FNODOBFM::`string'+c1f1
fffff800`03017ee4 8a01 mov al,byte ptr [rcx]

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 000007ffffff0000

READ_ADDRESS: 000007ffffff0000

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR: 0x1E_c0000005

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: devenv.exe

CURRENT_IRQL: 1

TRAP_FRAME: fffff8801d86ae70 -- (.trap 0xfffff8801d86ae70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000007ffffff0000 rbx=0000000000000000 rcx=000007ffffff0000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003017ee4 rsp=fffff8801d86b000 rbp=000000007343ac00
r8=0000000000000000 r9=0000000073473528 r10=fffff8801d86bba8
r11=0000000073420000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt! ?? ::FNODOBFM::`string'+0xc1f1:
fffff800`03017ee4 8a01 mov al,byte ptr [rcx] ds:000007ff`ffff0000=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800030da5d8 to fffff8000308ed00

STACK_TEXT:
fffff880`1d86a5e8 fffff800`030da5d8 : 00000000`0000001e ffffffff`c0000005 fffff800`03017ee4 00000000`00000000 : nt!KeBugCheckEx
fffff880`1d86a5f0 fffff800`0308e382 : fffff880`1d86adc8 fffff880`1d86b120 fffff880`1d86ae70 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x4987d
fffff880`1d86ac90 fffff800`0308cefa : 00000000`00000000 000007ff`ffff0000 fffff880`1d86af00 fffff880`1d86b120 : nt!KiExceptionDispatch+0xc2
fffff880`1d86ae70 fffff800`03017ee4 : 00000000`00004204 00000000`00010206 fffff880`1d86b020 00000000`00000018 : nt!KiPageFault+0x23a
fffff880`1d86b000 fffff800`0337f8ad : fffff880`00000000 00000000`73420000 fffff880`00000000 fffff880`00000000 : nt! ?? ::FNODOBFM::`string'+0xc1f1
fffff880`1d86b090 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PspGetSetContextInternal+0x265


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+c1f1
fffff800`03017ee4 8a01 mov al,byte ptr [rcx]

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+c1f1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd5b

FAILURE_BUCKET_ID: X64_0x1E_c0000005_nt!_??_::FNODOBFM::_string_+c1f1

BUCKET_ID: X64_0x1E_c0000005_nt!_??_::FNODOBFM::_string_+c1f1

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