On Fri, Jan 24, 2014 at 2:16 PM, <gale@audacityteam.org> wrote:

> > > > > I did this, and the crash still appeared.  It occurs when I cut a
> > song
> > > > from
> > > > > a track in one Audacity window and paste it into a different track in
> > > > > another Audacity window.  (This used to work fine in earlier

> > > The .bak files are definitely generated by Audacity
> > > itself - I have not seen a .bak file for several years (since Linux
> > > experiments) until these crashes started occurring.
> > >
> > 
> > Have you got Windows Explorer open while these mysterious .bak
> > files appear? Audacity should not be writing them.
> >
> Yes.

If you close Windows Explorer before launching Audacity, then don't
reopen it until after Audacity crashes, are the .bak files still created?

OK, I'll work without an Explorer window open, and open Explorer after the next crash - whenever that may occur.
> Only after a crash, an aup.bak file appears (along with a normal _data
> folder), and there is no .aup file.  When I "Recover" the file and save it,
> the .bak file disappears and an .aup file appears.  If I decline to
> "Recover", the .bak file disappears (I think).  On at least one occasion it
> didn't, and I discovered I could only load it by manually removing th e .bak
> second extension.

I suggest you run Process Monitor:

to find out what application writes these aup.bak files.

Ah!  Now you have exceeded my IQ.  I have gazed in astonishment at ProcMon in the past, and given up when my eyes crossed.

If you would like me to do this, I need to know:
- what settings must I set up in ProcMon?
- do I have to have ProcMon running when a .bak file is created (ie. during a crash)?
- do I have to use ProcMon immediately after a crash, or can it be any time after the .bak file is created?
- when I run ProcMon, what do I view, and what am I looking for?

Alternatively,  I've got a couch in the basement, if you feel like a visit to Ontario ....