Direct X error

[Rhino]

I get the following error the first time I launch COD2..then it plays just fine.

"DirectX(R) Enountered an unrecoverable error, Check the DirectX FAQ For possible solutions"


DirectX® 9.0c



Please refer to the DirectX website for further information or localization updates. http://www.microsoft.com/directx



Q. What is DirectX 9.0c and why do I need it?


A. DirectX 9.0c is a set of sound, video, input and network functions developed by Microsoft®. Call of Duty® 2 utilizes the functions that are included with DirectX 9.0c.



Q. If I don’t have DirectX 9.0c installed when I install Call of Duty 2 , can I install it later?


A. Yes. You will need to manually install it. You will need to download and install the current version of DirectX 9.0c from the Microsoft® DirectX® website: http://www.microsoft.com/directx



Q. I already have other Windows® 2000/XP games installed on my computer. Will the Microsoft DirectX Installer change my DirectX files?


A. If you already have other Windows 2000/XP games on your computer, chances are you already have a version of DirectX installed. In this case, the Microsoft installer will detect and overwrite any previous versions with DirectX 9.0c. At that point, you will need to restart your computer for the changes to take effect. If, however, you already have DirectX 9.0c installed on your computer, the Microsoft DirectX 9.0c installer will detect it and not overwrite any files. You will not need to restart your computer after installation in order to run Call of Duty 2.



Q. What do I do if the "DirectX Error DirectX has encountered an unrecoverable error. Please check DirectX Help document for possible details." error appears when I attempt to run Call of Duty 2?


A. Make sure you have DirectX 9.0c installed and properly functioning on your machine.

A. Please make sure that hardware acceleration is set to Full in your display properties as follows:
1. Right click the desktop
2. Select Properties
3. Click the settings tab
4. Click Advanced
5. Click the Troubleshooting tab
6. Verify that the Hardware Acceleration slider is set to Full.

A. Make sure that all DirectX features under the Display Tab in the DirectX Diagnostic Tool are set to Enabled as follows:
1. Click START
2. Click RUN
3. Type "dxdiag" and click OK
4. Click the Display tab of the DirectX Diagnostic tool.
5. Verify that all DirectX features are set to "Enabled".

A. Make sure you have the latest drivers installed from your video card's manufacturer.

DXDiag reported:

------------------
System Information
------------------
Time of this report: 9/21/2011, 13:31:07
Machine name: WINDOZE764
Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7600) (7600.win7_gdr.110622-1503)
Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: P55M-UD2
BIOS: Award Modular BIOS v6.00PG
Processor: Intel(R) Core(TM) i7 CPU 870 @ 2.93GHz (8 CPUs), ~2.9GHz
Memory: 8192MB RAM
Available OS Memory: 8184MB RAM
Page File: 1605MB used, 14759MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7600.16385 64bit Unicode

------------
DxDiag Notes
------------
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Sound Tab 2: No problems found.
Input Tab: No problems found.

[Mirfster Profile]

Has this happened from the first time you installed CoD2? If not, I would suggest get all MS updates and ensure XFire is updated as well. Been issues in the past where XFire was the culprit.

Also, are you running CoD2 in DX7 or DX9 mode?

[Rhino]

Not running xfire at all....

Has been doing this since I installed it and Windows 7 64 bit

Running the game in DX7.

[gitman]

have you tried running the game in DX9?

[Rhino]

I came to the conclusion that my EVGA GTX 570 was the issue because I had it overclocked. Once I lowered the speeds back down to stock it seemed to stabilize...then it happened again yesterday ...three times. Two time the screen went black and I had to force quit. The third time I got patchy artifacts on the screen and had to force shutdown the computer.

Today it seemed to run just fine. I have no idea what it causing it. I have read that sometimes in WIn 7 there are issues switching between gaming apps and the desktop...forcing the card to go from 3D to 2D and back again.

[Rhino]

I am gettting the same issue even though my card is now at stock settings. This morning it happen about 5 seconds after I logged in so nothing else was running.

I found this from a few years ago but it does accurately describe my issue even though I'm on Windows 7 64 bit.

NVIDIA statement on TDR Error Messages


Some Windows Vista users have reported that their systems are displaying an error message that says: "Display driver stopped responding, but has successfully recovered." This is called a Timeout Detection and Recovery error message.

Timeout Detection and Recovery (TDR) is a new feature of Windows Vista that attempts to detect problematic situations and recover to a functional desktop without forcing a reboot. Hangs can occur when the GPU is processing intensive graphics operations, typically during gameplay, and nothing is being updated on the monitor. To the user it appears that the system is frozen with no resolution to the problem; in previous operating systems users generally had to wait a few seconds and then reboot.

The TDR error message "Display driver stopped responding and has recovered" lets the user know that the NVIDIA display driver (specifically the "nvlddmkm.sys" file) has been re-initialized and the GPU is reset without requiring a reboot. The only visible artifact from the recovery is a screen flicker, the result of a screen redraw. Note that some older Microsoft DirectX applications may render to a black screen at the end of the TDR, requiring the user to restart these applications.

TDRs are not specific to a single driver problem, and can occur for a variety of reasons. When they occur, diagnostic information is collected in the form of a debug report that is sent to Microsoft through the Online Crash Analysis (OCA) mechanism if the user opts to provide feedback.


NVIDIA encourages users to submit their own bug reports via the NVIDIA Vista Quality Assurance Program, using the keyword "TDR" in the description of the problem. The NVIDIA bug report link is here:
https://surveys.nvid...8f09e040b4a437a

We understand that many users have expressed frustration with this issue, and we apologize for the inconvenience. Since the NVIDIA v101.41 beta driver release, NVIDIA has been fixing many TDR issues reported by users. Our software team is currently preparing a new driver which will dramatically reduce the number of TDR errors that users have reported on the forums. Thank you for your patience.

More information on TDRs can be found here:
http://www.microsoft...dm_timeout.mspx.

[gitman]

and what driver version are you on?

[Rhino]

I'm using the EVGA 280.26 drivers.

I made a discovery though. The Nvidia driver install application installed four HD audio drivers. I remember my first install of nvidia drivers did the same thing. Wierd. I also have a realtek HD audio driver for the built in audio on my MB. At first I disabled the nvidia drivers and ran the whole day with no issues...

Last night I completely uninstalled the Nvidia HD audio drivers.

I am thinking that may have been the conflict.

I'll report back.
Rhino