Lineage 2 Tower Forum

Full Version: l2tower causing to many problems
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
since ertheia i have been getting a lot of problems.
I only get crashes when using l2tower, ive spent a lot of time trying to identify and/or solve these issues.

what i have tried so far:
Re-installed windows 4 times
2 different windows ultimate 64 bit OS
Re-installed l2 6 times
installed l2 on HDD, SSD, Revodrive
Tried the 4 latest nvidia drivers.(Roll-back and clean uninstall/install)
Tried .net framework 4 and 4.5
Tried different DSETUP.dll, dsetup_setting, System folder
Went from 20 GB page file system to 65 gb to now 350 gb page file system.
And Fox was kind enough to try and help me.


These crashes Don't happen when logged with l2tower patched.
They do happen when running scripts/plugins and gui.
Conclusion is that l2tower is trying to do something that isn't supported.
-------------------------------------------------------------------------------
Version: EP10_Global,BLS,V2110409,19597456
BuildDate: Sun Aug 10 23:03:46 2014

Time: 2014.9.4 21:56:41 [GTick=385,LGTicks=328]
PosCode: 47148:148917:-3682
OS: Windows 7(64) 6.1 (Build: 7601), Service Pack 1.0
CPU: GenuineIntel Intel® Core™ i7-3930K CPU @ 3.20GHz @ 3200 MHz
RAM : 4095MB RAM
CPUInfo: 12,6,12,1
Video: NVIDIA GeForce GTX 760 (4052)
VideoResources: 40 MB
LANG: ENGLISH
IME: ???

Error: History: Advance <- GFxFlashObj::AdvanceAndRender <- Flash Name: ContainerHUD Tick Count: 18E <- GFxUIManager::RenderFlash <- GFxFlashWnd::OnPaint <- NCVirtualWndMain::DrawChildWindow <- NCVirtualWndMain::DrawChildWindow <- WM_PAINT <- NCVirtualWndMain::DispatchWndMsg <- NConsoleWnd::ConsolePostRender <- ConsolePostRender <- Draw <- UGameEngine::Draw <- GRenDev = fd410000 <- UWindowsViewport::RepaintGFxFlashObj::Invoke[7] <- UWindowsClient::Tick <= <- GFxFlashWnd::Invoke[7]ClientTick <- UGameEngine::Tick <= GFxFlashWnd::CallGFxFunction[7] <= UUIScript::execCallGFxFunction[7] <= UObject::ProcessEvent[7] <= (ChatWnd Transient.ChatWnd, Function Interface.ChatWnd.OnEvent, 0x150624F0, 0x36CCEA70, 16, 16)[7] <- UpdateWorld <- CMainLoop::UpdateTheWorld <- MainLoop

Exception:
Code [EXCEPTION_WRITE_VIOLATION DataAddress:0x0000000E]
Address [0x13522D15]
SegCs [0x0023]

NWindow.DLL [0x133C0000] Offset [0x00162D15]
-------------------------------------------------------------------------------------
Version: EP10_Global,BLS,V2110409,49175
BuildDate: Sun Aug 10 23:03:46 2014

Time: 2014.9.12 12:48:28 [GTick=2835,LGTicks=788]
PosCode: 46988:149479:-3739
OS: Windows 7(64) 6.1 (Build: 7601), Service Pack 1.0
CPU: GenuineIntel Intel® Core™ i7-3930K CPU @ 3.20GHz @ 3200 MHz
RAM : 4095MB RAM
CPUInfo: 12,6,12,1
Video: NVIDIA GeForce GTX 760 (4052)
VideoResources: 46 MB
LANG: ENGLISH
IME: ???

Error: History: UMaterial::ClearFallbacks <- ClearFallbacks <- UD3DRenderDevice::Flush <- UD3DRenderDevice::SetRes <- HandleBigChange <- DeviceResetFail: 0 <- UD3DRenderDevice::Lock <- UViewport::Lock <- UWindowsViewport::Lock <- UGameEngine::Draw <- GRenDev = fd410000 <- UWindowsViewport::Repaint <- UWindowsClient::Tick <- ClientTick <- UGameEngine::Tick <- UpdateWorld <- CMainLoop::UpdateTheWorld <- MainLoop

Exception:
Code [EXCEPTION_READ_VIOLATION DataAddress:0x000D0040]
Address [0x20007D7C]
SegCs [0x0023]

Engine.dll [0x20000000] Offset [0x00007D7C]
--------------------------------------------------------------------------
Version: EP10_Global,BLS,V2110409,49175
BuildDate: Sun Aug 10 23:03:46 2014

Time: 2014.9.3 15:34:58 [GTick=1121,LGTicks=955]
PosCode: 47852:149098:-3758
OS: Windows 7(64) 6.1 (Build: 7601), Service Pack 1.0
CPU: GenuineIntel Intel® Core™ i7-3930K CPU @ 3.20GHz @ 3200 MHz
RAM : 4095MB RAM
CPUInfo: 12,6,12,1
Video: NVIDIA GeForce GTX 760 (4052)
VideoResources: 53 MB
LANG: ENGLISH
IME: ???

