Prior to the patch (and recent Nvidia driver update), AC would cause a GPU crash (about a five second freeze accompanied by blue artifacts on the screen, sound would continue for a few more seconds, and then the monitor would lose the signal) and BSOD, listing the generic nvlddmkm.sys error. System would automatically reboot.
The pace of these crashes depended on graphic settings, specifically multisampling. Max setting would cause a crash within one minute of being in game (controlling Altair), with lower settings increasing the time before crashing to between 20 and 30 minutes.
After the patch and the 175.16 Driver Update, the time before crashing has been extended. Max Multisampling will last for about 30 minutes, with the lower settings increasing stability for upwards of an hour. Artifacting is gone.
System specs are all within requirements.
Everything is at factory settings.
CPU, GPU, and Case temperatures all within proper ranges.
DXDiag Report
quote:
------------------ System Information ------------------ Time of this report: 5/15/2008, 13:41:01 Machine name: XXXXX Operating System: Windows Vista™ Ultimate (6.0, Build 6001) Service Pack 1 (6001.longhorn_rtm.080118-1840) Language: English (Regional Setting: English) System Manufacturer: System manufacturer System Model: System Product Name BIOS: Phoenix - AwardBIOS v6.00PG Processor: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (4 CPUs), ~2.4GHz Memory: 4094MB RAM Page File: 2286MB used, 6081MB available Windows Dir: C:\Windows DirectX Version: DirectX 10 DX Setup Parameters: Not found DxDiag Version: 6.00.6001.18000 32bit 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.
------------- Sound Devices ------------- Description: Speakers (Creative SB X-Fi) Default Sound Playback: Yes Default Voice Playback: Yes Hardware ID: PCI\VEN_1102&DEV_0005&SUBSYS_00311102&REV_00 Manufacturer ID: 1 Product ID: 100 Type: WDM Driver Name: ctaud2k.sys Driver Version: 6.00.0001.1283 (English) Driver Attributes: Final Retail WHQL Logo'd: n/a Date and Size: 2/25/2008 09:46:02, 867224 bytes Other Files: Driver Provider: Creative HW Accel Level: Basic Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000 Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX(tm) 2.0 Listen/Src: No, No I3DL2(tm) Listen/Src: No, No Sensaura(tm) ZoomFX(tm): No
Description: SPDIF Out (Creative SB X-Fi) Default Sound Playback: No Default Voice Playback: No Hardware ID: PCI\VEN_1102&DEV_0005&SUBSYS_00311102&REV_00 Manufacturer ID: 1 Product ID: 100 Type: WDM Driver Name: ctaud2k.sys Driver Version: 6.00.0001.1283 (English) Driver Attributes: Final Retail WHQL Logo'd: n/a Date and Size: 2/25/2008 09:46:02, 867224 bytes Other Files: Driver Provider: Creative HW Accel Level: Basic Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000 Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX(tm) 2.0 Listen/Src: No, No I3DL2(tm) Listen/Src: No, No Sensaura(tm) ZoomFX(tm): No
--------------------- Sound Capture Devices --------------------- Description: Microphone (Creative SB X-Fi) Default Sound Capture: Yes Default Voice Capture: Yes Driver Name: ctaud2k.sys Driver Version: 6.00.0001.1283 (English) Driver Attributes: Final Retail Date and Size: 2/25/2008 09:46:02, 867224 bytes Cap Flags: 0x1 Format Flags: 0xFFFFF
Description: Line-In (Creative SB X-Fi) Default Sound Capture: No Default Voice Capture: No Driver Name: ctaud2k.sys Driver Version: 6.00.0001.1283 (English) Driver Attributes: Final Retail Date and Size: 2/25/2008 09:46:02, 867224 bytes Cap Flags: 0x1 Format Flags: 0xFFFFF
Description: "What U Hear" (Creative SB X-Fi) Default Sound Capture: No Default Voice Capture: No Driver Name: ctaud2k.sys Driver Version: 6.00.0001.1283 (English) Driver Attributes: Final Retail Date and Size: 2/25/2008 09:46:02, 867224 bytes Cap Flags: 0x1 Format Flags: 0xFFFFF
BDA Network Providers: Microsoft ATSC Network Provider,0x00200000,0,1,MSDvbNP.ax,6.06.6000.16386 Microsoft DVBC Network Provider,0x00200000,0,1,MSDvbNP.ax,6.06.6000.16386 Microsoft DVBS Network Provider,0x00200000,0,1,MSDvbNP.ax,6.06.6000.16386 Microsoft DVBT Network Provider,0x00200000,0,1,MSDvbNP.ax,6.06.6000.16386 Microsoft Network Provider,0x00200000,0,1,MSNP.ax,6.06.6001.18000
BDA Transport Information Renderers: BDA MPEG2 Transport Information Filter,0x00600000,2,0,psisrndr.ax,6.06.6001.18000 MPEG-2 Sections and Tables,0x00600000,1,0,Mpeg2Data.ax,6.06.6001.18000
1. Try again with Logitech RumblePad 2 USB unplugged (it is not compatible with the game).
2. It is unclear if you installed the chipset drivers. When you run dxdiag, untick the box "Check for WHQL digital signatures". Then save the file. Then open it, then the chipset drivers should be installed instead of "n/a". If NOT: then you must install them. To install the chipset drivers: download
quote:
2. INF Update Utility - Primarily for Intel® 3, 900 Series Chipsets (2347KB) 8.3.1.1009 9/24/2007
from this page. Right-click on the downloaded file > Properties > hit button "Unblock". Unpack (unzip), then doubleclick the setup.exe.
The gamepad is connected and disconnected depending on the game I play. I never tried to use it for AC, but whether its plugged in or not makes no difference in terms of crashes.
I'm not quite sure what you're looking for in terms of the chipset drivers. I installed them after upgrading to Vista64 from off Nvidia's site, since my motherboard (ASUS P5E32-E SLI) uses the nForce chipset and the drivers that came with the CD were still betas.
After reading your post I went back to Nvidia and found an upgrade for Vista64 and installed them, but there's no difference in terms of the DXDiag report. I ran the 64-bit version of DXDiag and the WHQL comes back Logo'd when the signature check is enabled, so maybe it's just a difference in versions. I didn't even realize there was a 64-bit version when I initially ran it.
Anyway, I haven't tried playing AC since the Chipset Driver update. I'll do some testing and report back.
After the chipset update, DXdiag looked fine. I played AC again, with the same result, except this time the artifacting was back and about ten times worse than before.
Normally I don't do BIOS updates unless I see something in a new revision that's applicable to my specific hardware. It's generally safer that way, and most of the revisions since my boards release have been betas until a few weeks ago. So I downloaded that, flashed it, and tried again.
AC worked on max settings for about a two hour period. I'm not sure if it was the BIOS update alone or that in combination with the chipset update, and I'm not sure if the crash period has just been extended further. But it seems as if some memory handling update in the BIOS is what did it, or better handling of multicore processors (AC is pretty much the only graphics-intensive multicore app I run). Whether or not its a permanent fix, only time will tell.
Personally, I blame Vista's TDR feature. It's virtually impossible to tell what's causing these crashes, since it's so generic. I'd personally caution anyone else of playing around with BIOS updates before looking at things like temperature settings and the memory timings of the GPU (either by underclocking or setting it back to factory settings if you overclock, which is what I did first with no solution).
Post Patch: Stability Improved, but Crashes Persist
I just applied both Forceware 175.16 and Patch in Windows XP x64. Seems to be running alright now. I have Texture: MAX AA: 2X Res: 1024x768 Shadows: On
Its unfortunate that its still giving u troubles. Try Setting Audio Hardware to basic and running the Game in XP. It really stresses on Vista and from what I see the difference is only shadow Quality. But XP would give u good FPS.
Good Luck Buddy.
Intel Core 2 Duo E4500 2.2GHz 2MB Abit IP35P Overspeed Edition 4G Transcend DDR2-800 5-5-5-18 XFX 8800GT Alpha Dog 600M PSU: Fast 700Watt Windows XP x64 Service Pack 1 Forceware: 175.16 WHQL
Turns out its not a permanent fix, in that crashes still occur. Major stability increase, tho, so I'm not too disappointed, and the game is actually playable.
As with pre-patch, lowering settings increases stability even more, and the game runs smooth enough at mid-settings multisampling and a lower resolution where I can play for the time I need, and I certainly don't want to switch back to XP for one application.
Sound Acceleration is already at basic, so I doubt that's it. My hunch is either there's some miset feature in either the video card or the motherboard, having to do with memory, but Im too risk-adverse to play around with clock settings, not to mention voltages, all that much, especially for a game that's pretty much playable despite a crash occuring every 3 hours.
Forums 
