Дампы 3 штуки
Попробовал сам дебугером что-то сделать, но кроме того, что это nvlddkm.sys - о чем я и писал при создании темы - мне ничего не понять
читать дальше »
Microsoft Windows [Version 6.1.7600]
c:\>kdfe.cmd -v "c:\120610-20529-01.dmp"
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [c:\120610-20529-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*C:\symbols*
http://msdl.microsoft.com/download/symbols
Executable search path is: srv*C:\symbols*
http://msdl.microsoft.com/download/sym
bols
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e49000 PsLoadedModuleList = 0xfffff800`03086e50
Debug session time: Mon Dec 6 13:42:05.786 2010 (UTC + 3:00)
System Uptime: 0 days 3:03:34.550
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
.................
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sy
s
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff880046ab97d, fffff880027c1e08, fffff8
80027c1670}
Probably caused by : nvlddmkm.sys ( nvlddmkm+ab97d )
Followup: MachineOwner
---------
0: kd> kd: Reading initial command '!analyze -v; q'
*******************************************************************************
* *
* 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: fffff880046ab97d, The address that the exception occurred at
Arg3: fffff880027c1e08, Exception Record Address
Arg4: fffff880027c1670, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 -
FAULTING_IP:
nvlddmkm+ab97d
fffff880`046ab97d 488b09 mov rcx,qword ptr [rcx]
EXCEPTION_RECORD: fffff880027c1e08 -- (.exr 0xfffff880027c1e08)
ExceptionAddress: fffff880046ab97d (nvlddmkm+0x00000000000ab97d)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000ffffffff
Attempt to read from address 00000000ffffffff
CONTEXT: fffff880027c1670 -- (.cxr 0xfffff880027c1670)
rax=0000000000000000 rbx=fffffa800b035010 rcx=00000000ffffffff
rdx=fffffa800b035010 rsi=0000000000000000 rdi=00000000ffffffff
rip=fffff880046ab97d rsp=fffff880027c2040 rbp=fffff8a000116920
r8=fffffa80093c6000 r9=0000000000000002 r10=0000000000000000
r11=fffff880027c2080 r12=0000000000000000 r13=fffff880027c22e0
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
nvlddmkm+0xab97d:
fffff880`046ab97d 488b09 mov rcx,qword ptr [rcx] ds
00000000`f
fffffff=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 -
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 00000000ffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030f10e0
00000000ffffffff
FOLLOWUP_IP:
nvlddmkm+ab97d
fffff880`046ab97d 488b09 mov rcx,qword ptr [rcx]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff880046ab97d
STACK_TEXT:
fffff880`027c2040 00000000`00000000 : 00000000`00000000 00000000`00000000 000000
00`00000000 00000000`00000000 : nvlddmkm+0xab97d
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nvlddmkm+ab97d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ab19d92
STACK_COMMAND: .cxr 0xfffff880027c1670 ; kb
FAILURE_BUCKET_ID: X64_0x7E_nvlddmkm+ab97d
BUCKET_ID: X64_0x7E_nvlddmkm+ab97d
Followup: MachineOwner
---------
quit:
Для продолжения нажмите любую клавишу . . .
- Вложения
00000000`f