Bridge CS6 Release: Crashes on startup

  • 5
  • Problem
  • Updated 6 years ago
  • Acknowledged
Fresh install of commercial release of CS6. Bridge (64-bit) crashes EVERY time I attempt to start it, *unless* I run it as admin.

Here's an example crash:

Log Name: Application
Source: Application Error
Date: 09/05/2012 17:13:26
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: MOO
Description:
Faulting application name: Bridge.exe, version: 5.0.0.399, time stamp: 0x4f5ec28e
Faulting module name: MMXCore.8BX_unloaded, version: 0.0.0.0, time stamp: 0x4f308138
Exception code: 0xc0000005
Fault offset: 0x000007feec3a4c10
Faulting process id: 0xc7c
Faulting application start time: 0x01cd2dfea885fd0d
Faulting application path: C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\Bridge.exe
Faulting module path: MMXCore.8BX
Report Id: e7c1012f-99f1-11e1-a2e4-f46d04942533
Event Xml:

1000
2
100
0x80000000000000

16996
Application
MOO

Bridge.exe
5.0.0.399
4f5ec28e
MMXCore.8BX_unloaded
0.0.0.0
4f308138
c0000005
000007feec3a4c10
c7c
01cd2dfea885fd0d
C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\Bridge.exe
MMXCore.8BX
e7c1012f-99f1-11e1-a2e4-f46d04942533

Different modules seem to crash, too. Often it's: Standard MultiPlugin.8BF
that crashes.

Not good...
Photo of Mark Harding

Mark Harding

  • 7 Posts
  • 0 Reply Likes
  • anxious

Posted 6 years ago

  • 5
Photo of Brett N

Brett N, Official Rep

  • 2258 Posts
  • 114 Reply Likes
If it takes running as admin to launch without a crash, it tells us that there are restricted permissions somewhere on your system. Some file that Bridge needs to access from the OS is denied.

Try testing an a brand new user account and see if it is user specific or a OS wide issue.
Photo of Mark Harding

Mark Harding

  • 7 Posts
  • 0 Reply Likes
Thanks, Brett.

It's interesting that those "restrictions" only affect Bridge CS6? NO other software on my PC shows such behaviour... I wonder what Bridge could be doing to hit such a restriction?

Do the plugins involved, eg MMXCore.8BX, hint at where the restriction might be?

For now I'll continue to use Admin mode until Bridge is fixed.

PC Information:

OS Name Microsoft Windows 7 Ultimate
Version 6.1.7601 Service Pack 1 Build 7601
System Type x64-based PC
Processor Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz, 3301 Mhz, 4 Core(s), 4 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 1503, 10/03/2011
SMBIOS Version 2.6
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.98 GB
Available Physical Memory 6.68 GB
Total Virtual Memory 12.4 GB
Available Virtual Memory 10.3 GB
Page File Space 4.39 GB
Page File S:\pagefile.sys
Photo of NORMAN BLACK

NORMAN BLACK

  • 33 Posts
  • 5 Reply Likes
I also find it "interesting" that these "restrictions" only affect Bridge.
Photo of NORMAN BLACK

NORMAN BLACK

  • 33 Posts
  • 5 Reply Likes
I and others had/have this problem with the CS6 Beta and Adobe were not able to resolve it by release. There are threads in the CS6 beta forum.

My CS6 final has not arrived yet.

I don't know the exact reason for the crash but I found that Bridge was creating a temp file in the root folder of my system drive (c:\). If they are raising an exception on the failure to create a necessary temp file it could be the cause of the crash.

I have an SSD(c:) system with a HD(d:) and UAC is enabled. Windows 7 by default protected my c:\ folder from generic user access. I did nothing to change the permissions.
Photo of Mark Harding

Mark Harding

  • 7 Posts
  • 0 Reply Likes
Have read on Adobe forums that a fix is being worked on for this issue.
Photo of NORMAN BLACK

NORMAN BLACK

  • 33 Posts
  • 5 Reply Likes
"we will consider fixing this in a dot release", so we will wait and see what happens.
Photo of Ken

Ken

  • 146 Posts
  • 34 Reply Likes
Same here on Win7 Home Premium x64, running under a standard user account.

Bridge (64-bit) from IL CS6 fails unless I run it "As Administrator".

WER:
Faulting application name: Bridge.exe, version: 5.0.0.399, time stamp: 0x4f5ec28e
Faulting module name: MMXCore.8BX_unloaded, version: 0.0.0.0, time stamp: 0x4f308138
Exception code: 0xc0000005
Fault offset: 0x000007fee7fd4c10
Faulting process id: 0x11cc
Faulting application start time: 0x01cd3262abb8dd56
Faulting application path: C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\Bridge.exe
Faulting module path: MMXCore.8BX
Report Id: ec36a929-9e55-11e1-bf4e-00269e7ed4d1

Ken
Photo of Fotowerkstatt Bauhaus Uni Weimar

Fotowerkstatt Bauhaus Uni Weimar

  • 2 Posts
  • 0 Reply Likes
Hi,
I've read somewhere this behavior happends, if you changed thze standard user Temp / tmp folder, if you use the standard setting Temp=%USERPROFILE%\AppData\Local\Temp
Tmp=%USERPROFILE%\AppData\Local\Temp
then everything works fine
give it a try

fotowerkstatt
Photo of Fotowerkstatt Bauhaus Uni Weimar

Fotowerkstatt Bauhaus Uni Weimar

  • 2 Posts
  • 0 Reply Likes
Hi,
I've read somewhere this behavior happends, if you changed thze standard user Temp / tmp folder, if you use the standard setting Temp=%USERPROFILE%\AppData\Local\Temp
Tmp=%USERPROFILE%\AppData\Local\Temp
then everything works fine
give it a try

