It's too bad that the thread seems to be fragmented.
Crysis + Visual C library + DX 10 + ATI Video drivers are involved.
Some NVIDIA card driver combos have similar problems.
The same general problem exists with Win 7
The Feb ATI drivers seem to help
Problem Event Name: BEX
Application Name: Crysis.exe
Application Version: 1.1.1.6156
Application Timestamp: 47d6d167
Fault Module Name: MSVCR80.dll
Fault Module Version: 8.0.50727.4927
Fault Module Timestamp: 4a2752ff
Application Name: Crysis.exe (CARRIER FIGHT)
Application Version: 1.1.1.6156
Application Timestamp: 47d6d167
Fault Module Name: d3d10core.dll
Fault Module Version: 6.1.7600.16385
Fault Module Timestamp: 4a5bd9a3
Exception Code: c0000005
Application Name: Crysis.exe (CARRIER FIGHT)
Application Version: 1.1.1.6156
Application Timestamp: 47d6d167
Fault Module Name: atidxx32.dll
Fault Module Version: 8.17.10.247
Fault Module Timestamp: 4b0ca08b
Exception Code: c0000005
Exception Offset: 00010668
OS Version: 6.1.7600.2.0.0.256.48
Problem Event Name: APPCRASH
Application Name: Crysis.exe
Application Version: 1.1.1.6156
Application Timestamp: 47d6d167
Fault Module Name: d3d10core.dll
Fault Module Version: 6.1.7600.16385
Fault Module Timestamp: 4a5bd9a3
Exception Code: c0000005
"StinkySQL" <StinkySQL@newsgroup> wrote in message
news:23AE24E8-101F-406F-8DCD-00B22110C7B1@newsgroup
>
> Its a shame you seem to be talking to yourself so let me add something.
>
> Same problems with Windows 7 (6.1.7600) and it really is the last two
> chapters. I had zero problems before then. I completed one chapter by just
> waiting in a corner and not looking at anything! I would agree with your
> assessment of the quality control as there is a LOT more blowing up here
> making failure exposure much more likely. If they didn't see it, well ...
>
> Crysis patches 1, 1.2 and 1.2.1 don't make much difference, nor did the
> uninstall and reinstall. I'm running ATI 4850 version 8 drivers and will
> see
> what an update to the new 9.6 will do.
>
> SS
>
>
>