Crash Problems

[AustinN360]

Crash Report 1: DCS-20100410-191702.crash

# -------------- 20100410-191702 --------------

C:\Eagle Dynamics\LockOn Flaming Cliffs 2\bin\x86\stable\d3d9.dll

# C0000005 ACCESS_VIOLATION at 03786D1C 01:00005D1C

#

# EAX = 00000000

# EBX = 00000000

# ECX = 0018F6F8

# EDX = 00000137

# ESI = 0018F7B4

# EDI = 0E1808F0

# CS:EIP = 0023:03786D1C

# SS:ESP = 002B:0018F774 EBP = 0E1808F0

# DS = 002B ES = 002B FS = 0053 GS = 002B

# Flags = 00010246

03786D1C 0E1808F0 0001:00005D1C C:\Eagle Dynamics\LockOn Flaming Cliffs 2\bin\x86\stable\d3d9.dll Direct3DCreate9()+19CC

03786D1C 0018F850 0001:00005D1C C:\Eagle Dynamics\LockOn Flaming Cliffs 2\bin\x86\stable\d3d9.dll Direct3DCreate9()+19CC

This I know is related to the *.dll that comes with this mod: http://forums.eagle.ru/showthread.php?t=51954

 

Crash Report 2: DCS-20100411-001857.crash

 

# -------------- 20100411-001857 --------------

C:\Eagle Dynamics\LockOn Flaming Cliffs 2\bin\x86\stable\UserInterface.dll

# C0000005 ACCESS_VIOLATION at 01E88AB9 01:00037AB9

#

# EAX = 00000000

# EBX = 00000003

# ECX = 00000000

# EDX = 00000007

# ESI = 5C0344C0

# EDI = FFFFFFFF

# CS:EIP = 0023:01E88AB9

# SS:ESP = 002B:0018FAD8 EBP = 00000000

# DS = 002B ES = 002B FS = 0053 GS = 002B

# Flags = 00010246

01E88AB9 00000000 0001:00037AB9 C:\Eagle Dynamics\LockOn Flaming Cliffs 2\bin\x86\stable\UserInterface.dll ?changeSelectedItem@MultiColumnListBox@@QAEXHHH@Z()+79

 

I have no idea what caused this one. Any Ideas

[EtherealN]

Could you supply a DxDiag, direction on how can be found here: http://forums.eagle.ru/showthread.php?t=52089

 

D3D9 looks loike a graphics card or driver issue - the DxDiag file would help clarify that situation.

[AustinN360]

------------------

System Information

------------------

Time of this report: 4/11/2010, 11:23:16

Machine name: ROUTEMASTER

Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7600) (7600.win7_rtm.090713-1255)

Language: English (Regional Setting: English)

System Manufacturer: Gigabyte Technology Co., Ltd.

System Model: GA-MA770-UD3

BIOS: Award Modular BIOS v6.00PG

Processor: AMD Athlon 7750 Dual-Core Processor (2 CPUs), ~3.0GHz

Memory: 4096MB RAM

Available OS Memory: 4094MB RAM

Page File: 2061MB used, 14313MB available

Windows Dir: C:\Windows

DirectX Version: DirectX 11

DX Setup Parameters: Not found

User DPI Setting: Using System DPI

System DPI Setting: 96 DPI (100 percent)

DWM DPI Scaling: Disabled

DxDiag Version: 6.01.7600.16385 64bit Unicode

 

------------

DxDiag.txt

[Panzertard]

Uhm, yes - mods can have such effect.

You can't tell if any of your problems is related to that replacement unfortunately.

So to eliminitate crashes, test without mods (on a fresh working FC2).

If crashes no longer occurs then you can hint the maker of the mod about the issues with his mod.

 

Didnt notice anything out of the ordonary in your DxDiag.

But also, if you notice a pattern to when the crashes happen - MP, SP, hosting, launching a weapon etc - that would certainly be helpful. :)

Edited April 11, 2010 by Panzertard

[jazzviper]

Hi there,this is very similar to my problem,my posts are on page 4 now,Problems running FC2,I could not find a solution.all drivers are good,tried many things to fix.BS runs like a dream,can't run this at all. thanx

[AustinN360]

The first crash was due to a mixture of the "Atmospheric Bluemore" mod and the Teamspeak 3 overlay thats built into Playclaw and this is now fixed as I have removed the mod.

 

The second crash was last night on the 104th Server. Cause unknown.

 

These are the only 2 crashes I have had.

 

