11-18-2016, 02:24 AM (This post was last modified: 11-18-2016, 10:43 PM by LoopyD.
Edit Reason: Issue resolved
)
Issue
PCSX2 randomly hangs up the main process, forcing you to hard reset your computer.
-OR-
During game play, PCSX2 crashes with the Windows error "PCSX2 has stopped working" with a "close program" button
Notes
Drivers are up to date
PCSX2 1.4.0
GDx SSE2
No other application using DirectX causes this issue
My computer specs are far beyond the recommended specifications to. run PCSX2 smoothly (aside the GPU, which is categorized as "running moderately smooth" on the "Will my computer run PCSX2?" thread.
Resolution
Two-fold: 1. CPU and GPU cooling issue. Checked temps in the morning after simple game play. 54°C CPU 55°C GPU 43°C FSB. Turned off overclocking and set Qfan to full speed. Let unit thermal diffuse for 3 minutes and then power off.
2. Razer Synapse and Motor joy conflict.
Uninstalled Motor Joy driver. Afterglow controller has its own WHQL certified drivers.
-
11-18-2016, 02:39 AM (This post was last modified: 11-18-2016, 02:43 AM by Teentitanbg.)
(11-18-2016, 02:24 AM)LoopyD Wrote: Issue
PCSX2 randomly hangs up the main process, forcing you to hard reset your computer.
-OR-
During game play, PCSX2 crashes with the Windows error "PCSX2 has stopped working" with a "close program" button
Notes
Drivers are up to date
PCSX2 1.4.0 GDx SSE2
No other application using DirectX causes this issue
My computer specs are far beyond the recommended specifications to. run PCSX2 smoothly (aside the GPU, which is categorized as "running moderately smooth" on the "Will my computer run PCSX2?" thread.
PCSX2 randomly hangs up the main process, forcing you to hard reset your computer.
-OR-
During game play, PCSX2 crashes with the Windows error "PCSX2 has stopped working" with a "close program" button
Notes
Drivers are up to date
PCSX2 1.4.0
GDx SSE2
No other application using DirectX causes this issue
My computer specs are far beyond the recommended specifications to. run PCSX2 smoothly (aside the GPU, which is categorized as "running moderately smooth" on the "Will my computer run PCSX2?" thread.
Reset your OC back to stock speeds and see if it still happens. The instability and freezing could just be caused by the OCing done. PCSX2 relies heavily on the CPU, so there's a good chance that now that your CPU is actually being stressed, those instabilities are coming forward.
Thank you. I will give both suggested solutions a shot. In order of request of course. Report back soon.
Update : SSE3 mode causes crash. Happened during Gummi Garage editing. I'll log future crashes. @Ryudo I will give your solution a shot when done testing all the SSE modes with the OC. This bug takes a while to get a hold of because it happens randomly.
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_pcsx2.exe_fc8f8dba21623ea5b42356a36ce85e792039b9_c4b923e5_20964b93
SSE3 crash dump (event viewer) #1: This event was raised before I hard reset due to disk inaccessibility (irreverent info, see SSE3 crash dump #2)
Code:
Error 11/17/2016 6:48:04 PM Application Error 1005 (100)
Log Name: Application
Source: Application Error
Date: 11/17/2016 6:48:04 PM
Event ID: 1005
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-6VLQM5R
Description:
Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program pcsx2.exe because of this error.
Program: pcsx2.exe
File:
The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_pcsx2.exe_d7ac4c3563ac9c0cd8425ccddf642ca8ff7919_c4b923e5_20c5dba4
11-18-2016, 10:45 PM (This post was last modified: 11-18-2016, 10:52 PM by LoopyD.
Edit Reason: Typos, mobile keypad. :/
)
Hey guys. Got it fixed. Ryudo's solution was correct, and the BSODs and emulator crashes where related to the Razer Synapse drivers for my keyboard and mouse throwing a fit because of Motor Joy. Noticed from the Event Viewer the BSODs where related to inputs on my controller and keyboard. Combined with the thermal overload, fixing both issues resolved the problem.