Unable to load image nv4_disp.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, bd0a9fa5, 9b0dc91c, 0}
Probably caused by : nv4_disp.dll ( nv4_disp+97fa5 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: bd0a9fa5, The address that the exception occurred at
Arg3: 9b0dc91c, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nv4_disp+97fa5
bd0a9fa5 8b7718 mov esi,dword ptr [edi+18h]
TRAP_FRAME: 9b0dc91c -- (.trap 0xffffffff9b0dc91c)
ErrCode = 00000000
eax=00000000 ebx=edf14580 ecx=edf17b64 edx=3bef5680 esi=e2e2ce00 edi=00000000
eip=bd0a9fa5 esp=9b0dc990 ebp=edf17fdc iopl=0 nv up ei pl zr ac pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010256
nv4_disp+0x97fa5:
bd0a9fa5 8b7718 mov esi,dword ptr [edi+18h] ds:0023:00000018=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: plugin-containe
LAST_CONTROL_TRANSFER: from 8054b6ed to bd0a9fa5
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
9b0dca4c 8054b6ed e1aaff0c e1aaf800 e1aafef4 nv4_disp+0x97fa5
9b0dcb18 805361f7 e4764e04 9b0dcb3c 00000000 nt!ExFreePoolWithTag+0x40d
9b0dcbb8 bf8f417b 9b0dcce8 9b0dccc0 00000000 nt!ExAcquireResourceExclusiveLite+0x67
9b0dcbf0 bd00bdbd 9b0dcce8 9b0dcd64 0466e948 win32k!WatchdogDdCreateSurface+0x38
9b0dcd3c 8054168c cf204ba2 0466eaf0 0466e954 dxg!dwDdCreateSurfaceOrBuffer+0x56d
9b0dcd3c 7c90e514 cf204ba2 0466eaf0 0466e954 nt!KiFastCallEntry+0xfc
0466ea14 00000000 00000000 00000000 00000000 0x7c90e514
STACK_COMMAND: kb
FOLLOWUP_IP:
nv4_disp+97fa5
bd0a9fa5 8b7718 mov esi,dword ptr [edi+18h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nv4_disp+97fa5
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nv4_disp
IMAGE_NAME: nv4_disp.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 503f8b2a
FAILURE_BUCKET_ID: 0x8E_nv4_disp+97fa5
BUCKET_ID: 0x8E_nv4_disp+97fa5
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: bd0a9fa5, The address that the exception occurred at
Arg3: 9b0dc91c, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nv4_disp+97fa5
bd0a9fa5 8b7718 mov esi,dword ptr [edi+18h]
TRAP_FRAME: 9b0dc91c -- (.trap 0xffffffff9b0dc91c)
ErrCode = 00000000
eax=00000000 ebx=edf14580 ecx=edf17b64 edx=3bef5680 esi=e2e2ce00 edi=00000000
eip=bd0a9fa5 esp=9b0dc990 ebp=edf17fdc iopl=0 nv up ei pl zr ac pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010256
nv4_disp+0x97fa5:
bd0a9fa5 8b7718 mov esi,dword ptr [edi+18h] ds:0023:00000018=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: plugin-containe
LAST_CONTROL_TRANSFER: from 8054b6ed to bd0a9fa5
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
9b0dca4c 8054b6ed e1aaff0c e1aaf800 e1aafef4 nv4_disp+0x97fa5
9b0dcb18 805361f7 e4764e04 9b0dcb3c 00000000 nt!ExFreePoolWithTag+0x40d
9b0dcbb8 bf8f417b 9b0dcce8 9b0dccc0 00000000 nt!ExAcquireResourceExclusiveLite+0x67
9b0dcbf0 bd00bdbd 9b0dcce8 9b0dcd64 0466e948 win32k!WatchdogDdCreateSurface+0x38
9b0dcd3c 8054168c cf204ba2 0466eaf0 0466e954 dxg!dwDdCreateSurfaceOrBuffer+0x56d
9b0dcd3c 7c90e514 cf204ba2 0466eaf0 0466e954 nt!KiFastCallEntry+0xfc
0466ea14 00000000 00000000 00000000 00000000 0x7c90e514
STACK_COMMAND: kb
FOLLOWUP_IP:
nv4_disp+97fa5
bd0a9fa5 8b7718 mov esi,dword ptr [edi+18h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nv4_disp+97fa5
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nv4_disp
IMAGE_NAME: nv4_disp.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 503f8b2a
FAILURE_BUCKET_ID: 0x8E_nv4_disp+97fa5
BUCKET_ID: 0x8E_nv4_disp+97fa5
Followup: MachineOwner
---------
2: kd> lmvm nv4_disp
start end module name
bd012000 bd45b380 nv4_disp T (no symbols)
Loaded symbol image file: nv4_disp.dll
Image path: nv4_disp.dll
Image name: nv4_disp.dll
Timestamp: Thu Aug 30 21:47:54 2012 (503F8B2A)
CheckSum: 0044A380
ImageSize: 00449380
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
