Crash at startup, only windows result screen shows up

I have uninstalled and reinstalled firefox, plus performed a virus/malware scan, nothing shows up.
Here's the report information:
Problem Event Name: APPCRASH
Application Name: firefox.exe
Application Version: 34.0.5.5443
Application Timestamp: 5475e0b9
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.18247
Fault Module Timestamp: 521ea91c
Exception Code: c0000005
Exception Offset: 00052df6
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: e646
Additional Information 2: e646ae9d02dea5a3bae8b2b9c507d30d
Additional Information 3: 02ed
Additional Information 4: 02edd2bbe3adaaff7ecfc1cdfedc76a0

I was able to get it half working... I had to run it in XP compatibility mode. This is after a uninstall/reinstall also. Also I am not computer savvy, so please be patient with me.
Here's the info from Firefox and not windows 7:
Application Basics
Name: Firefox
Version: 34.0.5
User Agent: Mozilla/5.0 (Windows NT 5.1; rv:34.0) Gecko/20100101 Firefox/34.0
Multiprocess Windows: 0/1
Crash Reports for the Last 3 Days
All Crash Reports (including 1 pending crash in the given time range)
Extensions
Name: Adblock Plus
Version: 2.6.6
Enabled: true
ID: {d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}
Name: MEGA
Version: 2.0.212
Enabled: true
ID: [email protected]
Name: Weather Forecast
Version: 0.1.5
Enabled: true
ID: jid1-aqwHRwQpv3JUMs@jetpack
Graphics
Adapter Description: Intel(R) HD Graphics
Adapter Drivers: igdumdx32 igd10umd32
Adapter RAM: Unknown
ClearType Parameters: Gamma: 3600 Pixel Structure: R ClearType Level: 50 Enhanced Contrast: 300
Device ID: 0x0046
Direct2D Enabled: true
DirectWrite Enabled: true (6.2.9200.16571)
Driver Date: 1-12-2011
Driver Version: 8.15.10.2281
GPU #2 Active: false
GPU Accelerated Windows: 1/1 Direct3D 11 (OMTC)
Subsys ID: 00000000
Vendor ID: 0x8086
WebGL Renderer: Google Inc. -- ANGLE (Intel(R) HD Graphics Direct3D9Ex vs_3_0 ps_3_0)
windowLayerManagerRemote: true
AzureCanvasBackend: direct2d
AzureContentBackend: direct2d
AzureFallbackCanvasBackend: cairo
AzureSkiaAccelerated: 0
Important Modified Preferences
browser.cache.disk.capacity: 358400
browser.cache.disk.smart_size.first_run: false
browser.cache.disk.smart_size.use_old_max: false
browser.cache.frecency_experiment: 2
browser.places.smartBookmarksVersion: 7
browser.sessionstore.upgradeBackup.latestBuildID: 20141126041045
browser.startup.homepage_override.buildID: 20141126041045
browser.startup.homepage_override.mstone: 34.0.5
dom.mozApps.used: true
extensions.lastAppVersion: 34.0.5
font.internaluseonly.changed: false
gfx.direct3d.last_used_feature_level_idx: 1
media.gmp-gmpopenh264.lastUpdate: 1419832641
media.gmp-gmpopenh264.version: 1.1
media.gmp-manager.lastCheck: 1420883560
network.cookie.prefsMigrated: true
places.database.lastMaintenance: 1420883561
places.history.expiration.transient_current_max_pages: 85317
plugin.disable_full_page_plugin_for_types: application/pdf
plugin.importedState: true
privacy.sanitize.migrateFx3Prefs: true
storage.vacuum.last.index: 1
storage.vacuum.last.places.sqlite: 1419833107
Important Locked Preferences
JavaScript
Incremental GC: true
Accessibility
Activated: true
Prevent Accessibility: 0
Library Versions
NSPR
Expected minimum version: 4.10.7
Version in use: 4.10.7
NSS
Expected minimum version: 3.17.2 Basic ECC
Version in use: 3.17.2 Basic ECC
NSSSMIME
Expected minimum version: 3.17.2 Basic ECC
Version in use: 3.17.2 Basic ECC
NSSSSL
Expected minimum version: 3.17.2 Basic ECC
Version in use: 3.17.2 Basic ECC
NSSUTIL
Expected minimum version: 3.17.2
Version in use: 3.17.2
Experimental Features
---------------------

Similar Messages

Lync 2013 crashes on startup in Windows 8.1 on Dell latitude E6520 machines

Lync 2013 crashes on startup in Windows 8.1 on Dell latitude E6520 machines. Every E6520 with windows 8.1.
Error message is:
Log Name:      Application
Source:        Application Error
Date:          4/15/2014 3:54:06 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      ***
Description:
Faulting application name: lync.exe, version: 15.0.4420.1017, time stamp: 0x5067326f
Faulting module name: igdumd32.dll_unloaded, version: 9.17.10.3517, time stamp: 0x532b0b5b
Exception code: 0xc0000005
Fault offset: 0x00001040
Faulting process id: 0x10a0
Faulting application start time: 0x01cf58ecd02118cc
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\lync.exe
Faulting module path: igdumd32.dll
Report Id: 14b4ce16-c4e0-11e3-8255-8c705a44a074
Faulting package full name:
Faulting package-relative application ID:
Video driver in the image was originally out of date, changed the driver to the latest and greatest available straight from Intel for the Intel HD 3000 graphics card and this error still appears. Driver 9.17.10.3517 exceeds the minimum requirement
for Lync 2013. The faulting module is related to the graphics driver, but reinstalling does nothing, uninstalling and then reinstalling does nothing, it cannot further be upgraded. This same error affects all the Dell latitude e6520's. It
also only occurs in Windows 8.1. The windows 7 image using the exact same driver version (both the outdated driver and latest driver) works just fine with Lync 2013.
Running Lync with administrative permissions does nothing, disabling hardware acceleration did nothing. None of our laptops come with the bluetooth adapter, and also updated all other drivers such as chipset and soundcard. Error occurs on the
RTM version of Lync, and Lync with SP1 fully updated. The rest of Office 2013 works fine. I am currently at a loss here short of telling the help desk to not image E6520's with Windows 8.1 because Lync 2013 doesn't work on it. But there has
to be a reason for it. Calling out for some suggestions here.
Thanks!

