Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[Bug Report] PCSX2 Crash after changing window focus
#1
If I change window focus from PCSX2 to another program, PCSX2 will later stutter and likely crash, depending on how often you change program focus, and how long you have focus away from PCSX2.

This only appears to happen if I change focus away from PCSX2 while it is running a game. If I pause emulation and change focus(Say, to firefox to scroll down a Walkthrough on GameFAQs), it does not crash.

If I change focus once and back quickly, the game will stutter several minutes later, then continue without problem.

If I change focus as much as four or five times, PCSX2 will crash within the next ten to twenty minutes.

If I change focus to something else, and walk away without pausing emulation or returning to PCSX2, it will crash within an hour.

I'm running Windows 7, 64bit.

I'm currently using PCSX2 1.0(The problem happens on 0.9.8 as well). My emulation settings are the default. The problem occurs whether or not speedhacks are enabled.

GSDX 5334: Direct3D 10, Weave bff, native resolution.
SPU2-X 5324: Default settings

If this is a duplicate, I apologize. The only thing I found with the search was a post that had been closed because the original poster apparently didn't already own a PS2.
Reply

Sponsored links

#2
not reproducible

check drivers, bios settings, power supply, etc.
Reply
#3
(09-06-2012, 02:16 AM)Squall Leonhart Wrote: not reproducible

check drivers, bios settings, power supply, etc.

I'll try to get it on video while I check everything.

Would it be worth it to post the Windows Event Logs of PCSX2 crashes?

In any case, here are all of the event logs of crashes since I updated to 1.0.

Faulting application name: pcsx2-r5350.exe, version: 0.0.0.0, time stamp: 0x50191438
Faulting module name: XAudio2_7.dll_unloaded, version: 0.0.0.0, time stamp: 0x4c0641e5
Exception code: 0xc0000005
Fault offset: 0x6cc5a5e0
Faulting process id: 0x12e0
Faulting application start time: 0x01cd8a5d61f0751a
Faulting application path: C:\Program Files (x86)\PCSX2 1.0.0\pcsx2-r5350.exe
Faulting module path: XAudio2_7.dll
Report Id: 6df8482b-f653-11e1-b1a5-0026187df54b

Faulting application name: pcsx2-r5350.exe, version: 0.0.0.0, time stamp: 0x50191438
Faulting module name: XAudio2_7.dll_unloaded, version: 0.0.0.0, time stamp: 0x4c0641e5
Exception code: 0xc0000005
Fault offset: 0x6c0fa5e0
Faulting process id: 0x11ec
Faulting application start time: 0x01cd7d8ec383846f
Faulting application path: C:\Program Files (x86)\PCSX2 1.0.0\pcsx2-r5350.exe
Faulting module path: XAudio2_7.dll

Faulting application name: pcsx2-r5350.exe, version: 0.0.0.0, time stamp: 0x50191438
Faulting module name: d3dx9_43.dll_unloaded, version: 0.0.0.0, time stamp: 0x4bf7318d
Exception code: 0xc0000005
Fault offset: 0x6d15a5e0
Faulting process id: 0x10b8
Faulting application start time: 0x01cd84d924e63913
Faulting application path: C:\Program Files (x86)\PCSX2 1.0.0\pcsx2-r5350.exe
Faulting module path: d3dx9_43.dll

Faulting application name: pcsx2-r5350.exe, version: 0.0.0.0, time stamp: 0x50191438
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b8f
Exception code: 0xc0000374
Fault offset: 0x000ce6c3
Faulting process id: 0xf40
Faulting application start time: 0x01cd7e4a971875d7
Faulting application path: C:\Program Files (x86)\PCSX2 1.0.0\pcsx2-r5350.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll

Given that I play several hours a day and updated on the day 1.0 came out, crashes are pretty rare. Every crash I've ever observed happened while I was alt-tabbed from the game, however. I'll do my best to get it on video.
Reply
#4
i can leave pcsx2 sitting minimised for hours (using my pc as a heater :>)


a crash in ntdll, like i surmised, indicates a system instability.
Reply
#5
(09-06-2012, 04:41 AM)Squall Leonhart Wrote: i can leave pcsx2 sitting minimised for hours (using my pc as a heater :>)


a crash in ntdll, like i surmised, indicates a system instability.

I see. Thank you. Because it only happened for PCSX2, I'd assumed it to be PCSX2.
Reply
#6
Since it's crashing in a random DLL, that most likely is a memory issue. I would bet that you would be having a lot of BSODs. You can do a memory test and if it turns out that there is a problem it most likely is only in one ram stick. You can remove that stick and things should be better.

(09-06-2012, 02:16 AM)Squall Leonhart Wrote: not reproducible

check drivers, bios settings, power supply, etc.
If it was the power supply it would crash the entire computer.
Reply
#7
Quote: If it was the power supply it would crash the entire computer.

not at all, a video card might take a dip and trigger a tdr
Reply
#8
It could happen but that would be the best possible outcome when your video card isn't getting enough power. But we're getting off topic and I don't want to argue Smile

Most likely a memory problem. Hope you find out what's wrong!
Reply
#9
Moved out of bug reports
[Image: newsig.jpg]
Reply
#10
tried testing all your components with occt 4.3.1? (google it)

it checks and stresses your computer for faults in the system.

if everything DOES complete with no error MAYBE it can ben pcsx2 (can be alot of things really)
------------------------
status:
------------------------
trolling mode: ACTIVE!
Reply




Users browsing this thread: 1 Guest(s)