pcsx assert failure: pcsx: ../libpcsxcore/ix86_64/ix86-64.c:158: MEMADDR_OP: La declaración `!isreg || reg != 0' no se cumple.

[XMouse]

pcsx can't launch games in full screen mode.

I will try to change to windowed mode.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: pcsxr 1.9.92-4
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AssertionMessage: pcsx: ../libpcsxcore/ix86_64/ix86-64.c:158: MEMADDR_OP: La declaración `!isreg || reg != 0' no se cumple.
CurrentDesktop: XFCE
Date: Sat Sep 24 04:08:10 2016
ExecutablePath: /usr/games/pcsx
InstallationDate: Installed on 2016-04-22 (154 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcCmdline: pcsx
ProcEnviron:
 LANGUAGE=es_ES
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: pcsxr
StacktraceTop:
 __assert_fail_base (fmt=<optimized out>, assertion=assertion@entry=0x55d01b9beba1 "!isreg || reg != 0", file=file@entry=0x55d01b9beb40 "../libpcsxcore/ix86_64/ix86-64.c", line=line@entry=158, function=function@entry=0x55d01b9bebd0 "MEMADDR_OP") at assert.c:92
 __GI___assert_fail (assertion=0x55d01b9beba1 "!isreg || reg != 0", file=0x55d01b9beb40 "../libpcsxcore/ix86_64/ix86-64.c", line=158, function=0x55d01b9bebd0 "MEMADDR_OP") at assert.c:101
 ?? ()
 ?? ()
 ?? ()
Title: pcsx assert failure: pcsx: ../libpcsxcore/ix86_64/ix86-64.c:158: MEMADDR_OP: La declaración `!isreg || reg != 0' no se cumple.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1562592, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.