fotowerkstatt
Photo of Mikko Jokinen

Mikko Jokinen

  • 13 Posts
  • 0 Reply Likes
Thanks, this workaround works, but does take a toll on my SSD, compared to the ramdisk.

Now it's easy to fix in Bridge.
Photo of aaron cho

aaron cho

  • 1 Post
  • 0 Reply Likes
how to change the setting? do you do it in regedit, or Bridge. If you do it in bridge how do you access it? I can't get bridge to open at all.

Thanks
Photo of Mikko Jokinen

Mikko Jokinen

  • 13 Posts
  • 0 Reply Likes
It's done on Operating system level.
This is how I accessed it in win7: tap the windows key (to the left of alt) - write "system environment variables" without quotes and press enter - click Environment Variables... - find the TEMP and TMP variables from User variables.. and System variables and change.
I don't recall if a reboot/relogin was needed. I'd reboot if it doesn't seem to work.
Photo of Dan Barba

Dan Barba

  • 3 Posts
  • 0 Reply Likes
Hi everyone,
To solve this problem completely, just place a ~ (tilde) (it's just above the Tab key on any keyboard) in front (no space) of the MMXCore.8BX file everywhere it appears inside a PS CS6 folder, both in Bridge and PS.
If it doesn't work, just delete the ~(tilde) symbol from those files and everything will get back to the way it was before. (The ~ (tilde) symbol makes any file become totally invisible to the system, at least in Windows systems.
Good luck!
Photo of Giuseppe Sannicolo

Giuseppe Sannicolo

  • 1 Post
  • 0 Reply Likes
I had this problem on one of my computers running Windows 7. I reinstalled Photoshop a hundred times as a normal user and as administrator. No way.
Finally I did the following and the problem disappeared:
1. Uninstalled Photoshop
2. Run the Adobe CS clean up
3. Restarted my system
4. Reinstalled Photoshop unchecking the three items you have in the installation screen (I cannot remember what they are and do not wont to risk running the installation again)
Bridge works beautifully.
Good luck!

Pino
Photo of Stuart OB

Stuart OB

  • 5 Posts
  • 0 Reply Likes
I am getting the same crashes as described above in Photoshop CS6, with files around 60-100mb - and I'm not sure is it is only bigger files or rather all files. It happens +- every 3rd save. I have now had to start using my cs5 again as I cant afford to loose the amounts of work that I do in-between the autosave interval. Please have a look at his Adobe because I want to rather use your awesome new CS6 again :)

p.s. my Event Viewer error in Win7 Ultimate

Faulting application name: Photoshop.exe, version: 13.0.0.0, time stamp: 0x4f61beba
Faulting module name: MMXCore.8BX, version: 13.0.0.0, time stamp: 0x4f61b779
Exception code: 0xc0000005
Fault offset: 0x00011f7c
Faulting process id: 0x1c14
Faulting application start time: 0x01cd64194bca85b8
Faulting application path: C:\Program Files\Adobe\Adobe Photoshop CS6\Photoshop.exe
Faulting module path: C:\Program Files\Adobe\Adobe Photoshop CS6\Required\Plug-Ins\Extensions\MMXCore.8BX
Report Id: d249bcdf-d014-11e1-be65-1c6f654ede89
Photo of Wolfgang Eilers

Wolfgang Eilers

  • 51 Posts
  • 1 Reply Like
I have installed PS CS6 on a new Win 7 Home Premium 64-bit SP1 machine with a SSD OS drive (C:|). The Bridge crash on faulting module MMXCore.8BX is something I have also encountered. Apparently Bridge creates a temp file named “Photoshop Tempxxxxxx” under the root of C drive and this causes issues unless Bridge is is run as administrator.

It's been several months since an Adobe engineer has identified this as an issue with a fix expected in a future point release. Is a fix on the horizon or will we have to endure the annoying "run as administrator" as a permanent work-around?
Photo of Mathilde mupe

Mathilde mupe

  • 1 Post
  • 0 Reply Likes
Just a late answer.
Bridge CS6 also crashes on this I7 win x64 7 machine when started as user.
Indesign CS6 same story .

When I installed win 7 on this machine I gave my user account full admin priviledges. But still I can only run Bridge / Indesign when started with ' Run as Admin'.
Photo of Paul savage

Paul savage

  • 17 Posts
  • 1 Reply Like
I can confirm that changing the temp directories back to defaults fixed the issue on my computer
Photo of Dave Kuttler

Dave Kuttler

  • 2 Posts
  • 0 Reply Likes
I have been working with Adobe support on this and this is the latest as of today...

I have created a TechNote on this issue: http://helpx.adobe.com/bridge/kb/brid...

I should be updating that TechNote when the fix is released. However, feel free to ping me when Bridge updates, if the TechNote isn't updated.

I wish I had better news, but it looks like at this point it will be fixed.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 764 Reply Likes
Someone might want to run a spelling checker on that technote....
Photo of NORMAN BLACK

NORMAN BLACK

  • 33 Posts
  • 5 Reply Likes
OMG! I don't have to report this any more! Maybe now the lumps on my forehead can heal.
Photo of Mikko Jokinen

Mikko Jokinen

  • 13 Posts
  • 0 Reply Likes
Fixing "this" has been taking too long.
I know something about sw dev processes. Not much but some.
Adobe could do better.
I'm sure they saved big money on QA.
These issues were reported already on beta cs6, about a year ago. Why weren't they addressed?
Lack of communications between qa and dev? Did qa find these or was it only on beta testers' reports. Who handled beta testers' reports? We'll never know.
I do not see a fix coming for cs6, because this is such a basic thing. If they were going to fix it, that would have been done ages ago.
So, no fix, but there are workarounds which are quite ok, at least for nerds like me.