Dragging files to storage media is causing crashes!!

Mac 9.2.2 crashes with error 11, and others) when I try to drag or backup medium size folders to a new LaCie Porche 250 firewire 400 external HD. Same with a Syquest HD. Happens sometimes with cd's too. I t only works if I drag one tiny file at a time, but that gets tedious. If it happens to be a larger file, crashes sometimes occur as well. I have a MAC Quicksilver with 9.2.2 (I removed OSX files for now)
I'm a designer on production deadline and need help please!
Thank you.
Oceans

More info on Type 11 Errors (Warning: Info overload)
Probable Causes: A miscellaneous hardware exception error indicates a hardware conflict has occurred, though this error may also be caused by an extension conflict or corrupt software. Hardware-related causes can be related to cache cards and SCSI devices.
Possible Solutions: When a system error occurs in only one application, try running the application with extensions disabled. If the error does not recur, begin troubleshooting for extension conflicts.
http://docs.info.apple.com/article.html?artnum=30929 Mac OS: Extension Conflict Troubleshooting/Extensions Manager Features
If this error occurs only in one application and while extensions are disabled, try trashing the application's preferences so the application creates a new one. If the error does not recur, a damaged preferences file was the cause.
If you're using is a cache card or accelerator card, remove it and try to re-create the problem.
Note: Do this only if you are familiar with installing and uninstalling Macintosh hardware. If you are not, and you believe the problem is hardware related, consider taking your Macintosh to a qualified service provider for help.
Another possible cause is one or more SCSI devices. Try troubleshooting the SCSI chain to determine if this is the case.
If, after performing these solutions, the error recurs, your hard disk may have problems such as bad sectors or a corrupted directory tree. Use a Macintosh disk utility to check for -- and possibly repair -- problems.
Also see Apple Knowledge Base Article http://docs.info.apple.com/article.html?artnum=16004 This article discusses troubleshooting Type 11 errors.

Similar Messages

Files Corrupted on Timeline and Causing Crash--PE4

Greetings all.
PE4 has always been crash-happy on my machine, the specs of which I list:
CPU: Intel Core 2 Duo @2.66GHz
RAM: 4GB DDR2
OS: Win7 x64 service pack
Graphics card: nVidia GeForce GT 520 (2GB)
Harddrive: 1TB (Seagate, I think...could be Western Digital) with 645GB free space
From the threads I've read, I've seen that nVidia cards can sometimes cause problems with Adobe software, so that could be part of the general crash problem. My driver is the latest (updated today, 7/3/13.)
Anyway, I've begun encountering a problem with a 33-minute-long animated film I've been editing in PE4. The movie has a lot of material on the timeline because all the animated video clips were split up with freeze frames in post-production to sync footage with dialog, and then there are a bunch of short sound effect clips on top of that plus music. Total, I have two video tracks and 8 audio tracks. I published the movie as an MPEG to my computer last night and then this afternoon, I burned a few DVDs of the finished project. When I reached a point about 13 minutes into the film, the speakers on my TV emitted a horrid screaching noise that lasted for about two seconds. In the film, a .wmv clip is playing with an ambient sound effects clip and a series of three short, consecutive sound effects for a character knocking on a wood box. (These audio clips are in separate tracks and are not a part of the .wmv file; I added them separately.) I thought perhaps my TV speakers were the problem, but my computer speakers acted the same way. Next I assumed that some glitch had occurred in media encoding and so I closed PE4, reopened, and burned a new disk with the same result. I checked the .mpg file that I exported last night, and the screach was absent from it.
I next tried to examine that specific spot in my timeline, but when I scrolled to it and zoomed in to a level where I could see <1 second long sound clips, the program crashed without mentioning a specific error. The Windows error reporting box popped up and simply informed me that "Adobe PE4 has encountered a problem and needs to close." Sceneline mode doesn't crash at that point, but timeline does. The only thing I can conclude is that somehow files on the timeline got corrupted between last night and this afternoon, but since I can't even look at that part of the timeline without a crash, I can't even replace the clips at that area. Am I overlooking something silly here? Any help would be appreciated. If I haven't supplied needed information, I'm sorry; and I'll be happy to add it.
Thanks,
Andrew Hild

