Crash

[Logite]

Got this while playing. I also got an error while placing a unit in the editor yesterday. It didn't crash the game however, so I don't have a .crash file from that.

 

.crash: http://www.mediafire.com/?gyw2wognkzm

 

Error.log: http://www.mediafire.com/?y4kyduly2yv

 

errors.log: http://www.mediafire.com/?nvmw3dtyjdh

client-20100527-142418.miz.trk

DxDiag.txt

Edited May 27, 2010 by Logite

[EtherealN]

I notice that you have done nothing to help us diagnose the issue. ;)

 

http://forums.eagle.ru/showthread.php?t=44466

[Logite]

I notice that you have done nothing to help us diagnose the issue. ;)

 

http://forums.eagle.ru/showthread.php?t=44466

 

Ahem.

[Logite]

Bump

[Logite]

Any idea yet what's causing this?

[Logite]

Bump

[Logite]

I'd like to play my game now, please.

 

Bump

[Logite]

Is there anything I can do to help speed along a response to my issue?

[Panzertard]

Sorry, I cant really see why it crashed - or give you any advice.

All I could suggest is that you take a close look at your system to see if you have anything there that may assist in introducing the problem.

 

I've reattached your attachments for convenience - not too fond of mediafire.

 

# -------------- 20100527-214657 --------------

C:\Windows\system32\KERNELBASE.dll

# E06D7363 at 75E69617 01:00008617

#

# EAX = 0012F710

# EBX = 7C36BB92

 

Strange ending in the "Error.log" - dont know if it may be a hint:

Received stop gun fire (0) at 1342.815000

Received stop gun fire (1) at 1342.815000

Received stop gun fire (2) at 1342.815000

Received stop gun fire (3) at 1342.815000

proc_rearm_pylon : pylon = 6 , CLSID = {446E122B-8E9D-457e-AE8E-7AE88E3E566B}

proc_rearm_pylon : pylon = 7 , CLSID = {446E122B-8E9D-457e-AE8E-7AE88E3E566B}

proc_rearm_pylon : pylon = 8 , CLSID = {DA8F810A-EA40-4091-8127-CC2E026041E7}

proc_rearm_pylon : pylon = 9 , CLSID = {DA8F810A-EA40-4091-8127-CC2E026041E7}

proc_rearm_pylon : pylon = 10 , CLSID =

 

I'm also noticing 32bit / 3gb memory configuration:

It may be relevant for later investigations.

   Operating System: Windows 7 Professional 32-bit (6.1, Build 7600) (7600.win7_rtm.090713-1255)
          Language: English (Regional Setting: English)
System Manufacturer: NVIDIA
      System Model: NFORCE 680i LT SLI
              BIOS: Phoenix - AwardBIOS v6.00PG
         Processor: Intel(R) Core(TM)2 Duo CPU     E6850  @ 3.00GHz (2 CPUs), ~3.0GHz
            Memory: 3072MB RAM
Available OS Memory: 2814MB RAM
         Page File: 1949MB used, 3677MB available
       Windows Dir: C:\Windows

crashlogs.rar

Edited May 31, 2010 by Panzertard

[Nasty]

one idea come my mind if computer crash then take overclocked back factory settings and look temps, my computer start crash 1-2 times year cos fans are too dust and not clean. Thanks to dog and cat.

[Logite]

Thanks for the response. I really do hope the ED team decides to take a look at it; nothing ruins the atmosphere of a good game than lots of tiny tiny bugs.

 

First the crash, then my helmet mounted sight decided to disappear (i didn't modify any files, thank you.), THEN finding out you aren't able to edit the resolution of the avi record feature without it breaking the .ogv file the game puts out.

[EtherealN]

Kernelbase.dll faulting might be something far more serious than just a DCS error, actually. To me that doesn't sound like a "tiny bug", if it happened on my machine I'd be picking it apart right now to try find anything that might cause that to happen. (EDIT: Well, not literally pick it apart, necessarily, but you get what I mean I hope.)

 

On the mounted sight thing - did you change any settings for your DirectX, graphics driver, Catalyst AI, forcing AA or AF or anything such in the driver manager? Did the computer do anything like that for you (through windows update or anything like that)?

Edited June 1, 2010 by EtherealN

[Logite]

Kernelbase.dll faulting might be something far more serious than just a DCS error, actually. To me that doesn't sound like a "tiny bug", if it happened on my machine I'd be picking it apart right now to try find anything that might cause that to happen. (EDIT: Well, not literally pick it apart, necessarily, but you get what I mean I hope.)

 

On the mounted sight thing - did you change any settings for your DirectX, graphics driver, Catalyst AI, forcing AA or AF or anything such in the driver manager? Did the computer do anything like that for you (through windows update or anything like that)?

 

It's funny how far a simple response goes in making a guy feel cared about :wub:

 

It may be an issue with my system that's caused this crash - however the resolution bug is most definitely a game bug.

 

I'll do some more investigation on this and report back my findings. Either I changed something and it broke the HMS or I didn't - but reinstalling fixed it so I couldn't diagnose it now if I wanted to.