Sign in to follow this  
JasonW

Someone please point me in a direction...

Recommended Posts

Im not far from pulling my hair out over here. Clean install on windows 10 with P3D, I was having this same problem with windows 7 also. The sim crashes almost every time, I cant even complete a flight anymore. Heres my appcrashview log, I have this same error over and over. Thanks for any advice.

 

 

Version=1
EventType=BEX
EventTime=130846002210226855
ReportType=2
Consent=1
UploadTime=130846002210622230
ReportIdentifier=27ad48c6-47b2-11e5-8099-bc5ff4ad5b8c
IntegratorReportIdentifier=90aefbbc-e635-4f8e-a8a6-39e07bcaab11
WOW64=1
NsAppName=rundll32.exe
Response.BucketId=3f1eaf9f08e7118548fa6ac1e566f843
Response.BucketTable=5
Response.LegacyBucketId=115992808413
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=rundll32.exe
Sig[1].Name=Application Version
Sig[1].Value=10.0.10240.16384
Sig[2].Name=Application Timestamp
Sig[2].Value=559f3c5a
Sig[3].Name=Fault Module Name
Sig[3].Value=StackHash_bdcb
Sig[4].Name=Fault Module Version
Sig[4].Value=0.0.0.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=00000000
Sig[6].Name=Exception Offset
Sig[6].Value=PCH_C9_FROM_ntdll+0x0006919C
Sig[7].Name=Exception Code
Sig[7].Value=c0000005
Sig[8].Name=Exception Data
Sig[8].Value=00000008
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.10240.2.0.0.768.101
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=bdcb
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=bdcb33e65a9843796b7ec31cc25bda3b
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=689d
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=689d12abf00dd47c453b5e1a156c0fa3
UI[2]=C:\WINDOWS\SysWOW64\rundll32.exe
UI[3]=Windows host process (Rundll32) has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\WINDOWS\SysWOW64\rundll32.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\SYSTEM32\KERNEL32.DLL
LoadedModule[3]=C:\WINDOWS\SYSTEM32\KERNELBASE.dll
LoadedModule[4]=C:\WINDOWS\system32\apphelp.dll
LoadedModule[5]=C:\WINDOWS\AppPatch\AcLayers.DLL
LoadedModule[6]=C:\WINDOWS\SYSTEM32\msvcrt.dll
LoadedModule[7]=C:\WINDOWS\SYSTEM32\USER32.dll
LoadedModule[8]=C:\WINDOWS\SYSTEM32\GDI32.dll
LoadedModule[9]=C:\WINDOWS\SYSTEM32\SHELL32.dll
LoadedModule[10]=C:\WINDOWS\SYSTEM32\windows.storage.dll
LoadedModule[11]=C:\WINDOWS\SYSTEM32\combase.dll
LoadedModule[12]=C:\WINDOWS\SYSTEM32\RPCRT4.dll
LoadedModule[13]=C:\WINDOWS\SYSTEM32\SspiCli.dll
LoadedModule[14]=C:\WINDOWS\SYSTEM32\CRYPTBASE.dll
LoadedModule[15]=C:\WINDOWS\SYSTEM32\bcryptPrimitives.dll
LoadedModule[16]=C:\WINDOWS\SYSTEM32\sechost.dll
LoadedModule[17]=C:\WINDOWS\SYSTEM32\advapi32.dll
LoadedModule[18]=C:\WINDOWS\SYSTEM32\shlwapi.dll
LoadedModule[19]=C:\WINDOWS\SYSTEM32\kernel.appcore.dll
LoadedModule[20]=C:\WINDOWS\SYSTEM32\shcore.dll
LoadedModule[21]=C:\WINDOWS\SYSTEM32\powrprof.dll
LoadedModule[22]=C:\WINDOWS\SYSTEM32\profapi.dll
LoadedModule[23]=C:\WINDOWS\SYSTEM32\OLEAUT32.dll
LoadedModule[24]=C:\WINDOWS\SYSTEM32\SETUPAPI.dll
LoadedModule[25]=C:\WINDOWS\SYSTEM32\CFGMGR32.dll
LoadedModule[26]=C:\WINDOWS\SYSTEM32\MPR.dll
LoadedModule[27]=C:\WINDOWS\SYSTEM32\sfc.dll
LoadedModule[28]=C:\WINDOWS\SYSTEM32\WINSPOOL.DRV
LoadedModule[29]=C:\WINDOWS\SYSTEM32\bcrypt.dll
LoadedModule[30]=C:\WINDOWS\SYSTEM32\sfc_os.DLL
LoadedModule[31]=C:\WINDOWS\SYSTEM32\IMM32.DLL
LoadedModule[32]=C:\WINDOWS\SYSTEM32\MSCTF.dll
LoadedModule[33]=C:\WINDOWS\SYSTEM32\imagehlp.dll
LoadedModule[34]=C:\Lockheed Martin\Prepar3D v2\MigTool.dll
LoadedModule[35]=C:\WINDOWS\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[36]=C:\WINDOWS\SYSTEM32\WS2_32.dll
LoadedModule[37]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9185_none_d0905a48442809b8\MSVCR80.dll
LoadedModule[38]=C:\WINDOWS\SYSTEM32\NSI.dll
LoadedModule[39]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9185_none_d0905a48442809b8\MSVCP80.dll
LoadedModule[40]=C:\WINDOWS\SYSTEM32\SHFOLDER.dll
LoadedModule[41]=C:\WINDOWS\system32\uxtheme.dll
LoadedModule[42]=C:\WINDOWS\system32\dwmapi.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=BEX
AppName=Windows host process (Rundll32)
AppPath=C:\WINDOWS\SysWOW64\rundll32.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=9BC1615E374B9E035089F4675B616686

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Are you getting an OOM? 

