Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Bridge 2018 Crashing

Contributor ,
Nov 03, 2017 Nov 03, 2017

I recently upgraded to Lightroom Classic CC 2018, Photoshop CC 2018, and Bridge CC 2018. So far I have had no problems with LR or PS.

But Bridge is randomly crashing a couple of times a day. The last few times were when simply restoring the app from the taskbar. It comes up but immediately throws up a Crash Report dialog. It's frozen and can only be dismissed from the task manager. A crash report was submitted. I have followed all the suggestions in the Adobe troubleshooting guide for Bridge which did fix crashes I was experiencing on startup. But the random crashes every few hours are still happening.

This was an upgrade from Bridge 2017 which worked well and was stable.

I am running a Win 7 64bit OS fully updated. Anyone else seeing this behavior?

1.2K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , Nov 06, 2017 Nov 06, 2017

Thank you for the information, appreciate your patience & support.

I would suggest you to follow these steps and check if it helps:

Method 1:
Try booting the computer in safe mode and check if the same issue occurs:
http://windows.microsoft.com/en-US/windows7/Start-your-computer-in-safe-mode

Method 2:
Try performing clean boot and check if it helps:
http://support.microsoft.com/kb/929135

NOTE: After you have finished troubleshooting, make sure you put back the computer to normal startup mode as suggeste

...
Translate
Adobe Employee ,
Nov 03, 2017 Nov 03, 2017

Hi JLCKJC,

Could you please let us know what happens if you launch and test bridge in a new user account with Administrator privilages?

Also, could you check the event viewer crash logs and share them with us? Check this link for steps: Using Windows Event Viewer to debug crashes - CodeProject

Regards,

Sahil

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Contributor ,
Nov 03, 2017 Nov 03, 2017

I tried your suggestion to launch and test Bridge in a new user account with Administrator privileges. The instability was still there that resulted in the crashes I reported.

Here is a copy of the of the crash report from my system's Event Viewer while running as an Administrator:

Log Name:      Application

Source:        Application Hang

Date:          11/2/2017 6:05:21 PM

Event ID:      1002

Task Category: (101)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      1204

Description:

The program Bridge.exe version 8.0.0.262 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.

Process ID: 2370

Start Time: 01d35435cb74b0fd

Termination Time: 0

Application Path: C:\Program Files\Adobe\Adobe Bridge CC 2018\Bridge.exe

Report Id:

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Application Hang" />

    <EventID Qualifiers="0">1002</EventID>

    <Level>2</Level>

    <Task>101</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2017-11-03T01:05:21.000000000Z" />

    <EventRecordID>93527</EventRecordID>

    <Channel>Application</Channel>

    <Computer>1204</Computer>

    <Security />

  </System>

  <EventData>

    <Data>Bridge.exe</Data>

    <Data>8.0.0.262</Data>

    <Data>2370</Data>

    <Data>01d35435cb74b0fd</Data>

    <Data>0</Data>

    <Data>C:\Program Files\Adobe\Adobe Bridge CC 2018\Bridge.exe</Data>

    <Data>

    </Data>

    <Binary>430072006F00730073002D007400680072006500610064000000430072006F00730073002D00700072006F00630065007300730000000000</Binary>

  </EventData>

</Event>

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

There was no additional information in the system's Action Center log.

Hope this helps with your analysis.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Nov 03, 2017 Nov 03, 2017

Please check this link to see how to find out the faulty module and let us know what is the Faulty module you are seeing. Using Windows Event Viewer to debug crashes - CodeProject

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Contributor ,
Nov 04, 2017 Nov 04, 2017

The crash report I posted earlier is from the Event Viewer but it does not contain all the information shown in the article you suggested I read. The most notable comments are:

Description: The program Bridge.exe version 8.0.0.262 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel. (Note: There was no additional information in the Action Center.)

Application Path: C:\Program Files\Adobe\Adobe Bridge CC 2018\Bridge.exe

Event: 1002, Application Hang

The only time I see Crash Reports with the additional information shown in the article (faulting module, etc) is when the Crash is reported as an Event 1000.

So, for the moment there's not much more I can tell you other than Bridge CC 2018 seems unstable on this machine whereas earlier versions were solid and stable. The program is choking on something and hanging as a result.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Nov 06, 2017 Nov 06, 2017
LATEST

Thank you for the information, appreciate your patience & support.

I would suggest you to follow these steps and check if it helps:

Method 1:
Try booting the computer in safe mode and check if the same issue occurs:
http://windows.microsoft.com/en-US/windows7/Start-your-computer-in-safe-mode

Method 2:
Try performing clean boot and check if it helps:
http://support.microsoft.com/kb/929135

NOTE: After you have finished troubleshooting, make sure you put back the computer to normal startup mode as suggested in step 7 from the above KB article.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines