Question : Problem: Inspect Mini Dump for Graphics Card

I have inspected the mini-dump file with WinDbg 6.8, but, I don't know what to do or what it means.

Playing Joint Operations or Call of Duty 4 crashes my PC during the game. I removed my NVIDIA drivers, and reinstalled them, and still it keeps crashing.

Here is the mini-dump for you to inspect.
http://www.nk-inc.com/downloads/download.aspx?FileName=Mini110707-01.zip


Here is my specs:
PCMCIS P4 ATX 520w Dual Fan PS w/Clear Window
Intel Core2 Duo E6600 2.4Ghz Socket 775
Gigabyte 965P-DQ6 Socket 775 Motherboard
XFX GeForce 8600 GTS Extreme 256MB PCIe W/Dual Lin
US Modular 4096MB PC6400 DDR2 800MHz (2x2048)



Could someone please tell me what it means and what can I do to fix the problem.
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini110707-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\local cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Wed Nov  7 16:28:28.222 2007 (GMT-5)
System Uptime: 5 days 2:22:24.732
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, {88c54a58, 886502c8, 8ac90de0, 1}



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

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: 88c54a58, Pointer to a stuck thread object.  Do .thread then kb on it to find
      the hung location.
Arg2: 886502c8, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 8ac90de0, 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:  88c54a58

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xEA

PROCESS_NAME:  iw3mp.exe

LAST_CONTROL_TRANSFER:  from 00000000 to bfa88635

STACK_TEXT:  
ae77bce4 00000000 00000000 e11c2028 00000000 nv4_disp+0xb3635


STACK_COMMAND:  .thread 0xffffffff88c54a58 ; kb

FOLLOWUP_IP:
nv4_disp+b3635
bfa88635 49              dec     ecx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nv4_disp+b3635

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nv4_disp

IMAGE_NAME:  nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  46ee3c9a

FAILURE_BUCKET_ID:  0xEA_IMAGE_nv4_disp.dll_DATE_2007_09_17

BUCKET_ID:  0xEA_IMAGE_nv4_disp.dll_DATE_2007_09_17

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

0: kd> lmvm nv4_disp
start    end        module name
bf9d5000 bff58e00   nv4_disp T (no symbols)          
    Loaded symbol image file: nv4_disp.dll
    Image path: nv4_disp.dll
    Image name: nv4_disp.dll
    Timestamp:        Mon Sep 17 04:36:42 2007 (46EE3C9A)
    CheckSum:         00586E00
    ImageSize:        00583E00
    Translations:     0000.04b0 0000.04e0 0409.04b0 0409.04e0
Mini Kernel Dump does not contain unloaded driver list

Answer : Problem: Inspect Mini Dump for Graphics Card

Do you have another video card you can try? Good possibility the video card is failing or overheating.