Opened log file 'c:\debuglog.txt'
0: kd> .sympath srv*c:\symbols*
http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\symbols*
http://msdl.microsoft.com/download/symbols
WARNING: Whitespace at end of path element
0: kd> .sympath srv*c:\symbols*
http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\symbols*
http://msdl.microsoft.com/download/symbols
0: kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q
Loading Kernel Symbols
.................................................. .................................................. .............................
Loading User Symbols
Loading unloaded module list
..........
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 *
* *
************************************************** *****************************
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: bfb09610, The address that the exception occurred at
Arg3: b59aca68, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a "0x%08lx" ha fatto riferimento alla memoria a "0x%08lx". La memoria non poteva essere "%s".
FAULTING_IP:
nv4_disp+135610
bfb09610 668b414c mov ax,word ptr [ecx+4Ch]
TRAP_FRAME: b59aca68 -- (.trap 0xffffffffb59aca68)
.trap 0xffffffffb59aca68
ErrCode = 00000000
eax=e1e9a480 ebx=e1e9b000 ecx=00000000 edx=ffffffff esi=0b1f1408 edi=b59acb74
eip=bfb09610 esp=b59acadc ebp=00000001 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
nv4_disp+0x135610:
bfb09610 668b414c mov ax,word ptr [ecx+4Ch] ds:0023:0000004c=????
.trap
Resetting default scope
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: fsx.exe
LAST_CONTROL_TRANSFER: from bfb54408 to bfb09610
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b59acad8 bfb54408 e1e9b000 00000000 00000000 nv4_disp+0x135610
b59acadc e1e9b000 00000000 00000000 b59acbb0 nv4_disp+0x180408
b59acae0 00000000 00000000 b59acbb0 e1ce0808 0xe1e9b000
STACK_COMMAND: kb
FOLLOWUP_IP:
nv4_disp+135610
bfb09610 668b414c mov ax,word ptr [ecx+4Ch]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nv4_disp+135610
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nv4_disp
IMAGE_NAME: nv4_disp.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 46ee3c9a
FAILURE_BUCKET_ID: 0x8E_nv4_disp+135610
BUCKET_ID: 0x8E_nv4_disp+135610
Followup: MachineOwner