Luv this mod but to many crashes makes it unplayable?

**TheNewKing** · August 30, 2011, 02:00 PM

i just spent nearly a hour on one battle i won clicked end battle then i get a crash to desktop

this happends quite a lot but not every turn

Problem signature:
Problem Event Name: APPCRASH
Application Name: GameOverlayUI.exe
Application Version: 1.15.33.65
Application Timestamp: 4e36ea77
Fault Module Name: unknown
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 7454e2d4
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057

Read our privacy statement online:
http://go.microsoft.com/fwlink/?link...8&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

**Brusilov** · August 30, 2011, 02:05 PM

You need to post this in the right place on the forum. If you had done so you would have seen this pinned topic: here

What specs is your system?

What grpahic settings are you using?

Have you read this thread: here

**TheNewKing** · August 30, 2011, 02:14 PM

my pc is new so should be ok how do i find out all my pc specs

**TheNewKing** · August 30, 2011, 02:20 PM

System Information
------------------
Time of this report: 8/30/2011, 20:16:59
Machine name: TAYLOR-PC
Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.110622-1506)
Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: GA-890GPA-UD3H
BIOS: Award Modular BIOS v6.00PG
Processor: AMD Phenom(tm) II X2 555 Processor (2 CPUs), ~3.2GHz
Memory: 8192MB RAM
Available OS Memory: 8190MB RAM
Page File: 2467MB used, 13910MB 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.7601.17514 32bit Unicode

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

--------------------
DirectX Debug Levels
--------------------
Direct3D: 0/4 (retail)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)

---------------
Display Devices
---------------
Card name: AMD Radeon HD 6900 Series
Manufacturer: Advanced Micro Devices, Inc.
Chip type: ATI display adapter (0x6719)
DAC type: Internal DAC(400MHz)
Device Key: Enum\PCI\VEN_1002&DEV_6719&SUBSYS_186B174B&REV_00
Display Memory: 1773 MB
Dedicated Memory: 2030 MB
Shared Memory: 3838 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor Name: Generic PnP Monitor
Monitor Model: SONY TV
Monitor Id: SNY2C02
Native Mode: 1920 x 1080(p) (60.000Hz)
Output Type: HDMI
Driver Name: aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiumd64.dll,atidxx64.dll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
Driver File Version: 8.17.0010.1091 (English)
Driver Version: 8.881.0.0
DDI Version: 11
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 8/22/2011 19:29:15, 852992 bytes
WHQL Logo'd: Yes
WHQL Date Stamp:
Device Identifier: {D7B71EE2-2459-11CF-B870-6138BEC2C535}
Vendor ID: 0x1002
Device ID: 0x6719
SubSys ID: 0x186B174B
Revision ID: 0x0000
Driver Strong Name: oem15.inf:ATI.Mfg.NTamd64.6.1:ati2mtag_NICayman:8.881.0.0:pci\ven_1002&dev_6719
Rank Of Driver: 00E62001
Video Accel: ModeMPEG2_A ModeMPEG2_C
Deinterlace Caps: {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{3C5323C1-6FB7-44F5-9081-056BF2EE449D}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{552C0DAD-CCBC-420B-83C8-74943CF9F1A6}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
D3D9 Overlay: Not Supported
DXVA-HD: Not Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled

**TheNewKing** · August 31, 2011, 02:39 AM

can any one help?

**Ybbon** · August 31, 2011, 05:21 AM

Have you changed the video options in game at all? If so, what did you use?

Most in-battle/after battle crashes are caused by graphics settings, in particular unit shaders on, antialiasing off, veg medium will solve most problems.

**Brusilov** · August 31, 2011, 06:31 AM

Originally Posted by ybbon66

Have you changed the video options in game at all? If so, what did you use?

Most in-battle/after battle crashes are caused by graphics settings, in particular unit shaders on, antialiasing off, veg medium will solve most problems.

I posted links to such things in my first post.

**TheNewKing** · August 31, 2011, 08:43 AM

how i meant to know what to have and not what to have in graphic wise? , i play shougun 2 in ultra everything and have antialiasing at its highest so why do i have problems with this game i would like to play it in ultra graphics and my pc can handle it but are you saying you cant play it with good graphics?

**Brusilov** · August 31, 2011, 09:14 AM

Shogun 2 is not a game that was released in 2005. R:TW does not support multiple cores, it does not use the latest graphic cards very well as the 'features' on them were not even though of back in 2004 when the game was being developed.

**apple** · August 31, 2011, 04:04 PM

Turn down some settings and see if the game still crashed. Do NOT turn off unit shaders.

**TheNewKing** · September 01, 2011, 05:44 AM

ok thanks everyone ill see what happends

**century x** · September 01, 2011, 12:02 PM

Make sure Unit shaders in the in game video options is turned on. that will fix vast majority of CTD's

**TheNewKing** · September 02, 2011, 02:45 AM

i have a idea will this work on my AMD vision engine control center i can set the anti-aliasing to use overide application settings or should i use use application settings what do you guys recomend, use every thing on use application settings?

**TheNewKing** · September 02, 2011, 11:43 AM

just had a crash after battle and i put no anti-aliasing on

**Brusilov** · September 02, 2011, 12:36 PM

With R:TW I set the anti-alaising off in-game and use my nVidia Control panel to override any game settings (or enhance them).

I used to use a product called nHancer but that has not worked with nVidia drivers for more than a year now (there were some fundamental changes made to the drivers).

Clearly this is not an AMD/ATI product but there must be similar out there - I used to have ATI cards a long time ago and there was something around then.