This problem began to be noticed on vista, but the vista laptop was too slow
to really get into crysis.
Crashes such as this one occur on both. In additon, Crysis may also fail to
menu, and be resumed with the resume game selection.
This is a new win 7 system with a quad core AMD Phenom II at 3.2ghz, not
overclocked, and a Diamond MM HD4890 video card also not overclocked.
4G OCX 1066 memory (dual channel) on an Asus M4A79 Deluxe MBD.
Video driver is ATI's last release.

I seem to remember that there might have been a reversion to an older copy
of MSVCR80.dll in order to patch some ATI video drivers.
The list at the bottom identifies the dash numbers I found on the system.
The system was fully patched as of yesterday morning.
Crysis has the Crysis update patches as well.



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 8/25/2009 Visual Studio r2005
Fault Module Timestamp: 4a2752ff
Exception Offset: 000127da
Exception Code: c000000d
Exception Data: 00000000
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional Information 1: e926
Additional Information 2: e9263950142051511ceadcb55c0aa80c
Additional Information 3: b8de
Additional Information 4: b8dea055e8c7e8472b7f4d399952f30f



8.00.50727.1801 621kb
..42 612kb
..762 778kb MS Hot fix
..4053 617kb
,4053 783 SISandra
..4927 617kb

ATI HD4800 (4890) video drivers

So far, no solution found. Crysis was reloaded from CD, and run without the
patches. At least in the earlier episodes, it runs better than with the
patches.
Possibilities to be looked at--
Saved games may contribute to the problem.
System option changes may make a difference.
ATI has released new video driver versions in the last few days.

The problems are most acute during the carrier attack, when the player is
shooting down the attackers.
Is there a real difference between the various resolution and video detail
modes in relation to the "dump to menu" and "crashout" failures.

Interestingly enough, Crysis Wars etc. does not have the same problems, or
at least to the same digree.



"Chuck" <cdkuder@newsgroup> wrote in message
news:%23Gfq4AtUKHA.3720@newsgroup

> This problem began to be noticed on vista, but the vista laptop was too
> slow to really get into crysis.
> Crashes such as this one occur on both. In additon, Crysis may also fail
> to menu, and be resumed with the resume game selection.
> This is a new win 7 system with a quad core AMD Phenom II at 3.2ghz, not
> overclocked, and a Diamond MM HD4890 video card also not overclocked.
> 4G OCX 1066 memory (dual channel) on an Asus M4A79 Deluxe MBD.
> Video driver is ATI's last release.
>
> I seem to remember that there might have been a reversion to an older copy
> of MSVCR80.dll in order to patch some ATI video drivers.
> The list at the bottom identifies the dash numbers I found on the system.
> The system was fully patched as of yesterday morning.
> Crysis has the Crysis update patches as well.
>
> 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 8/25/2009 Visual Studio r2005
> Fault Module Timestamp: 4a2752ff
> Exception Offset: 000127da
> Exception Code: c000000d
> Exception Data: 00000000
> OS Version: 6.1.7600.2.0.0.256.48
> Locale ID: 1033
> Additional Information 1: e926
> Additional Information 2: e9263950142051511ceadcb55c0aa80c
> Additional Information 3: b8de
> Additional Information 4: b8dea055e8c7e8472b7f4d399952f30f
>
>
>
> 8.00.50727.1801 621kb
> .42 612kb
> .762 778kb MS Hot fix
> .4053 617kb
> ,4053 783 SISandra
> .4927 617kb
>
> ATI HD4800 (4890) video drivers
>
>

Further investigation results--
The two updates to Crysis help, but do not eliminate the problems.
There is a bug in Crysis that eventually causes the save game function to
fail when a saved game is selected. The resoluton seems to be to uninstall
and completely reinstall Crysis and all the patches.
..DLL modules involved--
d3d10 & d3d10core
atidxx32 (ver 9.8, 9.9, 9.10 drivers)
msvcr80 (involved in crashes from menu) (Win 7 version)
Higher graphics resolution and high or ultra high detail increase the
failure frequency.