Error: History: GFxFlashObj::Invoke[7]Advance <- GFxFlashObj::AdvanceAndRender <= GFxFlashWnd::Invoke[7] <- Flash Name: ContainerHUD Tick Count: 46C <= GFxFlashWnd::CallGFxFunction[7] <- GFxUIManager::RenderFlash <- GFxFlashWnd::OnPaint <= UUIScript::execCallGFxFunction[7] <- NCVirtualWndMain::DrawChildWindow <- <= NCVirtualWndMain::DrawChildWindowUObject::ProcessEvent[7] <= (ChatWnd Transient.ChatWnd, Function Interface.ChatWnd.OnEvent, 0x150624F0, 0x35B9EA70, 16, 16)[7] <- WM_PAINT <- NCVirtualWndMain::DispatchWndMsg <- NConsoleWnd::ConsolePostRender <- ConsolePostRender <- Draw <- UGameEngine::Draw <- GRenDev = fd410000 <- UWindowsViewport::Repaint <- UWindowsClient::Tick <- ClientTick <- UGameEngine::Tick <- UpdateWorld <- CMainLoop::UpdateTheWorld <- MainLoop

Exception:
Code [EXCEPTION_WRITE_VIOLATION DataAddress:0x00000000]
Address [0x13691BC6]
SegCs [0x0023]

NWindow.DLL [0x13400000] Offset [0x00291BC6]
l2tower is trying to write on memory space that is already being used by lineage 2. Atleast thats what someone told me.

it would be nice to get a response from clockman.

Thanks for the reply Fox, but it didn't help:/
1. visual studio 2013 redistribute package x86
2. .net 3.5, 4.0, 4.5
3. use clean L2 system (download from forum, or patch own one)
4. turn off plugins, use clean l2tower
5. turn on L2tower logs (in logSettings.txt [Network, Base])
6. reproduce problem.
(09-15-2014 14:15 PM)ClockMan Wrote: [ -> ]1. visual studio 2013 redistribute package x86
2. .net 3.5, 4.0, 4.5
3. use clean L2 system (download from forum, or patch own one)
4. turn off plugins, use clean l2tower
5. turn on L2tower logs (in logSettings.txt [Network, Base])
6. reproduce problem.

I've done all that allready. This isnt Caused by windows, or missing drivers or lineage 2 for that matter.

it's certain functions inside the plugins and scripts that do this.
but if i make the scripts and plugins any dumber then this, i might as well play by hand.

I found another solution to my problems, because i wasted to much energy, time and money on this already. Thanks for the response though.
(09-16-2014 11:42 AM)dst5216 Wrote: [ -> ]
(09-15-2014 14:15 PM)ClockMan Wrote: [ -> ]1. visual studio 2013 redistribute package x86
2. .net 3.5, 4.0, 4.5
3. use clean L2 system (download from forum, or patch own one)
4. turn off plugins, use clean l2tower
5. turn on L2tower logs (in logSettings.txt [Network, Base])
6. reproduce problem.

I've done all that allready. This isnt Caused by windows, or missing drivers or lineage 2 for that matter.

it's certain functions inside the plugins and scripts that do this.
but if i make the scripts and plugins any dumber then this, i might as well play by hand.

I found another solution to my problems, because i wasted to much energy, time and money on this already. Thanks for the response though.

remove all plugins and scripts and try to use tower and see if u get any error if not start adding one by one plugins and scripts and u will find where is the problem
i re made all my plugins, scripts 5+ times now.
like i said in an earlier post. if i made them any dumber, ill have to play by hand.

óh and i'm not persuing this anymore. I'm actually done with tower for now.
It's got to your computer issue. Tons of people use tower with no major issues.
Maybe some one can team view you and check your computer.
(09-16-2014 18:31 PM)BotAgent007 Wrote: [ -> ]It's got to your computer issue. Tons of people use tower with no major issues.
Maybe some one can team view you and check your computer.
I'm using another bot right now, and its very stable. most stable i have seen in a while.

And i also have had had tons of people on my pc threw teamviewer to solve this. but ill be honest, it's not just these crashes that piss me of.

anyways it is a safe assumption since a while ago, that my pc isnt the problem. My operating system isn't the problem. and l2 isnt the problem.

Tried everything and my conclussion is that l2tower is shit.
(09-19-2014 11:03 AM)dst5216 Wrote: [ -> ]
(09-16-2014 18:31 PM)BotAgent007 Wrote: [ -> ]It's got to your computer issue. Tons of people use tower with no major issues.
Maybe some one can team view you and check your computer.
I'm using another bot right now, and its very stable. most stable i have seen in a while.

And i also have had had tons of people on my pc threw teamviewer to solve this. but ill be honest, it's not just these crashes that piss me of.

anyways it is a safe assumption since a while ago, that my pc isnt the problem. My operating system isn't the problem. and l2 isnt the problem.

Tried everything and my conclussion is that l2tower is shit.


Feel free to leave L2Tower and use your other "stable" bot ! Angel
Pages: 1 2
Reference URL's