Andrew Hild
Let us start with the usual drill.
Please check
Adobe Folder. For pile ups of previews in Adobe Premiere Elements Previews Folder and conformed audio (cfa and pek sets) in the Media Cache Folder.
Edit Menu/Preferences/Media. Click the Clean button to get rid of all conformed video (.mcdb) files.
Run the ccleaner (regular and registry cleaners)
http://www.piriform.com/ccleaner
Remember you have only a 32 bit application there with all the resource limitations of 32 bit system. That makes computer optimization, especially around the time of high productivity, important to keeping the subsequent workflows flowing to a successful completion.
You wrote
These audio clips are in separate tracks and are not a part of the .wmv file; I added them separately.)
But do they sit on top of .wmv footage that has its own audio so that the audio of the .wmv is in conflict with that of the audio clips above it?
You may have two problems, audio conflicting and resources compromised.
Please review and let us know if any of the above applies to your situation.
Thanks.
ATR

CC 2014 (18.1.0) | Text Field editing causing crashes (Windows)

Greetings;
I've noticed lately that when saving files from CC 2014 to a CS6 format - and having those files edited on Mac, in either CS6 or CC - when re-opening those files text fields have been causing crashes on the Windows client. When that same file is opened and text fields are edited on the Mac client, a prompt will just appear stating "Cannot Edit text" - yet it still allows it.
This has caused multiple issues for our teams as it has created files we're starting to refer to as "mine fields" - as working with the .ai file is like playing Russian roulette with text fields, you never know which one is going to crash the file.
I would love to work with a team member from Adobe to help find a resolution to the problem, and I'm willing to provide any additional details that might aid in that process.
Thanks!

Hello Pureweb,
Please upload the crashdumps on some file sharing website say Dropbox and share the link with us by sending a mail to "[email protected]". We will analyze the dump and will suggest you the workaround appropriately.
In parallel, please check that you do not have any 3rd Party plugins installed in it. Please try to remove them one-by-one and see which one causes the crashes or do reverse i.e. remove all the 3rd party plugins. Or Uninstall Ai and check at following location:
C:\Program Files\Adobe\Adobe Illustrator CC 2014
Please verify that nothing is left at above location on uninstalling Ai. Then try a fresh install and see if Ai works.
Also, verify that you have the updated Wacom drivers on your system. This might be an issue with the 3rd party program as well. One of the user who was having a similar issue reported on the Ai forum that one of the 3rd party Stahl's ImageWorx DTG RIP - a program for printing to a Direct To Garment printer was causing the issue. So, you may check if the similar thing is not happening in your case.
Regards,
Dhirendra

Finder crashes when I try dragging files in Yosemite

Upgraded to Yosemite (OS X 10.10) and am having trouble with Finder — when I try dragging files into new windows or documents the Finder window disappears and then reappears, sometimes in a previous window, authorities not. I searched and saw people are experiencing a Finder crash loop, but this isn't that. After the initial crash I can drag my files ok, at least until I use a different application, after which Finder will again crash when attempting to drag and drop. Any idea what's happening or what I can do? Thanks
MacBook Pro (Retina, 15-inch, Mid 2014), OS X 10.10
2.5 GHz Intel Core i7, 16 GB 1600 MHz DDR3, NVIDIA GeForce GT 750M 2048 MB

Try booting into the Safe Mode using your normal account. Disconnect all peripherals except those needed for the test. Shut down the computer and then power it back up. Immediately after hearing the startup chime, hold down the shift key and continue to hold it until the gray Apple icon and a progress bar appear. The boot up is significantly slower than normal. This will reset some caches, forces a directory check, and disables all startup and login items, among other things. When you reboot normally, the initial reboot may be slower than normal. If the system operates normally, there may be 3rd party applications which are causing a problem. Try deleting/disabling the third party applications after a restart by using the application un-installer. For each disable/delete, you will need to restart if you don't do them all at once.
Safe Mode
Safe Mode - About

OS Lion: Can't drag attachments into Mail message, Can't drag files into Trash

Dragging an attachment into a Mail causes a crash adn I have to force quit. I can attach files via the menu, but keep forgetting and have to keep force quitting.
Also (probably not connected), I can't move files into the Trash... Just get a Moving "xxxx" to "Trash" dialog and the progress bar never changes...
Have created a new User and the problem persists.
Any ideas?
Mac OS X Lion 10.7.3 (11D50)

damnfool wrote:
Have created a new User and the problem persists.
Boot up holding command-r keys into Lion Recovery Volume. Reinstall Lion and it will "install in place" so none of your own data or settings should be effected.

DVD-RW Storage Media

My cdrom manugacturer recommended JVC DVD-RW 4X for re-writable media. I've tried several on line stores, and they say the product is no longer available, and point me to Taiyo Yuden, which I have never heard of. One dealer remarked that JVC was no longer manufacturing re-writable media.
Having lost valuable files to "unpronounceable" media in the past, I am curious to know if someone can shed some light on this development. Like you, my work demands reliable storage.

