debugged minidmp, nv4_disp.dll problem

Yeh basically i have had problems with world of warcraft
i have also uninstalled all nvidia drivers then reinstalled again
when i load up wow this happens:
http://screenshot.xfire.com/screenshot/natural/8a621d8014343e4c91109b41cbfc6096080030fe.png
http://screenshot.xfire.com/screenshot/natural/9c8f1b131a766b62c3a8b6ba603f701af799165a.png

Then a bsod and reboot etc
minidump and sysdata comes up and i debugged the minidump and this comes up
:

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\Steven Frawley\My Documents\Mini053009-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.090206-1234
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sat May 30 11:39:29.109 2009 (GMT+10)
System Uptime: 0 days 0:27:17.748
Loading Kernel Symbols
...............................................................
................................................................
.......
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver 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                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck EA, {89e81020, 8ac62848, 8ad99598, 1}

Probably caused by : nv4_disp.dll ( nv4_disp+24132 )

Followup: MachineOwner
---------

0: kd> !analyze -v at the kd>
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

THREAD_STUCK_IN_DEVICE_DRIVER (ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines (OS builds <= 3790) it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 89e81020, Pointer to a stuck thread object.  Do .thread then kb on it to find
	the hung location.
Arg2: 8ac62848, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 8ad99598, Pointer to offending driver name.
Arg4: 00000001, Number of times this error occurred.  If a debugger is attached,
	this error is not always fatal -- see DESCRIPTION below.  On the
	blue screen, this will always equal 1.

Debugging Details:
------------------


FAULTING_THREAD:  89e81020

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xEA

PROCESS_NAME:  explorer.exe

LAST_CONTROL_TRANSFER:  from bf85a0eb to bf036132

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
b1d831e0 bf85a0eb b1d8367c 80539ac0 804d9190 nv4_disp+0x24132
b1d8320c 804ef19f 8ad07038 89a7aa28 00000014 win32k!GreDeviceIoControl+0x6f
b1d8324c bf85a17d 8ad07038 800d2000 b1d832a0 nt!IopfCallDriver+0x31
b1d83250 8ad07038 800d2000 b1d832a0 00000004 win32k!EngDeviceIoControl+0x1f
b1d83270 bf05dc3b 8ad07038 800d2000 b1d832a0 0x8ad07038
00000000 00000000 00000000 00000000 00000000 nv4_disp+0x4bc3b


STACK_COMMAND:  .thread 0xffffffff89e81020 ; kb

FOLLOWUP_IP: 
nv4_disp+24132
bf036132 897c240c        mov     dword ptr [esp+0Ch],edi

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nv4_disp+24132

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nv4_disp

IMAGE_NAME:  nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  49cd10ab

FAILURE_BUCKET_ID:  0xEA_IMAGE_nv4_disp.dll_DATE_2009_03_28

BUCKET_ID:  0xEA_IMAGE_nv4_disp.dll_DATE_2009_03_28

Followup: MachineOwner

so basically its something to do with nv4_disp.dll

 

ok how do i delete that ? do i just find it in nvidia folder?

 

ok i deleted all traces of nv4_disp through windows search, about 6 of them
then reinstalled latest geforce driver from nvidia

then rebooted, i logged into wow and got ingame, but then about 15 seconds later the game froze with colour and graphics stuffing up

then BSOD and reboot

humph...

 

http://img41.imageshack.us/img41/7231/damnwqe.jpg

temperatures are over 60degrees celcius, thats about 140 degrees fahrenheit, for the video card.

 

yeh the only other card i got is an hd3450 or something, which i cant run any games, but with the 9800gx2, even using firefox or browsing web will result in a graphic flicker and crash etc.
nothing like that with the 3450, ive already bought a new hd 4890, just incase if i were to buy another nvidia card and it still came up.

i would probably shit brix if it still happened with the 4890.
but yeh ive tried everything to fix it so its gotta be the card.

 

very broken 9800gx2, color and graphic botched, screenie included

Basically when i use this video card (9800GX2) all the colour and graphic is very "botched" and the colour is ruined.
i have uploaded a screenshot on what it looks like.

I have tried reinstalling the drivers, including completely removing the old one then installing new ones and also slightling older ones like 183.

I have tried the video card in two computers and on both of them it has the same turnout effect.

Before (two days ago) the computer would fine but when i ran any game such as world of warcraft of call of duty 4,5, the graphics would screw up and colour, then the computer will lock up resulting in blue screen of death and reboot.
But now the computer just looks like it is in the screenshot.

I have used the video card in my computer for about 12 months now with no problems anything near this.


Also my pc specs:
intel q9300
4 GB ram (only 3.5 because xp 32bit)
windows xp 32bit
500 W PSU

the screenshot is from another pc that uses vista, intel i7 and 750w psu
i tried using a HD3450 on my current computer with xp, and everything works fine (well besides i cant play games cos the card is crap lol)

screenshot:
http://img46.imageshack.us/img46/7425/ddddc.jpg

 

You know, I had problems with my old geforce4 with one of those nv4_disp bsod's when I booted up my computer. I could delete all of the drivers and I'd end up with the botched colours, but when I loaded the drivers, the bsod would just pop up.

I went and googled some of those error codes up on google. Turns out that my video card was busted. However, some of those codes meant that either my video card was busted, or my drivers were going wrong. Hopefully your problems are with your drivers, and not with your card. With your info though, I would think it's probably your card.

 

Ok, I had the same for about 2 months, search the web and did almost everything (cooling, temperature,new drivers, low level formating, reinstalling windows, etc) to fix that problem, but no luck, so, one day, i decided to update my BIOS version on my intel DG41TY, and somehow, fix the problem.

My NVIDIA 9400 GT 1GB XFX its working fine since.