My Graphics card specs:

 

My System Windows 7 Home Premium x64:

[HiJack]

The first crash was due to a mixture of the "Atmospheric Bluemore" mod ...

 

I also had terrible fps with the "Atmospheric Bluemore" mod and uninstalled it. I have also had an 100% increase in Windows 7 hung ups since starting using FC2 :( I've desided to go for a new install of FC2, again, and not change anything. No mods no nothing, just FC2 untill I've finished all the campaigns for all airplanes. After finishing the campaigns I can start modding :D but for now the Mod's is unfinished I belive.

 

®

[PoleCat]

Uhm, yes - mods can have such effect.

You can't tell if any of your problems is related to that replacement unfortunately.

So to eliminitate crashes, test without mods (on a fresh working FC2).

If crashes no longer occurs then you can hint the maker of the mod about the issues with his mod.

 

This is the larger point that people should catch on to. It only adds to the confusion when people post crashes or hangs on modded installs. Unless you have tested on a clean unmodded install of FC2 and can reproduce the error it is unlikely the correct thing to do is to report it here until you have done so IMHO. :music_whistling:

 

Out

[HiJack]

How to do this I guess is:

 

1. Install FC2 to an folder like "C:\FC2" but dont start the SIM when install is finished

2. Make a copy of "C:\FC2" and rename it to "C:\FC2-ORG"

3. Make a new copy of the C:\FC2-ORG" and name it "C:\FC2-MOD"

 

Use the ORG folder to compare files and the MOD folder for mods installed with MODMAN.

 

®

[RvEYoda]

I also get Userinterface.dll crash without such mods, it has nothing to do with

the graphics mod. However the d3d..dll crash definitely is very likely related to that

mod there.

 

AS has had the same crash (Userinterface.dll) quite frequently

[X-man]

I also get Userinterface.dll crash without such mods, it has nothing to do with

the graphics mod. However the d3d..dll crash definitely is very likely related to that

mod there.

 

AS has had the same crash (Userinterface.dll) quite frequently

 

So did I a few days ago! Three times in a row while on the 104th server. (Userinterface.dll)

[RvEYoda]

So did I a few days ago! Three times in a row while on the 104th server. (Userinterface.dll)

 

Thanks for reporting!

More people getting the userinterface.dll bug please write here!

 

Did you remember what you did when it happened?

we are trying to find out the exact cause of the bug.

Edited April 12, 2010 by =RvE=Yoda

[Panzertard]

6DOF mod - can it cause such issues? It's a server-side mod, transferred to the client.

Any other server-side mods btw?

Chat-box mods? (I seem to remember alot of the 104th gents were asking about the chatbox previously).

[AustinN360]

6DOF mod - can it cause such issues? It's a server-side mod, transferred to the client.

Any other server-side mods btw?

Chat-box mods? (I seem to remember alot of the 104th gents were asking about the chatbox previously).

 

I know we are using Servman which is a server side mod. as to anything else I'm not too sure.

Edited April 12, 2010 by Panzertard

[Panzertard]

I know we are using Servman which is a server side mod. as to anything else I'm not too sure.

 

oops, sorry bud - I pressed the wrong button when I replied, hence your post was edited by yours truly here ;)

 

As I was saying:

I've been flying over at the 104th for shorter periods, but not seen the crash myself.

But I might believe the chatbox-size mod may be a contributing factor - so it would be nice to hear if anyone without the chatbox mod got the crash too.

Anyone?

Edited April 12, 2010 by Panzertard

[AustinN360]

oops, sorry bud - I pressed the wrong button when I replied, hence your post was edited by yours truly here ;)

 

As I was saying:

I've been flying over at the 104th for shorter periods, but not seen the crash myself.

But I might believe the chatbox-size mod may be a contributing factor - so it would be nice to hear if anyone without the chatbox mod got the crash too.

Anyone?

 

Just to clarify. I thought the Chatbox mod was set Client-side.

 

