Microsoft (R) Windows Debugger Version 6.3.9600.16384 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\dumps\021214-17128.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Symbol Path validation summary ************** Response Time (ms) Location Deferred srv*C:\symbols*http://msdl.microsoft.com/download/symbols ************* Symbol Path validation summary ************** Response Time (ms) Location Deferred srv*C:\symbols*http://msdl.microsoft.com/download/symbols 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/symbols Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532 Machine Name: Kernel base = 0x8321d000 PsLoadedModuleList = 0x833664d0 Debug session time: Wed Feb 12 17:27:47.687 2014 (UTC + 2:00) System Uptime: 0 days 0:37:18.936 Loading Kernel Symbols . Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long. Run !sym noisy before .reload to track down problems loading 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.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {c0000005, 94f6bcaa, bbc8363c, bbc83220} Probably caused by : nvlddmkm.sys ( nvlddmkm+167caa ) Followup: MachineOwner --------- 2: 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: c0000005, The exception code that was not handled Arg2: 94f6bcaa, The address that the exception occurred at Arg3: bbc8363c, Exception Record Address Arg4: bbc83220, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - FAULTING_IP: nvlddmkm+167caa 94f6bcaa f7400400400000 test dword ptr [eax+4],4000h EXCEPTION_RECORD: bbc8363c -- (.exr 0xffffffffbbc8363c) ExceptionAddress: 94f6bcaa (nvlddmkm+0x00167caa) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 00000004 Attempt to read from address 00000004 CONTEXT: bbc83220 -- (.cxr 0xffffffffbbc83220;r) eax=00000000 ebx=00000002 ecx=89075000 edx=00000000 esi=89039120 edi=00000000 eip=94f6bcaa esp=bbc83704 ebp=bbc83704 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 nvlddmkm+0x167caa: 94f6bcaa f7400400400000 test dword ptr [eax+4],4000h ds:0023:00000004=???????? Last set context: eax=00000000 ebx=00000002 ecx=89075000 edx=00000000 esi=89039120 edi=00000000 eip=94f6bcaa esp=bbc83704 ebp=bbc83704 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 nvlddmkm+0x167caa: 94f6bcaa f7400400400000 test dword ptr [eax+4],4000h ds:0023:00000004=???????? Resetting default scope PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - EXCEPTION_PARAMETER1: 00000000 EXCEPTION_PARAMETER2: 00000004 READ_ADDRESS: GetPointerFromAddress: unable to read from 8338684c Unable to read MiSystemVaType memory at 83365e20 00000004 FOLLOWUP_IP: nvlddmkm+167caa 94f6bcaa f7400400400000 test dword ptr [eax+4],4000h BUGCHECK_STR: 0x7E DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre LAST_CONTROL_TRANSFER: from 950fc120 to 94f6bcaa STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. bbc83704 950fc120 00000000 89039120 00000000 nvlddmkm+0x167caa bbc83720 950b0baa 89030000 89039120 00000002 nvlddmkm+0x2f8120 bbc83744 950b2ce4 89030000 89075000 89075000 nvlddmkm+0x2acbaa bbc83764 950875bc 89030000 89075000 00000005 nvlddmkm+0x2aece4 bbc83780 95188ae9 89030000 89075000 00000005 nvlddmkm+0x2835bc bbc837a0 95007b09 89098000 89075000 00000005 nvlddmkm+0x384ae9 bbc837b4 94fb284c 89030000 89075048 00000005 nvlddmkm+0x203b09 bbc837f0 9510c658 01030000 00000005 00000000 nvlddmkm+0x1ae84c bbc83840 9510c6c3 8907a000 00000003 00000001 nvlddmkm+0x308658 bbc8385c 94f5024f 89030000 00000001 86f3d000 nvlddmkm+0x3086c3 bbc838f0 94eb8fb2 00000000 00000000 00000001 nvlddmkm+0x14c24f bbc8398c 94eb88be 00000001 00000001 00000002 nvlddmkm+0xb4fb2 bbc83a50 9560178e ffffffff 00000001 00000002 nvlddmkm+0xb48be bbc83a84 956046b3 86f3d000 ffffffff 00000001 nvlddmkm+0x7fd78e bbc83aac 958adf15 86f3d000 ffffffff 00000001 nvlddmkm+0x8006b3 bbc83ad0 958aee4a 86ebf818 86f3d000 ffffffff dxgkrnl!DpiDxgkDdiSetPowerState+0x36 bbc83afc 958aec13 86f18020 00000001 00000004 dxgkrnl!DpiFdoSetAdapterPowerState+0x202 bbc83b40 958ae8c4 86f18020 e9caf760 bbc83b74 dxgkrnl!DpiFdoHandleDevicePower+0x346 bbc83b50 958ae03a 86f18020 e9caf760 e9caf818 dxgkrnl!DpiFdoDispatchPower+0x21 bbc83b74 94f08689 86f18020 e9caf760 00000023 dxgkrnl!DpiDispatchPower+0xc8 bbc83be0 94f081ca 86f18020 e9caf760 86f18020 nvlddmkm+0x104689 bbc83bf8 83232e79 86f18020 e9caf760 00000000 nvlddmkm+0x1041ca bbc83c50 8342613d 8ac0c4b0 9be8dff8 00000000 nt!PopIrpWorker+0x351 bbc83c90 832cd559 83232b28 8ac0c4b0 00000000 nt!PspSystemThreadStartup+0x9e 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nvlddmkm+167caa FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 5280d902 STACK_COMMAND: .cxr 0xffffffffbbc83220 ; kb FAILURE_BUCKET_ID: 0x7E_nvlddmkm+167caa BUCKET_ID: 0x7E_nvlddmkm+167caa ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x7e_nvlddmkm+167caa FAILURE_ID_HASH: {f11a8de3-a1a1-0c61-08b4-3e4dc5caaaac} Followup: MachineOwner --------- quit: