Skip to main content
tristans58324631
Participant
April 21, 2017
Answered

Bridge CC 2017 will not launch, "Faulting module path: C:\WINDOWS\SYSTEM32\d3d9.dll"

  • April 21, 2017
  • 1 reply
  • 1410 views

From the Event Viewer:

Faulting application name: Bridge.exe, version: 7.0.0.93, time stamp: 0x57f774d5

Faulting module name: d3d9.dll, version: 10.0.15063.0, time stamp: 0x631de416

Exception code: 0xc0000005

Fault offset: 0x000000000000fd0c

Faulting process id: 0x308c

Faulting application start time: 0x01d2baf0fbf1db58

Faulting application path: C:\Program Files\Adobe\Adobe Bridge CC 2017\Bridge.exe

Faulting module path: C:\WINDOWS\SYSTEM32\d3d9.dll

Report Id: 98b81b38-4dd0-4be5-9230-7692d8df2147

Faulting package full name:

Faulting package-relative application ID:

Uninstalled, deleted all files, reinstalled multiple times.

Did DXDIAG everything fine
Did sfc /scannow everything fine.
All other Adobe apps/directX programs are fine.
Thanks for your help.

    This topic has been closed for replies.
    Correct answer SonyXP

    Still does not work. Overall, I cannot recommend Adobe CC. I am now using XNViewMP: XnViewMP · Image viewer, Photo Resizer, Graphic Converter for Bridge-related task.


    I finally found the culprit on my end - it finally works.

    Can't blame the Adobe Devs on this one at all!

    As a hobby photographer and likewise passionate gamer (yeah, grew up with it. Never gets old ), I do have MSI Afterburner (former RivaTuner) alongside with RivaTuner Statistics Server installed. Especially latter one hooks up into the d3d9.dll file to poll data for it's on-screen overlay (fps, GPU and MEM clocks etc.).

    THIS is exactly what seems to collide when Bridge tries to initialize and access DirectX functions aswell.

    I can imagine, this will happen with any known tool that gathers system / GPU data on the fly by touching the DirectX API at the time you want to start Adobe Bridge.

    @Tristan - can you leave a reply, if you use a similar tool on your system? Maybe it works for you aswell! (fingers crossed)

    1 reply

    Sahil.Chawla
    Adobe Employee
    Adobe Employee
    May 1, 2017

    Hi tristans,

    As your Bridge is not launching due to D3D9.dll you can try the following steps and let us know if it works for you: -

    • Update Microsoft DirectX. To diagnose DirectX problems and to make sure you have the latest version, see Diagnosing basic problems with DirectX
    • Update your drivers GPU driver from manufacturer's website
    • Check if any updates are pending for your Windows.

    Regards,

    Sahil

    SonyXP
    Participant
    May 6, 2017

    Hello Sahil and Tristan,

    I do have the exact same problem, running Windows 10 Build 1703 (15063.250), aswell as the same DX Version, which is shipped with Windows 10 1703 (Creators Update).

    This leads to the conclusion, that there's no possibility to "update" the DirectX components, as the latest, downloadable runtime was released in 2011. Every newer, major Version, was distributed via the OS itself, from Windows 8 onwards.

    My GPU Driver is uptodate - using a Zotac 1070 GTX Amp!, that is ForceWare 382.05 WHQL.

    Reverting to an older driver did not help either, so I am having hopes the Adobe Devs have a look into this.

    Considering other web ressources, this problem started to occur with the release of the Creators Update of Windows 10.

    Thanks a lot in advance!

    SonyXP
    Participant
    May 12, 2017

    Any news on this one? I still can't use Bridge CC 2017 as described above