(that is if we are talking about the same thing: http://forums.eagle.ru/showthread.php?t=51748

 

In order to change how big the chat log is (while the chat box is not active) you need to edit the following file chat-log.res located in /FUI/Resources/Multiplayer/

 

\dialog
\begin
   \tag{-1}
   \coord{0, 18, 1023, [color=Red]60[/color]}
       \musthavecursor{0}
       \acceptmouse{0}
       \topmost
       \layer{900}
\end

\multicolumnlistbox
\begin
   \tag{2}
   \coord{20, 0, 1003, [color=Red]60[/color]}
     \defaultitem{Multiplayer/def_list_box_item.res}
   \columnswidth{200, 803}
   \rowsnum{10}
   \readonly{1}
   \visiblescrollbar{0}
\end

You need to edit the \coord{x, y, w, h} lines. The last parameter is responsible for height, each line of text is 20px as such setting this parameter to 60 (highlighted in RED) will only leave 3 lines of text max while the chat window is CLOSED.

 

To edit how the chat window appears when it is open you need to edit chat-say.res, but it is a little more complex as there are way more coordinates to mess with.

 

Credits for this go to Distiler and Acedy (http://forums.eagle.ru/showpost.php?p=676501&postcount=52).

 

Thanks and enjoy.

[Panzertard]

Yes, the chatbox is client side - we agree on that, I was still thinking since it's a userinterface crash - and the chatbox may be such an object, it may be related to just this.

I should have been more clear about that. :)

Edited April 12, 2010 by Panzertard
my english ****

[Distiler]

I've played lots of hours there and I've never crashed and I'm using chatbox-size mod, F-15 by Gys, Simmod A-10a Skypat's package and 3GO Su-27 (separated, not the 3in1 pack).

 

Route, you're using nvidia 197.25 instead of latest "final" release 197.13, might be because that? btw I also have a 9600gt

Edited April 12, 2010 by Distiler

[RvEYoda]

I know we are using Servman which is a server side mod. as to anything else I'm not too sure.

 

The UserInterface.dll crash has happened for us without any 6dof mod I belive.

Also without/before servman

[Panzertard]

Hm, okai - so back to chasing ghosts.

[FA_Crazy-Canuck]

Crash Log

 

For what its worth heres my crash log. Flying on 104th Server

 

# -------------- 20100414-021358 --------------

C:\Program Files\Eagle Dynamics\LockOn Flaming Cliffs 2\bin\x86\stable\UserInterface.dll

# C0000005 ACCESS_VIOLATION at 021B8AB9 01:00037AB9

#

# EAX = 00000000

# EBX = FFFFFFFF

# ECX = 00000000

# EDX = 528DF0C0

# ESI = 50BF2008

# EDI = FFFFFFFF

# CS:EIP = 001B:021B8AB9

# SS:ESP = 0023:0012FB10 EBP = 00000000

# DS = 0023 ES = 0023 FS = 003B GS = 0000

# Flags = 00210246

021B8AB9 00000000 0001:00037AB9 C:\Program Files\Eagle Dynamics\LockOn Flaming Cliffs 2\bin\x86

\stable\UserInterface.dll ?changeSelectedItem@MultiColumnListBox@@QAEXHHH@Z()+79

 

Diaxdiag Attached :thumbup:

DxDiag.txt

[Raimir]

For what its worth heres my crash log. Flying on 104th Server

 

# -------------- 20100414-021358 --------------

C:\Program Files\Eagle Dynamics\LockOn Flaming Cliffs 2\bin\x86\stable\UserInterface.dll

# C0000005 ACCESS_VIOLATION at 021B8AB9 01:00037AB9

#

# EAX = 00000000

# EBX = FFFFFFFF

# ECX = 00000000

# EDX = 528DF0C0

# ESI = 50BF2008

# EDI = FFFFFFFF

# CS:EIP = 001B:021B8AB9

# SS:ESP = 0023:0012FB10 EBP = 00000000

# DS = 0023 ES = 0023 FS = 003B GS = 0000

# Flags = 00210246

021B8AB9 00000000 0001:00037AB9 C:\Program Files\Eagle Dynamics\LockOn Flaming Cliffs 2\bin\x86

\stable\UserInterface.dll ?changeSelectedItem@MultiColumnListBox@@QAEXHHH@Z()+79

 

Diaxdiag Attached :thumbup:

 

HI,

today it happened twice to me on 104th server with same *.crash file output i mean problem with UserInterface.dll. I don't use any mod, my OS is WinXP SP2 32bit. And i realized it crashed when i fly quite long (at least half an hour) and enable radar by button combination on my saitex x52 (that was same on both crashes). But i was able of course enable radar earlier during fly.

Until now it never crashed on our squad server or when i tested it offline.

I will try to test it more and figure out some more details.

[71st_Mastiff]

http://www.youtube.com/watch?v=KxGwUCcowqo

 

Hm, okai - so back to chasing ghosts.