Authentic Old-School Mabinogi Experience
Posted at 10-27-18, 02:56 am Link | #41
The game screen is turning all black on me and i cant seem to fix it. Got any idea whats wrong?
Posted at 04-10-19, 02:43 am Link | #42
Missing MSVCP140.dll and VCRUNTIME140.dll upon hitting "Start Game". Googled it. Said to install Visual Studio C++ 2015 Redistributable. Downloaded it. Wouldn't install because of a preexisting version. Brand new laptop though. Any tips?
Posted at 04-10-19, 03:20 am Link | #43
Posts: 2285Missing MSVCP140.dll and VCRUNTIME140.dll upon hitting "Start Game". Googled it. Said to install Visual Studio C++ 2015 Redistributable. Downloaded it. Wouldn't install because of a preexisting version. Brand new laptop though. Any tips?
Missing MSVCP140.dll and VCRUNTIME140.dll upon hitting "Start Game". Googled it. Said to install Visual Studio C++ 2015 Redistributable. Downloaded it. Wouldn't install because of a preexisting version. Brand new laptop though. Any tips?
Problem solved.
Posted at 08-06-19, 12:57 am Link | #45
Bump for Veikei's reply. Have the same problem.
Posted at 10-21-19, 04:28 am Link | #46
The game screen is turning all black on me and i cant seem to fix it. Got any idea whats wrong?
How do you guys fix this issue? Someone help please!
I got code.client.msg.error.6 message box and inside of it is code.client.msg.error.5
Posted at 09-13-20, 10:05 pm Link | #48
The game screen is turning all black on me and i cant seem to fix it. Got any idea whats wrong?
How do you guys fix this issue? Someone help please!
I am having the same issue; after clicking start at the character select screen, game screen goes black and stays black. Client doesn't go unresponsive, screen just stays black.
Posted at 10-04-26, 08:53 am Link | #50
Re: Constant lock up on cutscene skipping, closing ego chat, closing the mailbox, etc.
There were other users still encountering the issue despite these fixes and I dug deeper into the issue. Windows Error Reporting isn't the problem.
Closing one of these dialogs (mailbox, ego) makes the game throw an exception inside a micro thread, which it normally catches itself. On recent Windows, a security check called SEHOP ("Validate exception chains") rejects how the game's micro threads are set up, so Windows won't let the game catch it and ends the game instead. With error reporting on, the game freezes while Windows dumps memory, then closes. With error reporting off, the game just closes instantly. Either way the crash happens.
The fix is to turn SEHOP off for Client.exe:
1. Open Windows Security → App & browser control → Exploit protection settings.
2. Go to Program settings → Add program to customize → Add by program name, and type Client.exe.
3. Find Validate exception chains (SEHOP), tick Override system settings, switch it Off, and click Apply.
4. Restart the game.
Or, in PowerShell as administrator: Set-ProcessMitigation -Name Client.exe -Disable SEHOP
This fixed a player whose game closed every time they pressed the [X] on the mailbox dialog and spoke with ego and exited via [X]. You no longer need to disable error reporting; if you did, Enable-WindowsErrorReporting in an administrator PowerShell turns it back on. To undo the SEHOP change, you can always remove Client.exe from Program settings.
There were other users still encountering the issue despite these fixes and I dug deeper into the issue. Windows Error Reporting isn't the problem.
Closing one of these dialogs (mailbox, ego) makes the game throw an exception inside a micro thread, which it normally catches itself. On recent Windows, a security check called SEHOP ("Validate exception chains") rejects how the game's micro threads are set up, so Windows won't let the game catch it and ends the game instead. With error reporting on, the game freezes while Windows dumps memory, then closes. With error reporting off, the game just closes instantly. Either way the crash happens.
The fix is to turn SEHOP off for Client.exe:
1. Open Windows Security → App & browser control → Exploit protection settings.
2. Go to Program settings → Add program to customize → Add by program name, and type Client.exe.
3. Find Validate exception chains (SEHOP), tick Override system settings, switch it Off, and click Apply.
4. Restart the game.
Or, in PowerShell as administrator: Set-ProcessMitigation -Name Client.exe -Disable SEHOP
This fixed a player whose game closed every time they pressed the [X] on the mailbox dialog and spoke with ego and exited via [X]. You no longer need to disable error reporting; if you did, Enable-WindowsErrorReporting in an administrator PowerShell turns it back on. To undo the SEHOP change, you can always remove Client.exe from Program settings.
Powered by mabi.pro v1.0035-arisa (View credits)
MabiPro is not associated with Nexon Co., Ltd. in any way shape or form.