Emulator Issues #11453

Super Monkey Ball crashes without Dual Core Mode

Added by Punkinator7 over 1 year ago. Updated about 1 year ago.

% Done:


Operating system:
Issue type:
Relates to usability:
Relates to performance:
Relates to maintainability:
Regression start:
Fixed in:


Game Name?

Super Monkey Ball
Game ID? (right click the game in the game list, properties, info tab)


MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)


What's the problem? Describe what went wrong.

When I disabled Dual core mode, the Emulator told me this in a pop up then promptly closed when I tried to open Super Monkey Ball:
GFX FIFO: Unknown Opcode (0xff @ 00000285B6BD0000, preprocess=false)
This means one of the following:
*the emulated GPU got desynced, disabling dual core can help
* Command stream corrupted by some spurious memory bug
*this really is an unknown opcode (unlikely)
* Some other sort of bug

Further errors will be sent to the Video Backend log and
Dolphin will now likely crash or hang, Enjoy.
it works fine when I turned dual core mode back on.

What steps will reproduce the problem?

  1. go to config,
  2. uncheck the box next to "Enable Dual Core (speedup)", the box should be empty.
  3. close it
  4. attempt to launch Super Monkey ball via the Rom list
  5. Bug does its thing

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, I could do it with the latest version, 5.0-9115

Is the issue present in the latest stable version?

Nope, it starts up fine with 5.0

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 and anyone who is building Dolphin on their own can use git bisect.)

the earliest build I've tested is 5.0-7999, the issue may exist before that.

What are your PC specifications? (CPU, GPU, Operating System, more)

My Computer consists of:
OS- Windows 10 Home
CPU- Intel i3-4170 @ 3.70GHz
GPU- NVIDIA GeForce GT 730
8 GB Ram

Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)

Screenshot of the error, on the latest Dolphin Build:


#1 Updated by Stenzek over 1 year ago

If you click OK on the error, does the game start as normal?

#2 Updated by Punkinator7 over 1 year ago

It wouldn't even let me click ok.

#3 Updated by Punkinator7 over 1 year ago

sorry about the late reply, it was like 2:00 when I posted

#4 Updated by Punkinator7 over 1 year ago

I would also like to note that the message wouldn't go away without using Task Manager, and the buttons are inrespondive. it crashes about 5-8 minutes later, after the message appears.

#5 Updated by JMC4789 over 1 year ago

  • Status changed from New to Accepted

that's a new behavior in Windows itself... I've noticed it after the last few Windows updates...

Anyway, this is a GPU timing issue as a top secret slow GPU timing branch makes this work. It's kinda the opposite of that issue where I stick all the dualcore issues.

#6 Updated by Kribuchman about 1 year ago

Just finished bisecting this issue, look like it first occurred in 5.0-681, here's a link to the PR.

My PC Specs are
OS- Arch Linux 5.1.0-arch1-1
CPU - R7 2700X
GPU - Vega 56 (OpenGL renderer string: Radeon RX Vega (VEGA10, DRM 3.30.0, 5.1.0-arch1-1-ARCH, LLVM 9.0.0)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.1.0-devel (git-2d2927938f)

It sounds like OP is unable to progress after the error but I am able to press okay and the game starts up and then runs correctly. The first warning screen shows a different Opcode than OP -- 0xff @ 0x7fa478abd000, preprocess=false and here is the second screen --

Also available in: Atom PDF