We also have the same issue with Dell E6420 running Windows 8.1. Lync application does not respond after start-up. Did you try looking for the error file under
C:\users\username\appdata\local\Microsoft\Windows\WER\Reportarchive
it should create file like AppHang_lync.exe_some numbers. search for the latest one.
Interesting, I don't have any 6420's handy but figured the issue would exist on those also. I looked up the location you mention and see many crash logs for Lync. Not really sure what the error is, just says it stopped working.
Version=1
EventType=BEX
EventTime=130420688460358806
ReportType=2
Consent=1
UploadTime=130420688461296414
ReportIdentifier=14b4ce17-c4e0-11e3-8255-8c705a44a074
IntegratorReportIdentifier=14b4ce16-c4e0-11e3-8255-8c705a44a074
WOW64=1
Response.BucketId=3a18275b4e359a3d32b33b327b07846b
Response.BucketTable=5
Response.LegacyBucketId=81648064370
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=lync.exe
Sig[1].Name=Application Version
Sig[1].Value=15.0.4420.1017
Sig[2].Name=Application Timestamp
Sig[2].Value=5067326f
Sig[3].Name=Fault Module Name
Sig[3].Value=igdumd32.dll_unloaded
Sig[4].Name=Fault Module Version
Sig[4].Value=9.17.10.3517
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=532b0b5b
Sig[6].Name=Exception Offset
Sig[6].Value=00001040
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=6.3.9600.2.0.0.256.4
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\Program Files (x86)\Microsoft Office\Office15\lync.exe
UI[3]=Microsoft Lync 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:\Program Files (x86)\Microsoft Office\Office15\lync.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\SYSTEM32\ADVAPI32.dll
LoadedModule[6]=C:\windows\SYSTEM32\ole32.dll
LoadedModule[7]=C:\windows\SYSTEM32\OLEAUT32.dll
LoadedModule[8]=C:\windows\SYSTEM32\MSVCR100.dll
LoadedModule[9]=C:\Program Files (x86)\Microsoft Office\Office15\LyncModelProxy.dll
LoadedModule[10]=C:\Program Files (x86)\Microsoft Office\Office15\LyncDesktopViewModel.dll
LoadedModule[11]=C:\Program Files (x86)\Microsoft Office\Office15\PropertyModel.dll
LoadedModule[12]=C:\Program Files (x86)\Microsoft Office\Office15\PropertyModelProxy.dll
LoadedModule[13]=C:\Program Files (x86)\Microsoft Office\Office15\RtmMvrAs.dll
LoadedModule[14]=C:\windows\SYSTEM32\MSVCP100.dll
LoadedModule[15]=C:\windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.9600.16384_none_dadf89385bc5c7d7\gdiplus.dll
LoadedModule[16]=C:\windows\SYSTEM32\IMM32.dll
LoadedModule[17]=C:\windows\SYSTEM32\MSIMG32.dll
LoadedModule[18]=C:\windows\SYSTEM32\DWrite.dll
LoadedModule[19]=C:\windows\SYSTEM32\msvcrt.dll
LoadedModule[20]=C:\windows\SYSTEM32\sechost.dll
LoadedModule[21]=C:\windows\SYSTEM32\RPCRT4.dll
LoadedModule[22]=C:\windows\SYSTEM32\combase.dll
LoadedModule[23]=C:\windows\SYSTEM32\GDI32.dll
LoadedModule[24]=C:\windows\SYSTEM32\USER32.dll
LoadedModule[25]=C:\windows\SYSTEM32\MSVCR110.dll
LoadedModule[26]=C:\Program Files (x86)\Microsoft Office\Office15\RtmPal.dll
LoadedModule[27]=C:\Program Files (x86)\Microsoft Office\Office15\RtmCodecs.dll
LoadedModule[28]=C:\windows\SYSTEM32\dxva2.dll
LoadedModule[29]=C:\windows\SYSTEM32\d3d9.dll
LoadedModule[30]=C:\windows\SYSTEM32\d3d11.dll
LoadedModule[31]=C:\windows\SYSTEM32\MSCTF.dll
LoadedModule[32]=C:\windows\SYSTEM32\SspiCli.dll
LoadedModule[33]=C:\windows\SYSTEM32\WINMM.dll
LoadedModule[34]=C:\windows\SYSTEM32\WS2_32.dll
LoadedModule[35]=C:\windows\SYSTEM32\PSAPI.DLL
LoadedModule[36]=C:\windows\SYSTEM32\POWRPROF.dll
LoadedModule[37]=C:\windows\SYSTEM32\pdh.dll
LoadedModule[38]=C:\windows\SYSTEM32\MSVCP110.dll
LoadedModule[39]=C:\windows\SYSTEM32\IPHLPAPI.DLL
LoadedModule[40]=C:\Program Files (x86)\Microsoft Office\Office15\dbghelp.dll
LoadedModule[41]=C:\windows\SYSTEM32\bcrypt.dll
LoadedModule[42]=C:\windows\SYSTEM32\SETUPAPI.dll
LoadedModule[43]=C:\windows\SYSTEM32\WTSAPI32.dll
LoadedModule[44]=C:\windows\SYSTEM32\PROPSYS.dll
LoadedModule[45]=C:\windows\SYSTEM32\VERSION.dll
LoadedModule[46]=C:\windows\SYSTEM32\dwmapi.dll
LoadedModule[47]=C:\windows\SYSTEM32\dxgi.dll
LoadedModule[48]=C:\windows\SYSTEM32\CRYPTBASE.dll
LoadedModule[49]=C:\windows\SYSTEM32\WINMMBASE.dll
LoadedModule[50]=C:\windows\SYSTEM32\NSI.dll
LoadedModule[51]=C:\windows\SYSTEM32\WINNSI.DLL
LoadedModule[52]=C:\windows\SYSTEM32\CFGMGR32.dll
LoadedModule[53]=C:\windows\SYSTEM32\bcryptPrimitives.dll
LoadedModule[54]=C:\windows\SYSTEM32\DEVOBJ.dll
LoadedModule[55]=C:\windows\SYSTEM32\nvinit.dll
LoadedModule[56]=C:\PROGRA~2\Sophos\SOPHOS~1\SOPHOS~1.DLL
LoadedModule[57]=C:\Program Files (x86)\Common Files\Microsoft Shared\Office15\mso.dll
LoadedModule[58]=C:\windows\SYSTEM32\d2d1.dll
LoadedModule[59]=C:\windows\system32\uxtheme.dll
LoadedModule[60]=C:\windows\SYSTEM32\WINSTA.dll
LoadedModule[61]=C:\windows\SYSTEM32\SHELL32.dll
LoadedModule[62]=C:\windows\SYSTEM32\SHLWAPI.dll
LoadedModule[63]=C:\windows\SYSTEM32\shcore.dll
LoadedModule[64]=C:\windows\SYSTEM32\kernel.appcore.dll
LoadedModule[65]=C:\Program Files (x86)\Microsoft Office\Office15\Uc.dll
LoadedModule[66]=C:\Program Files (x86)\Microsoft Office\Office15\RtmMvrCs.dll
LoadedModule[67]=C:\windows\SYSTEM32\WINSPOOL.DRV
LoadedModule[68]=C:\windows\SYSTEM32\HID.DLL
LoadedModule[69]=C:\windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.16384_none_a9f4965301334e09\Comctl32.dll
LoadedModule[70]=C:\windows\SYSTEM32\msi.dll
LoadedModule[71]=C:\Program Files (x86)\Microsoft Office\Office15\1033\lyncDesktopResources.dll
LoadedModule[72]=C:\windows\SYSTEM32\DavClnt.DLL
LoadedModule[73]=C:\windows\SYSTEM32\DAVHLPR.dll
LoadedModule[74]=C:\windows\SYSTEM32\d3d10_1.dll
LoadedModule[75]=C:\windows\SYSTEM32\d3d10_1core.dll
LoadedModule[76]=C:\windows\SYSTEM32\D3D10Warp.dll
LoadedModule[77]=C:\windows\SYSTEM32\sppc.dll
LoadedModule[78]=C:\windows\SYSTEM32\Secur32.dll
LoadedModule[79]=C:\windows\SYSTEM32\clbcatq.dll
LoadedModule[80]=C:\Program Files (x86)\Microsoft Office\Office15\UccApi.dll
LoadedModule[81]=C:\Program Files (x86)\Microsoft Office\Office15\Win32MsgQueue.dll
LoadedModule[82]=C:\windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.9600.16384_none_7c55c866aa0c3ff0\Comctl32.dll
LoadedModule[83]=C:\Program Files (x86)\Microsoft Office\Office15\1033\ocapires.dll
LoadedModule[84]=C:\Program Files (x86)\Microsoft Office\Office15\Psom.dll
LoadedModule[85]=C:\Windows\SYSTEM32\msxml6.dll
LoadedModule[86]=C:\Program Files (x86)\Microsoft Office\Office15\OcImport.DLL
LoadedModule[87]=C:\Program Files (x86)\Microsoft Office\Office15\ocrec.dll
LoadedModule[88]=C:\windows\system32\mlang.dll
LoadedModule[89]=C:\windows\SYSTEM32\usp10.dll
LoadedModule[90]=C:\windows\system32\windowscodecs.dll
LoadedModule[91]=C:\Program Files (x86)\Microsoft Office\Office15\RtmMediaManager.dll
LoadedModule[92]=C:\windows\SYSTEM32\AVRT.DLL
LoadedModule[93]=C:\Program Files (x86)\Microsoft Office\Office15\AppSharingMediaProvider.dll
LoadedModule[94]=C:\Program Files (x86)\Microsoft Office\Office15\RTMPLTFM.dll
LoadedModule[95]=C:\windows\SYSTEM32\WINTRUST.dll
LoadedModule[96]=C:\windows\SYSTEM32\CRYPT32.dll
LoadedModule[97]=C:\windows\SYSTEM32\MSASN1.dll
LoadedModule[98]=C:\ProgramData\Sophos\Web Intelligence\swi_ifslsp.dll
LoadedModule[99]=C:\windows\system32\mswsock.dll
LoadedModule[100]=C:\windows\SYSTEM32\dhcpcsvc6.DLL
LoadedModule[101]=C:\windows\SYSTEM32\dhcpcsvc.DLL
LoadedModule[102]=C:\windows\SYSTEM32\wlanapi.dll
LoadedModule[103]=C:\windows\System32\MMDevApi.dll
LoadedModule[104]=C:\windows\SYSTEM32\MFPlat.dll
LoadedModule[105]=C:\windows\SYSTEM32\RTWorkQ.DLL
LoadedModule[106]=C:\Program Files (x86)\Intel\Media SDK\mfx_mft_h264ve_32.dll
LoadedModule[107]=C:\windows\SYSTEM32\EVR.dll
LoadedModule[108]=C:\windows\system32\NV\nvumdshim.dll
LoadedModule[109]=C:\windows\system32\nvd3dum.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=BEX
AppName=Microsoft Lync
AppPath=C:\Program Files (x86)\Microsoft Office\Office15\lync.exe
ApplicationIdentity=00000000000000000000000000000000

