03-28-2010
|
|
|
|
Re: Crysis Crashes in Win7 Vista & XP
The real cause is a Crysis vs. DX10 compatibility problem!
Running Crysis in DX 9 (Used a .bat file with -DX9 option)
Eliminates or at least reduces the crashes in the end game on the
carrier deck. DX9 only uses the high not very high mode, so there are
some game mods that needs to be made to properly enable the very high mode.
Ran on a win 7 DX 11 capable system with 2 HD 5770 XFX cards in
Crossfire using 10.3 drivers.
On 1/18/2010 4:17 PM, Chuck wrote:
> Anybody have any ideas?
> The crash data is from win7
> Similar crashes occur in the other win versions.
> These seem to occur --
> Most often in the fight on the Carrier
> Most often in the higher resolutions
> Most often during complex game play (Combat)
> They do not occur in Crysis Warhead.
> The win 7 Machine is stable with virtually all other testing and apps.
>
> ATI HD4890 video card with 9.12 drivers at 1024x768 windowed
> 4 Gig memory
> AMD 955 4 core processor
> Asus M4A79 Dlx Mbd
> Sata HD
> 910 W PS
>
> Problem signature:
> 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
> 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: cb1f
> Additional Information 2: cb1fe6b93db0978beda1ab69b0e435d1
> Additional Information 3: 2d23
> Additional Information 4: 2d23d47d2c5aaf91edc9292addde71e5
>
> Problem Event Name: APPCRASH
> 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
> Exception Offset: 00025ba1
> OS Version: 6.1.7600.2.0.0.256.48
> Locale ID: 1033
> Additional Information 1: b734
> Additional Information 2: b73487accf731f26b221fad07e86306d
> Additional Information 3: d90a
> Additional Information 4: d90a409ec50a92f4a47cfd7da20d902e
>
> Problem Event Name: APPCRASH
> 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
> Locale ID: 1033
> Additional Information 1: 0ba8
> Additional Information 2: 0ba81c2e8e578b238023a9a9189b2a21
> Additional Information 3: 399e
> Additional Information 4: 399e891637f2ebef529945d61a4e57f1
>
> crash from menu (Settings save)
> Problem signature:
> 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
> 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: 7567
> Additional Information 2: 75673da64fbf8d328303dcbfde3b8945
> Additional Information 3: 0c6c
> Additional Information 4: 0c6cb209f1480c5c3f2d6b9ccbfd3ac3
>
> During game play on Carrier Battle (high graphics level)
>
> Problem signature:
> 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
> Exception Offset: 00025ba1
> OS Version: 6.1.7600.2.0.0.256.48
> Locale ID: 1033
> Additional Information 1: b734
> Additional Information 2: b73487accf731f26b221fad07e86306d
> Additional Information 3: d90a
> Additional Information 4: d90a409ec50a92f4a47cfd7da20d902e
>
> Secondary Crash on return from above crash
> Problem signature:
> Problem Event Name: APPCRASH
> Application Name: Crysis.exe
> 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
> Locale ID: 1033
> Additional Information 1: 0ba8
> Additional Information 2: 0ba81c2e8e578b238023a9a9189b2a21
> Additional Information 3: 399e
> Additional Information 4: 399e891637f2ebef529945d61a4e57f1
>
> Problem signature:
> 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
> Exception Offset: 00025ba1
> OS Version: 6.1.7600.2.0.0.256.48
> Locale ID: 1033
> Additional Information 1: b734
> Additional Information 2: b73487accf731f26b221fad07e86306d
> Additional Information 3: d90a
> Additional Information 4: d90a409ec50a92f4a47cfd7da20d902e
>
> Problem signature:
> Problem Event Name: APPCRASH
> Application Name: Crysis.exe
> 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
> Locale ID: 1033
> Additional Information 1: 0ba8
> Additional Information 2: 0ba81c2e8e578b238023a9a9189b2a21
> Additional Information 3: 399e
> Additional Information 4: 399e891637f2ebef529945d61a4e57f1
|
Linear Mode
