[Bug 45984] New: Skyrim Special Edition does not get past loading screen on high core count or high memory systems
https://bugs.winehq.org/show_bug.cgi?id=45984
Bug ID: 45984 Summary: Skyrim Special Edition does not get past loading screen on high core count or high memory systems Product: Wine Version: 3.18 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: tom@r.je Distribution: ---
Skyrim SE gets stuck at the loading screen on certain hardware configurations. It doesn't freeze as keeps displaying different loading screen tips but does so forever.
I posted on the Steam forums about this: https://steamcommunity.com/app/221410/discussions/8/1734336452599497070/
With a blank wineprefix (no savegames, no mods, just a fresh install from steam) click "New game". It sits at the loading screen forever.
Almost everyone affected has:
AMD Threadripper 1950x
= 32gb RAM
### Software information
Skyrim Special Edition (Steam) (With or without DXVK)
### System information - GPU: nvidia 980ti - Driver: 410 (396.54 also affected) - Wine version: 3.18
There are several systems listed in the steam thread:
///// Arch Linux AMD Threadripper 1950x 32gb RAM nvidia 980ti with 396.54 driver ///// Ubuntu 18.04 AMD Threadripper 1950x 64gb RAM Nvidia Titan XP /// Arch Linux AMD Threadripper 1950x 32gb RAM AMD Vega 64 ////
Both AMD and nVidia GPUs are affected so it's unlikely to be a driver issue. The common elements are:
32gb or more of RAM AMD Threadripper 1950x
### What I've tried
Knowing that it only affects high CPU core systems or high RAM systems I have tried the following:
- taskset -c 0-7 wine steam.exe I wasn't sure whether this would limit just steam.exe, when steam.exe spawns SkyrimSE.exe does this have all 32 cores enabled?
- Disabling SMT in the bios. This effectively disables half the cores so there are only 16 available. This would be similar to someone playing on a Ryzen 7 (8 cores + smt) and I haven't seen any reports with 16 thread CPUs
- It seems like it might be a memory issue. I've tried enabling/disabling NUMA in the bios to no effect
- With NUMA enabled I've tried using `numactl -m 0 -t wine Steam.exe` to force WINE to only use one bank of memory (effectively limiting it to 16gb in the process)
- Running off a SSD rather than NVME driver (It could be a scheduler issue??)
None of this made any difference. How else can I debug this?
Looking around, posts regarding similar issues on windows suggests it's a memory problem. Perhaps it's something to do with having 32gb RAM in the system?
Please let me know if you need any kind of trace/log. WINEDEBUG=all makes steam take so long to start it eventually crashes, so I couldn't provide that, I can try with requested debug options though.
https://bugs.winehq.org/show_bug.cgi?id=45984
--- Comment #1 from Tom B tom@r.je --- Update: running with minimal logs IO get this error in the output:
0122:err:d3d:wined3d_debug_callback 0x27989c70: "GL_INVALID_OPERATION error generated. <program> object is not successfully linked, or is not a program object.".
repeated infinitely until I force quit SkyrimSE.exe
https://bugs.winehq.org/show_bug.cgi?id=45984
Andrew Wesie awesie@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |awesie@gmail.com
--- Comment #2 from Andrew Wesie awesie@gmail.com --- If you redirect the logs to a file, you should see an error about why the link failed before you ever see: "GL_INVALID_OPERATION error generated. <program> object is not successfully linked, or is not a program object.".
If you see something like "0044:fixme:d3d_shader:shader_glsl_validate_link Program 178 link status invalid.", then please post the full log file with that.
https://bugs.winehq.org/show_bug.cgi?id=45984
--- Comment #3 from Tom B tom@r.je --- Thanks for the quick response, the log file was 11mb so too big to attach. I've uploaded it here:
https://r.je/tmp/wine-skyrimse.txt
I can't see anything obvious causing the error but there are a log of fixme's before it (Though they don't seem directly related)
https://bugs.winehq.org/show_bug.cgi?id=45984
Georgy Kirichenko kirichenkoga@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |kirichenkoga@gmail.com
--- Comment #4 from Georgy Kirichenko kirichenkoga@gmail.com --- Hi! I have performed some investigation and found that reverting the commit https://source.winehq.org/git/wine.git/commit/1312c6642851 fixes the issue.
https://bugs.winehq.org/show_bug.cgi?id=45984
zzzzzyzz@hacari.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |zzzzzyzz@hacari.org
https://bugs.winehq.org/show_bug.cgi?id=45984
C0rn3j spleefer90@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |spleefer90@gmail.com
--- Comment #5 from C0rn3j spleefer90@gmail.com --- (In reply to Tom B from comment #3)
Thanks for the quick response, the log file was 11mb so too big to attach. I've uploaded it here:
You can just compress it in the future and add it through the bug tracker directly, that way it doesn't get lost with time.
The compress ratio on log files is pretty good.
https://bugs.winehq.org/show_bug.cgi?id=45984
--- Comment #6 from Tom B tom@r.je --- (In reply to Georgy Kirichenko from comment #4)
Hi! I have performed some investigation and found that reverting the commit https://source.winehq.org/git/wine.git/commit/1312c6642851 fixes the issue.
Thanks for the suggestion, I tried reverting 1312c6642851d4a0c5de9a71c824800935f96691 but it had no effect. It still sits on the loading screen forever.
https://bugs.winehq.org/show_bug.cgi?id=45984
--- Comment #7 from Tom B tom@r.je --- Ok, looking again that may not be the case.
If I use wine 3.18 I cannot log in to windows Steam, it can't log in with "could not connect to the steam network". This is true if I use the Arch Linux wine package or build from source (Either the latest git master or the 3.18 tag). This is a separate issue but makes it difficult to test this bug.
To test reverting 1312c6642851d4a0c5de9a71c824800935f96691 above I used wine staging and just realised that the build script checks out a particular branch. undoing the reversion.
I'd rather not use staging as it adds an extra variable but as it stands this makes it very difficult to test as I can't seem to compile a version of wine that allows me to log in on Steam and have the commit reverted at the same time.
https://bugs.winehq.org/show_bug.cgi?id=45984
--- Comment #8 from Gijs Vermeulen gijsvrm@gmail.com --- (In reply to Tom B from comment #7)
To fix the steam issue, revert b79fd400c05547457bb10e74776b8f312bacae8c.
https://bugs.winehq.org/show_bug.cgi?id=45984
fryst.helvetet@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fryst.helvetet@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=45984
--- Comment #9 from Tom B tom@r.je --- I'm still struggling to test this.
After reverting both b79fd400c05547457bb10e74776b8f312bacae8c and 1312c6642851d4a0c5de9a71c824800935f96691 SkyrimSE gives me just a black screen (With and without DXVK enabled).
I'm getting closer to getting a proper test but still cannot confirm whether reverting 1312c6642851d4a0c5de9a71c824800935f96691 fixes the loading issue.
I do not know whether the black screen is caused by reverting the commits because I cannot log in to steam with standard 3.19.
https://bugs.winehq.org/show_bug.cgi?id=45984
GloriousEggroll@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |GloriousEggroll@gmail.com
--- Comment #10 from GloriousEggroll@gmail.com --- Hi all, I was the one on the steam forum with the
Arch Linux AMD Threadripper 1950x 32gb RAM AMD Vega 64
configuration. I just tested reverting commit 1312c6642851d4a0c5de9a71c824800935f96691 on wine-staging 3.16 and it fixes the infinite loading loop on my system.
https://bugs.winehq.org/show_bug.cgi?id=45984
--- Comment #11 from GloriousEggroll@gmail.com --- reverting that commit also fixes it in vanilla wine 3.16
https://bugs.winehq.org/show_bug.cgi?id=45984
--- Comment #12 from Gijs Vermeulen gijsvrm@gmail.com --- Did b9af36933fdf47cbbe139626e98750da72142dce help for this bug?
https://bugs.winehq.org/show_bug.cgi?id=45984
Alec Joiner joineral2@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |joineral2@gmail.com
--- Comment #13 from Alec Joiner joineral2@gmail.com --- This seems like it may be caused by the same root issue as this: https://bugs.winehq.org/show_bug.cgi?id=45453
https://bugs.winehq.org/show_bug.cgi?id=45984
--- Comment #14 from GloriousEggroll@gmail.com --- (In reply to Gijs Vermeulen from comment #12)
Did b9af36933fdf47cbbe139626e98750da72142dce help for this bug?
Can confirm that patchset fixes the issue! Tested in FO4, Skyrim SE, and the Neverwinter launcher.
https://bugs.winehq.org/show_bug.cgi?id=45984
pattietreutel katyaberezyaka@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |katyaberezyaka@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=45984
--- Comment #15 from Tom B tom@r.je --- Can also confirm that the patchset above fixes the issue. It runs fine in wine-staging 4.0-rc4
https://bugs.winehq.org/show_bug.cgi?id=45984
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |b9af36933fdf47cbbe139626e98 | |750da72142dce Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED
--- Comment #16 from Gijs Vermeulen gijsvrm@gmail.com --- (In reply to Tom B from comment #15)
Can also confirm that the patchset above fixes the issue. It runs fine in wine-staging 4.0-rc4
Thank you for reporting back. Marking FIXED.
https://bugs.winehq.org/show_bug.cgi?id=45984
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |ntdll
https://bugs.winehq.org/show_bug.cgi?id=45984
--- Comment #17 from Tom B tom@r.je --- I am unsure if this is related to my high core count or the patch mentioned above, but skyrim will freeze (0% cpu usage) after several minutes of gameplay. Nothing out of the ordinary appears in the log:
Could not find page for trampoline in +/- 2GB range of function to hook Error allocating trampoline memory (no memory within +/-2gb? prior failures?) \src\common\opensslconnection.cpp (1887) : Assertion Failed: COpenSSLConnection(c00CD7BC0) BAsyncSend after shutdown
That's the last line and I believe it's from steam rather than skyrim. It seems to be intermittent, The desktop environment is still responding as in KDE I can ctrl+esc and kill the process.
I had played for about 30 minutes before it froze, but I just tried again and it froze after a couple of minutes. It's not temperature related as my cpu and gpu are watercooled and neither went above 55c. Other games work fine so I don't think it's a hardware problem.
Unfortunately I have no idea if it is related to the patch as I cannot test without it.
https://bugs.winehq.org/show_bug.cgi?id=45984
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #18 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 4.0-rc5.
-
wine-bugs＠winehq.org