windows 8.1nvlddmkm.sys probleme
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff801770df753, The address that the exception occurred at
Arg3: ffffd000d199bc68, Exception Record Address
Arg4: ffffd000d199b470, Context Record Address
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
FAULTING_MODULE: fffff800ffc1f000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 5463c853
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
FAULTING_IP:
nvlddmkm+269753
fffff801`770df753 3938 cmp dword ptr [rax],edi
EXCEPTION_RECORD: ffffd000d199bc68 -- (.exr 0xffffd000d199bc68)
ExceptionAddress: fffff801770df753 (nvlddmkm+0x0000000000269753)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 000000001957b0f0
Attempt to read from address 000000001957b0f0
CONTEXT: ffffd000d199b470 -- (.cxr 0xffffd000d199b470;r)
rax=000000001957b0f0 rbx=0000000000000000 rcx=ffffd000d199bed8
rdx=0000000000000008 rsi=ffffe000171159f0 rdi=0000000054445352
rip=fffff801770df753 rsp=ffffd000d199bea0 rbp=ffffd000d199bef0
r8=0000000000000000 r9=0000000000000000 r10=ffffd000ca4e7260
r11=ffffd000d199bed0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
nvlddmkm+0x269753:
fffff801`770df753 3938 cmp dword ptr [rax],edi ds:002b:00000000`1957b0f0=????????
Last set context:
rax=000000001957b0f0 rbx=0000000000000000 rcx=ffffd000d199bed8
rdx=0000000000000008 rsi=ffffe000171159f0 rdi=0000000054445352
rip=fffff801770df753 rsp=ffffd000d199bea0 rbp=ffffd000d199bef0
r8=0000000000000000 r9=0000000000000000 r10=ffffd000ca4e7260
r11=ffffd000d199bed0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
nvlddmkm+0x269753:
fffff801`770df753 3938 cmp dword ptr [rax],edi ds:002b:00000000`1957b0f0=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: AV
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
LAST_CONTROL_TRANSFER: from ffffe000171bc000 to fffff801770df753
STACK_TEXT:
ffffd000`d199bea0 ffffe000`171bc000 : ffffe000`1705c790 ffffd000`d199bf90 fffff801`7701b203 ffffd000`d199bf30 : nvlddmkm+0x269753
ffffd000`d199bea8 ffffe000`1705c790 : ffffd000`d199bf90 fffff801`7701b203 ffffd000`d199bf30 00000000`00000001 : 0xffffe000`171bc000
ffffd000`d199beb0 ffffd000`d199bf90 : fffff801`7701b203 ffffd000`d199bf30 00000000`00000001 00000000`1957b0f0 : 0xffffe000`1705c790
ffffd000`d199beb8 fffff801`7701b203 : ffffd000`d199bf30 00000000`00000001 00000000`1957b0f0 00000000`1957b0f0 : 0xffffd000`d199bf90
ffffd000`d199bec0 ffffd000`d199bf30 : 00000000`00000001 00000000`1957b0f0 00000000`1957b0f0 00000000`00000004 : nvlddmkm+0x1a5203
ffffd000`d199bec8 00000000`00000001 : 00000000`1957b0f0 00000000`1957b0f0 00000000`00000004 000000ff`00000000 : 0xffffd000`d199bf30
ffffd000`d199bed0 00000000`1957b0f0 : 00000000`1957b0f0 00000000`00000004 000000ff`00000000 ffffe000`171bc000 : 0x1
ffffd000`d199bed8 00000000`1957b0f0 : 00000000`00000004 000000ff`00000000 ffffe000`171bc000 ffffe000`1705c790 : 0x1957b0f0
ffffd000`d199bee0 00000000`00000004 : 000000ff`00000000 ffffe000`171bc000 ffffe000`1705c790 fffff801`76e76000 : 0x1957b0f0
ffffd000`d199bee8 000000ff`00000000 : ffffe000`171bc000 ffffe000`1705c790 fffff801`76e76000 00000000`00000000 : 0x4
ffffd000`d199bef0 ffffe000`171bc000 : ffffe000`1705c790 fffff801`76e76000 00000000`00000000 ffffe000`171159f0 : 0x000000ff`00000000
ffffd000`d199bef8 ffffe000`1705c790 : fffff801`76e76000 00000000`00000000 ffffe000`171159f0 00000000`00000000 : 0xffffe000`171bc000
ffffd000`d199bf00 fffff801`76e76000 : 00000000`00000000 ffffe000`171159f0 00000000`00000000 ffffd000`d199bf58 : 0xffffe000`1705c790
ffffd000`d199bf08 00000000`00000000 : ffffe000`171159f0 00000000`00000000 ffffd000`d199bf58 fffff801`770dfe64 : nvlddmkm
FOLLOWUP_IP:
nvlddmkm+269753
fffff801`770df753 3938 cmp dword ptr [rax],edi
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nvlddmkm+269753
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr 0xffffd000d199b470 ; kb
BUCKET_ID: WRONG_SYMBOLS
FAILURE_BUCKET_ID: WRONG_SYMBOLS
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:wrong_symbols
FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8}
Followup: MachineOwner
---------