>> This might be a stab in the dark, but have you considered switching the affinity of the cores for AC?

Doubt that would be an issue, as AC is single-threaded.

See I told you VI would be along to set me right.
Sometimes my random ideas... not so good...

 

-----signature-----

Well thanks for the stab in the dark at least...but no one has any solutions to my problems??? well what seems like for mine and Reluke's problem I should say.

Check your Event Viewer. Dunno if they moved it in Vista, but in XP it is in:

Control Panel -> Administrative Settings -> Event Viewer -> Application


Are there a bunch of .NET Runtime errors littered throughout the log?


If so, this appears to affect everyone I know who runs Decal, especially with some sort of combination of LTx and other plugins. At times I can get lucky and remain stable for over 12 hrs, but that's only if I have 1 client running. 2 clients and everything crashes much faster, usually within a few mins to a few hours. There's many posts of this issue and that it may involve a memory leak. That would make sense then, that 2 clients crash faster, as the memory is leaking twice as fast.

interesting, I do have a lot of .net 2.0 errors. I also have lots of ac client application errors. It seems to me, that if I'm leaking memory, I'm leaking faster than I should be. I could run the same amount on a 128mb video card as i do on my new 512 video card. is there something i can do like update my .net framework, like a driver?

Check windows updates to make sure .net is patched all the way up to date.

What exactly are the contents of the error reports for .net and ac client? Are they always the same? (you can click into the reports and use copy & paste on them)
Just saying you have an error means there is a problem, knowing the contents of the report can help figure out whats going on. Much like BSOD, getting one means something went wrong, but unless you write down the information theres no way to know what the source problem is. When you hit the Debug option, does it save an extra file somewhere? The debug button doesn't mean windows debugs the code, it just generates information about what lead to the error...

