Frequent BEX64 / d3dx9_43.dll / d3d9.dll crashes

[davem]

Hi all,

Sorry if this has been posted before but I've searched for fixes and tried pretty much everything suggested on forums over the past 2 years of threads from the DEP change to deleting the config and letting it rebuild itself and letting dxdiag run its course but they errors are still happening.

 

I let NVidia update drivers to 347.88 for my 660Ti but have to admit that I'm not sure if the errors were happening before this or not and or if they were happening before the recent updates on Steam.

 

Apart from scrapping the whole lot and starting again, does anyone have any suggestions or know of any fixes that are being worked on for these errors?

 

Thanks!

[SkateZilla]

Please archive/zip and attach relavent logs and dxdiag readout for sys specs for the devs to analyze.

[davem]

A quick flight before work got this BEX crash after about half an hour.

All relevant logs attached.

I'll try and create more this evening.

BEX crash 240315 am.zip

[davem]

And a d3dx9 crash from this evening incl logs

d3dx9 crash pm.rar

[AtaliaA1]

Have U considered adding the stand alone DCS. ver. of the Simulator to your PC?

 

Last time I saw this error it was due to the video drivers but that was an AMD Graphics card. You are using only the dedicated Graphics right?

 

The BIOS date in your PC is from 2012. I would suggest checking to see if there is an updated ver. available. Although I can't seem to find it there was an older gentlemen from the African Coast who had the error also, and the update of his BIOS fixed it for him.

 

Another users had to add 13.9 dll to the default DCS folder to rid him of this error the one with the Ati card had to use Atiumdag dll along with the Atiumd64 dll in addition.

 

I recall them because I downloaded and added them to my back up drive for later investigation. It wasn't needed as the next iteration of DCS. got rid of the crashes and few others had this error.

 

Insure U have the latest DX9 C++ Redistributed files for the Steam ver. U are running (if U don't want stand alone ver. from DCS.) get them here http://www.microsoft.com/en-ca/download/details.aspx?id=6812

 

Will look again later to see if I can find the posts. I am sure they were well over a yr. ago though.

Edited March 25, 2015 by AtaliaA1
While U R at it

[davem]

Thanks for the hints and suggestions.

 

I'm using a dedicated Gfx card an NVidia 660Ti

 

Just going to run through the SDK you linked to and have also got the latest BIOS version downloaded for the MoBo.

 

I think I've got the standalone files somewhere and if not I'll get them overnight and try it to see if this cures it by not going thru Steam.

 

Thx for your helps so far! :thumbup:

[davem]

Thanks for all the help.

I've installed DCS and the bits I have as a standalone and without trying it suspect that the standalone installation has put some .dll files or suchlike somewhere where they should have been in the first place as I have just spent a decent hour on a Mav training mission oin the A10 without failure, a mission which would crash without fail after about 10 minutes or less when I first reported the problem.

 

Many thanks! :beer:

Dave.

[AtaliaA1]

Thanks for all the help.

I've installed DCS and the bits I have as a standalone and without trying it suspect that the standalone installation has put some .dll files or suchlike somewhere where they should have been in the first place as I have just spent a decent hour on a Mav training mission oin the A10 without failure, a mission which would crash without fail after about 10 minutes or less when I first reported the problem.

 

Many thanks! :beer:

Dave.

 

If U don't mind, would U run the Steam Ver. with the new files from Microsoft to see how it goes. Other users with this issue may find it helpful to know if it fixes this error. It is Up to U of course.

[davem]

Hi,

 

I did run the Steam version when I trialled it without any apparent issue - I've not yet run the standalone version.

 

Here's what I did...

 

I downloaded the DirectX SDK files from the link you kindly supplied: http://www.microsoft.com/en-ca/download/details.aspx?id=6812 and installed them.

 

When it got to the installation of the C++ redist files, it told me that I had a later version running (10.0.4???) so uninstalled these and then re-ran the installer which installed 10.0.30319 for both x86 and x64.

 

Unfortunately without then trying to run DCS through Steam to see if this alone had cured the issues, I also installed the standalone version of DCS, A10 & FC3 which of course updates the various .dll files & DirectX files so I have to admit that I sadly cannot put a confirmation as to which course of action cured the problem(s).

 

I have only played it once since I did this but it ran for a good 2 hours without issue. I've got a couple of hours free this evening so will give it a go again via Steam and see if it has cured it.

[davem]

OK, I typed too soon... :furious:

 

Log for the d3d9 crash attached here - was after about an hour on the Steam version during a guns training mission on the A10.

d3d9 crash.zip

[davem]

...and just for good measure a Bex / Stackhash crash on the same guns / LAU A10 training mission in pretty much the same place (juast approaching target)

Logs attached.

bex stackhash 2703.zip

[AtaliaA1]

If I remember correctly a stack hash is a matter of the files in the program being truncated, among other things.

 

Have you done the steam check yet? Right click DCS in the User interface and click Properties U can check the program there. It uses a ver. of Hash checking.

[Wolf Rider]

Try disabling all the Start Up items...

 

 

 

http://support.microsoft.com/en-us/kb/929135

Edited March 28, 2015 by Wolf Rider

[davem]

I've done the 'validating Steam files' for it once (didn't find anything) but am running again just now.

 

