I am trying to help a friend fix his frequent bsods but I am fairly new at debugging the minidump info, if anybody can tell me what the following means I would be very grateful thanks in advance.
Code:
*******************************************************************************
* *
* 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: bfae521f, The address that the exception occurred at
Arg3: b4cbfad0, 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+11021f
bfae521f 8b8884000000 mov ecx,dword ptr [eax+84h]
TRAP_FRAME: b4cbfad0 -- (.trap 0xffffffffb4cbfad0)
ErrCode = 00000000
eax=69536972 ebx=00200000 ecx=e68841e8 edx=77beef00 esi=e68840c0 edi=00000000
eip=bfae521f esp=b4cbfb44 ebp=e68841e8 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nv4_disp+0x11021f:
bfae521f 8b8884000000 mov ecx,dword ptr [eax+84h] ds:0023:695369f6=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: left4dead.exe
LAST_CONTROL_TRANSFER: from bf819804 to bfae521f
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b4cbfb78 bf819804 b4cbfc64 bfdd2540 bfa8e2d1 nv4_disp+0x11021f
b4cbfc3c bf8f7441 b4cbfcfc e170b714 e2cf1590 win32k!EngSaveFloatingPointState+0x2a
b4cbfc74 bf9cc530 b4cbfcfc bf8f74dc e170b714 win32k!WatchdogDdDestroySurface+0x38
b4cbfd30 bf9ce3a4 e170b008 e2cf1590 b4cbfd50 dxg!vDdDisableSurfaceObject+0x294
b4cbfd54 8054162c e170b008 00000001 0012e5a0 dxg!DxDdDestroySurface+0x42
b4cbfd54 7c90e4f4 e170b008 00000001 0012e5a0 nt!KiFastCallEntry+0xfc
0012e5a0 00000000 00000000 00000000 00000000 0x7c90e4f4
STACK_COMMAND: kb
FOLLOWUP_IP:
nv4_disp+11021f
bfae521f 8b8884000000 mov ecx,dword ptr [eax+84h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nv4_disp+11021f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nv4_disp
IMAGE_NAME: nv4_disp.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 48ebd26f
FAILURE_BUCKET_ID: 0x8E_nv4_disp+11021f
BUCKET_ID: 0x8E_nv4_disp+11021f
Followup: MachineOwner