Inbuilt isight camera is detected in system profiler but no image is being detected only a black screen shows up. I have tried all of the troubleshooting instructions and it still wont work. The iMac im using is OS X 10.6 and was an ex-floor model

inbuilt isight camera is detected in system profiler but no image is being detected only a black screen shows up. I have tried all of the troubleshooting instructions and it still wont work. The iMac im using is OS X 10.6 and was an ex-floor model

Hi,
I would try a Safe Boot first. (This will take longer than a normal Boot and you will need to Restart afterwards).
If it were an older OS I would also suggest going to System Preferences > Displays and making sure the display is set to Millions. (My MacBook Pro does not have this option in Snow Leopard so I did presume Snow Leopard does not have it).
With some laptops there have been some issues with the cable up the back of the screen pulling loose with regular and frequent use of the lid, but this will not apply to you based on your specs. (it does take time to appear and is also somewhat rare). However it seems enough contact with the camera can make it appear in System Profiler and power it on but not give a pic.
If a Safe Boot does not work I would also try a PRAM reset.
Shut down the computer.
Restart it holding down Apple/CMD (or ⌘)+ALT( ⌥)+P+R Keys until you have heard three Start Up Bongs.
This is actually "less" destructive in that it clears less memory items than Safe Boot but they are different enough to warrant trying.
Do you have an older version of iGlasses installed ?
The one for Leopard does not work for Snow Leopard.
Do you have Web Browser open ?
This may point to Google Video Chat Plug-in and Flash Conflict. It would be rare to allow another app to access the camera even if not displayiong a Pic.
(Chrome Installs the Plug-in as does the standalone download).
Knowing what "any application" exactly you are trying might help us pin it down.
Any additional downloaded apps that can use the camera ?
Do you happen to have something balck in front of the camera ?
8:20 PM Sunday; October 9, 2011
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb( 10.6.8)
 Mac OS X (10.6.8),