Will also try the clean boot method as suggested and report back.

 

Thanks!

D.

[davem]

Validated OK, Clean boot done and then crashed in the same training A10 guns Mission with a Stackhash (075e?) error.

 

Going to try it standalone now to see if I can recreate the error.

[davem]

Ugh....

 

So... it crashes on both versions of the game (latest was a d3dx9_43.dll ver 9.29.952.3111 crash in standalone mode).

 

However, most of the testing has been in training missions, most recently the same A10 guns / rockets training msision so I'll give something like instant action a go if I can survive that long!

 

Log attached which does involve terrain / texture errors in it at the bottom which TBH I don't understand!

d3dx9 crash 2803.zip

[davem]

Ok, here goes - last set of error logs (A10A crash in instant action this time) that I'll bother with - getting to be a waste of time this as it almost seems to be a hardware / software thing rather than a Steam issue...?

 

I have had the same crash with the F15C so presume it's not just a corrupt A10 file.

 

I suppose I could delete the whole lot and just start afresh?

 

 

:helpsmilie: :chair:

d3dx9 sat am.zip

Edited March 28, 2015 by davem

[BitMaster]

Does the system otherwise run stable ?

 

Do you own any other hardware stressing game that runs for hours without problems ?

 

My advice, before you put more time into finding a sw problem, check your hardware !

 

There are many good test suites around to do that, some of them are:

 

prime95 ( CPU and RAM stress test )

MSI Afterburner Suite ( works on all GPUs )

memtestx86 ( bootable linux image, found for example on any ubuntu CD or standalone, best tool to find RAM flaws, let it run for at least 30min, bad errors come in less than 5 minutes though, best run for 24h to validate your RAM in case of question )

 

If you own a Haswell Intel CPU you better NOT use prime95 as some say it may harm its overvoltage circuit etc... better safe than sorry.

( If the CPU burns with prime95, it burns with scientific workloads too, as prime95 is a misused scientific prime finder. Intel, what didcha do ? LoL )

 

 

Bit

[davem]

Hi Bit and thanks for the info.

 

Right - I think I could be in the mire here with this system... More errors but first answers to your questions.

 

I've had it almost 2 years now and it's not used to run very high demand things - FSX and F1 2013 / 2014 probably the main things.

 

I had an issue with Assassins Creed 4 which was found to be caused by a dodgy sound driver but apart from that it's been fine.

 

It's an i5-3570K at 3.4 OC to 4.4 by Scan and the rest of the details are on the dxdiag I posted at the top of the thread.

 

I was about to say that Prime95 was running in the background but while typing this first time around the screen flashed and it too crashed with an error message at the same time as I got a "there was a problem with Internet Explorer and it had to restart". Not sure if one caused the other or not...

 

Just re-running it now.

 

Aaaand here we go again... 2 MORE errors...This time something new??

 

1)

Problem signature:

Problem Event Name: BEX64

Application Name: Explorer.EXE

Application Version: 6.1.7601.17567

Application Timestamp: 4d672ee4

Fault Module Name: Explorer.EXE

Fault Module Version: 6.1.7601.17567

Fault Module Timestamp: 4d672ee4

Exception Offset: 00000000000fffd8

Exception Code: c0000005

Exception Data: 0000000000000008

OS Version: 6.1.7601.2.1.0.768.3

Locale ID: 2057

Additional Information 1: 65c8

Additional Information 2: 65c8231404e170463ed6c47e8fc2fa32

Additional Information 3: 661f

Additional Information 4: 661f31afd84f76336b57bede1a0cb137

Read our privacy statement online:

http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:

C:\Windows\system32\en-US\erofflps.txt

 

 

2)

Problem signature:

Problem Event Name: APPCRASH

Application Name: prime95.exe

Application Version: 28.5.1.0

Application Timestamp: 5387ede6

Fault Module Name: prime95.exe

