this post was submitted on 13 May 2024
20 points (95.5% liked)
Linux Gaming
15825 readers
78 users here now
Gaming on the GNU/Linux operating system.
Recommended news sources:
Related chat:
Related Communities:
Please be nice to other members. Anyone not being nice will be banned. Keep it fun, respectful and just be awesome to each other.
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
EDIT: As discussed above, turning on ‘Above 4G Decoding’ and ‘Resizable BAR Support’ settings in my BIOS fixed the problem.
I had updated my BIOS recently, and the ‘Above 4G Decoding’ and ‘Resizable BAR Support’ was turned off, instead of inheriting the previous BIOS version setting of them being turned on.
Not sure if its related, but throwing this reply your way, just in case.
WoW has been crashing for me too last couple of days, consistently. Launched via Battle.net launcher.
Its weird, but the only way I can get it to not crash is by letting the first WoW session crash on startup, NOT closing the exception error message dialog or the report the crash to Blizzard dialog, and then start up a second session of WoW. That second session plays fine.
I had played first session WoW normally for a week, then stopped to have lunch one day, and when I came back from lunch and started up WoW again, this crashing crap had just started.
I tried using Bottles (both native and flatpak), Lutris, and Steam. The 'run twice' trick is being done on Steam (native not flatpak) using experimental. Using Fedora/KDE spin.
Not sure where to report this 'bug' to on the Internet. Any ideas?
~Anti~ ~Commercial-AI~ ~license~ ~(CC~ ~BY-NC-SA~ ~4.0)~