"Limit the Logs to the Bits above Binary Images."  No, Seriously

InDesign CS6 crashes at startup after windows 7 update

InDesign crashes at startup after windows 7 update: Faulting module path: C:\Windows\system32\MSVCR100.dll (Microsoft Visual C runtime and update KB2538243 and KB2565063)
Reinstalling did not help
Also Adobe Encore CS6 seems to be affected

I looked at the recovery files in:
C:\Users\MyName\AppData\Local\Adobe\InDesign\Version 8.0\en_US\Caches\InDesign
I deleted all the files and Indesign started up fine. feeling good I closed Indesign and restarted.
Indesign Crashed again.
Deleted all files again and reloaded.
I went to "Edit:Preferences:File Handling:Document Recovery Data" to:
G:\Adobe\Indesign\Cache\Recovery
Interestingly, the Indesign application recovery files still reside in the user directory above. But the document recovery data moves to the G drive above.
There is no clear reason why Indesign quit loading today. It worked fine since initial installation last year. But separating the document recovery data from the application recovery data seems to fix the problem for now.

WindowsServer crashes on startup - only blue screen

HI all.
I have a problemwith an intel macbook after installing a few updates (iweb, keyboard update, etc.). There weren't made any updates in the past few months so i updated to 10.5.4 and eveything was ok. Then a few more updates with Software-Update; after that I got only a blue screen on reboot and system.log shows the windowServer crashing permanentely.
Any solutions except of Archive&Install?
Thank for Your help.
Rainer

Not as far as I can tell. According to http://support.apple.com/kb/TS1545 that's the answer.

Lync 2013 RTM client crashing on startup in Windows 8 RTM

Lync 2013 client crashes during startup with the following event:
Faulting application name: lync.exe, version: 15.0.4420.1017, time stamp: 0x5067326f
Faulting module name: KERNELBASE.dll, version: 6.2.9200.16384, time stamp: 0x5010ac2f
Exception code: 0xe06d7363
Fault offset: 0x00014b32
Faulting process id: 0x15bc
Faulting application start time: 0x01cdc372c8b81886
Faulting application path: C:\Program Files (x86)\Office 2013\Office15\lync.exe
Faulting module path: C:\Windows\SYSTEM32\KERNELBASE.dll
Report Id: 06d225ad-2f66-11e2-be7f-000ffedc7546
I'm running Windows 8 64-bit, but Office 32-bit for compatibility reasons. Office 2010 and Lync 2010 worked beautifully. Other Office 2013 applications work fine. Lync 2010 client works fine as well. Only see this problem with Lync 2013.
Any ideas how to troubleshoot or correct?

Hi,
Have you tried to remove Lync 2010 client and test it again?
How about the other machines? Please also log on the problem machine with another account and test it.
Please try to disable any local antivirus software to see if that fixes the issue.
Please remove Silverlight and reinstall it:
http://www.microsoft.com/silverlight/
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

OS 10.4.5 failure to startup-login window/ black screen/ blue screen-frozen

Hi there,
To anybody that can help me, I thank you very much indeed in advance.
G4 Powerbook, 1.5gHz, 2gb Ram (1gb kingston ram added since purchase date), OS 10.4.5, security update 2006-002 (v1.1 (?) recently installed).
My current problem is that i cannot log into OS X. It boots as far as the login window, which is unresponsive, and then it then flicks to a black screen with 2 or 3 lines of white text and then flicks to a totally 'mac-blue' screen with the black arrow pointer still active.
A history of my problem;
1) Yes, unfortunately I tried to get front row to work on my machine (the hack with the front row enabler etc), and subsequently removed all traces of it after it screwed up a few things (menu bar missing, failure to restart). This tidy-up involved doing something with system library, bezel services...etc.
2) I recently installed the first version of security update 2006-002. i am not saying this is the cause, but sometime after I did this, things started going wrong again. another thing i did recently which i hadnt in the past was to have itunes appear at startup and a few days later i emptied my hard drive of all my music and had this linked to a lacie 250gb via firewire 800. The problem at this was that login/startup was incredibly slow and sometimes the finder would keep relaunching itself on its own once the operating system was up and running. Also, when i tried safe boot, the login window would appear and then it would flick to a black screen. it would let me type in a username, but it would not let me input anything for the password.(I did use disk utility to repair permissions when i did manage to logon).
This whole problem seemed to go away for a day or two, but the login was still slower than usual the past few days.
I then turned on my powerbook this morning and login was extremely long and never completed fully- lots of pinwheel spins, menu bar not loading, itunes not appearing.
After a few forced shutdowns I left the computer for maybe 5-10 mins and it seemed to sort itself out after a few finder relaunches etc, and so i tried a few things;
3) I tried installing the newer version of the security update 2006-002 version 1.1 i think? At the same time i took itunes off the startup launches and also switched off auto login for my account (a silly idea it seems).
Since restarting from the security update, the operating system gets to the login window, which is unresponsive, and then it then flicks to a black screen with 2 or 3 lines of white text and then flicks to a totally 'mac-blue' screen with the black arrow pointer still active.(this is with the power adaptor connected only, no other cables etc)
I have tried Resetting PRAM, and using fsck, although I am slightly unsure as to whether or not this is useful to me anyway. I cannot reinstall the operating system until next week as my mum has my copy of tiger at home a few hundred miles away!
Any help at all would be so greatly appreciated, especially on the eve of my two year anniversary with my powerbook!
Kind regards,
Henry Harker

