[September 3, 2023]Abyss Patcher

[destindfate2]

Hey guys,

I'm having trouble with abyss crashing my client again. I fiddled with it so much I finally just uninstalled mabi and re-installed it. Here again, just like last week, fresh install of Mabi runs just fine. As soon as I drop a fresh copy of Abyss.ini, ijl11.dat, and ijl11.dll into the folder I execute MabiDirectLaunch as admin and get the appcrash error. If I remove those files and revert back to the ones installed with the game, it runs fine again.  I'm running nothing but abyss by itself.

Any ideas?

[atralen]

NGS error as of April 6th, 2017, 3:43 PST; Abyss updated and everything.

[Fl0rn]

@destindfate2 and atralen
check NGS thread, if it's NGS errors post in that thread please.  I'm not dismissing the possibility of NGS updating, but it has been working for a while, and others have been having odd issues.  So please do at least make sure you've tried the stuff listed in NGS thread, so you can confirm that NGS is actually updated.

[destindfate2]

@destindfate2 and atralen
check NGS thread, if it's NGS errors post in that thread please.  I'm not dismissing the possibility of NGS updating, but it has been working for a while, and others have been having odd issues.  So please do at least make sure you've tried the stuff listed in NGS thread, so you can confirm that NGS is actually updated.

Thanks Fl0rn, but I'm not even getting as far as an NGS error due to the fact I can't even get the game to launch, which is why I posted here instead of the NGS thread.  I've been following both threads and trying the various things suggested. When all that failed, I opted to just uninstall and try from scratch. Nothing is working for me. It appears to be the same issue I had last week with something not updating causing the crash, but as I mentioned in the last post, it appears to be updated just fine. It's just when I replace ijl11.dll from abyss, I'm getting the crashing.

EDIT:  Okay, so I just ran Blade's file integrity checker app and I'm getting fails on ijl11.dll, BlackCipher\BlackCall.log, BlackCipher\BlackCipher.log, BlackCipher\BlackXchg.log, and BlackCipher\NGClient.log.  Something about ijl11.dll is definitely disagreeing with my set up (obviously), and anything beyond this is above my head. lol

[NovaDracon28]

this is a semi-important question (for me anyway) Is the dll loader still broken? I'm trying to use ENB.

[Blade3575]

this is a semi-important question (for me anyway) Is the dll loader still broken? I'm trying to use ENB.

It was broken?

[Happix100]

After a little bit of time logged in, the game kicks me out saying that there's an NGS threat. Any idea which feature's making that happen?

I currently have data folder reading disabled but I have nearly everything else enabled...

[skylaar727]

After a little bit of time logged in, the game kicks me out saying that there's an NGS threat. Any idea which feature's making that happen?

I currently have data folder reading disabled but I have nearly everything else enabled...

See the NGS thread, its the same problem as was happening 1/2 weeks ago but unfortunately the old fix doesn't work, were currently trying to figure out how to solve it this time, no solution as of yet.

[destindfate2]

For what it's worth. I just attempted to install abyss into my mabi folder again after today's update. I've been running this last week with a clean client. Prior to loading abyss, mabi runs just fine. Dropped abyss in the folder and I'm getting app crash error again, just like the previous two weeks. I still can't even get the game to load once abyss is placed in the folder. I'm running straight abyss, using MabiDirectLaunch, and nothing else. I still feel like it has something to do with ijl11.dll, but I'm definitely no expert on the matter.

Thanks for all the work you guys have been putting into this every week for all these years!

EDIT: Here's the error I'm receiving, for convenience. NOTE, my client is updated, however when I load abyss it acts like it isn't:

Problem signature:
  Problem Event Name:   APPCRASH
  Application Name:   Client.exe
  Application Version:   1.0.0.1
  Application Timestamp:   58e4a795
  Fault Module Name:   StackHash_fa4e
  Fault Module Version:   0.0.0.0
  Fault Module Timestamp:   00000000
  Exception Code:   c0000005
  Exception Offset:   7473e4e4
  OS Version:   6.1.7601.2.1.0.256.4
  Locale ID:   1033
  Additional Information 1:   fa4e
  Additional Information 2:   fa4e53f55b3f1b0dcef608c873e6615d
  Additional Information 3:   5712
  Additional Information 4:   5712f2934fcdf402192801a2ca9e93ff

EDIT 2: I've just run Blade's File Integrity Checker and attached the results.

