Posts: 58
Threads: 5
Joined: Jan 2009
Reputation:
1
05-25-2016, 06:55 PM
(This post was last modified: 05-27-2016, 08:08 AM by ssakash.)
# PCSX2 version: PCSX2 1.5.0-20160511140759
# CPU options: All at default settings, all hacks disabled.
# Plugins used: GSdx 20160511140759 avx2, SPU2-X20160123134516 2.0.0
# Description: Software mode crash pcsx2 on boot before the memory cards screen.
No problem with hardware mode.
I tried a lot of videos plugins and they all act the same.
Posts: 20.368
Threads: 405
Joined: Aug 2005
Reputation:
555
Location: England
does it still happen on newer git builds? That one is a few weeks old now.
Posts: 3.031
Threads: 4
Joined: Aug 2015
Reputation:
134
05-25-2016, 11:59 PM
(This post was last modified: 05-25-2016, 11:59 PM by FlatOut.)
Was something fixed for software mode only that would fix it?
Posts: 58
Threads: 5
Joined: Jan 2009
Reputation:
1
I took the last rev and did a fresh install and the issue remains.
The software mode crash between
# Restart Without Memory Clear Done.
and
Get Reboot Request From EE
from the log. (2nd line read with hw mode)
Posts: 15.298
Threads: 431
Joined: Aug 2005
Reputation:
353
Location: Athens,Greece
Did you try SW mode of OpenGL, DX9 and DX11?
Posts: 8.597
Threads: 105
Joined: May 2014
Reputation:
169
Location: 127.0.0.1
Could you provide the full emulog text when you reproduce the crash ?
Posts: 6.069
Threads: 68
Joined: May 2010
Reputation:
167
Location: Grenoble, France
A stack trace would be more useful. It is likely a buffer overflow access of the gs memory.
Posts: 58
Threads: 5
Joined: Jan 2009
Reputation:
1
It goes a bit further with dx9 software but still crashes.
Here are the 2 emulogs 1 from opengl 1 from dx9, all software.
For a stack trace, I'd need to know how to provide a such info.
Posts: 58
Threads: 5
Joined: Jan 2009
Reputation:
1
Hi, I tried the game again with the latest build "pcsx2-v1.5.0-dev-1277-g6589fea-windows-x86".
The game now boots correctly.
Posts: 20.368
Threads: 405
Joined: Aug 2005
Reputation:
555
Location: England
Thank you for your report.
This bug report has now been marked as Resolved since it has been fixed on our code base.
This thread will now be closed and moved to the resolved bug reports subforum.