Hi Henry
I've just encountered this problem with one of our computers at work. Hopefully this will help.
It's a Login Window Prefs problem. It's probably corrupted so you need to remove the prefs file.
1. Startup in safe mode (hold down shift). You should get a login window for the master admin account.
2. Delete the file: userName>Library>Preferences>com.apple.loginwindow.plist
3. Restart.
Let me know how you go.
Cheers
MattD
PowerMac G5, dual 2.5 Mac OS X (10.4.5)

Crashes on startup in windows 7

Hi, I downloaded the trial version of Premiere Elements 11 on my computer because I need it for a school project-- I need to convert the .prel to a more usable format like .wmv etc. Everytime that I attempt to start the program the program crashes, however the photo editor works fine. My computer specs are as followed: AMD Phenom II X6 1035T processor clocked at 2.6 Ghz, 8 Gb of ram, Windows 7 Home Premium Service Pack 1. The model is a Dell Studio XPS 7100, if that matters. Could someone please help me get elements running, or point me to some other .prel converter? Thanks.

thisguy11111
Premiere Elements 11 Windows 7 (assumed 64 bit system)
Are you or the program setting for the project preset? Whoever is doing it, verify the project settings via Edit Menu/Project Settings/General. The project preset should match the properties of your source media.
What are the properties of what you are putting on the Timeline? You mentioned files with a .mp4 file extension. What is the video and audio compression, frame rate, duration among other things?
1. You say that you have the latest version of QuickTime installed. Correct?
2. Are you running the program from a User Account with Administrative Priviledges? And/or have you right clicked the program's desktop icon and selected Run As Administrator?
Among the other considerations, this is what I would like you to do first, that is, delete the Adobe Premiere Elements Prefs file. The path to it in Windows 7 64 bit is:
Local Disk C
Users
Owner
AppData
Roaming
Adobe
Premiere Elements
11.0
and in the 11.0 Folder is the Adobe Premiere Elements Prefs file that you delete.
Make sure that you are working with Folder Options Show Hidden Files, Folders, and Drives On.
When you did the download and/or installation of Premiere Elements 11, did you do so with antivirus and firewalls Off?
We will be watching for your results.
Thanks.
ATR
Add On..if the above does not work, we may have to consider a complete and clean deactivate, uninstall, reinstall of Premiere Elements 11 as well as an uninstall/reinstall for QuickTime. Do you have an Premiere Elements 11 installation disc or installation files if it comes to this?

Adobe Premiere CC crashes on startup on windows 7