If you're really into backing up your photos on a lasting medium, it's best to use gold CDs, which are not rewriteable. Because such a disk's surface is coated with a thin layer of gold, instead of aluminum, and because gold is virtually immune to anything in breathable air that could corrode it, real backup freaks use gold CDs. The downside, of course, is that CDs don't hold nearly as much information as DVDs, so you wind up having to store rooms full of CDs somewhere in a relatively safe locale. And, at about 4 bucks a pop, they ain't all that cheap. Unfortunately, for a technical reason that's virtually impossible for idiots like me to understand, manufacturers can't make gold coated DVDs; so, we're stuck with CDs.
As for brands of DVDs, in my experience, any of the name brands, such as TDK, Memorex, etc. work fine. I've been backing up my photos since 2002 on normal non-rewriteable DVDs and CDs and, so far (knock on wood), I can still access the photos on them. However, I also back up my shots on a 1 TB external hard drive, which, so far (knock on wood) has not exhibited any problems. Hard drives do crash, so it pays to have an alternate backup.
Interesting note: the Library of Congress in its never ending quest to archive everything it collects as permanently as possible, uses lacquer disks and needles to record and preserve all its audio works. They don't trust CDs, DVDs, or, god forbid, magnetic tape.

Export to windows media encoder-PPro crashes

Every time I try to export to Adobe Media encoder: windows media: PPro crashes.
I am working on a 64k computer using the 32k version of PPro CS3.
Every other format in the media encoder works fine.
Does anyone have any solutions or know why this happens?
Thanks,
J.

