Critical Errors and Solutions

[Licozo]

Here is a list of a few critical errors.


Error: History: FL2GameData::ObsceneDataLoad <- FL2GameData::Load() <- UGameEngine::Init <- InitEngine

Cause: The client cannot properly load banned messages.

Solution: Delete obscene-e.dat from System folder.

Error: General protection fault! History: UOrcMove::CalculateCRC32 <- UGameEngine::Init <- InitEngine

Cause: The client is missing one or more vital files that are required to load the game. You have not installed the patch or updater properly, you have accidently deleted files, or you are not using the right Chronicle.

Solutions: Apply a Full Update with our Launcher or try to install everything from scratch.

Error: Negative delta time! History: UGameEngine::Tick <- UpdateWorld <- MainLoop

Cause: Your Lineage 2 client could not properly read your CPU clock speeds. This usually only happens with AMD processors.

Solutions: Download the [AMD Dual Core Optimizer] program and install it.

Error: Failed to enter Entry: Can't find file 'Entry'. History: UGameEngine::Init <- InitEngine

Cause: Your client is missing one or more required files to launch the game. This may also occur if you install the L2 Server patch onto the wrong version of the game (Hellbound, Gracia, C5, etc).

Solutions: Install the patch in the MAIN Lineage II folder, not the system folder or anywhere else. Installing it in the wrong place can cause this error.

Error: Application failed to initialize properly

Cause: This usually appears when you are using modded video card drivers, very outdated video card drivers, do not have the .NET Framework installed, or any combination of the three.

Solutions: Update your video card drivers to the latest stable ones.

Error: General protection fault! History: UObject:: DissociateImports <- UObject::EndLoad <- UObject:taticLoadObject <- (Engine.SkeletalMesh =anything can be here=) <- IsLoadedResource <- User:etPawnResource <- UNetworkHandler::Tick <- Function Name=NpcInfoPacket <- UGameEngine::Tick <- UpdateWorld <- MainLoop

Cause: This is 99% of the time caused by video card drivers being unable to load textures, or it can be very rarely caused by a missing texture.

Solutions

1. Update your video card drivers to the latest stable ones.

2. If step 1 does not work, do some searching to find out what driver versions work best for your video card. In my case and many others, the latest drivers have caused issues, and older drivers work much better.

Error: History: FArchiveFileReader:eek <- ULinkerLoad:eek <- TLazyArray<< <- FMipmap<< <- SerializeMips <- UTexture:erialize <- LoadObject <- (Texture LineageMonstersTex.death_knight.death_knight_t00 99684524==99684524/133323252 99683358 132383) <- ULinkerLoad:reload <- PreLoadObjects <- UObject::EndLoad <- UObject:taticLoadObject <- (Engine.Texture LineageMonstersTex.Death_Knight_T00 NULL) <- UOrcMove::CalculateCRC32 <- UGameEngine::Init <- InitEngine

Cause: You have a corrupt texture, potentially from another private server that doesn't know how to create a proper patch or from an action you have done yourself.

Solutions

1. Install everything from scratch.

2. If step 1 does not work, reinstall DirectX and update your video card drivers to the latest stable ones.

Error: History: NConsoleWnd::RequestAuthLogin <- NCAuthWnd::OnLoginBtnClick <- NCAuthWnd::OnPasswordDone <- NControl:endEventMessage <- NCEditBox::OnKeyDown <- NCVirtualWndMain:assToFocusedWindow <- NCVirtualWndMain:assToFocusedWindow <- NCVirtualWndMain:assToFocusedWindow <- NCVirtualWndMain:ispatchWndMsg <- NConsoleWnd:ispatchWndMsgX <- NConsoleWnd:ispatchWndMsg <- UWindowsViewport::ViewportWndProc <- WWindow:taticProc <- DispatchMessage <- 006903B0 256 <- MessagePump <- MainLoop

Cause: Another program is intercepting your connection with the Auth server when you click 'Login'. This can be from almost anything.

Solutions

1. If you have an anti'virus program such as AVG, disable all active protection while logging in and enable it again only once you are ingame.

2. Also close any other games that utilise an anti'cheat program, whether it be Gameguard, nProtect, etc. You should now be able to login.

3. Go to C:WINDOWSsystem32driversetc and open the file "hosts" with notepad. Other than all lines starting with the character '#', make sure that this is the only line there.

Unless you have added other lines there and know what you are doing, you can leave those, but delete all lines with L2authd.lineage2.com, L2testauthd.lineage2.com, auth.lineage2.com.tw, auth.lineage2.jp, L2auth.Lineage2.in.th, L2auth.Lineage2.ph, or anything else you see that relates to Lineage 2 Auth.

Error: General protection fault! History: UUIScript::execGetPartyMemberCount <- UObject:rocessEvent <- (MinimapWnd Transient.MinimapWnd0, Function Interface.MinimapWnd.OnLoad) <- NCFrameWnd::OnXMLLoad <- XMLDataManager::CreateWindows <- XMLUIManager::CreateWindows <- NConsoleWnd::InitializeXMLUI <- NConsoleWnd::Initialize <- NConsoleWnd::Init <- UGameEngine::Init <- InitEngine

Cause: Apply a Full Update with our Launcher or try to install everything from scratch.

Error: General protection fault! History: FL2GameData::LoadL2DataBin <- FL2GameData::ObsceneDataLoad <- FL2GameData::Load <- UGameEngine::Init <- InitEngine

Solution: Delete your system folder and try to apply a Fast Update with our Launcher


Critical Error when buying from Shops:

Solution: press: ctrl+alt+del -> task manager -> process -> find L2.exe - > right mouse -> set affinity -> and select only 1 core!