Fault Module Version: 28.5.1.0

Fault Module Timestamp: 5387ede6

Exception Code: c000001d

Exception Offset: 00000000019b8b7e

OS Version: 6.1.7601.2.1.0.768.3

Locale ID: 2057

Additional Information 1: bc14

Additional Information 2: bc14b5e06eae8f2480d5041e36f427fc

Additional Information 3: 3be4

Additional Information 4: 3be41263d3ccb9c9ccd34c2ff88af1eb

Read our privacy statement online:

http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:

C:\Windows\system32\en-US\erofflps.txt

 

Maybe I'd better just go and stick to nice easy to run low-stress games!? :doh:

[davem]

OK, Prime95 results...

 

Ver 26.6 gave no errors.

Ver 28.5 gave the following...

[sat Mar 28 13:32:17 2015]

FATAL ERROR: Rounding was 0.5, expected less than 0.4 Hardware failure detected (CPU 4), consult stress.txt file.

 

I've run Coretemp and managed to get 1 core to touch 90 degrees momentarily with Prime95 running along with lots of other things but generally temps are a lot lower and around the 70 degree mark or lower.

 

So far this morning also 2 BSODs and a thought towards whether my sound card / drivers could be at fault - ASUS Xonar DG. Had issues with it before and had to turn GX mode off so might try this one as I'm finding little or no info on various forum searches above what I've done already.

[Wolf Rider]

Something which has helped others, when running an oc system is the revert the system back to stock speeds

 

 

Also, what is your system's DEP setting?

(Control Panel/ System/ Advanced system settings/ Advanced(tab)/ Performance- settings/ Data Execution Prevention

 

another to consider, if not already mentioned, could be to open the Mission in the Mission Editor and re-save it. (some older Missions get a little wonky when being run on a later version DCS)

[davem]

Thanks, this reversion was discussed last night with someone who knows far more than I do about these things, then to flash the BIOS with the new version and try again. When I ran them through the BIOS settings they thought the voltage applied (1.330V) was a lot higher than it should have been for a 4.4Ghz oc/ from 3.4.

 

DEP setting was one of the first changes I made to the settings everyone suggested on my first bits of research for these crashes (now allows everything).

 

I think that Prime95 stress testing shows it's something to do with the hardware and or settings as trying to do things while under 100% load gives me these crashes and BSODs as well reporting "Page fault in non paged area" which with 0x00000050 error code. A quick research into that points towards memory fault but memtest86 has run and found no errors.

 

I have noticed a large increase in the number of reports of overclocked i5-3570K crashes with dates that are relatively recent (March 2015). What are the chances that a Windows update could have screwed around with something making it a generic thing rather than DCS-centric??

 

I have turned the clock down to 4.3Ghz and may well drop to 4.2 to try to drop the voltage down and see if it becomes more stable.

 

 

...or I could just stick to FSX :surrender: :smilewink:

[AtaliaA1]

Can U switch out hardware with a friend?

 

It helps with the "Process of elimination thing.

 

I am thinking the GPU or the RAM. I know U ran memtest, it doesn't always catch everything. and the "None Page Area" sounds like it. This is also a HDD error as the "Instruction" sent through RAM gets Processed by the HDD when needed, i.e. Page File/Cache. Getting the BSOD in IE. is also a clue to potential HDD or RAM.

[davem]

I wish I could do! Anyone I know of with a silimar rig is miles and miles away and I know nobody close by with a gaming-type rig.

 

If it's RAM error it'll be cheaper than any other fault at least.

 

I'm going to try the return-to-stock settings and see if it restores stability and if so flash the BIOS with the more up to date one (about 2 years newer) then see if I can o/c it again myself to a stable level.

 

I'll keep you posted and thanks for all the info.

[davem]

Perhaps interesting update for those of you who know what causes what in terms of hardware stress...

 

I ran the same problematic missions in "low" details mode and then "medium" detail mode with no problems whatsoever and coretemp never got about 56 degrees.

 

I turned down the draw radius and got rid of clutter and trees and will try again with the texture and settings on high to see if it is struggling for any reason with these, but surely if it were simply settings that are too high, the game should run slower rather than crash??

 

As an aside, an interesting discovery...

 

When I zoom in close to the A10 on the training missions, the skin changes when I get close! At distance it has tailcode OS with a yellow check tip to the vert stabs and a Black Horse on the fuselage and no teeth on the nose, when you zoom closer the tailcode changes to FT with a blue / white lightning 74th flash and teeth on the nose....:huh:

 

Just me??

Edited March 30, 2015 by davem