Welcome to Apple Support Communities.
It's a very old thread, but it's nice to revisit some of these and perhaps offer some new insights.
The original report began this thread with Snow Leopard OS X 10.6.4. Other OS versions have been mentioned, but in this thread at least, 10.6 seemed to be the prime culprit.
I think everyone in this thread (me included) has overlooked two critical factors up to this point:
1) FREE RAM AVAILABLE
and
2) FREE HARD DRIVE SPACE
in addition to what's required for the data to be burned to a new DVD.
I don't burn many DVD's (a few a month), and no DL's that I can recall, mostly a few single layer discs for backups (programs downloads to RW and photos archived to +R) these days,
NEW INSIGHT: I've found that most of my burn failures (as well as other App 'freezes', 'hangs', or 'beachballs' in OS X 10.6 Snow Leopard) are because OS X simply "runs out of" Free RAM, when it gets down to 20Mb or so 'free'.
When the operating system runs out of free RAM, it buffers data to the hard drive as "Swap used", and that's hundreds of times slower than writing to RAM. Burning a disc is MUCH more timing-dependent than other program processes. If your DVD burner runs out of data to write, it eventually 'times-out' and causes an error.
If your data is on your local hard drive, when you burn it to DVD, the same SATA interface in your computer is reading the data from the HD to RAM, AND writing from RAM to the DVD. When it begins to run out of RAM, it starts writing the data (it just read from the hard drive) back to the hard drive to buffer it because RAM is full.
... 'beachballs' occur... burn fails. If you're reading or writing that data from an external HD or DVD drive via USB, you've added another interface that runs significantly slower than SATA.
With hangs in other apps where I'm NOT trying to burn a disc, patience can be a virtue. Quitting ALL other apps to free more RAM often lets them recover from the hang in a matter of a few minutes. Disc-burning is not nearly as forgiving...
Have you looked at how much Free RAM (the green part of the memory 'pie' chart in Activity Monitor) is available, especially when the DL burn fails? I run Activity Monitor (yes, it uses some RAM and Processor, and might contribute to the problem) and I set the Dock icon to 'Show Memory Usage'. It gives me a picture of what is going on. Safari, especially when I'm on social media sites for several hours, seems to eventually swallow ALL available RAM.
Which screen size of mid-2009 MBP and what clock speed?
How much RAM is installed in your system?
How much free space is on your hard drive?
Is the data you're burning on an internal or an external drive?
Are you burning to an internal or external DVD drive?
Are you running any other apps at the same time during the burns?
My OS X 10.6.8 MacBook is a mid-2007 2.16Ghz with 3GB RAM (4GB installed, but the early Core2Duos only make use of 3GB) and a 500GB HGST hard drive with at least 120GB free. Since I've monitored RAM and hard disk free space and used the SLOWEST speed available to burn, I've not had any 0x80020022 errors (April 2010 was my first post). I have had discs fail to VERIFY, and produced a few 'coasters', but most of them were scratched RW's I was attempting to re-use.
Summary: Those who reported some improvement in 0x80020022 errors have mentioned some or all of the following:
1) rebooting right before burning (='maximizes' available RAM)
2) burning a slower speed (=more time for the interfaces to buffer and transfer data successfully)
3) ensuring they had LOTS of free hard disk space by various means (15-20GB is the suggested minimum free hard disk space anyway)
4) "brand name" discs worked better for some people
5) cleaning the DVD drive lens - I recommend compressed air ONLY (CAUTION: Most "brush-type" lens cleaner on a disc CAN and probably WILL damage slot-type CD/DVD drives, or get stuck in the slot!)
Message was edited by: kostby