J.Charette, "Export to windows media encoder-PPro crashes" #, 15 Jan 2009 12:24 pm
This thread is getting a bit old now but I'm now having the exact same problem as J.Charette. I think I may have some light to shed on it as well. I was successfully running CS3 master collection and exporting to WMV files in PPro/AE for the past year under XP64. I was given a new computer (again XP64) and didn't have any problems until I installed Microsoft Windows Media Encoder 64 (I used to use the 32 bit version successfully and this time figured I'd just get the 64 bit one instead).
Now that I've installed WME I can't export as WMV from any AE/PPro CS3. As soon as AME comes up with the format selection screen, if I select WMV from the drop down box it immediately crashes. I've tried uninstalling WME, reinstalling it and even uninstalling WME & CS3 and reinstalling from scratch. Still doesn't work.
In my case at least, there is a definite correlation between installing WME64 and its interaction with Adobe Media Encoder... Anyone have any suggestions? It seems to me there must be some registry setting / config file for AME that is causing it to try to use WME64 for something which causes a crash (since 32 and 64 bit apps can't call each other).
Ideas?
Thanks,
Christopher Grant

Can not drag files off iphone onto windows 7 Laptop (Error: A device attached to the system is not functioning!) Any ideas on how to resolve this, Much appreciated

Connect phone to laptop, AutoPlay Box appears, click open Device to view files, internal storage, DCIM, Drag all Pictures/Videos into folder on desktop. Message pops up within a few seconds, Saying 'A Device Attached To The System Is Not Functioning.'
Can any be of assistance?
Many Thanks.
Callum.

Is the computer in question connected to the Internet, and if so, is the Internet connection working correctly?
It is possible that Adobe Reader tries to check for updates when it is launched, then finds a faulty network connection.
Check the Device Manager for non-functioning network devices.
Also try http://fixitcenter.support.microsoft.com/ to find other potential problems on that system.

IAccessible on Windows 8.1 and uiautomation reference leaks causing crashes in our applications.

We have started crashing on Windows 8.1 and I have traced the problem to uiautomation.dll and combase.dll. The root cause of the problem is reference counting. It appears that on Windows 8.1 uiautomation is using keyboard hooks and other means to constantly
query for interfaces leading to reference leaks on UI objects. We use MFC and have code that has relied on reference couting to to lead to calls to DestroyWindow. However on Windows 8.1, in cases where we expect, and historically have had, the window get destroyed,
we have windows now hanging around due to elevated reference counts. I can set breaks in the MFC oleunk.cpp and monitor the reference count going up in CCmdTarget::ExternalAddRef for say, a command bar (menu) and after constantly clicking the menu, the reference
count just keeps increasing and increasing. I can quite quickly cause the reference count to zoom into the hundreds. We started getting reports of crashes on Windows 8.1 from customers and at first I didn't duplicate the issue. Then my Windows 8.1 box rebooted
on me (that's another issue as it did so on its own even though I said to defer the restart and I lost data thanks to that nasty Win 8 feature) and after updates installed, I could easily duplicate the crash.
The version now installed for uiautomation is "7.2.9600.17415 (winblue_r4.141028-1500)" and "6.3.9600.17415 (winblue_r4.141028-1500)" as seen from the Visual Studio debugger's modules window. I do see some release calls coming from
a function named "AccessibleObjectFromWindowTimeOut" and wonder what the "TimeOut" implies. That is because the easiest way for a user to crash our app on Windows 8.1 is to use GoToMeeting on Windows 8.1 and invite a participant to take
control of the application. I can also crash on Windows 8.1 simply by setting various break points and trace points to print messages as I track what is going on. That is, the crashes appear to be dependent on some sort of race condition and the debugger interferes
with the proper functioning of whatever is occurring inside uiautomation and combase. I have never seen the debugger "interfere" with a process in this way. I can run the same app and perform the same tasks on Windows 7 and these calls that cause
the ref count to constantly increase simply are not made (and combase.dll doesn't get injected into our process on Windows 7). I think Microsoft needs to look into what they are doing on Windows 8 and start releasing interfaces they are leaking when obtaining
the IAccessible interface from windows that implement it.
R.D. Holland

A dump file doesn't show the cause of the crash - an ever increasing reference count. I changed an implementation of OnGetObject (MFC API) and and didn't return the IAccessible interface and the reference count remained the same on Windows 8.1 as it does
on Windows 7. I did that after tracing the ever increasing reference count to calls to get IAccessible coming from those MS DLLs. Eventually I made sure we destroy the window when we think it should be destroyed instead of relying on the MFC reference counting
mechanism. We have testing code that relies on UI automation so just refusing to give out IAccessible isn't an option as I don't know the context of the request.
R.D. Holland

Can't drag files. Help!

Hoping someone can help me. I came the other day to find that none of the files on our iMac G5 could be dragged. Stuff on the desktop couldn't be moved, re-arranged, etc. Even in iTunes, files couldn't be dragged to new playlists.
I'm not sure what happened. My wife said she was playing a game that crashed suddenly, then all of a sudden this.
Any advice? I just can't figure this one out.
Thanks in advance.

Didn't work … I'm ready to kill this machine!
The funny thing is, because I can no longer drag files, I had to control click on those files to move them to the trash.
For the life of me I can't figure out what's going on. I'm thinking I may have the bring the machine to the local Mac dealer or reinstall the OS.
Any other thoughts?

Can't drag files into the queue window on some computers

For some reason, on my new desktop and my laptop. I cannot drag files into the Queue window in Media encoder. I have tried dragging avi's, wav, and mp4. As the files I am dragging hover over the queue window, my mouse turns into the "circle with a line through it" pointer and I cannot add the files that way. I can click the plus sign and then browse to its location to add. I just want to have my drag n drop feature working again... Any ideas why i can on some computers and not others?
I did try running media encoder as administrator. All my computers are running windows 8.1.

do you have source patching turned on for audio?

Photoshop CS4 and graphic cards. Can cause crashing?

Since upgrading to CS4 I seem to have increased crashing.
Here are my system specs.
Mac 2 x 2.66 GHz Dual-Core Intel Xeon
9 GB of Ram
250 GB internal dedicated scratch disc
NVDIA GeForce 7300 GT with 256 VRAM
After having endless techs look at my machine and upgrading everything. I am beginning to suspect the graphics card.
With OpenGL can a underperforming video card cause crashing in photoshop especially with massive file sizes ( multilayered CMYK poster sized files the can exceed 7 GB)?

Did you install the 11.0.1 update?
Is your OS up to date with patches?
Have you tried disabling OpenGL in preferences to avoid using the GPU/Graphics card?

Adobe Media Encoder CS4 Crashing Immediately

Hello,
I am running the CS4 Production Premium suite on a Windows 7 64-bit computer with 12GB RAM. Up til last week, the whole Adobe suite had been running smoothly. (I primarily use Premiere, Media Encoder, Photoshop, and Encore). However, Encore started locking up the computer any time I tried to work on authoring a Blu-ray (it locked up immediately upon opening a Blu-ray project, and only locked up on a new project when I switched from DVD to Blu-ray mode).
I assumed that some of Encore's source code had either been moved, overwritten by something else, or that there was possibly a program incompatibility with something else on my computer. So I took the step to uninstall and reinstall Encore from the install DVDs.
Upon a "successful" reinstallation, I then went into Premiere CS4 to encode a timeline to a P2 file. Premiere seemed to be doing its normal exporting process fine, but Media Encoder would crash after the red splash screen disappeared. To be more explicit, the red splash screen would disappear and be replaced by a window the normal size of the Encoder program, but nothing appeared on screen in the window other than a small white box in the upper left with the rest just being plain gray (see attached photo). At the same time this white window appeared, Win 7 popped up a box saying that Adobe Media Encoder has stopped working and that it would search for a solution to the problem, which it never could do.
I then tried deactivating the suite, uninstalling the full suite and reinstalling, updating so the patches would bring it up to date, and then tried running Adobe Media Encoder again, this time running from the Start menu rather than from Premiere. Yet, it was still the same response: the program crashes immediately.
I would appreciate any suggestions and help that people can provide.
Sincerely,
Kevin T
San Diego, CA

Here is the only relevant info I could find in the Event Viewer:
Faulting application name: Adobe Media Encoder.exe, version: 4.2.0.0, time stamp: 0x4af13937
Faulting module name: WatchFolder.dll, version: 0.0.0.0, time stamp: 0x4af1344e
Exception code: 0xc0000005
Fault offset: 0x00011f03
Faulting process id: 0x834
Faulting application start time: 0x01ca9d3e4234c82b
Faulting application path: C:\Program Files (x86)\Adobe\Adobe Media Encoder CS4\Adobe Media Encoder.exe
Faulting module path: C:\Program Files (x86)\Adobe\Adobe Media Encoder CS4\WatchFolder.dll
Report Id: 89095e2b-0931-11df-a5f1-00248c778de6
Does this seem fixable to anyone?

Adobe Media Encoder CS5 crashes at a certain point while rendering

Adobe Media Encoder CS5 crashes at a certain point while rendering, I have also tried to render directly from Premiere Pro but this only makes PremPro crash instead.
The clip I am trying to render right now is 20 mins long, 1600x900 and is a .avi file. The output settings are H.264/HDTV 720p 29.97fps High Quality.
This all started happening after I re-installed windows.
Machine Specs:
Intel i5 3570k
8GB 1866MHz RAM
Intel HD 4000 graphics (yes I know I should get CUDA)
I made sure that CS5 was updated before posting this.

>1600x900 and is a .avi file
That size description makes me think this is a screen capture, not a camera file... if it is a screen capture, what codec/software did you use?
Read Bill Hunt on a file type as WRAPPER http://forums.adobe.com/thread/440037
What is a CODEC... a Primer http://forums.adobe.com/thread/546811
What CODEC is INSIDE that file? http://forums.adobe.com/thread/440037
Report back with the codec details of your file, use the programs below... a screen shot works well to SHOW people what you are doing
http://forums.adobe.com/thread/592070?tstart=30
For PC http://mediainfo.sourceforge.net/en or http://www.headbands.com/gspot/

Suddenly I can't drag files from explorer into audition anymore.

Hi any help on this would be greatly appreciated.
I was having some trouble with my m-track ASIO interface drivers so I went through some steps to try and fix this, and made some changes to audition and windows 7. I made some changes listed here http://avid.custkb.com/avid/app/selfservice/search.jsp?DocId=349411
anyway, none of it helped my issue, and to make matters worse now I cant just drag files from explorer windows into audition (which would usually load them in the menu on the left and place them into multitrack editor)
I can still load files through the open menu but this is pretty inefficient way of doing it.
Now I tried to reverse the changes I made but I still cant drag and drop into audition.
does anybody know what might cause this and how to fix it?
thanks

Well, just finished my weekly podcast using Garageband and the "new and improved" iTunes. Here are the clunkers I've found:
1. Original problem of not being able to drag from iTunes to GarageBand. JamButty, I'll try out your workaround... for this show I literally had to drag all of the files I needed out of iTunes into a folder... Then why use iTunes at all?! Really stupid.
2. I noticed when I dragged the final show off of iTunes to a folder I use to upload to my S3 account, it now just has the black mp3 icon... not the image I use for the show. Granted, not a functional problem, but just stupid none the less why they would eliminate that.
3. Show notes in the metadata. Usually I'd copy my first paragraph of show notes (what goes on the web page) into Info > Comments in the metadata. And, if was too long, it would just chop off the end of it. This time I got a "bink" sound and nothing copied in. Tried it a couple of different ways with the same results until I figured out to just put half the copy in. Again, stupid, useless, time-consuming change.
I love Apple to death, but I hate what they do sometimes. The make a great product... then eventually screw it up with dumb changes (for example, the latest version of Final Cut)

Dragging files to storage media is causing crashes!!

Similar Messages

Maybe you are looking for