Share via

Experiencing many App Crashes - Bex Errors on multiple apps

Anonymous
2013-04-22T08:30:11+00:00

I have a windows 7 (service pack 1), 64-bit machine. i7 with 8gb ram. I have recently been experiencing a large number of App Crashes which all appear to associate the problem with a BEX Error. Examples below:

Problem signature:

Problem Event Name: BEX

Application Name: wlstartup.exe

Application Version: 16.4.3505.912

Application Timestamp: 50510e61

Fault Module Name: StackHash_0a9e

Fault Module Version: 0.0.0.0

Fault Module Timestamp: 00000000

Exception Offset: 060807f8

Exception Code: c0000005

Exception Data: 00000008

OS Version: 6.1.7601.2.1.0.768.3

Locale ID: 2057

Additional Information 1: 0a9e

Additional Information 2: 0a9e372d3b4ad19135b953a78882e789

Additional Information 3: 0a9e

Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

I first noticed this when I was attempting to launch any of the windows live essential apps, but since then it has occurred on numerous other apps such as IE10, mouse pointer etc etc.

I have tried restoring my machine to an early point in time when everything was working but to no avail. I have also started the machine with all startup apps and services stopped other than the standard windows services, but the problem still occurs before I invoke any service or apps. I have noticed on the web people advising to turn DEP off for the affected apps, however in the case of windows live essentials, it doesn't appear to allow this. I feel that I must have a more significant underlying problem that needs rectifying.

Can anyone help / advise on the next course of action I should try.

Many Thanks

Glen

Windows for home | Previous Windows versions | Apps

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

3 answers

Sort by: Most helpful
  1. Anonymous
    2013-04-28T01:57:56+00:00

    Hi Glen,

    Since the issue persists, you may try the following steps and check if it helps.

    Method 1:

    Follow the steps to change the DEP settings and check if it helps.

    a) Click Start

    b) Right click on Computer, and select Properties.

    c) Click on Advanced System Settings, click the Advanced Tab

    d) In the Performance section, click Settings

    e) Select the "Data Execution Protection" tab, and then click the 'Turn on DEP for all programs and services except those I select' option.

    f) **** Click the Add button, and then browse to C:\Windows\System32\dllhost.exe

    g) Click open, click OK on the warning message.

    h) **** Click Apply/OK.

    Check if the issue still persists.

    For further information, refer to the article:

    Change Data Execution Prevention settings

    Data Execution Prevention: frequently asked questions

    Method 2:

    If that doesn’t help try creating a new User account and check if the issue occurs.

    Refer the article to create new user account:

    Create a user account

    Step 2:

    If you are not facing the issue in new user account, then issue is related to a corrupt user account.

    You may follow the steps from the article to repair the corrupt user profile:

    Fix a corrupted user profile

    Hope the information helps.

    6 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2013-04-26T09:28:19+00:00

    Hi

    I'm not sure when the error first started as I noticed on live essentials about 4 or 5 weeks ago but as it was only happening on a singlke app at the time, to be honest I was not that concerned. Over recent weeks it has got much worse affecting many apps.

    The main updates to my machine over this time were standard windows updates and I loaded a game - Sniper Elite, which uses Steam. The latter has since been removed.

    I followed your advice to remove IE10 and found the following:

    IE10 successfully removed and made IE9 available. IE9 also crashes with the following error:

    Problem signature:

    Problem Event Name: BEX

    Application Name: iexplore.exe

    Application Version: 9.0.8112.16470

    Application Timestamp: 510c8801

    Fault Module Name: StackHash_3597

    Fault Module Version: 0.0.0.0

    Fault Module Timestamp: 00000000

    Exception Offset: 08bead10

    Exception Code: c0000005

    Exception Data: 00000008

    OS Version: 6.1.7601.2.1.0.768.3

    Locale ID: 2057

    Additional Information 1: 3597

    Additional Information 2: 3597c31010c86d2765350bffe3a6632f

    Additional Information 3: c5d5

    Additional Information 4: c5d58da11334106ace5de1eb17ed0f93

    What is intersting is that I have noticed that the above error is displayed when I attempt to launch IE 9 or 10 32bit version. When I launch the IE10 64BIT version, I do not get the error.

    I know I have a 64 bit machine but 32bit apps have always worked fine including Essentials and IE 9 or 10.

    Appreciate you help so far.

    Glen

    One additonal point I have noticed is that I have also on a couple of occasions over the last 5 weeks received an error stating ' Com Surrogate has stopped working'. This just tends to appear at random points, not necessarilly when I launch an app.

    0 comments No comments
  3. Anonymous
    2013-04-23T07:01:53+00:00

    Hi Glen,

    Do you remember making any changes to the computer prior to the issue?

    Since the issues persists after performing System restore and disabling third party services and startup items, let’s try the following steps and check if it helps.

    If you are using Internet Explorer 10, then as a diagnostic method, you may try to uninstall IE 10, revert to IE9 and check if the BEX error occurs.

    a. Close all programs.

    b. Click **Start,**and then click Control Panel.

    c. Under Programs, Click Uninstall a Program.

    d. In the Task pane, click View installed updates.

    e. In the list of installed updates, double-click Windows Internet Explorer 10.

    f. In the Uninstall an update dialog box, click Yes.

    g. Restart the computer and check if it helps.

    Hope the information helps.

    0 comments No comments