View Full Version : Always can't play

05-14-2011, 08:57 PM
I tried all ways in the forums.
And I let Steam auto update this game.
But it always can't play.
MY OS is windows 7,CPU is AMD X2 3600+,and video card is ATI HD 4670.
To play this game,I have re-install twice my computer OS.
I don't like spend $18 to buy a can't playing game.
It always crash during startup.
Below the logs:

Crash report
Process: Garshasp.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 001B:73E58D99
Attempt to read from 0x6ED83310
Thread ID: 0x754 [1876]

Call stack
73E58D99 MMDevAPI.DLL Ordinal2 + 0x2008 (0x00348D48 0x00000000 0x003A885C 0x00000000)
73E54C6A MMDevAPI.DLL Ordinal3 + 0x27B2 (0x00000000 0x00000000 0x00348D48 0x00000000)
73E51674 MMDevAPI.DLL Ordinal15 + 0x520 (0x0B45FE64 0x00000000 0x0B45FE28 0x00000000)
73E5191B MMDevAPI.DLL Ordinal15 + 0x7C7 (0x0B45FE64 0x00000000 0x0034BBE8 0x00000000)
7722C844 ntdll.dll RtlWow64EnableFsRedirectionEx + 0x1EB (0x0B45FE64 0x00000000 0x00343AE8 0x00000000)
77240842 ntdll.dll RtlIsCriticalSectionLockedByThread + 0x2EC (0x003381B8 0x00000000 0x0B45FFD4 0x00000000)
75DE3C45 kernel32.dll BaseThreadInitThunk + 0x12 (0x003381B8 0x00000000 0x7C7D20E9 0x00000000)
772737F5 ntdll.dll RtlInitializeExceptionChain + 0xEF (0x772403E7 0x00000000 0x003381B8 0x00000000)
772737C8 ntdll.dll RtlInitializeExceptionChain + 0xC2 (0x772403E7 0x00000000 0x003381B8 0x00000000)

Date/time: 15/5/2011, 10:18:44:228
Number of CPUs: 2
Processor type: 586
System: Unknown Windows version - 6.1 (Service Pack 1)

Memory status
Total Reserved: 74784K (73M) bytes
Total Commited: 246220K (240M) bytes
Total Free: 1776084K (1734M) bytes
Largest Free: 695904K (679M) bytes

EAX=01E7A7C0 EBX=00348DA8 ECX=00000000 EDX=6ED832F4
ESI=0B45FD70 EDI=0B45FD30 EBP=0B45FFEC ESP=0B45FFDC EIP=772737C8
FLG=00010212 CS=001B DS=0023 SS=0023 ES=0023 FS=003B GS=0000

Mini dump saved successfully.

Someone can help me find the problem?
Thank you for your attention!

05-15-2011, 03:03 AM
u can follow the problem here http://forums.steampowered.com/forums/showthread.php?t=1880935

05-15-2011, 11:05 AM
This issue is resolved and a patch has been submitted.