Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
http://steamcommunity.com/sharedfiles/filedetails/?id=500687692
Thanks for the help, it doesn't do anything, I have to force shutdown via power button
Thanks for the help, I will try that, I'll post results later
2. Type this in it
3. Click File > Save As > File name: KillSkyrim > Save as type: All Files (IMPORTANT)
4. Move the file to your Windows Start menu for ease of access.
5. Whenever Skyrim crashes, just alt-tab partially/ctrl +alt +tab and search for this file through the Widows icon. Double click/Enter to open the file and it will close Skyrim.
Also you can try quiting the game by opening console and typing "qqq" without quotes and pressing enter.
I already tried that, nothing happens, it's completely frozen. I guess I'll have to forget the game
I'm running the test now, although I doubt is a windows problem, as in last week, the problem occurred, and I formatted the PC after that, has I bought a ssd pcie-nvme.
Ok, I checked windows event logs, and the strange thing is that there is nothing related to the game. This is intriguing. I guess I'll try to write some code to monitor the skyrim process and find out what the hell it's trying to do.
Finished the test, and no problem was found. :(
Basically, the game can't freeze your computer to the point where not even Ctrl+Alt+Del does anything, so you're not going to find anything "directly" linked to it in the logs. It can trigger a fault, but it is not, in itself, at fault.
Drivers are the most likely suspect. Catch is that whatever's at fault may also be preventing any further log writes, so the system may not be able to note down the true cause at all. It's a bit of a shame about the format, as there goes your update history...