Opened 7 years ago

Closed 3 years ago

#4821 closed defect (needsinfo)

GPU stops working as soon as match begins

Reported by: vikingr Owned by:
Priority: Must Have Milestone:
Component: Core engine Keywords:
Cc: Patch:

Description

I am unable to play the game. Everything is fine, until I start the match. about 3 seconds after the game starts, it freezes, and the screen turns black. A few seconds later the screen comes on again, and I get a message that the GPU stopped working and was restarted. Also, the computer closes the game as well.

At one point I got an error message from the application, saying that I should report the error here, and attach error logs. But there are no logs under the logs folder

I am using windows 7, and Nvidia GTX1050TI

Attachments (2)

crashlog.txt (15.5 KB ) - added by vikingr 7 years ago.
crashlog.dmp (103.8 KB ) - added by vikingr 7 years ago.

Download all attachments as: .zip

Change History (11)

comment:1 by elexis, 7 years ago

Sounds like an issue with your graphics driver, can you try updating it? Perhaps also try disabling all graphics options in 0AD and a smaller map.

Checked the right logs folder? wiki:GameDataPaths

by vikingr, 7 years ago

Attachment: crashlog.txt added

by vikingr, 7 years ago

Attachment: crashlog.dmp added

comment:2 by vikingr, 7 years ago

I tried disabling as much graphics options as possible. Will try the driver update. Found the logs after your tip, I will try to attach them here

comment:3 by elexis, 7 years ago

errno = 13 (Insufficient access rights to open file)

Might be a false positive, but it could indicate a file or directory permission problem (could test by running as admin or messing with the directory permissions of the cache and config directory).

Stan might find the stacktrace of that crashfile, then we should know a bit more.

(If it turns out to be some kind of sound thing, it might be #4786)

comment:4 by vikingr, 7 years ago

None of the above worked either..

comment:5 by Stan, 7 years ago

>	pyrogenesis.exe!PerformErrorReaction(ErrorReactionInternal er=ERI_BREAK, unsigned int flags=0, volatile int * suppress=0x00000000) Line 426	C++
 	pyrogenesis.exe!debug_DisplayError(const wchar_t * description=0x0035e658, unsigned int flags=0, void * context=0x0035ee68, const wchar_t * lastFuncToSkip=0x0122c260, const wchar_t * pathname=0x0035eb70, int line=0, const char * func=0x0035d650, volatile int * suppress=0x00000000) Line 483	C++
 	pyrogenesis.exe!wseh_ExceptionFilter(_EXCEPTION_POINTERS * ep=0x0035ecf4) Line 289	C++
 	pyrogenesis.exe!CallStartupWithinTryBlock() Line 365	C++
 	msvcr120.dll!strncpy_s() + 141 bytes	Unknown
 	[Frames below may be incorrect and/or missing, no symbols loaded for msvcr120.dll]	
 	msvcr120.dll!_except_handler4_common() + 137 bytes	Unknown
 	ntdll.dll!ExecuteHandler2@20
()	Unknown
 	ntdll.dll!ExecuteHandler@20
()	Unknown
 	pyrogenesis.exe!GUI<int>::RecurseObject(int RR=-139264, IGUIObject * pObject=0x0035f87c, void(IGUIObject::*)() pFunc=0x770f9902) Line 295	C++
 	kernel32.dll!@BaseThreadInitThunk@12
()	Unknown


I've never seen that one before. The only time I had something like what you reported, is when I seriously messed up the Intel Drivers and AMD ones. Since you are on a desktop unless you have something like Lucid Virtu MVP I don't really see where it's coming from.

comment:6 by elexis, 7 years ago

If we search trac for "wseh" we find some results. This stack is very similar #4743. But the stack looks rather like the one that displays the exception, not the broken code.

The last line looks suspicious: GUI<int>::RecurseObject. Sounds like some GUI event that is only called on your platform when the game finishes, or your window manager doing something to that window then.

But having a broken graphics card driver might also be an option.

comment:7 by elexis, 7 years ago

It still sounds like this is an issue with your hardware+driver combination (or 0AD in not liking that combination in particular).

The monitor going black is something which ought not happen no matter how 0AD is programmed.

The DisplayError reported in the crash might just be a consequence of an underlying graphics card issue.

GTX1050TI sounds like a good graphics card, so if it is indeed an issue with that combination, it sounds like a driver issue.

Are you able to play other games or 3D applications correctly?

comment:8 by Imarok, 5 years ago

Component: UI & SimulationCore engine

Move tickets to their correct component.

comment:9 by Freagarach, 3 years ago

Milestone: Backlog
Resolution: needsinfo
Status: newclosed

Given the conversation above, we need more information. (Also try whitelisting 0ad on your antivirus and check if the correct videocard is being used.)

Note: See TracTickets for help on using tickets.