01-22-2020, 06:36 AM
(This post was last modified: 01-22-2020, 06:45 AM by iDeaL.
Edit Reason: wording
)
Hello everyone,
Lately, I have been playing SOCOM II multiplayer on pcsx2 through LAN. Everything runs smoothly in Gsdx 11 Hardware mode, but certain maps in the game require Software mode to be used. In software mode, everything chugs along just fine, with the exception of some very minor slowdown in certain spots in certain maps. But every time I'm playing in software mode, pcsx2 will unexpectedly hang with no warning and no obvious cause. Whatever frame is being rendered on screen at the time just stays there, and attempting to close the program leads to it "not responding" and needing to be force closed. Below, I will post the emulog starting from the point I switch to software mode until the hang. I will also include the Windows Event viewer entry. If this information is enough, is there anyone that can provide any input in regards to why this may be happening? To me, nothing really sticks out.. you will notice the last 2 lines of the log just before the application hang also appear at other times prior to the hang, but don't cause hanging at that moment. Also something to note, it has been happening both with and without the "MTVU (Multi-Threaded MicroVU1)" checkbox selected under speedhacks settings. Any insight will be very much appreciated!
PC specs:
MOBO: ASUS ROG STRIX B450-F
CPU: AMD Ryzen 7 2700X 8-Core
GPU: XFX Radeon RX 590 Fatboy "Core Edition"
RAM: 16 GB G.SKILL TridentZ RGB Series DDR4
OS: Microsoft Windows 10 Pro (build 18362), 64-bit
PCSX2 Version: 1.5.0-dev-2928 g1ae48db87
DEV9 Plugin version: CLR DEV9 0.7.0
emulog:
Event Viewer entry:
The program pcsx2.exe version 0.0.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
Process ID: 1044
Start Time: 01d5d0c174640099
Termination Time: 25
Application Path: C:\pcsx2 1.5 dev git\pcsx2.exe
Report Id: 59217071-ab95-422c-bf21-88e7d5c25172
Faulting package full name:
Faulting package-relative application ID:
Hang type: Unknown
Lately, I have been playing SOCOM II multiplayer on pcsx2 through LAN. Everything runs smoothly in Gsdx 11 Hardware mode, but certain maps in the game require Software mode to be used. In software mode, everything chugs along just fine, with the exception of some very minor slowdown in certain spots in certain maps. But every time I'm playing in software mode, pcsx2 will unexpectedly hang with no warning and no obvious cause. Whatever frame is being rendered on screen at the time just stays there, and attempting to close the program leads to it "not responding" and needing to be force closed. Below, I will post the emulog starting from the point I switch to software mode until the hang. I will also include the Windows Event viewer entry. If this information is enough, is there anyone that can provide any input in regards to why this may be happening? To me, nothing really sticks out.. you will notice the last 2 lines of the log just before the application hang also appear at other times prior to the hang, but don't cause hanging at that moment. Also something to note, it has been happening both with and without the "MTVU (Multi-Threaded MicroVU1)" checkbox selected under speedhacks settings. Any insight will be very much appreciated!
PC specs:
MOBO: ASUS ROG STRIX B450-F
CPU: AMD Ryzen 7 2700X 8-Core
GPU: XFX Radeon RX 590 Fatboy "Core Edition"
RAM: 16 GB G.SKILL TridentZ RGB Series DDR4
OS: Microsoft Windows 10 Pro (build 18362), 64-bit
PCSX2 Version: 1.5.0-dev-2928 g1ae48db87
DEV9 Plugin version: CLR DEV9 0.7.0
emulog:
Code:
Current Renderer: Direct3D 11 (Software renderer)
GSdx Lookup CRC:3D98F252
Loading GS
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
EE/iR5900-32 Recompiler Reset
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:Tap Error: 6 : Packet Recive Error :System.IO.IOException: The parameter is incorrect.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.BeginWriteCore(Byte[] bytes, Int32 offset, Int32 numBytes, AsyncCallback userCallback, Object stateObject)
at System.IO.FileStream.FlushWrite(Boolean calledFromFinalizer)
at System.IO.FileStream.Read(Byte[] array, Int32 offset, Int32 count)
at CLRDEV9.DEV9.SMAP.Tap.TAPAdapter.Recv(NetPacket& pkt)
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:Tap Error: 6 : Packet Recive Error :System.IO.IOException: The parameter is incorrect.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.BeginWriteCore(Byte[] bytes, Int32 offset, Int32 numBytes, AsyncCallback userCallback, Object stateObject)
at System.IO.FileStream.FlushWrite(Boolean calledFromFinalizer)
at System.IO.FileStream.Read(Byte[] array, Int32 offset, Int32 count)
at CLRDEV9.DEV9.SMAP.Tap.TAPAdapter.Recv(NetPacket& pkt)
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
989snd Error: cause 3 -> 314893946, 314893946, 0, 0
989snd Error: cause 3 -> 314893946, 314893946, 0, 0
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
989snd Error: cause 3 -> 314893946, 314893946, 0, 0
989snd Error: cause 3 -> 314893946, 314893946, 0, 0
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
989snd Error: cause 3 -> 314893946, 314893946, 0, 0
989snd Error: cause 3 -> 314893946, 314893946, 0, 0
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : rSMAP
CLR_DEV9:SMAP Information: 4 : wSMAP
989snd Error: cause 3 -> 314893946, 314893946, 0, 0
989snd Error: cause 3 -> 314893946, 314893946, 0, 0Event Viewer entry:
The program pcsx2.exe version 0.0.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
Process ID: 1044
Start Time: 01d5d0c174640099
Termination Time: 25
Application Path: C:\pcsx2 1.5 dev git\pcsx2.exe
Report Id: 59217071-ab95-422c-bf21-88e7d5c25172
Faulting package full name:
Faulting package-relative application ID:
Hang type: Unknown