To try to combat the leaks you could shut down some of the HUDs you don't absolutely need to have open and drawing.
If your fighting in a static location (IE your super secret spot in EO where you don't move from) you could lower the draw distance down alot, maybe lower some of the detail.

Not permanent fixes, but some ideas to try and extend the amount of time before the leak gets so huge it crashes you.

 

-----signature-----

Here are errors that I got today. They are usally the same errors every time.

Faulting application acclient.exe, version 0.0.11.2169, stamp 498b7706, faulting module acclient.exe, version 0.0.11.2169, stamp 498b7706, debug? 0, fault address 0x00149634.

Faulting application acclient.exe, version 0.0.11.2169, stamp 498b7706, faulting module decalnet.dll, version 2.9.6.0, stamp 45744771, debug? 0, fault address 0x00033910.

Faulting application acclient.exe, version 0.0.11.2169, faulting module decalnet.dll, version 2.9.6.0, fault address 0x00033910.

Fault bucket 1138573974.

The first two are .net errors, and the second two are application errors. Also

The instruction at 0xc90100b referenced memory at "0x00000014". The memory could not be "read".

hurm decalnet.dll.... i gots nuffin.
I'm mildly gifted at pondering things, but this looks like its the client having issues with a portion of decal and thats way outta my field.

I'm sure VI or the others will wander thru shortly now that the patch surge is over...

Did you check to make sure your .net is all up to date and happy?

if it was failing at the same addresses I would suggest making a MemTest x86 bootdisk and letting it run to make sure your ram is happy, but those locations are different.

 

-----signature-----

I run an AMD Phenom 9500 with 4gb of ram and a ATI Radeon HD 3400 256mb video and I go 5-7 days of botting and hunting w/o a problem (not switching toons). Below is my export. Maybe there is something in there that can help you fix your decal.

Decal (DenAgent.exe) version: 2.9.6.0

type, enabled, name, version, clsid
Plugins, 1, Decal Hotkey System, 2.9.6.0, {6B6B9FA8-37DE-4FA3-8C60-52BD6A2F9855}
Plugins, 0, Find It!, 2.9.7.0, {70DD5EF7-FE29-46C3-B0B3-4185327A35F1}
Plugins, 1, MiniMap, 1.1.0.104, {92C09018-E815-4C22-987B-8E553154146E}
Plugins, 0, Quest Timer, 2.4.0.2, {BB51962C-2EEE-4E67-A032-EEC1F11E66C8}
Plugins, 1, AgentZ, 1.0.0.0, {359E547B-5302-4134-80F2-3BE5C31EC828}
Plugins, 1, GoArrow, 1.2.0.1, {46BBF551-8578-4A59-B2FB-B5D9F4C719FA}
Plugins, 1, CastAway, 1.7.0.894, {4EB455CB-A2DA-44B6-90F2-09517A4B1476}
Plugins, 0, QuickCast, 1.0.06.1219, {67426B7F-58A5-4690-9EE3-7678C78FF525}
Plugins, 1, HWAC_Stats.dll, 1.4.0.4, {1D17D4A2-D62C-46B5-881E-A06EEF47D7DF}
Plugins, 0, Imp Inventory, 1.0.0.4, {006D1FA0-DDB5-42BC-9DAA-6D1DC696712E}
Plugins, 0, The Deep, 2.7.0.20, {E72999D8-9218-4FB8-A978-DF4320E64AF1}
Plugins, 1, Radar Add-on, 1.2.0.49, {CA23F8D7-7E71-423A-A928-BC5CDD8FBD96}
Plugins, 0, Alinco, 1.5.0.0, {4338186E-7AE8-4B9E-985D-98D692036EA8}
Plugins, 0, Virindi Follower, 0.0.0.4, {F99EC4CF-2C9B-4A8A-84A5-BAA7222F8A07}
Plugins, 0, Make It!, 5.9.7.0, {70DD2CC6-E638-4F43-9F15-C84A0FC7DC76}
Plugins, 1, LifeTank X, 11.9.0.8, {910C0F8E-827A-4E35-A980-50D57D0B1296}
Plugins, 1, SkunkVision, 1.0.0.7, {B8B64AFD-3D96-490D-A70B-CE962227148A}
Network Filters, 1, ACDC Core Filter, 7.2.2.0, {2DB1B641-4039-4D69-831A-79915EC266CE}
Network Filters, 1, Echo Filter 2, 2.9.6.0, {34239EAD-6317-4C40-A405-193BA5232DD8}
Network Filters, 1, Character Stats Filter, 2.9.6.0, {4540C969-08D1-46BF-97AD-6B19D3C10BEE}
Network Filters, 1, World Object Filter, 2.9.6.0, {53092D1B-F0B0-46FF-BF11-8F031EC9B137}
Network Filters, 1, Decal FileService, 2.9.6.0, {5E9B2FC3-C251-4589-8CE3-2BCA542B98B6}
Network Filters, 1, Identify Queue Filter, 2.9.6.0, {B0C05A9A-273D-4BC4-B7BA-E27CF94C8EF4}
Network Filters, 1, SpellFilter, 2.9.6.0, {C2D43735-BE7E-4829-AF73-F2E7E820EB16}
Network Filters, 1, Population_Filter.Filter, 0.0.0.1, {39EACE9F-1BF2-4E4F-BFBC-2FD9EB76A47B}
Network Filters, 1, Alinco X Filter, 1.5.0.0, {375A7C84-B4FD-49BB-B63D-15CCC004E979}
Network Filters, 1, Darkside Filter, 11.9.0.8, {F93FD48F-BA68-4BF5-A7B3-7908D1634331}
Services, 1, Decal .NET Lifetime Service, 2.9.6.0, {71A69713-6593-47EC-0001-0000000DECA1}
Services, 1, Decal Dat Service, 2.9.6.0, {37B083F0-276E-43AD-8D26-3F7449B519DC}
Services, 1, Decal Render Service, 2.9.6.0, {FB3C8286-88ED-4B4D-B413-94B40F346239}
Services, 1, Decal Inject Gateway Service, 2.9.6.0, {FEFE5CAB-10E4-404F-AD4D-184BCB506099}
Services, 1, Decal Input Service, 2.9.6.0, {B33307BA-706D-474A-80B9-70BB8D13EF3E}
Services, 1, Decal Networking Service, 2.9.6.0, {C8C406F8-BA2E-4964-8B04-FF38394A8E0E}
Services, 1, Decal D3DService, 2.9.6.0, {F0CC07A0-2C89-4FA4-9356-714665BC2F8B}
Surrogates, 1, Decal.Adapter Surrogate, 2.9.6.0, {71A69713-6593-47EC-0002-0000000DECA1}
Surrogates, 1, Prefilter Network Filter Surrogate, 2.9.6.0, {443D4A68-5422-4E0C-9460-973F8FBDB190}
Surrogates, 1, ActiveX Plugin Surrogate, 2.9.6.0, {7559F22F-C56F-4621-AE08-9C354D799D4B}
Surrogates, -1, Version 1 Plugin Surrogate, 2.9.6.0, {3D837F6E-B5CA-4604-885F-7AB45FCFA62A}
Input Actions, 1, Delay Input Action, 2.9.6.0, {324D76B8-D8C7-4A81-B867-E4E1F874E488}
Input Actions, 1, Mouse Move Input Action, 2.9.6.0, {57D18578-0BF0-4DE5-A0A9-E7CB531C0429}
Input Actions, 1, Restore Input Action, 2.9.6.0, {6EE2F682-7129-44BE-84B9-787BAE35EC1C}
Input Actions, 1, Polled Delay Input Action, 2.9.6.0, {762335B2-2274-4BB4-8B1F-F7286C949FF7}
Input Actions, 1, Typing Input Action, 2.9.6.0, {9CDCEEDC-F8AC-42D5-9A05-52B9346D00A4}
Input Actions, 1, Event Input Action, 2.9.6.0, {D6E4BD19-4900-4515-BCE2-A9EA4AAE2699}

Operating System:
Microsoft Windows XP Professional Service Pack 3 (Build 2600)

[Protected Storage Service] : Automatic

Decal Settings
: Timer (Default)
[Portal Path] : C:\Program Files\Turbine\Asheron's Call - Throne of Destiny\
[Launcher App] : ACDCClient.exe
: http://update.decaldev.com
[memlocs.xml] : 24536 bytes, Version 0.0.11.2169
[messages.xml] : 54173 bytes, Version 2008.04.15.1
[Video Memory] : 793509856

D3DX Libraries (Only d3dx9_30 is required)
[d3dx9_24.dll] : Installed (9.5.132.0)
[d3dx9_25.dll] : Installed (9.6.168.0)
[d3dx9_26.dll] : Installed (9.7.239.0)
[d3dx9_27.dll] : Installed (9.8.299.0)
[d3dx9_28.dll] : Installed (9.10.455.0)
[d3dx9_29.dll] : Installed (9.11.519.0)
[d3dx9_30.dll] : Installed (9.12.589.0)


---Support Libraries ---
Note: The following libraries are not necessary for Decal to function and are only provided to be of use to plugin developers.


.NET Frameworks
[v1.0.3705] (1.0 Final) : Not Installed
[v1.1.4322] (1.1 Final) : Installed (Service Pack 1)
[v2.0.50215] (2.0 Beta 2) : Not Installed
[v2.0.50727] (2.0 Final) : Installed (Service Pack 2)

C++ Libraries
[msvbvm60.dll] : Installed (6.0.98.2)
[atl70.dll] : Not Installed
[mfc70.dll] : Not Installed
[msvcr70.dll] : Not Installed
[msvcp70.dll] : Not Installed
[atl71.dll] : Not Installed
[mfc71.dll] : Installed (7.10.3077.0)
[msvcr71.dll] : Installed (7.10.3052.4)
[msvcp71.dll] : Installed (7.10.3077.0)

Microsoft XML Libraries
[msxml3.dll] : Installed (8.100.1048.0)
[msxml4.dll] : Installed (4.20.9870.0)


---Video Device Information---
[Device] : ATI Radeon HD 3400 Series
[Device Name] : \\.\DISPLAY1
[KeyDeviceID] : Enum\PCI\VEN_1002&DEV_95C5&SUBSYS_E400174B&REV_00
[KeyDeviceKey] : \Registry\Machine\System\CurrentControlSet\Control\Video\{52657CE6-6510-4617-9BBB-7C6AD61512CF}\0000
[Manufacturer] : ATI Technologies Inc.
[ChipType] : ATI Radeon Graphics Processor (0x95C5)
[DACType] : Internal DAC(400MHz)
[Revision] :
[MemoryLocalised] : 256.0 MB
[MemoryEnglish] : 256.0 MB
[DisplayLocalised] : 1280 x 1024 (32 bit) (75Hz)
[DisplayEnglish] : 1280 x 1024 (32 bit) (75Hz)
[DisplayWidth] : 1280
[DisplayHeight] : 1024
[DisplayBpp] : 32
[RefreshRate] : 75
[MonitorName] : Plug and Play Monitor
[MonitorMaxRes] : 1600,1200
[DriverName] : ati2dvag.dll
[DriverVersion] : 6.14.0010.6806
[DriverAttributes] : Final Retail
[DriverLangEnglish] : English
[DriverLangLocal] : English
[DriverDateEng] : 5/12/2008 10:54:44
[DriverDateLocal] : 5/12/2008 10:54:44
[DriverSize] : 305152
[MiniVdd] : ati2mtag.sys
[MiniVddDateEng] : 5/12/2008 11:30:02
[MiniVddDateLocal] : 5/12/2008 11:30:02
[MiniVddSize] : 3007488
[Vdd] : n/a
[RenderWindow] : Yes
: No
[Debug] : No
[Signed] : No
[SignValid] : No
: {D7B71EE2-D685-11CF-6D6E-0AC4A1C2CB35}
[DDIVer] : 9
[DDIVerEng] : 9 (or higher)
[DDIVerLocal] : 9 (or higher)
: 0
[VendorID] : 0x1002
[DeviceID] : 0x95C5
[SubSystemID] : 0xE400174B
[RevisionID] : 0x0000
[WHQL Level] : 0
[NoHardware] : 0
[DDAccelEnabled] : Yes
[3DAccelExists] : Yes
[3DAccelEnabled] : Yes
[AGP Enabled] : Yes
[AGPExists] : Yes
[AGPExistsValid] : Yes

 

-----signature-----

Got the same .net runtime error message, except for the fault address is different.


Faulting application acclient.exe, version 0.0.11.2169, stamp 498b7706, faulting module decalnet.dll, version 2.9.6.0, stamp 45744771, debug? 0, fault address 0x000338ed.

Also- Thank you very much for all the help, I really appreciate it!

You have to nail down which error is causing the actual crash, because like a house of cards, once the crash occurs, it will cause multiple other errors to occur, and those errors will clutter up the Event Viewer. In other words, only one error in there probably matters, the rest are subsequent errors and can be ignored.


I don't think you have bad memory, or a failing hard drive, graphics card, etc., because many people get those exact same 'types' of errors whenever acclient locks up. The different memory locations the error points to can be caused by the many different memory configurations and graphic adapters we all are using, and I think the actual location is moot.


I recently rebuilt many core parts of my system, including 2x 2GB paired memory, brand new HD and Power Supply. Kept were CPU, SLI graphics card and all ROM drives. I installed a brand new XP SP3 MSN final release on the new HD. First thing I loaded up were AC, Dual Client and Decal (with all my used plugins), so therefore there was absolutely no other bloat on the system, and it still crashed rather regularly. The one thing I can say, which again points to some sort of memory leaking issue is, when going from 2GB total memory to 4GB paired memory, it takes longer to crash most of the time now.


IMO, this just simply has to be some little routine embedded in either Decal or a plugin that is very slowly spinning out of control. So slow, it's nearly impossible to detect and therefore devs haven't even seen it, much less been able to fix it. This routine may only spiral out of control only when paired up with a system with a certain configuration (of which there seems to be a LOT of!). I just simply have learned to live with it... you crash, you login, go pick up your corpse and start over. I don't think anyone is going very deep into the core of Decal to do anything, so I don't expect this to ever go away.