Runtime Error

[McVittees]

I seem to keep getting runtime errors (screen shot attached with crash and error logs). Today I've had two in the last two hours and on saturday I had a couple CTDs during MP. On both of today's occasions I was heads down in the cockpit when the game froze.

 

I'm using CAT 10.10 drivers on a HD5850.

 

Any suggestions that could help troubleshoot these crashes would be greatly appreciated.

:cry:

 

More info from Windows Event log:

Faulting application name: simulator.exe, version: 1.2.1.0, time stamp: 0x4bed01e6

Faulting module name: atiumdva.dll, version: 8.14.10.279, time stamp: 0x4ca294f1

Exception code: 0xc0000005

Fault offset: 0x00001535

Faulting process id: 0x1754

Faulting application start time: 0x01cb7b43ca6bd71c

Faulting application path: C:\Program Files\Eagle Dynamics\Ka-50\bin\x86\stable\simulator.exe

Faulting module path: C:\Windows\system32\atiumdva.dll

Report Id: 6c615d2a-e73c-11df-9553-002215971e74

DxDiag.txt

Error.log.txt

DCS-20101103-111947.crash.txt

Edited November 3, 2010 by McVittees
where's my attachments???

[McVittees]

Just got another runtime error after seeing if using earlier Ati driver would help. Looking at the windows event viewer I see if refers to 'protect.dll'. Is this a Starforce issue?

 

Faulting application name: simulator.exe, version: 1.2.1.0, time stamp: 0x4bed01e6

Faulting module name: protect.dll, version: 5.70.13.2, time stamp: 0x4bed03ee

Exception code: 0x40000015

Fault offset: 0x00e4ab94

Faulting process id: 0x1658

Faulting application start time: 0x01cb7b5b32fdfb42

Faulting application path: C:\Program Files\Eagle Dynamics\Ka-50\bin\x86\stable\simulator.exe

Faulting module path: C:\Program Files\Eagle Dynamics\Ka-50\bin\x86\stable\protect.dll

Report Id: 359abff2-e754-11df-9878-002215971e74

[Panzertard]

Nothing that I can point the finger at, except the overclocking.

- Try to run a few days without O/C. Yes, other software may work perfectly, but all kinds of software is unique.

Some days of non-O/C MP just to establish if you still have the crashes.

 

- Mods? Have you tried with a clean install of DCS with no mods? Not only uninstalled with modman - but a separate DCS install which never been modded.

 

The first problem mentions C++ libraries and a ati-dll. The second reffers to protect.dll - also using C++ libraries.

Perhaps you can use Windows Update to find some updates for the C++ libraries you have installed no your computer?

 

A final note - some of the MP servers may offer *huge* scenarios, you might be seeing a memory issue of DCS, where there's no more memory left.

- This usually happens on 'large scale scenarios' and when flying for an hour or two on such servers.

Try to fly some smaller missions / scenarios to verify it's not one of these situations.

[KeyCat]

A final note - some of the MP servers may offer *huge* scenarios, you might be seeing a memory issue of DCS, where there's no more memory left.

- This usually happens on 'large scale scenarios' and when flying for an hour or two on such servers.

Try to fly some smaller missions / scenarios to verify it's not one of these situations.

 

It's not limited to MP only it happens in SP as well. I don't know if/how this will work on other machines/OS'es but here is how I can reproduce the CTD 100% of time in both SP and MP on my machine.

 

If it is the memory handling bug/issue you see maybe it can help you rule things out...

 

Repro steps for memory handling issue in FC2 1.2.1 and DCS:BS 1.0.2

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

 

