PCSX2 Crashing
#31
Hey Carsonmyr,

This could be unrelated to your issue but I started having the same issue with all builds used (Git build 1.3.1-1109 and previous ones dating back about 2 weeks. I don't currently have their version number sorry) when I changed the SPU2-X setting to "XAudio2" (Recommended). After changing it (either back to original setting or if I tried the setting, can't remember) to DirectSound (Nice), it stopped the crashing regardless of the game.

Before setting the SPU2-X to DirectSound, every game I played would crash approximately every 3 to 5 minutes and especially during intense action scenes. Since changing the setting, I haven't had any issue
Reply

Sponsored links

#32
Sorry I have been busy for the last few days haven't had time to test, I will do a broader search as suggested.

@zwastik This is a problem with OGL, not DX11. DX11 worked fine.

@Cryotech I have never had to change the sound settings for this game, I'm positive it's a graphical thing.

@Everyone I jumped down to 1.3.1-814 (I figured 200 revisions was far enough for the first hop) and I got an app crash, pcsx2 stopped responding and needs to close. Event viewer lists it as a event 1000, application error (with no useful information of course) and I noticed that from the time I started this thread til now I have a whole bunch of 1000 and 1005 app errors, which were generated from all the other crashes. Idk if that's helpful or not. I'll hop down another 200 or so revisions and try again.
Desktop:
Ryzen 7 5800X | MSI MAG CORELIQUID 360R | MSI X570 unify | 32GB DDR4@3600 MHz (14-14-14-34) | EVGA RTX 3070 FTW3 Ultra
1TB + 2TB WD Black SN770 | Windows 11 Pro x64
Reply
#33
Hopped down to 1.3.1-590, another pcsx2 has stopped responding and needs to close. Moving right along here...

EDIT:
1.3.1-401 also produced a PCSX2.exe has stopped responding and needs to close.
1.3.1-199 also produced a PCSX2.exe has stopped responding and needs to close.


I'm really beginning to wonder if this is unique to me....? How could this go unnoticed for 600+ builds...? And I'm not positive because it was months ago but I could have swore 199 was the one that worked flawlessly on OGL for me =/
Desktop:
Ryzen 7 5800X | MSI MAG CORELIQUID 360R | MSI X570 unify | 32GB DDR4@3600 MHz (14-14-14-34) | EVGA RTX 3070 FTW3 Ultra
1TB + 2TB WD Black SN770 | Windows 11 Pro x64
Reply
#34
So that's essentially the whole git library, now what should I do Sad
Desktop:
Ryzen 7 5800X | MSI MAG CORELIQUID 360R | MSI X570 unify | 32GB DDR4@3600 MHz (14-14-14-34) | EVGA RTX 3070 FTW3 Ultra
1TB + 2TB WD Black SN770 | Windows 11 Pro x64
Reply
#35
(09-24-2015, 04:35 AM)Carsomyr Wrote: So that's essentially the whole git library, now what should I do Sad

you could find the commit which worked perfectly and just do git bisect from there and figure it out, do you mean that even the oldest build at the build bot has this issue ?
We're supposed to be working as a team, if we aren't helping and suggesting things to each other, we aren't working as a team.
- Refraction
Reply
#36
Well no I haven't had the time to go any lower, and I will when I do, but I remember the perfect build for me being in the 100's, and I'm almost positive it was after the snowblind fixes...
Desktop:
Ryzen 7 5800X | MSI MAG CORELIQUID 360R | MSI X570 unify | 32GB DDR4@3600 MHz (14-14-14-34) | EVGA RTX 3070 FTW3 Ultra
1TB + 2TB WD Black SN770 | Windows 11 Pro x64
Reply




Users browsing this thread: 1 Guest(s)