I have converted one of the dumps into a debuglog, can anyone decipher what is happening here?
Opened log file 'c:\debuglog.txt'
kd> .sympath srv*c:\symbols*
http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\symbols*
http://msdl.microsoft.com/download/symbols
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
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* 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: bfa7dc54, The address that the exception occurred at
Arg3: b36016d0, 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+a8c54
bfa7dc54 8b5610 mov edx,dword ptr [esi+10h]
TRAP_FRAME: b36016d0 -- (.trap 0xffffffffb36016d0)
.trap 0xffffffffb36016d0
ErrCode = 00000000
eax=00000001 ebx=004f005e ecx=00000000 edx=00000000 esi=53657661 edi=004f005e
eip=bfa7dc54 esp=b3601744 ebp=00000001 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+0xa8c54:
bfa7dc54 8b5610 mov edx,dword ptr [esi+10h] ds:0023:53657671=????????
.trap
Resetting default scope
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: msnmsgr.exe
LAST_CONTROL_TRANSFER: from bf907c09 to bfa7dc54
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b36017c0 bf907c09 e261d000 e19cec68 e1af2714 nv4_disp+0xa8c54
b36017f8 bf9c940b b3601810 b3601864 01b1e430 win32k!WatchdogDdGetAvailDriverMemory+0x3b
b3601854 8053ca28 0b200001 01b1e448 01b1e430 dxg!DxDdGetAvailDriverMemory+0xbb
b3601854 7c90eb94 0b200001 01b1e448 01b1e430 nt!KiFastCallEntry+0xf8
01b1e430 00000000 00000000 00000000 00000000 0x7c90eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
nv4_disp+a8c54
bfa7dc54 8b5610 mov edx,dword ptr [esi+10h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nv4_disp+a8c54
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nv4_disp
IMAGE_NAME: nv4_disp.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 453bdc7a
FAILURE_BUCKET_ID: 0x8E_nv4_disp+a8c54
BUCKET_ID: 0x8E_nv4_disp+a8c54
Followup: MachineOwner
---------
eax=00000001 ebx=004f005e ecx=00000000 edx=00000000 esi=53657661 edi=004f005e
eip=bfa7dc54 esp=b3601744 ebp=00000001 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+0xa8c54:
bfa7dc54 8b5610 mov edx,dword ptr [esi+10h] ds:0023:53657671=????????
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be wrong.
Update: Just replaced my 2 gigs with a 256MB Geil stick of RAM, and the same problem occurred with the same error message.
As the RAM was not faulty, tried the driver verifer in windows. Caused IO system verification error in stream.sys, wdm driver error 22e. Uninstalled video card drivers, reinstalled, and it seems to be working perfectly.