UPDATE: After multiple attempts to get abyss to run on its own to no avail, I decided to try installing it using Frontend. Ended up with the same result. Use Frontend with abyss installed - appcrash error. Remove abyss using Frontend - game runs just fine. After all this, I opted to just install Kanan. Incidentally, I attempted to use Playtime's Kanan standalone and couldn't get that to run either. Ended up having to get Kanan from the github link.

[Teto Hashiba]

See the NGS thread, its the same problem as was happening 1/2 weeks ago but unfortunately the old fix doesn't work, were currently trying to figure out how to solve it this time, no solution as of yet.

Why is everyone so awfully fast at redirecting to the NGS Error Thread?
So i was made aware of the issue by my sister who currently plays Mabinogi a lot more active than i do.
I decided to check here and saw that everyone seemed to dismiss the possibility of it being Abyss and redirecting to the NGS Error Thread.
So i thought it may be something else than Abyss causing it like a file that was updated and missing data triggering it.
I made sure i was getting the Error as well.

After copying all the new files over my Custom packages which i have active it turned out that NONE was updated and all are still functional as is.
So i decided to go against what this thread has told me and boot up the Game WITHOUT Abyss.

Been online awfully long now.
Quite sure now it IS Abyss being detected and yes i run the newest Version. As for the error it's just that after 2-3 Minutes of being ACTUALLY ingame NGS triggers and boots me for a security threat.
To note: Since the last time i played my BlackCipher updated, so you may wanna look at that.

[skylaar727]

Why is everyone so awfully fast at redirecting to the NGS Error Thread?
So i was made aware of the issue by my sister who currently plays Mabinogi a lot more active than i do.
I decided to check here and saw that everyone seemed to dismiss the possibility of it being Abyss and redirecting to the NGS Error Thread.
So i thought it may be something else than Abyss causing it like a file that was updated and missing data triggering it.
I made sure i was getting the Error as well.

After copying all the new files over my Custom packages which i have active it turned out that NONE was updated and all are still functional as is.
So i decided to go against what this thread has told me and boot up the Game WITHOUT Abyss.

Been online awfully long now.
Quite sure now it IS Abyss being detected and yes i run the newest Version. As for the error it's just that after 2-3 Minutes of being ACTUALLY ingame NGS triggers and boots me for a security threat.
To note: Since the last time i played my BlackCipher updated, so you may wanna look at that.

Because all of the information we've discovered so far, including everything you've just stated, has been tested and recorded in the NGS thread. It's really as simple as keeping all NGS related info in one place without cluttering up Abyss's own technical support issues. Really isn't anything more to it, NGS stuff goes in the NGS thread so we can figure out whats going on.

[Teto Hashiba]

Because all of the information we've discovered so far, including everything you've just stated, has been tested and recorded in the NGS thread. It's really as simple as keeping all NGS related info in one place without cluttering up Abyss's own technical support issues. Really isn't anything more to it, NGS stuff goes in the NGS thread so we can figure out whats going on.

Well, just sounded like everyone was blaming Computers and OS over anything related to the mods in general.

[skylaar727]

Well, just sounded like everyone was blaming Computers and OS over anything related to the mods in general.

Nah were not blaming OS, we started collating people's system specs because the majority of abyss users still dont have issues, whereas those of us suffering them are the same people that had the delete nexonguard and repair installation thing a week or 2 back. Likewise some people's friends using the same setups or even the exact same INIs arent NGSing, so its a little more complicated than it just being Abyss itself, though atm an Abyss update looks like a potential fix.

As things stand atm, people using the same mod configs are playing fine with abyss while some of us NGS, suggesting patching issues or some such, but this time around even clean installing mabi and abyss doesn't fix it, which points it back at abyss. Thats why things are a mess, because thus far we don't know what specifically is causing NGS detection of abyss on a handful of players and not the rest of them. And every time we come across a lead it stops making sense soon after.

That all aside, I wouldn't mind an abyss update from blade just to see if it resolves the issue, since kanans still seems to work for us suffering the issues, but blade is a busy person so we don't want to just waste his time on a whim that might not make a difference either.

So ye, atm things are just a mess while we figure out whats going on, thats why the NGS thread is jumping all over different angles, nobody is specifically blaming users of having a bad pc config or anything.

[Teto Hashiba]