Nope. It just crashes to the desktop over and over.

Share this post


Link to post
Share on other sites

 


Sig[6].Value=PCH_C9_FROM_ntdll+0x0006919C
Sig[7].Name=Exception Code
Sig[7].Value=c0000005
Sig[8].Name=Exception Data
Sig[8].Value=00000008

 

BEX can be a result of several issues, but based on the info above, I'd start with your RAM and disable any OC and default your RAM memory profile to whatever manufacturer suggests.

 

If you have 4 RAM sticks, try just using 2 RAM sticks for diagnostics and swap the memory sticks around (shift one out each time) if you still have the BEX error.

 

Cheers, Rob.

Share this post


Link to post
Share on other sites

What's this?

 

LoadedModule[34]=C:\Lockheed Martin\Prepar3D v2\MigTool.dll

Share this post


Link to post
Share on other sites

 

 


LoadedModule[34]=C:\Lockheed Martin\Prepar3D v2\MigTool.dll

 

Flightsim Estonia Migration Tool.

 

OP:  not arguing with Rob's suggestion (I don't have any of my own) but before opening your computer up and messing around, keep your current settings and simply run a stress test and see if it fails. If you have an Intel processor, start with Intel Extreme Tuning Utility (it's free). Install it and run both the CPU and memory stress tests. If either or both of those fail then you may be on the right path.

 

But again, doing this first simply prevents you from having to rummage around in your comp case...

Share this post


Link to post
Share on other sites

 

 


Flightsim Estonia Migration Tool.

 

Does that need to be loaded while his sim is running?  I always shut it down unless I'm installing something.

Share this post


Link to post
Share on other sites

 

 


Does that need to be loaded while his sim is running?

 

Not really. In one of their later builds they started loading that driver in everyone's DLL file. I didn't understand the need for it so I removed it from the DLL file and yet it still works fine. That being said, it shouldn't be causing a BEX error. Just checked the Flightsim Estonia support board and didn't see anyone complaining of BEX errors so...

Share this post


Link to post
Share on other sites

Flightsim Estonia Migration Tool.

 

OP:  not arguing with Rob's suggestion (I don't have any of my own) but before opening your computer up and messing around, keep your current settings and simply run a stress test and see if it fails. If you have an Intel processor, start with Intel Extreme Tuning Utility (it's free). Install it and run both the CPU and memory stress tests. If either or both of those fail then you may be on the right path.

 

But again, doing this first simply prevents you from having to rummage around in your comp case...

Memory and Processor both passed 5 min tests.

 

BEX can be a result of several issues, but based on the info above, I'd start with your RAM and disable any OC and default your RAM memory profile to whatever manufacturer suggests.

 

If you have 4 RAM sticks, try just using 2 RAM sticks for diagnostics and swap the memory sticks around (shift one out each time) if you still have the BEX error.

 

Cheers, Rob.

I only have two sticks of 8 gig ram (Corsair Vengeance 16GB (2x8GB) DDR3 2133 MHz) t I havent tried to OC the ram and even have the correct timings and ghz set in my bios.  My processor (i7 3770k) is overclocked but it seems to pass any stress test and prime 95 runs. My motherboard is a ASROCK Z77 Extreme 4

 

Does that need to be loaded while his sim is running?  I always shut it down unless I'm installing something.

Thats the first I have noticed it running and its odd because I havent used it in a while. Latest build for final 2.5 P3D.

 

Windows memory test didnt find anything either..  :fool:

Share this post


Link to post
Share on other sites

We have a pretty similar setup. Can you paste the entire contents of both your EXE and DLL files here?

 

Also, 5 minutes for a stress test is nothing. You'll want to do at least a couple of hours for each. I know it sounds like a lot but trust me...

Share this post


Link to post
Share on other sites

My processor (i7 3770k) is overclocked but it seems to pass any stress test and prime 95 runs. My motherboard is a ASROCK Z77 Extreme 4

 

The basic diagnostics idea is to remove as many variables as possible ... Overclocking is one of those variables.  You don't need to open the case (in your case only two sticks of RAM so you have no choice other than to use them both), just boot into your EFI/BIOS and make sure you save your OC profile (assume your EFI/BIOS allows several OC profiles).  Now set all your EFI/BIOS parameters to a CPU spec, be aware that "Auto" sometimes does NOT mean "Default" and save that as a "Base Profile".

 

Agree, you need to stress test for at least 1 hour ... I usually stress test for about 5 hours to 24 hours, pending on how critical the PC is to my needs.  Flight Sim PC's aren't mission critical so I don't stress test them as long.  I use RealBench for my stress testing as some Prime95 tests can actually cause CPU damage on high OCs.

 

You've eliminated the OS as a variable because the same issue happens in both Win7 and Win10.

 

Cheers, Rob.

Share this post


Link to post
Share on other sites

We have a pretty similar setup. Can you paste the entire contents of both your EXE and DLL files here?

 

Also, 5 minutes for a stress test is nothing. You'll want to do at least a couple of hours for each. I know it sounds like a lot but trust me...

EXE
 
<?xml version="1.0"?>
<SimBase.Document Type="Launch" version="1,0">
  <Descr>Launch</Descr>
  <Filename>exe.xml</Filename>
  <Disabled>False</Disabled>
  <Launch.ManualLoad>False</Launch.ManualLoad>
  <Launch.Addon>
    <Name>as_btstrp_config_manager</Name>
    <Disabled>False</Disabled>
    <Path>as_srv\as_btstrp_config_manager.exe</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Name>UT2</Name>
    <Path>C:\Lockheed Martin\Prepar3D v2\Flight One Software\Ultimate Traffic 2\UT2Services.exe</Path>
    <NewConsole>True</NewConsole>
  </Launch.Addon>
</SimBase.Document>
 
 
 
DLL
<?xml version="1.0"?>
<SimBase.Document Type="Launch" version="1,0">
  <Descr>Launch</Descr>
  <Filename>dll.xml</Filename>
  <Disabled>False</Disabled>
  <Launch.ManualLoad>False</Launch.ManualLoad>
  <Launch.Addon>
    <Name>Migration Tool Plugin</Name>
    <Path>MigTool.dll</Path>
    <DllStartName>module_init</DllStartName>
    <DllStopName>module_deinit</DllStopName>
  </Launch.Addon>
  <Launch.Addon>
    <Name>ObjectFlow_KMRY_P3D</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>C:\Lockheed Martin\Prepar3D v2\ORBX\FTX_NA\FTX_AA_KMRY\scenery\ObjectFlow_KMRY_P3D.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>ObjectFlow</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>C:\Lockheed Martin\Prepar3D v2\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow_P3D.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>as_connect</Name>
    <Disabled>False</Disabled>
    <Path>as_srv\as_btstrp.dll</Path>
  </Launch.Addon>
</SimBase.Document>

Did you try a clean install of P3D2?

Yea, both OS and P3D are fresh installs.

The basic diagnostics idea is to remove as many variables as possible ... Overclocking is one of those variables.  You don't need to open the case (in your case only two sticks of RAM so you have no choice other than to use them both), just boot into your EFI/BIOS and make sure you save your OC profile (assume your EFI/BIOS allows several OC profiles).  Now set all your EFI/BIOS parameters to a CPU spec, be aware that "Auto" sometimes does NOT mean "Default" and save that as a "Base Profile".

 

Agree, you need to stress test for at least 1 hour ... I usually stress test for about 5 hours to 24 hours, pending on how critical the PC is to my needs.  Flight Sim PC's aren't mission critical so I don't stress test them as long.  I use RealBench for my stress testing as some Prime95 tests can actually cause CPU damage on high OCs.

 

You've eliminated the OS as a variable because the same issue happens in both Win7 and Win10.

 

Cheers, Rob.

So if I set my efi to default it should save my OC profiles right? I will download RealBench and give it a try, thanks

Share this post


Link to post
Share on other sites

So if I set my efi to default it should save my OC profiles right? I will download RealBench and give it a try, thanks

 

That is not true. We have the same MoBo: you need to go the "OC Tweaker" tab and scroll aaallll the way down and then save a profile. So, save everything as-is right now before doing anything else. To then set everything to default, click on the "Exit" tab and then hit "Load UEFI Default"

 

Keep in mind that in doing so, you may reset which video card is being used (you may wind up activating the one integrated on the CPU) and you'll also reset plenty of non-overclock settings that could cause some headaches (USB settings, peripheral stuff, etc.).

 

Also, your EXE and DLL files look pretty good and simple. The only thing that I don't have experience with running is UT2 (I use MyTraffic). Last I checked UT2 wasn't compatible. Has that been working fine previously? Or did you start having BEX issues after installing it? May seem like a dumb couple of questions but I'd like to rule out a simple software conflict before messing with hardware...

Share this post


Link to post
Share on other sites

If the problem keeps happening in rundll32 that would make me think that it's a dll...a particular dll that's causing the issue.  With my system, if it's an overclock issue I get all kinds of weird behavior...sudden shutdowns, freezes, crashes.  I'd look to eliminate as many DLLs as possible before you start to see if doing so results in a stable sim.

 

Here's a simple guide I found that might help give you more info on the rundll32 problem and how to go about working on it.  Check your event logs to see if there are any pre-crash clues in there.

 

http://www.howtogeek.com/howto/windows-vista/what-is-rundll32exe-and-why-is-it-running/

 

Also, think about what you've installed that was the same as your prebuild system.  Antivirus?

Share this post


Link to post
Share on other sites

So I loaded all of the defaults on my motherboard today and its still doing the same thing over and over.

 

 

 

 

 

I dont understand what has happened, this machine used to run 2.3 without a hiccup. I moved and the computer sat in the closet for a few months until I could get around to hooking everything back up. The only thing I have changed is im using 2.5 and Im running DSR instead of Nvidia inspector.


Alos passed an hour stress test.

Share this post


Link to post
Share on other sites

heres a new one

 

Version=1
EventType=BEX
EventTime=130846693025440524
ReportType=2
Consent=1
UploadTime=130846693025910972
ReportIdentifier=ff7825a9-4852-11e5-80a4-bc5ff4ad5b8c
IntegratorReportIdentifier=be4f68cd-0150-4052-8077-80a1b972420a
WOW64=1
NsAppName=Prepar3D.exe
Response.BucketId=fc5af97c479fa2ebfd754aa951543e0d
Response.BucketTable=5
Response.LegacyBucketId

Share this post


Link to post
Share on other sites

 

 


UI[2]=C:\WINDOWS\SysWOW64\rundll32.exe
UI[3]=Windows host process (Rundll32) has stopped working

 

Gregg is on the right track and, since you enabled DSR, this may be the problem.  If you check your system configuration - http://www.tenuser.com/spec/msc.htm you can disable all of the items under the Startup tab safely.  One or two of them should be from Nvidia/rundll32.  Try disabling them and see if this fixes the problem.

 

Best regards,

Share this post


Link to post
Share on other sites

Gregg is on the right track and, since you enabled DSR, this may be the problem.  If you check your system configuration - http://www.tenuser.com/spec/msc.htm you can disable all of the items under the Startup tab safely.  One or two of them should be from Nvidia/rundll32.  Try disabling them and see if this fixes the problem.

 

Best regards,

Thanks for the suggestion but it didnt help.

 

 

this is from event viewer of the latest crash

 

 

Log Name:      Application
Source:        Application Error
Date:          8/21/2015 10:24:12 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-AVL1BCS
Description:
Faulting application name: Prepar3D.exe, version: 2.5.12946.0, time stamp: 0x555f2e54
Faulting module name: MSVCP100.dll, version: 10.0.40219.325, time stamp: 0x4df2be41
Exception code: 0xc0000005
Fault offset: 0x00033744
Faulting process id: 0x1074
Faulting application start time: 0x01d0dc80abc76984
Faulting application path: C:\Lockheed Martin\Prepar3D v2\Prepar3D.exe
Faulting module path: C:\WINDOWS\SYSTEM32\MSVCP100.dll
Report Id: f89dad94-d4ef-4554-b1ab-2ea321c5dbf4
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-08-22T02:24:12.000000000Z" />
    <EventRecordID>1898</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-AVL1BCS</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>2.5.12946.0</Data>
    <Data>555f2e54</Data>
    <Data>MSVCP100.dll</Data>
    <Data>10.0.40219.325</Data>
    <Data>4df2be41</Data>
    <Data>c0000005</Data>
    <Data>00033744</Data>
    <Data>1074</Data>
    <Data>01d0dc80abc76984</Data>
    <Data>C:\Lockheed Martin\Prepar3D v2\Prepar3D.exe</Data>
    <Data>C:\WINDOWS\SYSTEM32\MSVCP100.dll</Data>
    <Data>f89dad94-d4ef-4554-b1ab-2ea321c5dbf4</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Share this post


Link to post
Share on other sites

Now the faulting module is part of Microsoft Visual C++ 2010.  Microsoft Visual programs are used by developers to make sure their product is installed properly.  Other than that, there's nothing in the codes that anyone can use to find the reason for your crashes.  Best solution is to completely uninstall P3D and reinstall.  When you reinstall, make sure you reinstall with Administrative rights.  Make sure User Access Controls (UAC) is disabled, make sure any anti-virus program is not running in the background.  It should not be running while you are using P3D.  Once reinstalled, go to the P3D.exe in the main P3D folder and right click it.  Select Properties.  Look at the Compatibility tab.  Make sure there are no tick marks under the compatibility tab except at the bottom where it states, Run this application as an Administrator.  Go Fly!

 

Best regards,

Share this post


Link to post
Share on other sites

Finally figured out what was going on. Turns out something in the bios settings had gotten out of whack. When I loaded the defaults on the motherboard it was telling me that I was back to stock 3.whatever ghz but when I loaded the stress test in the intel test tool, it was still going well over 4 ghz. I ended up doing a hard reset on the motherboard and have successfully made two flights from KRDD to KMRY without and crashes. Im a happy flyer again!!!! Thanks so much to those of you who posted here you all got me to looking in the right places. I guess now ill have to take another crash course in overclocking to get back over 4ghz. 

 

 

Thanks again!!!!

Share this post


Link to post
Share on other sites

This is why is is very difficult to find a solution for most crashes as everyone has a different configuration, within FSX, P3D, FSX-SE, with Windows, and with the Motherboard configuration.  Hence the reason for the AVSIM CTD Guide suggesting that everyone must investigate their own situation.  The guide provides some guidance and probable solutions to many repeated crashes but there's a lot of things that happen in "The Naked City" and it is very difficult to pinpoint the cause for everyone (we do suggest returning the BIOS settings to the optimal default settings though). 

 

Glad you were able to find your problem and fix it and appreciate your response telling us how you got it fixed.  It could help many other members in the future.

 

Best regards,

Share this post


Link to post
Share on other sites

I have been a flight simmer for about 30 years and have been using the AVSIM forums, longer than I can remember, for advice and solutions. It truly amazes me the time members take to try and solve the problems other members are having with their flight sim setups. I read though this thread and I'm humbled by the patience exhibited in trying to find "the fix" for Jason. I do not post that often but in this case its extremely warranted. Greg, Gregg, Rob and Jim you did something good here ... THANKS!

 

Sheldon

Share this post


Link to post
Share on other sites

 

 


I loaded the defaults on the motherboard it was telling me that I was back to stock 3.whatever ghz but when I loaded the stress test in the intel test tool, it was still going well over 4 ghz. I ended up doing a hard reset on the motherboard and have successfully made two flights from KRDD to KMRY without and crashes. Im a happy flyer again!!!!

 

Glad you got it sorted, BEX errors are usually related to OC issues (be it CPU or RAM).  Your event log message was a very good clue and the fact you got the same error in Win7 and in Win10 was another important clue to check hardware.

 

Cheers, Rob.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this