Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

nv4_disp.dll cod4 Crash


  • Please log in to reply
3 replies to this topic

#1 proxzor781

proxzor781

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:07:07 AM

Posted 13 February 2009 - 08:47 PM

Hey guys. I am running windows XP 64 bit pro. My problem is that when I play call of Duty with no antialiasing or antialiasing at 2x, the computer will crash with a bsod showing the following error message below. It never crashs when I have antialiasing set to 4x. This is annoying and very strange. You guys are my last hope. Please help. I run dual sli 8800 GTS and Intel Core 2 Quad Q6600. It never does it on a previous driver version. I belive it was the Nvidia 165 driver version. I updated direct x and nvidia drivers to no avail.


Microsoft Windows Debugger Version 6.11.0001.402 AMD64
Copyright Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini021309-02.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:
*** WARNING: Unable to verify checksum for ntkrnlmp.exe
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 3790.srv03_sp2_gdr.080813-1204
Machine Name:
Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d4140
Debug session time: Fri Feb 13 20:20:42.515 2009 (GMT-5)
System Uptime: 0 days 2:17:37.615
*** WARNING: Unable to verify checksum for ntkrnlmp.exe
Loading Kernel Symbols
...............................................................
................................................................
...
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff97ffd10efd8, fffffadf894cad40, 0}

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
Probably caused by : nv4_disp.dll ( nv4_disp+e6fd8 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff97ffd10efd8, Address of the exception record for the exception that caused the bugcheck
Arg3: fffffadf894cad40, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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+e6fd8
fffff97f`fd10efd8 8b08 mov ecx,dword ptr [rax]

CONTEXT: fffffadf894cad40 -- (.cxr 0xfffffadf894cad40)
rax=0000000000000000 rbx=fffffa8006991d00 rcx=0000000000000000
rdx=0000000000000240 rsi=0000000000000000 rdi=0000000000002041
rip=fffff97ffd10efd8 rsp=fffffadf894cb550 rbp=000000000000001f
r8=0000000000000000 r9=0000000000000000 r10=00082c41a0000000
r11=0000000000202000 r12=fffffa80056367a8 r13=0000000000100009
r14=0000000000000000 r15=fffffa8006991d00
iopl=0 nv up ei ng nz ac pe cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010293
nv4_disp+0xe6fd8:
fffff97f`fd10efd8 8b08 mov ecx,dword ptr [rax] ds:002b:00000000`00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: iw3mp.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffffa8003cc3100 to fffff97ffd10efd8

STACK_TEXT:
fffffadf`894cb550 fffffa80`03cc3100 : 00000000`00000001 00000000`00000000 00000000`00000001 00000000`00000000 : nv4_disp+0xe6fd8
fffffadf`894cb558 00000000`00000001 : 00000000`00000000 00000000`00000001 00000000`00000000 fffffa80`06992000 : 0xfffffa80`03cc3100
fffffadf`894cb560 00000000`00000000 : 00000000`00000001 00000000`00000000 fffffa80`06992000 00000000`0083e800 : 0x1


FOLLOWUP_IP:
nv4_disp+e6fd8
fffff97f`fd10efd8 8b08 mov ecx,dword ptr [rax]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nv4_disp+e6fd8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_disp

IMAGE_NAME: nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 496ebfdf

STACK_COMMAND: .cxr 0xfffffadf894cad40 ; kb

FAILURE_BUCKET_ID: X64_0x3B_nv4_disp+e6fd8

BUCKET_ID: X64_0x3B_nv4_disp+e6fd8

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

0: kd> lmvm nv4_disp
start end module name
fffff97f`fd028000 fffff97f`fd8aff00 nv4_disp T (no symbols)
Loaded symbol image file: nv4_disp.dll
Image path: nv4_disp.dll
Image name: nv4_disp.dll
Timestamp: Wed Jan 14 23:47:27 2009 (496EBFDF)
CheckSum: 0088ABA0
ImageSize: 00887F00
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

Edited by proxzor781, 13 February 2009 - 08:53 PM.


BC AdBot (Login to Remove)

 


#2 proxzor781

proxzor781
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:07:07 AM

Posted 14 February 2009 - 03:34 AM

Well reinstalled Nvidia Drivers. No longer the BSOD saying Nv4_disp.dll. Now it says dxg.sys. HELP!!!!

#3 proxzor781

proxzor781
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:07:07 AM

Posted 14 February 2009 - 05:37 PM

Microsoft ® Windows Debugger Version 6.11.0001.402 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini021409-02.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:
*** WARNING: Unable to verify checksum for ntkrnlmp.exe
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 3790.srv03_sp2_gdr.080813-1204
Machine Name:
Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d4140
Debug session time: Sat Feb 14 17:27:46.093 2009 (GMT-5)
System Uptime: 0 days 4:36:39.815
*** WARNING: Unable to verify checksum for ntkrnlmp.exe
Loading Kernel Symbols
...............................................................
................................................................
..
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff97ffd016144, fffffadf88bd18f0, 0}

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
Probably caused by : nv4_disp.dll ( nv4_disp+100d97 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff97ffd016144, Address of the exception record for the exception that caused the bugcheck
Arg3: fffffadf88bd18f0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
dxg!DxDdFreePrivateUserMem+94
fffff97f`fd016144 488b5870 mov rbx,qword ptr [rax+70h]

CONTEXT: fffffadf88bd18f0 -- (.cxr 0xfffffadf88bd18f0)
rax=0000000000000000 rbx=fffffa800517f950 rcx=fffffa800517f968
rdx=000000002eda0000 rsi=fffffa800083d700 rdi=000000002eda0000
rip=fffff97ffd016144 rsp=fffffadf88bd2100 rbp=0000000000000008
r8=0000000000000008 r9=0000000000000000 r10=0000000000000001
r11=fffffadf9a120408 r12=0000000000000000 r13=0000000000000007
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
dxg!DxDdFreePrivateUserMem+0x94:
fffff97f`fd016144 488b5870 mov rbx,qword ptr [rax+70h] ds:002b:00000000`00000070=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: iw3mp.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff97ffd128d97 to fffff97ffd016144

STACK_TEXT:
fffffadf`88bd2100 fffff97f`fd128d97 : 00000000`00000000 00000000`0000000b fffffa80`06ad5440 00000000`00000000 : dxg!DxDdFreePrivateUserMem+0x94
fffffadf`88bd2130 00000000`00000000 : 00000000`0000000b fffffa80`06ad5440 00000000`00000000 00000000`00000000 : nv4_disp+0x100d97


FOLLOWUP_IP:
nv4_disp+100d97
fffff97f`fd128d97 ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nv4_disp+100d97

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_disp

IMAGE_NAME: nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 496ebfdf

STACK_COMMAND: .cxr 0xfffffadf88bd18f0 ; kb

FAILURE_BUCKET_ID: X64_0x3B_nv4_disp+100d97

BUCKET_ID: X64_0x3B_nv4_disp+100d97

Followup: MachineOwner


PLEASE HELP

#4 fineyoung25

fineyoung25

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:08:07 AM

Posted 05 March 2009 - 07:22 PM

Hi, have you found a solution to your problem ?

I have the very same problem.

It seems like a copy/paste of my situation. :thumbsup:

I can't play COD4 for hours without having to reboot because of a BSOD.

Usually its because of my nvidia GPU driver ( nv4_disp.dll )
I use windebug to parse crash reports.

Sometimes COD4 crashes to desktop and I still need to reboot to be sure it wont crash again in few minutes.

I've use everest to monitor my GPU temps and I found out that my 8800 GTS 640 was a bit warn while playing COD4 so
I 've forced my GPU fan to spin at 90% while playing (Using rivatuner).

I think that has made a difference, but I'm not sure. Since it seems only to happen less frequently.

No GPU overclocking here, just my CPU is.

Tonight I'm gonna try an Audigy sound card because I've found many issues related to realtek integrated sound device.
(we can find this device in many NVidia NForce based mobos like mine)


Well, if it doesn't work, I will re-install forceware drivers and directX as well.

This game is great but I'm always fearing a crash while playing it. :flowers:

Regards.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users