Other trivia.
The desktop PC runs win 7 RTM Pro (same as retail)
Video card is a Diamond ATI HD4890
CPU AMD Phenom II 955 3.2G
MBD ASUS M4A79 (DDR2 memory 4G two matched strips OCZ1066G
910W PS
CPU & GPU temps never exceeed 55dC (Lots of fans and airflow.)

My Vista HP Laptop (totally different hardware) exhibited similar problems
with the exception of NVIDIA laptop GPU & drivers instead of ATI drivers &
hardware.
Since the problems occur more frequently in the last two game chapters, it
seems that they were likely not debugged as well as the earlier chapters.
Crysis Wars does not exhibit the same problems or at least not to the level
that prevents playing the game to it's end.

And, I noticed that EA is going to lay off 250 employees. What do you want
to bet that the minimal support for Crysis goes completely away.



"Chuck" <cdkuder@newsgroup> wrote in message
news:OT9wUp3VKHA.5368@newsgroup

> So far, no solution found. Crysis was reloaded from CD, and run without
> the patches. At least in the earlier episodes, it runs better than with
> the patches.
> Possibilities to be looked at--
> Saved games may contribute to the problem.
> System option changes may make a difference.
> ATI has released new video driver versions in the last few days.
>
> The problems are most acute during the carrier attack, when the player is
> shooting down the attackers.
> Is there a real difference between the various resolution and video detail
> modes in relation to the "dump to menu" and "crashout" failures.
>
> Interestingly enough, Crysis Wars etc. does not have the same problems, or
> at least to the same digree.
>
>
>
> "Chuck" <cdkuder@newsgroup> wrote in message
> news:%23Gfq4AtUKHA.3720@newsgroup

>> This problem began to be noticed on vista, but the vista laptop was too
>> slow to really get into crysis.
>> Crashes such as this one occur on both. In additon, Crysis may also fail
>> to menu, and be resumed with the resume game selection.
>> This is a new win 7 system with a quad core AMD Phenom II at 3.2ghz, not
>> overclocked, and a Diamond MM HD4890 video card also not overclocked.
>> 4G OCX 1066 memory (dual channel) on an Asus M4A79 Deluxe MBD.
>> Video driver is ATI's last release.
>>
>> I seem to remember that there might have been a reversion to an older
>> copy of MSVCR80.dll in order to patch some ATI video drivers.
>> The list at the bottom identifies the dash numbers I found on the
>> system. The system was fully patched as of yesterday morning.
>> Crysis has the Crysis update patches as well.
>>
>> 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 8/25/2009 Visual Studio
>> r2005
>> Fault Module Timestamp: 4a2752ff
>> Exception Offset: 000127da
>> Exception Code: c000000d
>> Exception Data: 00000000
>> OS Version: 6.1.7600.2.0.0.256.48
>> Locale ID: 1033
>> Additional Information 1: e926
>> Additional Information 2: e9263950142051511ceadcb55c0aa80c
>> Additional Information 3: b8de
>> Additional Information 4: b8dea055e8c7e8472b7f4d399952f30f
>>
>>
>>
>> 8.00.50727.1801 621kb
>> .42 612kb
>> .762 778kb MS Hot fix
>> .4053 617kb
>> ,4053 783 SISandra
>> .4927 617kb
>>
>> ATI HD4800 (4890) video drivers
>>
>>

>
>

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

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
>
>
>

To carry the thread on--

The major problems many have with Crysis seem to be in the last one or two
episodes-- flying the plane and carrier defense.
It looks like among other things, getting killed in the carrier defense end
game can trigger a crash (Win7, Vista)
If you setup a batch file, and run it from the CMD window, you can see if
forcing dx9 helps. (Quick and dirty)
key content of the batch file is the line
crysis.exe -DX9

The DX10 related problems still occur with win7 32 & ATI 10.3 drivers.

If you have the Crysis Demo, you can use the demo start batch file as an
example of how to write.


"Chuck" <cdkuder@newsgroup> wrote in message
news:u9pQf%237qKHA.1800@newsgroup

> 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
>>
>>
>>

>
>

It seems that the real problem is that Crysis was never fully debugged
for DX10. DX9 mode (even with the very high quality patches) works well
for the last two levels.
ATI 10.3 drivers, Win 7 32, 2x HD5770 Video cards in crossfire)
The same problems existed in Vista and in Win 7 with different video
hardware and drivers.


On 3/29/2010 6:40 PM, Chuck wrote:

> To carry the thread on--
>
> The major problems many have with Crysis seem to be in the last one or two
> episodes-- flying the plane and carrier defense.
> It looks like among other things, getting killed in the carrier defense end
> game can trigger a crash (Win7, Vista)
> If you setup a batch file, and run it from the CMD window, you can see if
> forcing dx9 helps. (Quick and dirty)
> key content of the batch file is the line
> crysis.exe -DX9
>
> The DX10 related problems still occur with win7 32& ATI 10.3 drivers.
>
> If you have the Crysis Demo, you can use the demo start batch file as an
> example of how to write.
>
>
> "Chuck"<cdkuder@newsgroup> wrote in message
> news:u9pQf%237qKHA.1800@newsgroup

>> 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
>>>
>>>
>>>

>>
>>

>
>