Emulator Issues #13419
closedPoA (GAZS69) stuck on a black screen on boot
0%
Description
Game Name?
Harry Potter Prisoner of Azkaban
Game ID? (right click the game in the game list, Properties, Info tab)
GAZS69
MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)
f150ce3ef73bfcb788facd19cff0e483
What's the problem? Describe what went wrong.
PoA gets stuck on a black screen immediately after the GC logo.
What steps will reproduce the problem?
Just boot the game.
Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
Yes. 5.0-20555.
Is the issue present in the latest stable version?
Probably not.
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.)
5.0-20555.
If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer
[Attach any fifologs if possible, write a description of fifologs and screenshots here to assist people unfamiliar with the game.]
What are your PC specifications? (CPU, GPU, Operating System, more)
3700X
1080Ti
Win10 22H2
Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)
Looks like https://bugs.dolphin-emu.org/issues/9709 all over again. That was fixed by 5.0-310 'Revert "JitCache: Support for VMEM + MSR bits"'. 5.0-20555 messed with the MSR bits again and now PoA is broken again. It does keep flushing the JIT cache every few seconds, so there's a possibility that it would eventually go ingame; but it might take a pretty long time.