hello - new to forum - not new to PC support. I'm simply looking for some additional eyes on this bug check analysis. I want to say it's a video driver issue, but not 100% sure and wanted some input...any thoughts? Any input or help troubleshooting would be greatly appreciated! :)

=============================

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

Symbol search path is: E:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Dec 1 23:06:26.375 2009 (GMT-8)
System Uptime: 0 days 16:22:31.104
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
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
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {e76584d8, 1, bd11a028, 1}


Could not read faulting driver name
Probably caused by : nv4_disp.dll ( nv4_disp!vppSubPictureUsingCelsius+8e8 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: e76584d8, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: bd11a028, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000001, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: e76584d8

FAULTING_IP:
nv4_disp!vppSubPictureUsingCelsius+8e8
bd11a028 895118 mov dword ptr [ecx+18h],edx

MM_INTERNAL_CODE: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: iw3sp.exe

LAST_CONTROL_TRANSFER: from bd0bc363 to bd11a028

STACK_TEXT:
9f2cb7e4 bd0bc363 e1dd3800 00000000 e6a606c0 nv4_disp!vppSubPictureUsingCelsius+0x8e8
9f2cb820 bd135c11 e20b4a40 bd0cb14d e18149e4 nv4_disp!_def_nv_d3d_context::ComputeUniqueness+0x b3
9f2cbaf4 e472bcd0 00000001 e17d28f0 00000000 nv4_disp!CVideoRankine::DiBltExSubpic+0xc21
WARNING: Frame IP not in any known module. Following frames may be wrong.
9f2cbb28 00000000 00000000 00000000 00000000 0xe472bcd0


STACK_COMMAND: kb

FOLLOWUP_IP:
nv4_disp!vppSubPictureUsingCelsius+8e8
bd11a028 895118 mov dword ptr [ecx+18h],edx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nv4_disp!vppSubPictureUsingCelsius+8e8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_disp

IMAGE_NAME: nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 4ac001a1

FAILURE_BUCKET_ID: 0x50_nv4_disp!vppSubPictureUsingCelsius+8e8

BUCKET_ID: 0x50_nv4_disp!vppSubPictureUsingCelsius+8e8

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

0: kd> lmvm nv4_disp
start end module name
bd012000 bd5b2880 nv4_disp M (pdb symbols) e:\windows\symbols\dll\nv4_disp.pdb
Loaded symbol image file: nv4_disp.dll
Image path: nv4_disp.dll
Image name: nv4_disp.dll
Timestamp: Sun Sep 27 17:21:53 2009 (4AC001A1)
CheckSum: 005A34A0
ImageSize: 005A0880
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

=======================

PC Specs:
+-----------------------------------------+
| System Summary |
+-----------------------------------------+
Processor
Processor: Intel Core 2 Duo 6300 1866 MHz
CPU Clock: 1866.7 MHz (7.0 x 266.7 MHz QDR)
Level 1 Cache: 2 x 32+32 kB (data+instr.)
Level 2 Cache: 1 x 2048 kB
Motherboard
Motherboard Vendor: Asustek Computer Inc.
Board Model: ASUSTeK Computer INC. P5B-Deluxe
BIOS Version: AMI BIOS 08.00.12
Chipset Name: Intel P965/G965 Express (Broadwater)
Chipset Vendor: Intel Corporation
Chipset: P965/G965 Memory Controller Hub
Southbridge Vendor: Intel Corporation
Southbridge: 82801HB/HR (ICH8/R) LPC Interface Controller
DMI/SMBIOS Version: 2.4
Memory
Memory Size: 2096236 kB (2047.11 MB)
System Memory: 2048 MB
Memory Module: 1024MB DDR2-800 SDRAM (Golden Empire)
Memory Module: 1024MB DDR2-800 SDRAM (Golden Empire)
Storage
HDD Model: Maxtor 7H500F0
HDD Size: 476940 MB (465.76 GB)
HDD Model: SAMSUNG HD160JJ
HDD Size: 152627 MB (149.05 GB)
HDD Model: Ext Hard Disk
HDD Size: 476940 MB (465.76 GB)
CD/DVD Model: TSSTcorpCD/DVDW SH-S182D
CD/DVD Speed: 48x (Write: 48x)
CD/DVD Model: ASUS DRW-1612BL
CD/DVD Speed: 48x (Write: 48x)
Video
Monitor Vendor: BenQ
Monitor Model: BenQ FP222W (Digital)
Video Chip Vendor: Nvidia Corp
Video Chip: GeForce 8800 GT
Video Memory Size: 512 MB
Sound
Sound Chip Vendor: Intel Corporation
Sound Chip: 82801H (ICH8 Family) HD Audio Controller
AC'97/HDA Codec Name: Analog Device AD1988B
Operating System
Operating System: MS Windows XP Professional (5.1.2600 Service Pack 3)

Welcome to D-A-L.

See if this is of any help to you;
http://www.ehow.com/how_5155420_stop-nvdispdll.html

Thanks for the suggestion, Danny

But don't I need that DLL for proper NVIDIA driver function?

I did read on that page you referenced that the Nv4_disp.dll was intended for Win2k compatibility, yes, but that particular file also shows as the main DLL for the driver in general when I do a sys info....so I'm confused.

I'm running winxp sp3 w/ Nvidia gpu - 8800GT - I guess I assumed that DLL was necessary for driver functionality either way...no?

As the article states, it's basically for Win 2000.

Try renaming the file and rebooting. If things are OK after the reboot, you can then either retain it, or delete it.