1. Run FC2/BS in fullscreen mode (haven't had time to try this in windowed, I do all my flying in fullscreen since I gain FPS compared to windowed).

 

2. The higher graphic settings I have the more RAM is used and the faster the CTD/freeze happens. Also in MP the total number of players connected to the server also matters, more players = earlier CTD/freeze.

 

3 a. I usually join a server on-line since MP is my main interest and where I test but this also happens in SP it just takes longer to reach the limit where ther CTD happens.

 

3 b. or start any SP mission and jump into a plane or Ka-50.

 

4. Start up the plane/heli but don't take off (not necessary to start up but it probably use up some more RAM).

 

5. Press F11 to get to the free cam view.

 

6. If you test in SP you can use time accelerate (LCTRL-Z) to speed things up, then fly around at low altitude with the mouse in the 3D world long enough (for me ~15-30 min depending on time accelerate and what objects/terrain I fly over) and when RAM usage of simulator.exe fills up and reaches ~1.35 GB (since I do not see the TaskManager all the time this value could be somewhat wrong but it's in the ballpark at least, setting up a counter in Performance Monitor would be better but I leave that to ED and it's testers) I will either CTD (or freeze, see note below).

 

Notes to above

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

* When not using the /3GB swith in Boot.ini (XP Pro) FC2/BS CTD with various stuff written to the *.crash file (for examples see previous posts in this thread http://forums.eagle.ru/showthread.php?t=54162).

 

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect /noexecute=OptOut

 

When using the /3GB (with or without the /USERVA=xxxx parameter) computer freezes without any error messages at all and require a hard restet. Beware that MS warns for other potential issues when enabling the /3GB switch and as far as I understand it is for specific uses not generic ones.

 

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect /noexecute=OptOut /3GB

 

Also check out the following threads for more info on same/similar issues, IIRC I had similar references to protect.dll in my Event viewer...

 

In DCS: BS section - CTD's in MP after 1.0.2 patch

 

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

 

In FC2 section - Runtime error and crash

 

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

 

/KC

Edited November 4, 2010 by KeyCat

[Panzertard]

O/C is the most important factor to eliminate - it can contribute to other factors and make everything much worse. Please turn it off.

[Mustang]

Over the weekend i performed a reinstall of my OS, and after getting FC2.0 and DCS up and running i encountered yet again the dreaded C++ Runtime error CTD's.

 

After looking back through this thread and stumbling across this thread http://www.cadforum.cz/cadforum_en/qaID.asp?tip=5551 i successfully managed to nail my crashes.

 

So, all i had to do was enter this command via a DOS window (start/run/cmd.exe) and reboot.

 

bcdedit /set IncreaseUserVa 3072

[McVittees]

Thanks for the replies - as suggested Panzertard I'll cut the OC'g out of the equation first.

[McVittees]

Over the weekend i performed a reinstall of my OS, and after getting FC2.0 and DCS up and running i encountered yet again the dreaded C++ Runtime error CTD's.

 

After looking back through this thread and stumbling across this thread http://www.cadforum.cz/cadforum_en/qaID.asp?tip=5551 i successfully managed to nail my crashes.

 

So, all i had to do was enter this command via a DOS window (start/run/cmd.exe) and reboot.

 

bcdedit /set IncreaseUserVa 3072

 

Are you running 32bit or 64bit OS?

[Mustang]

Are you running 32bit or 64bit OS?

 

Windows 7 32bit with 2GB of RAM.

 

It seems i was getting the crash at the 1.2gb resource usage mark, the BCDedit seems to help it cross that line with no problems.

Edited November 4, 2010 by Mustang

[McVittees]

Just got another crash - runtime message didn't appear but I was kicked out of game back to debrief screen (which like the other occasions has had no data in it). Anyway, noticed something interesting in event viewer: 875 instances of Driver sfdrv01.sys has been blocked from loading. Not all today and plenty when I haven't even being playing DCS BS! I assume sfdrv01.sys is a starforce driver.

 

Windows 7 32bit with 2GB of RAM.

 

It seems i was getting the crash at the 1.2gb resource usage mark, the BCDedit seems to help it cross that line with no problems.

 

I'll give it a go and see if it helps (Thank you)...but not tonight :(

=================================================

Further update:

 

Digging into administrative events I discovered a load of these warnings:

 

The application (StarForce Protection, from vendor StarForce) has the following problem: The installed StarForce Protection driver is not compatible with this version of Windows and will be disabled. Applications that require this driver will not function properly without a patch.

 

Looking at the starforce site I seem to have the latest version of the starforce protect.dll. Oh boy I'm beginning to feel royally screwed. Could I have installed a dodgey copy of windows??!!

Edited November 4, 2010 by McVittees

[Panzertard]

IMO sfdrv01.sys is the old starforce - pre FC2/DCS.

Perhaps it's been latent in the background causing you issues?

If you don't play lomac / FC1 anymore, you can uninstall those. Altough I'm not sure about the old SF removal, how to do it.

Perhaps these 3 steps: http://www.gamehourz.com/steps-removing-StarForce-drivers-ftopict136689.html

 

The Starforce in DCS isnt installing any drivers / loading drivers to protect DCS. It's no longer the "bad SF" everyone was so worried about.

AFAIK it's rather a encryption scheme used to encrypt / decrypt (some of) the files on the fly when you start DCS.

Edited November 4, 2010 by Panzertard

[igormk]

I also had the same problem (and got used to Alt+Tab every 10minutes), but after trying Mustang's suggestion - it works.

 

I just had 2 hours of continuous flight with no error, so I suggest you try it your self.

 

Mustang, thank you mate for this!!! :thumbup:

 

 

PS one of my friends with the same symptoms also confirms it works.

[Mustang]

I also had the same problem (and got used to Alt+Tab every 10minutes), but after trying Mustang's suggestion - it works.

 

I just had 2 hours of continuous flight with no error, so I suggest you try it your self.

 

Mustang, thank you mate for this!!! :thumbup:

 

 

PS one of my friends with the same symptoms also confirms it works.

 

Yes, this really does seem like the definative fix for many of us who have been suffering with the runtime errors, i'm very happy that it worked for you and your squadmates (good long sortie tonight too, nice flying :thumbup:)

[Panzertard]

I really hope with 64bit will see an end to the memory related variant, sometime in the future when BS is patched to the correct levels.

[KeyCat]

Good catch Mustang and glad it worked for you guys and lets hope it works for McVittees as well...

 

Looking back at my notes I took back in May/June I don't see I tested with that specific value (3072) as parameter to /USERVA in Windows XP when using the /3G option.

 

I did test with quite a few other values with no success and IIRC there was a limit that when crossed I couldn't boot into Windows XP. Anyway, I will give it another try someday and see what happens.

 

@Mustang: How far have you gone? Can you fill up the RAM usage of "simulator.exe" way beyond 1.2 GB (should be easy to test by flying around in F11 view with high time accelereration)? Wierd that for you the limit is/was 1.2 GB and for me on XP it's ~1.35 GB, anyone have ideas why (besides we are using different versions of Windows)?

 

@Igormk: I assume you use Vista or Windows 7 32-bit, correct?

 

/KC

Edited November 6, 2010 by KeyCat

[igormk]

@Igormk: I assume you use Vista or Windows 7 32-bit, correct?

 

/KC

Windows 7 32-bit, correct.

[McVittees]

Well, played few short multiplayer missions on friday night and then a long single player mission tonight and so far no crashes, so I'm feeling much more positive than I was last week!:) I haven't used that memory switch (yet) so it's the de-installation of FC2 and the removal of the old starforce drivers that seems to have done the trick (hopefully I'm not speaking to soon).

 

Big thanks to everyone who replied - much appreciated. Sometimes it is easy to think your post is gonna sink without a trace. Anyway, lets see how things go...I still have a disappearing cockpit bug that require alt tabbing in and out of the game to cure but lets save that one for another day!:joystick:

[Mustang]

I still have a disappearing cockpit bug that require alt tabbing in and out of the game to cure but lets save that one for another day!:joystick:

 

That sounds like the early signs of the memory running out prior to the runtime error crash, i've witnessed it myself many times in the past :)

[McVittees]

That sounds like the early signs of the memory running out prior to the runtime error crash, i've witnessed it myself many times in the past :)

 

Right. Memory switch time it is then!