Does anyone else have trouble saving big files when using the FM option "save all files"?

[Rob Shell]

I am using Adobe FrameMaker 9.p255 in a Windows 7 32 bit environment
I have a quad processor with 4 gigabytes RAM and two new Seagate drives of
one terrabytes each partitioned in three equal sized partitions
I am using the book feature of FM and adding cross-references which can most
conveniently be done with all files open.
The files are heavily formatted with jpeg illustrations (small 50 to 100kb)
Every 20 minutes or so I save all files.
This is the most likely time and place for the application to crash.

Here I enclose a crash report:

Log Name:      Application
Source:        Application Error
Date:          1/30/2012 5:55:16 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Rob-PC
Description:
Faulting application name: FrameMaker.exe, version: 9.0.0.0, time stamp:
0x4beba27f
Faulting module name: FrameMaker.exe, version: 9.0.0.0, time stamp:
0x4beba27f
Exception code: 0xc0000005
Fault offset: 0x0021503a
Faulting process id: 0x1624
Faulting application start time: 0x01ccdf1198062418
Faulting application path: C:\Program Files\Adobe\Adobe Technical
Communication Suite 2\Adobe FrameMaker 9\FrameMaker.exe
Faulting module path: C:\Program Files\Adobe\Adobe Technical Communication
Suite 2\Adobe FrameMaker 9\FrameMaker.exe
Report Id: ccc7905c-4b5a-11e1-8af1-001fc60d0248
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="2012-01-30T15:55:16.000000000Z" />
    <EventRecordID>60740</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Rob-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>FrameMaker.exe</Data>
    <Data>9.0.0.0</Data>
    <Data>4beba27f</Data>
    <Data>FrameMaker.exe</Data>
    <Data>9.0.0.0</Data>
    <Data>4beba27f</Data>
    <Data>c0000005</Data>
    <Data>0021503a</Data>
    <Data>1624</Data>
    <Data>01ccdf1198062418</Data>
    <Data>C:\Program Files\Adobe\Adobe Technical Communication Suite 2\Adobe
FrameMaker 9\FrameMaker.exe</Data>
    <Data>C:\Program Files\Adobe\Adobe Technical Communication Suite 2\Adobe
FrameMaker 9\FrameMaker.exe</Data>
    <Data>ccc7905c-4b5a-11e1-8af1-001fc60d0248</Data>
  </EventData>
</Event>

I then tried to log the fault using the resource monitor thinking that
perhaps the big files I was using were having problems in the disk queing
process

My realtime logs reveal the message
"The average disk query may be at its maximum transfer capacity"

I then used the MS resource monitor to visualize the problem as it was
happening.
The graphs were maxed out at over 100MB per second! No other apps running
I also received a warning from Norton that FrameMaker was registering HIGH
disk usage

I then tried to invoke the "wait chain" as suggested by microsoft.

I then received a message from Resource monitor that it could not analyse
the wait chain as 
"FrameMaker.exe.  is not responding."
 However, The Resource montor showed clearly that it was still working as
busy as a bee.

My feeling is that there may be a serious flaw in FM's ability to save many
large files. 
I have taken the option of saving one file at a time which seems to be a
tedious workaround.

Rob Shell