Hello out of Lurk..

Something odd has happened. Don't know whether it's from today's update or a unlisted corrupted file. I just created a new account and did the normal route leading to the Kikaigahara Rest Area evacuation quest, then almost right out the Rest stop portal on the following subquest suddenly the music goes staccato and ragged and the screen freezes and a Error message: onigiri.exe has experienced a problem and needs to close.

Error signature AppName: onigiri.exe AppVer:0.0.0.0 ModName: kgllib.dll Offset 002883c7

Repeated this twice and each dash out of the Rest area crashes. The sudden ragged music almost seems the cause of the crash. I created another new account an hour later and the same thing not only occurs but even while the splash screen to Kikaigahara Rest Area starts up. I trashed my whole 4 gig Onigiri folder and reinstalled, No dice. That would seem to kill the corrupted folder theory. Is this an upgrade bug?

Running on System 7 and never had a crash in Onigiri before.

Thanx for any assist!

This thread has had problems with the same dll file (it's an OpenGL library). Updating your graphic drivers should fix the problem, since you seem to have moved to a new setup recently? And, make sure you're running on the correct GPU if you have more than one (i.e. Intel Intergrated Graphics).

it not work , reinstall many times still crash when chose character but my friend don't duno why

Happened on another different machine with a fresh Onigiri install. Could there be some kind of failed handshaking going on between onigiri.exe and CS servers? This issue only cropped up after yesterday's update. Any confirmations?

I can't replicate the issue with a new character evacuating Kikaigahara Rest Stop, nor can I with a character that has already cleared the area. Is it possible that the latest patch fixed it? Could you provide screenshots or video?

Otonashi wrote:I can't replicate the issue with a new character evacuating Kikaigahara Rest Stop, nor can I with a character that has already cleared the area. Is it possible that the latest patch fixed it? Could you provide screenshots or video?

Skimmed and screenshot what I could...

<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="onigiri.exe" FILTER="GRABMI_FILTER_PRIVACY">
<MATCHING_FILE NAME="onigiri.exe" SIZE="47712" CHECKSUM="0x6C69FFA3" MODULE_TYPE="WIN32" PE_CHECKSUM="0x17E89" LINKER_VERSION="0x0" LINK_DATE="06/30/2014 03:17:28" UPTO_LINK_DATE="06/30/2014 03:17:28" />
<MATCHING_FILE NAME="bin\gcml.dll" SIZE="126464" CHECKSUM="0x50D25B51" BIN_FILE_VERSION="1.0.0.6" BIN_PRODUCT_VERSION="1.0.0.6" PRODUCT_VERSION="1,0,0,6" FILE_DESCRIPTION="GCML" COMPANY_NAME="CyberStep, Inc." PRODUCT_NAME="gcml" FILE_VERSION="1,0,0,6" ORIGINAL_FILENAME="gcml.dll" INTERNAL_NAME="gcml" LEGAL_COPYRIGHT="Copyright (C) 2014 CyberStep, Inc." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x224A8" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.6" UPTO_BIN_PRODUCT_VERSION="1.0.0.6" LINK_DATE="06/06/2014 01:37:00" UPTO_LINK_DATE="06/06/2014 01:37:00" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="bin\kgllib.dll" SIZE="4032000" CHECKSUM="0x2ABBEDDB" MODULE_TYPE="WIN32" PE_CHECKSUM="0x3D999F" LINKER_VERSION="0x0" LINK_DATE="07/09/2014 05:34:08" UPTO_LINK_DATE="07/09/2014 05:34:08" />
</EXE>
<EXE NAME="kgllib.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="kgllib.dll" SIZE="4032000" CHECKSUM="0x2ABBEDDB" MODULE_TYPE="WIN32" PE_CHECKSUM="0x3D999F" LINKER_VERSION="0x0" LINK_DATE="07/09/2014 05:34:08" UPTO_LINK_DATE="07/09/2014 05:34:08" />
</EXE>
<EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="kernel32.dll" SIZE="993280" CHECKSUM="0x599F4100" BIN_FILE_VERSION="5.1.2600.6532" BIN_PRODUCT_VERSION="5.1.2600.6532" PRODUCT_VERSION="5.1.2600.6532" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.6532 (xpsp_sp3_qfe.140312-0419)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xF63D5" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.6532" UPTO_BIN_PRODUCT_VERSION="5.1.2600.6532" LINK_DATE="03/12/2014 10:48:50" UPTO_LINK_DATE="03/12/2014 10:48:50" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
</DATABASE>


https://onedrive.live.com/redir?resid=5 ... lder%2cjpg



,

Seems like the patch removed support for older OS's. If that's the case, I can't really help you there, if you want to try sending a ticket or something that might help. There is a slim chance that disabling UI (press U) in that area will prevent a crash.

But this isn't like it's just older computers hit as other posts indicate! Past new players tripping over this bug, which isn't good for trying to keep them on and passing on a good word about the game, Onigiri works just fine with gamers with some mileage in so it's not a driver bug. Something minor was inadvertently scratched or added in the update to cause this bug. I hope CS is at least aware of this.

It would be Tech Support, not CS, since this a bug and a very big one. You right it isn't the old OS, but the new OS as well. Tech Support is supposed to fix the bugs in the software and update the client. CS is the ones we contact, and the problem is either sent up to TS or given a canned response. At least when I was in a IT Department, is who is fixing the bugs.