PC freezes with CS4 when editing imported image in imported 1.5 project

Question

I am new to CS4.  I have imported a PPro 1.5 project into CS4.  Initially, I tried to launch the CS4 project by double clicking the 1.5 project.  The 1.5 project was converted to CS4, however, when the CS4 project opened, there was not timeline.  I deleted the CS4 project, then opened CS4 as a new project selecting the corresponding 1.5 sequence.  A timeline was created.  I then imported the 1.5 project.  However, this time there was no indication of a project conversion.  I cut the project where I wanted to insert three jpg photos that were dragged from the project area into the timeline.  I used the 'Change to Color' Effect to harmonize the color in the three photos.  Each time I tried the effect my PC froze requiring a restart.
What am I doing wrong or is there an error in the steps I have taken?

Answer 1

John,
I googled the error messg you got in your event log;  Got an answer like this below:
Source/Error #: Disk / error 51
Message: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.
Notes: This error indicates an I/O error during a hard page fault.   Discussed in KBs 304415 and 305547.
I've built a couple computers but I'm no expert.  I kind of thought when I first read about your problems that the crashing might be a memory page swapping problem though I couldn't tell you why ...maybe the specs on your machine being so fast and powerful and the size of your AVI..and the fact it was freezing.
I don't think this has anything at all to do with a hard drive driver, but latency between a memory page swap and getting through to your hard drive to finish the write to the drive.
Further googling about the error message gave me the following info: but it seems you'd have to extract what is applicable to your situation.
It may be that you have two variables happening at the same time in comparison to what you accomplished before with 1.5 ?
1) a new machine
2) a new program (CS4)
I thought the reference below to using the local (boot) disk (instead of Disk 04) might be interesting to try ??
follows is the info from googling the ms publications kb 304415 and 305547:
Your computer stops responding (hangs) or has slow response times. This can indicate that there is a high latency to the pagefile, and this may be accompanied by events in the System Log such as:
Event ID: 51
Event Type: Warning
Event Source: Disk
Description: An error was detected on device \Device\Harddisk0\DR0 during a paging operation.
Event ID: 11
Source: %HBA_DRIVER_NAME%
Description: The driver detected a controller error on Device\ScsiPort0.
Event ID: 9
Source: %HBA_DRIVER_NAME%
Description: The device, \Device\ScsiPort0, did not respond within the timeout period.
If the preceding error messages are in the System Log, it indicates that Windows was trying to access a disk and there was a problem. If the disk that is referenced is on the SAN, it could indicate a latency issue. If an Event ID 51 is shown, this indicates that Memory Manager was attempting to copy data to or from memory and had a problem. Another indicator of pagefile latency issues is if the Windows server has a system failure, and either of the following error messages are displayed on a blue screen:
0x00000050 PAGE_FAULT_IN_NONPAGED_AREA
or
0x0000000A IRQL_NOT_LESS_OR_EQUAL
A possible resolution is to place the pagefile on the host's local hard disk. Windows needs reliable access to the pagefile as data is paged in or out of memory. Having the pagefile local to the host guarantees that access is not influenced by other devices and hosts on the SAN.
Note If the pagefile is not on the same partition as the boot partition (typically c:\Windows or c:\WINNT), the creation of a Memory.dmp file will not occur. A Memory.dmp file is used for troubleshooting a Windows computer that has a STOP error. For information about how to configure your computer for a crashdump, see Windows Help.
There are several ways to resolve the preceding problems. The first method is to try and correlate the time with any events that are occurring on the SAN. For example, it HostA was doing a large copy operation and HostB reports the Error 9s, it may imply that proper LUN management is not in place. Another example is if HostB produces errors whenever HostA is rebooted. This may indicate that FC-AL is being used and HostB is being affected by a Loop Initialization Primitive (LIP) sequences from HostA. These can often be corrected by re-configuring the SAN, and this requires the assistance of the hardware vendor. Any type of latency issues might be resolved by placing pagefile on the Windows server's local hard disk, but again, this disables the creation of a memory dump. A key point to understand is that the hardware vendor of the SAN will have the most information about the proper configuration, and must be the first point of contact for all configuration questions and concerns.