Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[resolved] KH2FM English Patch - Frequent Emulator and PC hanging
#1
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.

-

Intel Core i7 6700k overvoltage 1.34v / 4.7 ghtz

ASUS SABERTOOTH Z170-S motherboard
G.skill DDR4 PC2400 x4 8 GB (32 GB RAM)
256 GB Samsung 950 Pro M.2 NMVe SSD 4x lanes
2x SATAe 3gb/s 1 TB RAID 0 (2 TB array, striped)
Nvidia GeForce GT 760
Windows 10 Home Build 1607
NTFS 256 GB SSD (operating system) partition 0-3 - OS
NTFS 500 GB (high speed VirtualBox) partition1 - VBOX
VeroCrypted RAID 1.5 TB (program data, videos, etc.) partitoon2 - SNOW
Reply

Sponsored links

#2
(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.

Will give logs if needed

Intel Core i7 6700k overvoltage 1.34v / 4.7 ghtz

ASUS SABERTOOTH Z170-S motherboard
G.skill DDR4 PC2400 x4 8 GB (32 GB RAM)
256 GB Samsung 950 Pro M.2 NMVe SSD 4x lanes
2x SATAe 3gb/s 1 TB RAID 0 (2 TB array, striped)
Nvidia GeForce GT 760
Windows 10 Home Build 1607
NTFS 256 GB SSD (operating system) partition 0-3 - OS
NTFS 500 GB (high speed VirtualBox) partition1 - VBOX
VeroCrypted RAID 1.5 TB (program data, videos, etc.) partitoon2 - SNOW

Edit: Try SSE 4.1.

Did get PCSX2 SVN (GIT) up to date yet?
http://buildbot.orphis.net/pcsx2/
[Image: B0sYUKo.png]
Reply
#3
(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.

Will give logs if needed

Intel Core i7 6700k overvoltage 1.34v / 4.7 ghtz

ASUS SABERTOOTH Z170-S motherboard
G.skill DDR4 PC2400 x4 8 GB (32 GB RAM)
256 GB Samsung 950 Pro M.2 NMVe SSD 4x lanes
2x SATAe 3gb/s 1 TB RAID 0 (2 TB array, striped)
Nvidia GeForce GT 760
Windows 10 Home Build 1607
NTFS 256 GB SSD (operating system) partition 0-3 - OS
NTFS 500 GB (high speed VirtualBox) partition1 - VBOX
VeroCrypted RAID 1.5 TB (program data, videos, etc.) partitoon2 - SNOW


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.
Intel Core i5-4670K @ 3.40GHz | 16GB (2x8GB) DDR3-1866 G.SKILL Sniper Series
AMD Radeon R9 280 @ 3 GB | 120GB SSD | Windows 7 Ultimate x64 (SP1)
Reply
#4
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.
Reply
#5
do you get the same without applying the english patch ?
CPU : I7 2600K Oc'ed @ 4.2Ghz
Mobo : Intel P67 southbridge
GPU : NVIDIA Geforce GTX 750 Ti
RAM : 6 Go
Reply
#6
(11-18-2016, 02:39 AM)Teentitanbg Wrote: Edit: Try SSE 4.1.

Did get PCSX2 SVN (GIT) up to date yet?
http://buildbot.orphis.net/pcsx2/

Suggestion to try different SSE modes
Status: testing

Notes: Noticed a BSOD somewhere in the error log. But it was unrelated to PCSX2...hm...

Here's the crash dumps and files:

SSE2 crash dump (event viewer):
Code:
Error    11/17/2016 3:14:03 PM    Application Error    1000    (100)
Log Name:      Application
Source:        Application Error
Date:          11/17/2016 3:14:03 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-6VLQM5R
Description:
Faulting application name: pcsx2.exe, version: 0.0.0.0, time stamp: 0x568bfd0e
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x306337ae
Faulting process id: 0x2308
Faulting application start time: 0x01d2411ba017ef5f
Faulting application path: C:\Program Files (x86)\PCSX2 1.4.0\pcsx2.exe
Faulting module path: unknown
Report Id: b590d2ad-be38-46cb-b0f3-af173315e4a5
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-11-17T23:14:03.355060500Z" />
    <EventRecordID>1786</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-6VLQM5R</Computer>
    <Security />
  </System>
  <EventData>
    <Data>pcsx2.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>568bfd0e</Data>
    <Data>unknown</Data>
    <Data>0.0.0.0</Data>
    <Data>00000000</Data>
    <Data>c0000005</Data>
    <Data>306337ae</Data>
    <Data>2308</Data>
    <Data>01d2411ba017ef5f</Data>
    <Data>C:\Program Files (x86)\PCSX2 1.4.0\pcsx2.exe</Data>
    <Data>unknown</Data>
    <Data>b590d2ad-be38-46cb-b0f3-af173315e4a5</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

-

Log Name:      Application
Source:        Windows Error Reporting
Date:          11/17/2016 3:14:07 PM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-6VLQM5R
Description:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: pcsx2.exe
P2: 0.0.0.0
P3: 568bfd0e
P4: StackHash_2beb
P5: 0.0.0.0
P6: 00000000
P7: c0000005
P8: PCH_0B_FROM_ntdll+0x0006E2CC
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3D2B.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_pcsx2.exe_fc8f8dba21623ea5b42356a36ce85e792039b9_c4b923e5_20964b93

Analysis symbol:
Rechecking for solution: 0
Report Id: b590d2ad-be38-46cb-b0f3-af173315e4a5
Report Status: 97
Hashed bucket:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Error Reporting" />
    <EventID Qualifiers="0">1001</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-11-17T23:14:07.123084200Z" />
    <EventRecordID>1787</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-6VLQM5R</Computer>
    <Security />
  </System>
  <EventData>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>APPCRASH</Data>
    <Data>Not available</Data>
    <Data>0</Data>
    <Data>pcsx2.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>568bfd0e</Data>
    <Data>StackHash_2beb</Data>
    <Data>0.0.0.0</Data>
    <Data>00000000</Data>
    <Data>c0000005</Data>
    <Data>PCH_0B_FROM_ntdll+0x0006E2CC</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3D2B.tmp.WERInternalMetadata.xml</Data>
    <Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_pcsx2.exe_fc8f8dba21623ea5b42356a36ce85e792039b9_c4b923e5_20964b93</Data>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>b590d2ad-be38-46cb-b0f3-af173315e4a5</Data>
    <Data>97</Data>
    <Data>
    </Data>
  </EventData>
</Event>

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.

Additional Data
Error value: 00000000
Disk type: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="49152">1005</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-11-18T02:48:04.265102100Z" />
    <EventRecordID>1843</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-6VLQM5R</Computer>
    <Security />
  </System>
  <EventData>
    <Data>
    </Data>
    <Data>pcsx2.exe</Data>
    <Data>00000000</Data>
    <Data>0</Data>
  </EventData>
</Event>

SSE3 crash dump (event viewer) #2:
Code:
Error    11/17/2016 6:48:04 PM    Application Error    1000    (100)
Log Name:      Application
Source:        Application Error
Date:          11/17/2016 6:48:04 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-6VLQM5R
Description:
Faulting application name: pcsx2.exe, version: 0.0.0.0, time stamp: 0x568bfd0e
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000096
Fault offset: 0x30b50c92
Faulting process id: 0x1cfc
Faulting application start time: 0x01d2413354da153e
Faulting application path: C:\Program Files (x86)\PCSX2 1.4.0\pcsx2.exe
Faulting module path: unknown
Report Id: 89c62ec2-7b20-4d0f-988c-3e0f791d6f55
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-11-18T02:48:04.264600800Z" />
    <EventRecordID>1842</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-6VLQM5R</Computer>
    <Security />
  </System>
  <EventData>
    <Data>pcsx2.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>568bfd0e</Data>
    <Data>unknown</Data>
    <Data>0.0.0.0</Data>
    <Data>00000000</Data>
    <Data>c0000096</Data>
    <Data>30b50c92</Data>
    <Data>1cfc</Data>
    <Data>01d2413354da153e</Data>
    <Data>C:\Program Files (x86)\PCSX2 1.4.0\pcsx2.exe</Data>
    <Data>unknown</Data>
    <Data>89c62ec2-7b20-4d0f-988c-3e0f791d6f55</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

-

Log Name:      Application
Source:        Windows Error Reporting
Date:          11/17/2016 6:48:11 PM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-6VLQM5R
Description:
Fault bucket 108342066490, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: pcsx2.exe
P2: 0.0.0.0
P3: 568bfd0e
P4: StackHash_2beb
P5: 0.0.0.0
P6: 00000000
P7: c0000096
P8: PCH_07_FROM_ntdll+0x0006E2CC
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC117.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_pcsx2.exe_d7ac4c3563ac9c0cd8425ccddf642ca8ff7919_c4b923e5_20c5dba4

Analysis symbol:
Rechecking for solution: 0
Report Id: 89c62ec2-7b20-4d0f-988c-3e0f791d6f55
Report Status: 0
Hashed bucket: 432f4a9d487708a2d9bdf0dbf28173e6
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Error Reporting" />
    <EventID Qualifiers="0">1001</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-11-18T02:48:11.143396300Z" />
    <EventRecordID>1844</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-6VLQM5R</Computer>
    <Security />
  </System>
  <EventData>
    <Data>108342066490</Data>
    <Data>1</Data>
    <Data>APPCRASH</Data>
    <Data>Not available</Data>
    <Data>0</Data>
    <Data>pcsx2.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>568bfd0e</Data>
    <Data>StackHash_2beb</Data>
    <Data>0.0.0.0</Data>
    <Data>00000000</Data>
    <Data>c0000096</Data>
    <Data>PCH_07_FROM_ntdll+0x0006E2CC</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC117.tmp.WERInternalMetadata.xml</Data>
    <Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_pcsx2.exe_d7ac4c3563ac9c0cd8425ccddf642ca8ff7919_c4b923e5_20c5dba4</Data>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>89c62ec2-7b20-4d0f-988c-3e0f791d6f55</Data>
    <Data>0</Data>
    <Data>432f4a9d487708a2d9bdf0dbf28173e6</Data>
  </EventData>
</Event>

SSE4.1: Testing...



Post attachments:

crashes.zip:
SSE2-report.wer - windows error details for crash on SSE2
SSE3-report.wer - windows error details for crash on SSE3


Attached Files
.zip   crashes.zip (Size: 5,1 KB / Downloads: 18)
Reply
#7
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.

Ryudo rep +1
Reply
#8
(11-18-2016, 07:36 AM)jesalvein Wrote: do you get the same without applying the english patch ?

Yes.   But issue resolved. It was a driver conflict + thermal overload.
Reply




Users browsing this thread: 1 Guest(s)