Hello @puppenklo, no OpenGL application should be capable of freezing the entire system, which hints that you might be seeing a video driver issue.
Please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.
Yesterday I have a similar issue, the problem was 2 precompile shader processes with 11GB of RAM usage each one, the game responsable for the shaders was Ghostrunner the demo, I remove the folder for the shaders and remove from the game from steam library (only a demo anyway), after fix no more crashes.
Yesterday I have a similar issue, the problem was 2 precompile shader processes with 11GB of RAM usage each one, the game responsable for the shaders was Ghostrunner the demo, I remove the folder for the shaders and remove from the game from steam library (only a demo anyway), after fix no more crashes.
I had the same problem just now, with the same game - Ghostrunner Demo. Only difference is that because my system is a Threadripper 1950X with 64GB RAM, it was running 16 shader compilers.
It didn't exactly lock up the machine, just made it extremely unresponsive. By ssh-ing in from another machine to reboot it (which took several minutes before the bash prompt even appeared), I could see that the load avg was over 200, and the oom killer was killing everything except steam. I tried leaving it running like that for an hour or so before rebooting just to see if it would eventually finish compiling the shaders, but it didn't.
Of course, it started trying to recompile the same shaders when I restarted steam after rebooting, so i had to disable background compiling...and by the time I unchecked the box in Settings the machine was getting unresponsive again, requiring a another reboot before the problem was solved. I uninstalled the demo after that.
Dunno if this is related to the OP's issue, but there definitely appears to be a problem with bad shader files in the Ghostrunner Demo. This is the only game that i've had this problem with.
Nothing extracted yet.
Your system information
Please describe your issue in as much detail as possible:
After playing Starbound or Stardew Valley for two or three hours sometimes the keyboard gets stucked on the d-key.
When the issue happened in full-screen there was no way for me to interact with my computer anymore.
I still can use the mouse, but both games can't be closed only using the mouse. Anyway this is not the real problem.
In both cases it is impossible to shutdown the device properly.
In window mode I can at least start the shutdown process, but it is very slow with lots of errors and gets stuck at one point.
The power button is not working anymore like the whole keyboard and additionally there is no way for me to disconnect
the battery. The only way to reboot for me is to wait until the battery is empty after some hours and then reconnect the
notebook to the power supply.
This happened already six or seven times since spring time this year.
Steps for reproducing this issue:
EDIT:
Same happened while playing Borderlands 2, but much faster. I played for maybe half an hour.
The distributor of the notebook said, it is possibly an issue about whole disk encryption, because there will occur writing problems, but I don't really think it is the problem. I bought a new ssd, did not encrypt it an dmoved the steam library there.
Today I experienced the same problem as before.
syslog output at the time of the freeze is as follows, where the last two blocks repeat alot more with different Args:
ACPI Error: AE_TIME, Returned by Handler for [EmbeddedControl] (20190816/evregion-266)
ACPI Error: Timeout from EC hardware or EC device driver (20190816/evregion-275)
Initialized Local Variables for Method [ZEVT]:
Local0: 0000000062932b42 Integer 0000000000000000
Initialized Arguments for Method [ZEVT]: (3 arguments defined for method invocation)
Arg0: 000000003b236198 Integer 0000000000000000
Arg1: 0000000079d415ba Integer 0000000000000063
Arg2: 00000000d3dd74aa Buffer(4) 00 00 00 00
ACPI Error: Aborting method _SB.WMI.ZEVT due to previous error (AE_TIME) (20190816/psparse-531)
ACPI Error: Aborting method _SB.WMI.WMBB due to previous error (AE_TIME) (20190816/psparse-531)
clevo_wmi.h: Error evaluating method
ACPI Error: AE_TIME, Returned by Handler for [EmbeddedControl] (20190816/evregion-266)
ACPI Error: Timeout from EC hardware or EC device driver (20190816/evregion-275)
Initialized Local Variables for Method [ZEVT]:
Local0: 00000000acac69c8 Integer 0000000000000000
Initialized Arguments for Method [ZEVT]: (3 arguments defined for method invocation)
Arg0: 0000000054c4573a Integer 0000000000000000
Arg1: 000000002909d1a3 Integer 000000000000006E
Arg2: 00000000793dd965 Buffer(4) 00 00 00 00
ACPI Error: Aborting method _SB.WMI.ZEVT due to previous error (AE_TIME) (20190816/psparse-531)
ACPI Error: Aborting method _SB.WMI.WMBB due to previous error (AE_TIME) (20190816/psparse-531)
clevo_wmi.h: Error evaluating method
ACPI Error: AE_TIME, Returned by Handler for [EmbeddedControl] (20190816/evregion-266)
ACPI Error: Timeout from EC hardware or EC device driver (20190816/evregion-275)