I have a HP Pavilion DV6t. it is windows 7 and has 8gb of ram, and an nvidia graphics processor.
I have just reset my system after a hdd failure and on that hdd it worked perfectly every time.
On my new hard drive, I still have windows 7, same drivers and same hardware but when I try to launch Premiere Pro CC, it crashes on the splash screen. Also, After Effects cc and Photoshop cc both work perfectly. (Nor does Primiere pro work in trial mode
My error log is:
Log Name:      Application
Source:        Application Error
Date:          10/09/2014 08:08:24
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      James-Price-HP
Description:
Faulting application name: Adobe Premiere Pro.exe, version: 7.2.1.4, time stamp: 0x52aed7f3
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000000000
Faulting process id: 0x1edc
Faulting application start time: 0x01cfccc5f1cfe79b
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC\Adobe Premiere Pro.exe
Faulting module path: unknown
Report Id: 41074635-38b9-11e4-ab86-faae70fdbd75
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-09-10T07:08:24.000000000Z" />
    <EventRecordID>116346</EventRecordID>
    <Channel>Application</Channel>
    <Computer>James-Price-HP</Computer>
    <Security />
</System>
<EventData>
    <Data>Adobe Premiere Pro.exe</Data>
    <Data>7.2.1.4</Data>
    <Data>52aed7f3</Data>
    <Data>unknown</Data>
    <Data>0.0.0.0</Data>
    <Data>00000000</Data>
    <Data>c0000005</Data>
    <Data>0000000000000000</Data>
    <Data>1edc</Data>
    <Data>01cfccc5f1cfe79b</Data>
    <Data>C:\Program Files\Adobe\Adobe Premiere Pro CC\Adobe Premiere Pro.exe</Data>
    <Data>unknown</Data>
    <Data>41074635-38b9-11e4-ab86-faae70fdbd75</Data>
</EventData>
</Event>
Any Suggestions??

I just scanned a few threads citing this exception code. Most often, the problem is either a graphics driver or, more specifically, having both an integrated graphics chip and a graphics card. In the latter case, disabling the integrated chip generally solves the problem. Here's an especially illuminating thread on just how tricky it can be to be sure that the graphics card situation is all settled: Unable to launch Photoshop CC 2014 - igdfcl64.dll

Skype 7.2 , 7.3, 7.4 crashes on startup on windows...

Skype is crashing when starting up / signing in since version 7.2 came out. I have re installed my intire computer now (so als Windows 8.1) and it is still doing the same. I have reverted to version 7.0.0.102 which I was able to find available on the internet.
Skype has removed all possibilities of downloading and installing older WORKING !!! version all together.
I have also spend more then 4 hour with a number of support "chats" resulting in NOTHING!!!
Now ity seems that also this posibility of "support"has been removed.
I am now going to actively advise my friends ansd famaly to NOT use skype any more .
Solved!
Go to Solution.

Please find below with the windows event log entries.
I reverted back to skype version 7.0.0.102 which was and is working fine !!
Please take this serious. There is most defenitly a bug in the program from version 7.2 onwords.
Best regards,
Log Name:      Application
Source:        Application Error
Date:          7-5-2015 15:21:48
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Erasmus
Description:
Faulting application name: Skype.exe, version: 7.4.80.102, time stamp: 0x55311f54
Faulting module name: MFCORE.DLL, version: 12.0.9600.17415, time stamp: 0x545036e9
Exception code: 0xc0000005
Fault offset: 0x001da525
Faulting process id: 0x1340
Faulting application start time: 0x01d088c8c065ee1d
Faulting application path: C:\Program Files (x86)\Skype\Phone\Skype.exe
Faulting module path: C:\Windows\SYSTEM32\MFCORE.DLL
Report Id: 03769d95-f4bc-11e4-826f-0022159d4cf3
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-05-07T13:21:48.000000000Z" />
    <EventRecordID>5688</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Erasmus</Computer>
    <Security />
</System>
<EventData>
    <Data>Skype.exe</Data>
    <Data>7.4.80.102</Data>
    <Data>55311f54</Data>
    <Data>MFCORE.DLL</Data>
    <Data>12.0.9600.17415</Data>
    <Data>545036e9</Data>
    <Data>c0000005</Data>
    <Data>001da525</Data>
    <Data>1340</Data>
    <Data>01d088c8c065ee1d</Data>
    <Data>C:\Program Files (x86)\Skype\Phone\Skype.exe</Data>
    <Data>C:\Windows\SYSTEM32\MFCORE.DLL</Data>
    <Data>03769d95-f4bc-11e4-826f-0022159d4cf3</Data>
    <Data>
    </Data>
    <Data>
    </Data>
</EventData>
</Event>
Log Name:      Application
Source:        Application Error
Date:          7-5-2015 15:07:42
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Erasmus
Description:
Faulting application name: Skype.exe, version: 7.4.80.102, time stamp: 0x55311f54
Faulting module name: MFCORE.DLL, version: 12.0.9600.17415, time stamp: 0x545036e9
Exception code: 0xc0000005
Fault offset: 0x001da525
Faulting process id: 0x1d04
Faulting application start time: 0x01d088c6af105890
Faulting application path: C:\Program Files (x86)\Skype\Phone\Skype.exe
Faulting module path: C:\Windows\SYSTEM32\MFCORE.DLL
Report Id: 0b31317e-f4ba-11e4-826f-0022159d4cf3
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-05-07T13:07:42.000000000Z" />
    <EventRecordID>5678</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Erasmus</Computer>
    <Security />
</System>
<EventData>
    <Data>Skype.exe</Data>
  <Data>7.4.80.102</Data>
    <Data>55311f54</Data>
    <Data>MFCORE.DLL</Data>
    <Data>12.0.9600.17415</Data>
    <Data>545036e9</Data>
    <Data>c0000005</Data>
    <Data>001da525</Data>
    <Data>1d04</Data>
    <Data>01d088c6af105890</Data>
    <Data>C:\Program Files (x86)\Skype\Phone\Skype.exe</Data>
    <Data>C:\Windows\SYSTEM32\MFCORE.DLL</Data>
    <Data>0b31317e-f4ba-11e4-826f-0022159d4cf3</Data>
    <Data>
    </Data>
    <Data>
    </Data>
</EventData>
</Event>
Log Name:      Application
Source:        Application Error
Date:          7-5-2015 14:18:32
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Erasmus
Description:
Faulting application name: Skype.exe, version: 7.4.0.102, time stamp: 0x55310e09
Faulting module name: MFCORE.DLL, version: 12.0.9600.17415, time stamp: 0x545036e9
Exception code: 0xc0000005
Fault offset: 0x001da525
Faulting process id: 0xdec
Faulting application start time: 0x01d088bfeac3e608
Faulting application path: C:\Program Files (x86)\Skype\Phone\Skype.exe
Faulting module path: C:\Windows\SYSTEM32\MFCORE.DLL
Report Id: 2ccfeec8-f4b3-11e4-826f-0022159d4cf3
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-05-07T12:18:32.000000000Z" />
    <EventRecordID>5620</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Erasmus</Computer>
    <Security />
</System>
<EventData>
    <Data>Skype.exe</Data>
    <Data>7.4.0.102</Data>
    <Data>55310e09</Data>
    <Data>MFCORE.DLL</Data>
    <Data>12.0.9600.17415</Data>
    <Data>545036e9</Data>
    <Data>c0000005</Data>
    <Data>001da525</Data>
    <Data>dec</Data>
    <Data>01d088bfeac3e608</Data>
    <Data>C:\Program Files (x86)\Skype\Phone\Skype.exe</Data>
    <Data>C:\Windows\SYSTEM32\MFCORE.DLL</Data>
    <Data>2ccfeec8-f4b3-11e4-826f-0022159d4cf3</Data>
    <Data>
    </Data>
    <Data>
    </Data>
</EventData>
</Event>

Lots of apps crashing at startup - only on ONE account

Hi,
i've got a serious probleme that seems to be caused by some corrupted preferences or settings in my "Library" Folder.
Mail, Pages, and some other non-apple softwares won't start -better said :icon bouncing, app loading, app launched for 1/4 sec and then quit.
This is very critical since I can't access my work files from this account... I need to copy them into another one, where the SAME apps DO WORK perfectly !! I tried to delete the prefs (com.apple.**), i also tried to replace the library folder with my last week's backup, but it didn't solve anything.
The only way to get my apps working was to DELETE the library folder... thus losing all my precious setting
Any way to get me out of this ?
Thx in advance
Flo

If it truly is corrupt preferences then you don't really have much option but to delete the corrupt files and start afresh (or copy back on from your backup). Since these seem to work from another account that would strongly suggest it is corrupt preferences files, though it is suspicious that they are suddenly all corrupt.
I would also recommend at least trying to repair permissions, and maybe just verifying your drive to make sure something else isn't happening.:
Boot from the installer disk, select language if applicable, choose utilities, run Disk Utility and verify (and repair if necessary) the drive. Then repair the permissions on your computer. You can also repair permissions from DU on your main drive while booted, but to properly verify and repair your drive you have to run it from a drive other than the boot drive. A limited repair is also performed as part of a Safe Mode boot.
[Resolve startup issues and perform disk maintenance with Disk Utility and fsck|http://docs.info.apple.com/article.html?artnum=106214]
[Using Disk Utility in Mac OS X 10.4.3 or later|http://docs.info.apple.com/article.html?artnum=302672]
[Disk Utility's Repair Disk Permissions|http://docs.info.apple.com/article.html?artnum=25751]
[Post by japamac about using fsk|http://discussions.apple.com/thread.jspa?threadID=1649143&tstart=0]
From BDaqua (couldn't have said it better):
"Try Disk Utility
1. Insert the Mac OS X Install disc that came with your computer (Edit: Do not use this disc if it is not the same general version as what you have currently on your computer, e.g. use a Tiger disc for a Tiger drive, not a Panther disc), then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu. (In Mac OS X 10.4 or later, you must select your language first.)
Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.
3. Click the First Aid tab.
4. Click the disclosure triangle to the left of the hard drive icon to display the names of your hard disk volumes and partitions.
5. Select your Mac OS X volume.
6. Click Repair. Disk Utility checks and repairs the disk.
Then Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes."
This article dates from 2004 but still applies. [Topic : kmosx: Apps unexpectedly quit|http://discussions.apple.com/thread.jspa?messageID=607542]

X crashes on startup with AMD dual screen setup

Ever since I bought my AMD Kaveri A10-7850K at the end of January last year I've been having trouble getting a dual screen setup to work properly. Initially I put this down to poor beta drivers, and as I had far too much going on to investigate the issue further beyond some fiddling with xorg.conf, I bought an AMD A4-4000 as a temporary solution while waiting for the Catalyst drivers to catch up.
In June last year I decided to give my A10-7850K another go, assuming that the Catalyst driver would have matured enough in the meantime to cater for the Kaveri processors. Unfortunately the situation was still the same, and I I didn't have the time nor want to be swapping processors all constantly to I decided to just give up on a dual monitor setup for the time being.
After many years of using two screens, however, it is very hard to get used to a single monitor again, and as January is a quiet month for me I decided today to have another at getting it to work properly.
My setup is as follows:
an LG LG 23EA63V connected via HDMI as my main monitor at 1920x1080
a Viewsonic VP-171b connected via DVI as my secondary monitor at 1280x1024
AMD A10-7850K APU
Catalyst 14.12-1 drivers installed from Vi0l0's repo
Xorg 1.15 installed from Vi0l0's repo
KDE 4.14.3 using kwin
KDM is launched using kdm.service
KMS disabled via nomodeset
fglrx module loaded on boot via cat /etc/modules-load.d/catalyst.conf
Tear free rendering enabled
After plugging in my secondary monitor configuring it in amdcccle to be to the right of my primary moniotor in multi-display desktop mode, everything works correctly. This even works in my preferred setup where the secondary monitor is rotated into portrait mode, although I currently have not configured rotation so as to not overcomplicate the troubleshooting.
Upon rebooting, however, X hangs with a static white cursor in the top left hand of both screens, which after a while disappears completely. I then have to unplug the secondary (DVI) monitor and hard reset the PC before I can boot into my desktop again. The bizarre thing is though that when I plug in my secondary monitor again and configure it as desired, either through amdcccle or krandr, everything works perfectly again.
This is, of course, an incredibly cumbersome way of working, especially when most of the time I forget to disconnect my DVI monitor prior to turning on my PC, hence me just making do with a single monitor for the past 7 months.
I did a complete fresh install of Catalyst yesterday (uninstall drivers, delete remaining config files, reinstall drivers from repo), to no avail.
Output from xrandr after rebooting with the secondary monitor disconnected:
$ xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
DFP1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 510mm x 290mm
1920x1080 60.00*+ 50.00 59.94 60.00 50.00 59.94
1776x1000 50.00 59.94 50.00 59.94
1680x1050 50.00 59.95
1400x1050 50.00 59.98
1600x900 50.00 60.00
1280x1024 50.00 60.02
1440x900 50.00 59.89
1280x960 50.00 60.02
1280x800 50.00 59.81
1152x864 50.00 59.96
1280x768 50.00 59.81
1280x720 60.00 50.00 59.94
1024x768 50.00 60.00
1152x648 50.00 59.94
800x600 50.00 60.32
720x480 50.00 60.00 59.94
640x480 50.00 60.00 59.94
DFP2 disconnected (normal left inverted right x axis y axis)
CRT1 disconnected (normal left inverted right x axis y axis)
Output from xrandr after reconnecting the secondary monitor:
$ xrandr
Screen 0: minimum 320 x 200, current 3200 x 1080, maximum 16384 x 16384
DFP1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 510mm x 290mm
1920x1080 60.00*+ 50.00 59.94 60.00 50.00 59.94
1776x1000 50.00 59.94 50.00 59.94
1680x1050 50.00 59.95
1400x1050 50.00 59.98
1600x900 50.00 60.00
1280x1024 50.00 60.02
1440x900 50.00 59.89
1280x960 50.00 60.02
1280x800 50.00 59.81
1152x864 50.00 59.96
1280x768 50.00 59.81
1280x720 60.00 50.00 59.94
1024x768 50.00 60.00
1152x648 50.00 59.94
800x600 50.00 60.32
720x480 50.00 60.00 59.94
640x480 50.00 60.00 59.94
DFP2 connected 1280x1024+1920+0 (normal left inverted right x axis y axis) 338mm x 270mm
1280x1024 60.02*+ 75.02
1280x960 75.02 60.02
1152x864 75.00 60.02
1280x768 75.02 60.02
1280x720 75.02 60.02
1024x768 85.00 75.03 70.07 60.00
800x600 85.06 72.19 75.00 60.32 56.25
640x480 85.01 75.00 72.81 66.61 59.94
CRT1 disconnected (normal left inverted right x axis y axis)
my xorg.conf file:
Section "ServerLayout"
Identifier "aticonfig Layout"
Screen 0 "aticonfig-Screen[0]-0" 0 0
EndSection
Section "Module"
EndSection
Section "Monitor"
Identifier "aticonfig-Monitor[0]-0"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Monitor"
Identifier "aticonfig-Monitor[0]-1"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Monitor"
Identifier "0-DFP1"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
Option "PreferredMode" "1920x1080"
Option "TargetRefresh" "60"
Option "Position" "0 0"
Option "Rotate" "normal"
Option "Disable" "false"
EndSection
Section "Monitor"
Identifier "0-DFP2"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
Option "PreferredMode" "1280x1024"
Option "TargetRefresh" "60"
Option "Position" "1920 0"
Option "Rotate" "normal"
Option "Disable" "false"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]-0"
Driver "fglrx"
Option "Monitor-DFP1" "0-DFP1"
Option "Monitor-DFP2" "0-DFP2"
BusID "PCI:0:1:0"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]-1"
Driver "fglrx"
Option "Monitor-DFP1" "0-DFP1"
BusID "PCI:0:1:0"
Screen 1
EndSection
Section "Screen"
Identifier "aticonfig-Screen[0]-0"
Device "aticonfig-Device[0]-0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Virtual 3200 3200
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "aticonfig-Screen[0]-1"
Device "aticonfig-Device[0]-1"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
My Xorg.0.log:
http://pastebin.com/ki5A0T7R
I'm quite desperate to get this working, almost a year after buying my new setup, so any pointers are welcome!
Thanks in advance!

Actually of the above listed commands only xclock is in xorg-apps .
pacman -S xorg-apps xorg-twm xterm
is needed.

FCP 7 / Crashing on Startup / Only occurs under one user account.

I have a MacPro with several user accounts - used by different departments for various FCS projects. Under one account, a new project was started a few days ago, but now, every time they launch, they get the error below. I've seen this type of problem posted before, but with no specific answer. In the case of my MacPro, it only happens under this user's account. I can logon as another user and have no trouble open FCP. I've seen posts asking about this issue in the past, but haven't seen a full response, so any information would be helpful.
Thanks!
Process: Final Cut Pro [84568]
Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Identifier: com.apple.FinalCutPro
Version: 7.0.2 (7.0.2)
Build Info: FCPApp-955601010~8
Code Type: X86 (Native)
Parent Process: launchd [83322]
Date/Time: 2010-08-30 10:27:42.232 -0400
OS Version: Mac OS X 10.6.4 (10F569)
Report Version: 6
Interval Since Last Report: 86 sec
Crashes Since Last Report: 2
Per-App Interval Since Last Report: 16 sec
Per-App Crashes Since Last Report: 2
Anonymous UUID: 16E224CD-D976-40D1-A9FA-D337E879D733
Exception Type: EXCBADACCESS (SIGBUS)
Exception Codes: KERNPROTECTIONFAILURE at 0x0000000000000010
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 libSystem.B.dylib 0xffff07fc __memcpy + 92
1 com.apple.FinalCutPro 0x0021d9e4 VerifyServiceFolders(KGFileSpec*) + 1252
2 com.apple.FinalCutPro 0x0021f77a InsureScratchDefaults(KGFileSpec*, unsigned char) + 1888
3 com.apple.FinalCutPro 0x00221746 KGPreferencesLibAction + 2860
4 com.apple.FinalCutPro 0x00244ac6 CallLibs(KGLibActionCode, unsigned char) + 618
5 com.apple.FinalCutPro 0x00244b59 KGFinishLibraries + 115
6 com.apple.FinalCutPro 0x00244c8d KGInit() + 173
7 com.apple.FinalCutPro 0x004128c5 OpenApplication(AEDesc const*, AEDesc*, long) + 73
8 com.apple.AE 0x95e41f58 aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned long, unsigned char*) + 166
9 com.apple.AE 0x95e41e57 dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 43
10 com.apple.AE 0x95e41d61 aeProcessAppleEvent + 197
11 com.apple.HIToolbox 0x95afb323 AEProcessAppleEvent + 50
12 com.apple.HIToolbox 0x95c7c30a AEProcessEvent + 160
13 com.apple.HIToolbox 0x95b8da26 HIStdAppHandler::HandleEvent(OpaqueEventHandlerCallRef*, TCarbonEvent&) + 206
14 com.apple.HIToolbox 0x95b8eb14 TEventHandler::EventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 64
15 com.apple.HIToolbox 0x95ac6f2f DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1567
16 com.apple.HIToolbox 0x95ac61f6 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 411
17 com.apple.HIToolbox 0x95ac6055 SendEventToEventTargetWithOptions + 58
18 com.apple.HIToolbox 0x95afabb0 ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 3006
19 com.apple.HIToolbox 0x95ac7380 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 2672
20 com.apple.HIToolbox 0x95ac61f6 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 411
21 com.apple.HIToolbox 0x95ae89bb SendEventToEventTarget + 52
22 com.apple.HIToolbox 0x95c71cc3 ToolboxEventDispatcher + 86
23 com.apple.HIToolbox 0x95c71dfb RunApplicationEventLoop + 243
24 com.apple.FinalCutPro 0x0015396f KGMainEvent(void*) + 51
25 com.apple.FinalCutPro 0x002c10e8 main + 54
26 com.apple.FinalCutPro 0x00002d7b _start + 209
27 com.apple.FinalCutPro 0x00002ca9 start + 41

Looks as if it was the last opened project causing the trouble.
Trashing the prefs (com.apple.FinalCutPro.plist, Final Cut Pro User Data and Final Cut Pro User Settings) worked initially, but as soon as I reopened the last project file being used, I got into the same crashing cycle. I deleted all the prefs again, but this time I created a new project file, imported the clips in that had been captured so far and now all is working.
Luckily, the project is still in the clip importing phase, so we haven't lost anything.

Bridge CS6 crashes on startup with Windows Vista

I have just installed Adobe Bridge CS6 on a Windows Vista system. When I try to open it I get a message "Adobe Bridge CS6 has stopped working". The program won't open. Solutions?

Hi there! Because the forum you originally posted in is for beginners trying to learn the basics of Photoshop, I moved your question to the Adobe Bridge forum, where you'll get more specialized help.

Black MacBook crashes upon startup - only solution wiping and reinstall?

My friends MacBook takes an abnormally long time to start up, and when it does, we don't get the top bar, but we do get the dock animations. Also, finder doesn't appear to be running - when we click on it though, it freezes for a minute or two and returns to the unfuctional state (finder not running).
I called support, ran the repair disk utility, and they said we're pretty much screwed as far as the OS goes - they recommended doing target disk mode and pulling off all the data before doing so. So i find a firewire, hook it all up, i can see the files on her hard drive, but whenever i try to access them my finder crashes and i'm left with none of the files. so i made a genius bar appt for her, and here i am wondering what happened and is there anything else i can do?
Let me also mention that about 10 minutes prior to this crash, her friend took her to a website with people doing unmentionable things...i assumed this was the reason, but she never downloaded anything, so that made me wonder is this a mac-based virus? i've never heard of it...any suggestions?

She could have a bad hard drive. There have been certain model drives in MacBooks failing recently.
MacOSG: MacBook Seagate hard drives catastrophically failing >>
-Bmer
Mac Owners Support Group - Join us @ MacOSG.com
  Mac611 Mobile Mac Support - about.Mac611.com
   iTunes:MacOSG Podcast | YouTube.MacOSG.com
                   An Apple User Group 
Have an iPhone or iPod touch? Enter Mac611.com in Safari on it for 'mobile Mac support.'

Crash at startup, only windows result screen shows up

Similar Messages

Maybe you are looking for