Hi
Here is piece of debuglog:
"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, bf0d08bd, ac88aef4, 0}
Probably caused by : nv4_disp.dll ( nv4_disp+be8bd )
Followup: MachineOwner
---------
kd> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
* *
* 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: bf0d08bd, The address that the exception occurred at
Arg3: ac88aef4, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - K sky osoitteessa 0x%08lx viittasi muistiin osoitteessa 0x%08lx. Muisti ei voi olla %s.
(finnish language, don't be worry
)
FAULTING_IP:
nv4_disp+be8bd
bf0d08bd 833800 cmp dword ptr [eax],0
TRAP_FRAME: ac88aef4 -- (.trap 0xffffffffac88aef4)
.trap 0xffffffffac88aef4
ErrCode = 00000000
eax=00000002 ebx=ac88b178 ecx=e2331380 edx=00000001 esi=e1deff80 edi=00000f40
eip=bf0d08bd esp=ac88af68 ebp=00000000 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+0xbe8bd:
bf0d08bd 833800 cmp dword ptr [eax],0 ds:0023:00000002=????????
.trap
Resetting default scope
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: Wow.exe
LAST_CONTROL_TRANSFER: from 00000000 to bf0d08bd
STACK_TEXT:
00000000 00000000 00000000 00000000 00000000 nv4_disp+0xbe8bd
STACK_COMMAND: kb
FOLLOWUP_IP:
nv4_disp+be8bd
bf0d08bd 833800 cmp dword ptr [eax],0
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nv4_disp+be8bd
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nv4_disp
IMAGE_NAME: nv4_disp.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 48ebd26f
FAILURE_BUCKET_ID: 0x8E_nv4_disp+be8bd
BUCKET_ID: 0x8E_nv4_disp+be8bd
Followup: MachineOwner"
- There maybe conflict between wow.exe and Nvidia's file nv4_disp.dll.
http://forums.worldofwarcraft.com/thread.html?topicId=2766067410&postId=27656746285&sid=1
There someone said he has used these drivers:
http://downloads.guru3d.com/download.php?det=1621
(I'm not sure did this user have same problem like you. It's there wow-forums on page 2)
Older drivers may be solution for your problem also.
Here is also one:
http://support.microsoft.com/kb/936653/en-us