Little Battlers eXperience crashes Citra

Citra Support
#1

Issue:
Little Battlers eXperience crashes Citra

System Information

  • Operating System: Windows 10

  • CPU: Intel(R) Core™ i7-9700

  • GPU: Nvidia 2060 Super

  • Citra Version (found in title bar): 1756

  • Game: Little Battlers eXperience

  • Screenshot of Issue (include the full Citra window including titlebar):

Diagnostic Log
Upload your log file as an attachment by dragging & dropping.

citra_log.txt.old.txt (12.0 KB)

In order to save a copy of the log, follow this guide:
https://community.citra-emu.org/t/how-to-upload-the-log-file/296

#2

System Information for Support

Client Version                               Canary 2064   HEAD-892913e
Operating System                             Windows 10 (10.0)
CPU                                          Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz | AVX2 | FMA
Graphics API                                 OpenGL 3.3.0
Graphics Renderer                            NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2
GPU Driver Version                           497.09
CPU JIT                                      [x]
Hardware Renderer                            [x]
Hardware Shader                              [x]
Hardware Shader, Accurate Multiplication     [x]
Shader JIT                                   [x]
System Region                                -1
Shader Disk Cache                            [x]

Here’s some issues I found with your log that might help.

  • Please enable the Vsync option if you are experiencing screen tearing.
#3

New log
citra_log.txt.old.txt (11.9 KB)

#4

System Information for Support

Client Version                               Nightly 1756   HEAD-25ad002
Operating System                             Windows 10 (10.0)
CPU                                          Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz | AVX2 | FMA
Graphics API                                 OpenGL 3.3.0
Graphics Renderer                            NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2
GPU Driver Version                           497.09
CPU JIT                                      [x]
Hardware Renderer                            [x]
Hardware Shader                              [x]
Hardware Shader, Accurate Multiplication     [x]
Shader JIT                                   [x]
System Region                                -1
Shader Disk Cache                            [x]

Here’s some issues I found with your log that might help.

  • Please enable the Vsync option if you are experiencing screen tearing.
#5

New log
citra_log.txt.old.txt (7.5 KB)

#6

System Information for Support

Client Version                               Nightly 1756   HEAD-25ad002
Operating System                             Windows 10 (10.0)
CPU                                          Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz | AVX2 | FMA
Graphics API                                 OpenGL 3.3.0
Graphics Renderer                            NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2
GPU Driver Version                           497.09
CPU JIT                                      [x]
Hardware Renderer                            [x]
Hardware Shader                              [x]
Hardware Shader, Accurate Multiplication     [x]
Shader JIT                                   [x]
System Region                                -1
Shader Disk Cache                            [x]

I did not find anything wrong in your log file. Please wait for a human moderator to assist.

#7 
[  13.473878] HW.Memory <Error> core/memory.cpp:Read:322: unmapped Read32 @ 0x000009FE at PC 0x00100000
[  13.473909] HW.Memory <Error> core/memory.cpp:Write:357: unmapped Write8 0x00000000 @ 0x00000000 at PC 0x00100004

This would seem to indicate that Citra ran into something corrupted. Since you don’t have a game update installed. My bet would be that it’s the ROM. You’ll need to redump your game. Please refer to our game dumping guides:

Dumping Game Cartridges
Dumping Installed Titles

Make sure your GM9 is up to date and that you have enough free storage space available on your SD-Card to perform the dum

#8

Redumping fixed the issue. Thanks.

1 Like