Ah, well i did test it on 5 different Setups (Specifically my own PC , the one of my Sister, Her Laptop, My New Laptop (All Win10) and my old Laptop (Win7 64-bit) and all seem to run into NGS errors with Abyss but not without....

[Fl0rn]

Why is everyone so awfully fast at redirecting to the NGS Error Thread?

Just focusing on this, since most anything else i'd cover is already in said ngs thread.

The NGS thread originated back after NGS had been around a while, and there were issues all over the place.  People didn't have a good spot to post NGS errors, and the info about it was just scattered all over the place, but mainly in abyss and tiara threads i believe.  I mentioned it to the staff, compiled what i could find into the thread, and we, as in the staff, myself, and other users through contributions, have been trying to keep it as up to date as possible.

Why info is still continued there, well somewhere in this thread was a mod, i think playtime, actually directly stating to post NGS errors in the ngs thread and not here.  This is meant for honest abyss discussion.  Our staff is lenient though, and will give leeway to people posting here, while i'll just generally discuss what's recently posted about, while also pointing to the NGS thread for reference and further conversation, out of respect for others and because it is honestly easier to track the information when it's all comprised in one spot.

I'll cut off here, to keep the rambling from getting outta hand.

[Lady Playtime]

Why is everyone so awfully fast at redirecting to the NGS Error Thread?

Sovereign Playtime - Today at 4:39 PM
We try and force all NGS posts there because when happens, we can just look in one singular place for details if we need them. It's a pain in the to go all over the place to find , especially when trying to fix a problem and we have to spend longer trying to get the info we need than actually fixing it.


Also lots of censored stuff because it was from a chat, don't feel like editing it for MM.  So censor emotes for EVERYONE

[Teto Hashiba]

I understand, i posted what i could contribute in the NGS Thread, not much else i can do i guess. Not feeling like messing too much with it today, maybe tomorrow i'll focus a bit more on fooling around, that'll also give me the possibility to dig out an Alt account i don't mind being banned.

[Rorin]

For what it's worth. I just attempted to install abyss into my mabi folder again after today's update. I've been running this last week with a clean client. Prior to loading abyss, mabi runs just fine. Dropped abyss in the folder and I'm getting app crash error again, just like the previous two weeks. I still can't even get the game to load once abyss is placed in the folder. I'm running straight abyss, using MabiDirectLaunch, and nothing else. I still feel like it has something to do with ijl11.dll, but I'm definitely no expert on the matter.

Thanks for all the work you guys have been putting into this every week for all these years!

EDIT: Here's the error I'm receiving, for convenience. NOTE, my client is updated, however when I load abyss it acts like it isn't:

Problem signature:
  Problem Event Name:   APPCRASH
  Application Name:   Client.exe
  Application Version:   1.0.0.1
  Application Timestamp:   58e4a795
  Fault Module Name:   StackHash_fa4e
  Fault Module Version:   0.0.0.0
  Fault Module Timestamp:   00000000
  Exception Code:   c0000005
  Exception Offset:   7473e4e4
  OS Version:   6.1.7601.2.1.0.256.4
  Locale ID:   1033
  Additional Information 1:   fa4e
  Additional Information 2:   fa4e53f55b3f1b0dcef608c873e6615d
  Additional Information 3:   5712
  Additional Information 4:   5712f2934fcdf402192801a2ca9e93ff

EDIT 2: I've just run Blade's File Integrity Checker and attached the results.

UPDATE: After multiple attempts to get abyss to run on its own to no avail, I decided to try installing it using Frontend. Ended up with the same result. Use Frontend with abyss installed - appcrash error. Remove abyss using Frontend - game runs just fine. After all this, I opted to just install Kanan. Incidentally, I attempted to use Playtime's Kanan standalone and couldn't get that to run either. Ended up having to get Kanan from the github link.

I have the exact same problem as you, I've tried turning off everything in abyss even and it will still crash me, I found that it seems to be a problem when interacting with the inventory or other people (such as trades) but i can't figure out how to fix it. I've crashed like 40 times today and even tried running Tiara, but to no avail I still crash.

[Fl0rn]

I have the exact same problem as you, I've tried turning off everything in abyss even and it will still crash me, I found that it seems to be a problem when interacting with the inventory or other people (such as trades) but i can't figure out how to fix it. I've crashed like 40 times today and even tried running Tiara, but to no avail I still crash.

Quick 'this is the impression i got from reading your post,' so correct me if i have any of this wrong.
Crash with abyss.  Crash with tiara.  Crash is from interacting with others' items.  You've tried turning off all features of abyss.

I'm actually not certain if you've tried tiara with abyss though, or tiara alone, without abyss.
As for the crashing, if you're using data mods it may be an outdated xml file.  I would suspect it to be something along the lines of data/db/itemdb.xml.  Rough guessing that name, don't have the file pulled up to check atm.  But you can see if removing it, just temporarily, will fix the issue.  As people have been having issues with abyss recently, i would also suggest attempting this test, without abyss installed as well.

[Rorin]

I've tried Tiara with abyss, not without yet. But it seems it is abyss since I also have a friend who is having prob with abyss aswell. I'll try removing the .xml file and get back to you.

[Rorin]

Tiara without abyss is fine (minus lack of mods), Tired it with abyss and I'm not sure what XML file your talking about but it still crashes. I've run a few more tests and as long as i only have my basic inv tab open and close all my bags the chance of crashing goes down a bit. Checking shops causes crashes, having more then 4 of the bags open does too, heck even being entrusted to ES has crashed me. This is also with just Abyss not Tiara.

[Fl0rn]

Tiara without abyss is fine (minus lack of mods), Tired it with abyss and I'm not sure what XML file your talking about but it still crashes. I've run a few more tests and as long as i only have my basic inv tab open and close all my bags the chance of crashing goes down a bit. Checking shops causes crashes, having more then 4 of the bags open does too, heck even being entrusted to ES has crashed me. This is also with just Abyss not Tiara.

Well, unless you have abyss set to read the data folder, which you said you toggled all options off for testing, then an xml file or any other data folder file shouldn't be an issue.
And as for the cause, i think once upon a time either view color of an item, or view dura of an item, would cause crashing.  But again, you said you toggled off all abyss options for testing, so i can't honestly say what your issue is.  It'd take someone more experienced than me.

[destindfate2]

Well, unless you have abyss set to read the data folder, which you said you toggled all options off for testing, then an xml file or any other data folder file shouldn't be an issue.
And as for the cause, i think once upon a time either view color of an item, or view dura of an item, would cause crashing.  But again, you said you toggled off all abyss options for testing, so i can't honestly say what your issue is.  It'd take someone more experienced than me.

I also attempted Tiara last week with and without Abyss. With Abyss, I get the crashing even with all options set to 0. Without Abyss, it works fine. As stated in my previous post I attempted the same with Frontend this morning; same result - Abyss is a no-go and causes crash every time. In fact, I can simply replace Blade's abyss ijl11.dll with the Nexon version and nothing else (leaving ijl11.dat and abyss.ini) in the folder and my client will run. The moment I drop the abyss ijl11.dll into the folder the appcrash error returns. Incidentally, I didn't have a data folder in the file structure at all, since I was only using Abyss prior to all the test runs with Tiara, Frontend, and Playtime's Kanan Standalone. I finally ditched all those efforts and I'm running fine now using Kanan from the github link.

Rorin, it sounds like you're able to at least load the game. I can't get that far with abyss loaded. The crash occurs as soon as I go to launch it using MabiDirectLaunch. I never even get to the login screen.

Also, it's worth mentioning, I too am running Win7 Enterprise 64-bit. Sounds like most everyone with Win7 is having some issue here.

[Rorin]

Well I'm running Win 10 myself and yes I can run the game fine until i open my inv (it only crashes randomly when opening it or at other specified occurrences). I'm going to try more later and see if i can find the cause but its driving my crazy.

[skylaar727]

Also, it's worth mentioning, I too am running Win7 Enterprise 64-bit. Sounds like most everyone with Win7 is having some issue here.

Personally while I won't rule it out completely there doesnt seem to be a strong enough link to OS at the moment. I initially asked people to start providing it over in the NGS thread to see if any people with win10 had the issues, and whether any win 7 64 didnt, both of which turned out to be true. You have to be careful making a link out of that sort of data because, if studies are to be believed, windows 7 still has a 49.42% market share, so its natural to see a large proportion of reports be from win 7 64. That said its Nexon, so I'm not at all ruling it out completely, as frankly while we now have a workaround for the NGSing side of things, we still don't know whats actually going on.

All that said, I wish you luck with resolving your issue, I'll leave the crashing side of things to the experts here