Emulator Issues #13007
closed
Dolphin crashes whenever I try to load any game
0%
Description
What's the problem? Describe what went wrong.
Since I updated Dolphin to some of the most recent dev builds, the emulator no longer loads any game. I don't know if I could call it a crash, because I don't get any error messages not even the Windows dialog asking me to force close the program. The emulator windows simply vanish. A short video-clip with the issue happening:
https://drive.google.com/file/d/1fjo4juxqr3qFsSph0-DdlKGkuxKLd8lB/view?usp=sharing
I have also tried downloading a new dev version and running it in a separate folder, and got the same results.
What steps will reproduce the problem?
Just open the emulator and try to run a game. It could be a clean portable install if you wanted to reproduce the condition on the video.
Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
dolphin-master-5.0-17150-x64
Is the issue present in the latest stable version?
Probably no, but it is too old so I didn't bother testing it.
If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)
dolphin-master-5.0-17105-x64
What are your PC specifications? (CPU, GPU, Operating System, more)
Windows 10 ver. 1809 (a.k.a LTSC)
i5-10400
GTX 1660 Ti driver 512.59
Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)
I have already installed MSVC 2022 from the available link recommended in this thread: https://forums.dolphin-emu.org/Thread-dolphin-won-t-launch-after-updating , but it didn't fix the problem. Here is a screenshot of my installed Control Panel MSVC versions:
Thank you for your time and work.
Files
Updated by Anonymous over 2 years ago
go to %localappdata%\CrashDumps in file explorer. There should be files like dolphin.exe.XXXX.dmp there. Find the most recent one (generated from when you ran 5.0-17150), compress the .dmp file and upload it to google drive, and share link here. thanks.
Updated by dezraj over 2 years ago
- File Dolphin.exe.8072.zip Dolphin.exe.8072.zip added
godisgovernment wrote:
go to
%localappdata%\CrashDumpsin file explorer. There should be files likedolphin.exe.XXXX.dmpthere. Find the most recent one (generated from when you ran 5.0-17150), compress the .dmp file and upload it to google drive, and share link here. thanks.
Thank you so much for the super fast reply. I have attached the dump to this reply. I hope it can help you somehow. Please tell me if you need something else.
Thank you again for your assistance.
Updated by Anonymous over 2 years ago
the error seems to be a regression from https://github.com/dolphin-emu/dolphin/pull/10872 which is happening because dolphin finds your timezone hard to deal with. is it set to something strange? You don't need to change it - it should be fixed in dolphin - but want to understand what value is causing the problem.
it seems to be the exception mentioned here: https://en.cppreference.com/w/cpp/chrono/current_zone however it's not entirely clear to me why an exception is being thrown, as the allocation seems to have succeeded (not bad allocation). maybe win10 17763 does not have required tzdb files (if such a thing even exists), I'm not sure atm.
Updated by Anonymous over 2 years ago
see this comment: https://github.com/compiler-explorer/compiler-explorer/issues/3500#issuecomment-1090940908
Specifically, updating the leap second database requires Windows 10 version 1809 or later, and time zones require icu.dll which is provided by Windows 10 version 1903/19H1 or later. This applies to both client and server OSes; note that Windows Server 2019 is based on Windows 10 version 1809.
Updated by Anonymous over 2 years ago
to clarify a little, when i said 17763, it's another term for 1809... :)
Updated by dezraj over 2 years ago
godisgovernment wrote:
the error seems to be a regression from https://github.com/dolphin-emu/dolphin/pull/10872 which is happening because dolphin finds your timezone hard to deal with. is it set to something strange? You don't need to change it - it should be fixed in dolphin - but want to understand what value is causing the problem.
it seems to be the exception mentioned here: https://en.cppreference.com/w/cpp/chrono/current_zone however it's not entirely clear to me why an exception is being thrown, as the allocation seems to have succeeded (not bad allocation). maybe win10 17763 does not have required tzdb files (if such a thing even exists), I'm not sure atm.
Thank you for your investigation.
As for your inquiry, my timezone is set to UTC -3:00 (Brasilia and Buenos Aires time). Here is a screen capture of Windows options:
https://imgur.com/a/kNuR4eO
Curiously some time ago I tried to update Windows clock using time.windows.com but Windows would not sync with the server, then I changed to time.nist.gov and the clock synced normally. Apparently this has been fixed in a Windows update because I have just tried to update using time.windows.com and it synced normally now.
Anyway, I hope this could be figured out eventually.
Thank you so much again.
Updated by Anonymous over 2 years ago
can you try this build and see if it works for you https://dl.dolphin-emu.org/prs/d0/68/pr-10963-dolphin-latest-x64.7z
Updated by dezraj over 2 years ago
godisgovernment wrote:
the error seems to be a regression from https://github.com/dolphin-emu/dolphin/pull/10872 which is happening because dolphin finds your timezone hard to deal with. is it set to something strange? You don't need to change it - it should be fixed in dolphin - but want to understand what value is causing the problem.
it seems to be the exception mentioned here: https://en.cppreference.com/w/cpp/chrono/current_zone however it's not entirely clear to me why an exception is being thrown, as the allocation seems to have succeeded (not bad allocation). maybe win10 17763 does not have required tzdb files (if such a thing even exists), I'm not sure atm.
Thank you for your investigation.
As for your inquiry, my timezone is set to UTC -3:00 (Brasilia and Buenos Aires time). Here is a screen capture of Windows options:
https://imgur.com/a/kNuR4eO
Curiously some time ago I tried to update Windows clock using time.windows.com but Windows would not sync with the server, then I changed to time.nist.gov and the clock synced normally. Apparently this has been fixed in a Windows update because I have just tried to update using time.windows.com and it synced normally now.
Anyway, I hope this could be figured out eventually.
Thank you so much again.
godisgovernment wrote:
see this comment: https://github.com/compiler-explorer/compiler-explorer/issues/3500#issuecomment-1090940908
Specifically, updating the leap second database requires Windows 10 version 1809 or later, and time zones require icu.dll which is provided by Windows 10 version 1903/19H1 or later. This applies to both client and server OSes; note that Windows Server 2019 is based on Windows 10 version 1809.
Thank you for the information. I checked here and my system doesn't seem to have this file in the System32 folder, this is all I find when I look for "icu" there:
https://imgur.com/a/9cftT9U
Would downloading this file and placing it there fix the problem with Dolphin?
Thank you again.
Updated by dezraj over 2 years ago
godisgovernment wrote:
can you try this build and see if it works for you https://dl.dolphin-emu.org/prs/d0/68/pr-10963-dolphin-latest-x64.7z
I'm sorry for missing this reply in my last response! This version seems to have fixed the issue here. The emulator no longer crashes with both Wii and Game Cube games loaded.
Please tell me if you need me to make any further testings.
Thank you so much again for your super fast work.
Updated by JosJuice over 2 years ago
- Status changed from New to Fixed
- Fixed in set to 5.0-17153